Spaz-505 Posted October 31, 2022 Posted October 31, 2022 I'm having an issue with a custom Mosquito skin not being displayed correctly in some missions. In the viewer, everything looks fine. Go into a mission, and it may or may not display correctly. Some missions its display correctly, others look like this. Appreciate any help with this issue! Thanks! Dave
Hanu Posted October 31, 2022 Posted October 31, 2022 (edited) Try renaming those skins: that should be ending "skin_name&1" (main skin) and "skin_name&1#1" (additional Mollins parts). Now you have # instead of & there. However there are some difficulties too after this; the Mission Editor switches to &1#1 -skin if you do not set the &1 skin active every time you open advanced properties. Edited October 31, 2022 by Hanu Corrections
Spaz-505 Posted October 31, 2022 Author Posted October 31, 2022 1 hour ago, Hanu said: Try renaming those skins: that should be ending "skin_name&1" (main skin) and "skin_name&1#1" (additional Mollins parts). Now you have # instead of & there. However there are some difficulties too after this; the Mission Editor switches to &1#1 -skin if you do not set the &1 skin active every time you open advanced properties. Thanks Hanu for getting back with me so quickly!.. quite frustrating with this as I've worked on it since the template was released, and never got this issue resolved. I the file names back as you specified above, still didn't resolve the issue. Now only the base colors show up, not the graphics I've added. Again, it looks fine in the Viewer. When I renamed them, now there is only 1 line showing up, not 2 as you see with the skins included with the aircraft. When I first created the custom skin months ago, 2 lines did show up... don't understand why its different now. I also changed the skin name removing the underscore prior to the "&", still not displayed correctly.
Hanu Posted October 31, 2022 Posted October 31, 2022 Yes, that is some sort of parsing issue within the editor as it does not display the whole name. What you could do is to open the mission file what the editor wrote there: If it looks like this it should work: (this is when you select the mosquitofbmkvis2_spaz_ one) and close the properties. Skin = "mosquitofbmkvis2\mosquitofbmkvis2_spaz_&1.dds"; But when you open properties again the skin name has been selected to Skin = "mosquitofbmkvis2\mosquitofbmkvis2_spaz_#1#1.dds"; if you have that name there. It seems to pick the one that has the most # hashtags there. Infuriating, yes. I reported this some time ago.You have to be very careful with Hurricane's and Mosquitos because of this. Summa summarum; if you have this kind of line on mission file regardless what you see in editor, it SHOULD work. I cannot try it myself now as I'm at work Skin = "mosquitofbmkvis2\mosquitofbmkvis2_spaz_&1.dds"; But of course this could be a new version of the same kind of issue also.
Spaz-505 Posted October 31, 2022 Author Posted October 31, 2022 1 hour ago, Hanu said: Yes, that is some sort of parsing issue within the editor as it does not display the whole name. What you could do is to open the mission file what the editor wrote there: If it looks like this it should work: (this is when you select the mosquitofbmkvis2_spaz_ one) and close the properties. Skin = "mosquitofbmkvis2\mosquitofbmkvis2_spaz_&1.dds"; But when you open properties again the skin name has been selected to Skin = "mosquitofbmkvis2\mosquitofbmkvis2_spaz_#1#1.dds"; if you have that name there. It seems to pick the one that has the most # hashtags there. Infuriating, yes. I reported this some time ago.You have to be very careful with Hurricane's and Mosquitos because of this. Summa summarum; if you have this kind of line on mission file regardless what you see in editor, it SHOULD work. I cannot try it myself now as I'm at work Skin = "mosquitofbmkvis2\mosquitofbmkvis2_spaz_&1.dds"; But of course this could be a new version of the same kind of issue also. Still not working, I named the file exactly like you put above... "mosquitofbmkvis2\mosquitofbmkvis2_spaz_&1.dds" When in the mission editor, I don't see 2 entries in the skin listing #1.dds and #1#.dds... it truncates and I only see everything to the left of the "&".
Hanu Posted October 31, 2022 Posted October 31, 2022 Strange, for me it works, even with underscore. I can see it truncates the name after &-sign but it does not matter. I even renamed them to be same as yours.
Spaz-505 Posted November 1, 2022 Author Posted November 1, 2022 Thats really strange! One thing I did realize as we messaged back n forth, the problem I'm seeing in some missions is the ..&1#1 is skin being displayed, I confirmed that by selecting it in the viewer. I'm going go back to the photoshop files and recreate my skin... and see what happens. I've put them on GDrive and made it available for you should you want to try. Sure appreciate your help with this... its quite frustrating. https://drive.google.com/file/d/1XVvr7OfReefHxLy5z2Z6f94NyuT7V5LV/view?usp=share_link
Taurus Posted November 3, 2022 Posted November 3, 2022 I have exactly the same issue as you Spaz-505 when I put my mosquito skins in missions. At the moment the only work around I know of, is to manually go into the .mission file and edit it back to the correct main texture file _#1. I have found that if you go in to the mission editor and edit the skin to the _#1 only ( and NOT do anything else), then save the mission, it usually works. I have not tested to see whether the mission editor save is appending the extra #1 to other skins that use similar secondary textures. Agreed, it is very frustrating.
Spaz-505 Posted November 3, 2022 Author Posted November 3, 2022 (edited) 11 hours ago, Taurus said: I have exactly the same issue as you Spaz-505 when I put my mosquito skins in missions. At the moment the only work around I know of, is to manually go into the .mission file and edit it back to the correct main texture file _#1. I have found that if you go in to the mission editor and edit the skin to the _#1 only ( and NOT do anything else), then save the mission, it usually works. I have not tested to see whether the mission editor save is appending the extra #1 to other skins that use similar secondary textures. Agreed, it is very frustrating. Thanks Taurus!.. now I know its not just my system. Beginning to look like something the team will need to address. I'm going to edit the .mission file and see if that corrects it temporarily. UPDATE: I looked at my .mission file, the mosquito skin was listed correctly. What I see now is the skin is not shown at all. Before it appeared like it was displaying the &1#1. The issue I'm seeing changed with the latest update, neither version the skin displayed correctly 100% of the time. The previous update, some missions it displayed correctly. Edited November 3, 2022 by Spaz-505 Update Testing Results
Taurus Posted November 3, 2022 Posted November 3, 2022 (edited) You skins MUST be named with the _#1.dds and _#1#1.dds to work properly in this instance. (For the Hurricane as well.) In your case; mosquitofbmkvis2_spaz_#1.dds (Main texture.) mosquitofbmkvis2_spaz_#1#1.dds (Secondary texture.) Your entry in the .mission file should be something like; Script = "LuaScripts\WorldObjects\Planes\mosquitofbmkvis2.txt"; Model = "graphics\planes\mosquitofbmkvis2\mosquitofbmkvis2.mgm"; Country = 102; Desc = "Spaz-505 Test"; Skin = "mosquitofbmkvis2\mosquitofbmkvis2_spaz_#1.dds"; As soon as you open the .mission file again in mission editor all bets are off. Edited November 3, 2022 by Taurus speeling.
Spaz-505 Posted November 6, 2022 Author Posted November 6, 2022 On 11/3/2022 at 2:53 PM, Taurus said: You skins MUST be named with the _#1.dds and _#1#1.dds to work properly in this instance. (For the Hurricane as well.) In your case; mosquitofbmkvis2_spaz_#1.dds (Main texture.) mosquitofbmkvis2_spaz_#1#1.dds (Secondary texture.) Your entry in the .mission file should be something like; Script = "LuaScripts\WorldObjects\Planes\mosquitofbmkvis2.txt"; Model = "graphics\planes\mosquitofbmkvis2\mosquitofbmkvis2.mgm"; Country = 102; Desc = "Spaz-505 Test"; Skin = "mosquitofbmkvis2\mosquitofbmkvis2_spaz_#1.dds"; As soon as you open the .mission file again in mission editor all bets are off. I named the two files as you listed above, still doesn't show correctly in the game... the "_#1#1" file is not being overlayed on the model. It does display correctly in the view though.
Taurus Posted November 11, 2022 Posted November 11, 2022 "I named the two files as you listed above, still doesn't show correctly in the game... the "_#1#1" file is not being overlayed on the model." The _#1.dds is the actual main texture of the mosquito. The _#1#1.dds is the secondary features texture for the exhaust covers etc. Are you saying that the modification to include the exhaust covers for example is not working, but the main skin texture is working?
Spaz-505 Posted December 2, 2022 Author Posted December 2, 2022 Hi Taurus, i apologize for not getting back earlier... yes, it is the exhaust covers that is not overlaying properly. Its best for me to show what's happening via a screenshot. Funny thing is, I've had the skin work properly in some missions, most it does not display correctly. The 1st three screenshots are in the viewer. The 1st one is displayed correctly by selecting the .._#1 skin, the 2nd & 3rd screenshot are selecting the _#1# skin (i did this to show how it displays sometimes in the mission). The last screenshot is taken in a mission... no sign of the exhaust cover skin. Other missions, it will display like the 2nd screenshot. Hopefully this helps clarify the issue.
E69_julian57 Posted December 2, 2022 Posted December 2, 2022 (edited) Hello @Spaz-505 I saw this post and its problems The psd files of the Mosquito FBMk VIs2. I name them: aircraft name_&1 aircraft name_&1#1 I have no problems viewing them and in the editor when I select the skin I put the _&1 Edited December 2, 2022 by E69_julian57 1
Spaz-505 Posted December 2, 2022 Author Posted December 2, 2022 (edited) 5 hours ago, E69_julian57 said: Hello @Spaz-505 I saw this post and its problems The psd files of the Mosquito FBMk VIs2. I name them: aircraft name_&1 aircraft name_&1#1 I have no problems viewing them and in the editor when I select the skin I put the _&1 Thanks!.. I believe I've tried that, will do again and check. Update: I just tried it, didn't work. Its not displaying the engine covers at all. Same as the last photo in my original post. Even in the Viewer now, its not displayed correctly. Edited December 2, 2022 by Spaz-505
KOHTYP Posted December 2, 2022 Posted December 2, 2022 Не исторический камуфляж. Thanks to Julian. I did it.it turned out. HERE IS THE LINK FOR THE TWO FILES. 2 1
Taurus Posted December 6, 2022 Posted December 6, 2022 @Spaz-505 It is definitely a problem with the mission editor. It will intermittently save the "skin=" as #1#1 (Exhaust covers) rather than #1 (Aircraft Skin) on saving. I haven't tried the Hurricane in a while but did have the same problem. To be sure your skins will work properly in a mission you MUST go back into the .mission file and manually re-edit the skin back to #1 (Not #1#1) in the "skin=" entry. I am continually frustrated by this so I am programming a soon to be released, user friendly, utility to help do the mission editing. While testing this utility I do occassionly see the mission editor do the change. I have a feeling it has to do with combinations of "looking" at mods in the mission editor that causes the parsing error on save. 1
Spaz-505 Posted December 6, 2022 Author Posted December 6, 2022 16 hours ago, Taurus said: @Spaz-505 It is definitely a problem with the mission editor. It will intermittently save the "skin=" as #1#1 (Exhaust covers) rather than #1 (Aircraft Skin) on saving. I haven't tried the Hurricane in a while but did have the same problem. To be sure your skins will work properly in a mission you MUST go back into the .mission file and manually re-edit the skin back to #1 (Not #1#1) in the "skin=" entry. I am continually frustrated by this so I am programming a soon to be released, user friendly, utility to help do the mission editing. While testing this utility I do occassionly see the mission editor do the change. I have a feeling it has to do with combinations of "looking" at mods in the mission editor that causes the parsing error on save. Thanks Taurus, I'll give that a try... sure sounds like this will temporarily fix the issue. I'll follow-up...
Spaz-505 Posted December 7, 2022 Author Posted December 7, 2022 @Taurus I just did some tests, interesting findings. 1. In the mission editor, I'll assign the #1 skin to the aircraft and save. If I close and pull up the mission again in the mission editor, it show the #1#1 is assigned. 2. Go into the .mission file, its shows the #1 skin is assigned, in the mission what is displayed is the #1#1 skin without the exhaust covers (#1) 3. If I switch the #1#1 and #1 so it references the other file, what shows up in the mission is only the exhaust covers (#1) I tried on 3 different maps to see if may that was a factor, same results. My assessment, its not reading both skin files. 1
Taurus Posted December 12, 2022 Posted December 12, 2022 (edited) Nice Work Spaz-505. Only thing now is for it to be fixed by the Dev's. UPDATE: Fixed in 5.004??????? 25. Mission editor: skins which consist of several textures are correctly displayed in the skin list; Edited December 22, 2022 by Taurus Add update details. 1 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now