Urbi

Hello ED! First of all, thank you for including the Ropucha BDK-775 as an integral part of DCS. With the new introduction, the assignment of the textures was recreated. As I could see, the assignment was only created for the BDK_775_LOD0.EDM. Since the BDK_775_LOD1-4.EDM are also independent model files and are also loaded, when a livery is created, the entries in the BDK_775.lods {"BDK_775_LOD1.EDM",300.000000}; {"BDK_775_LOD2.EDM",800.000000}; {"BDK_775_LOD3.EDM",2000.000000}; {"BDK_775_LOD4.EDM",50000.0}; only the main textures loaded. this means that the ship number of a livery disappears after a zoom.

I don't have a cockpit at takeoff

Hello ED team! It is unfortunately not possible with the Tu-22M3 to replace the textures Tu-22M3__f1, Tu-22M3__f2__f3 with a "false" entry with a new texture, although these entries in the description.lua are possible as "false" entries to be changed . the numbers on the nose wheel do not work the same way with the args 31 and 32 as with those of the tail numbers. I set the numbers to 8 each, i.e. in the ME to 088, the 10 appears on the nose wheel flap. Many thanks for accepting my notice.

Ed is in the process of creating his liveries in packed files. Under Windows 10 you can use the in-house template for this. Proceed as follows: In the folder with the name of the liveries to be selected, mark all files and right-click on the "send to" tab and select "zip-compressed folder" there. Then enter the name of the liveries and then transfer this compressed folder to his liveries. The normal folder of the liveries can then be deleted.

wrong textures of the pilots and the pilot helmets of the F-18C_hornet Blue Angels Jet Team (helmet) NAWDC black (helmet, pilot) NAWDC blue (helmet, pilot) NAWDC brown (helmet, pilot) NSAWC brown splinter (helmet, pilot) NSAWC gray (helmet, pilot) VFA-106 (helmet, pilot) VFA-106 high visibility (helmet, pilot) VMFA-251 high visibility (helmet, pilot) VMFA-312 (helmet, pilot) VMFA-314 (helmet, pilot) VMFAT-101 (helmet, pilot) VMFAT-101 high visibility (helmet, pilot) VMFAT-101 high visibility 2005 (helmet) VX-31 CoNA (helmet, pilot) the pixel size was not taken into account in the pilot textures. The pilot texture is therefore not in the area of 2048x2048. see image. The helmet texture is the wrong one.

Is the entry for the description.lua from the model.lua an error? the entry marked red appears twice. When changing the F16_bl50_GLASS-texture is probably added to the main texture of the F-16C texture folder.

A change of color for the cockpit glass only works if the main texture is replaced by a neutral glass, ie with the color white. The change of the user is not working because of a bug of ED. in the model.lua there is the entry for the glass texture two times.nun, all those who created the liveries should create a false one for the yellowish texture. F16_bl50_Glass.rar

In the exterior view you have the opportunity for the pilot and the Rio-Pilot to make the texture of the helmets different. Look at the pilot in the cockpit to the Rio pilot or vice versa, only the same helmet to see. In the model view of the cockpit in the ModelViewer, the texture file "HB_F14_EXT_RIO_HELMET" does not exist.

It would be so easy, at least for a specialist in textures. Divide the Args for the numbers into the left and right sides. The entries already exist in the description.lua. New they could be as follows: {"MIG19P_T2_R_FUSE1", DECAL, "MIG19_XXX_Decal", false}; {"MIG19P_T2_R_FUSE10", DECAL, "MIG19_XXX_Decal", false}; {"MIG19P_T2_R_FUSE100", DECAL, "MIG19_XXX_Decal", false}; {"MIG19P_T2_L_FUSE1", DECAL, "MIG19_XXX_Decal", false}; {"MIG19P_T2_L_FUSE10", DECAL, "MIG19_XXX_Decal", false}; {"MIG19P_T2_L_FUSE100", DECAL, "MIG19_XXX_Decal", false}; to be able to represent only two numbers, would have to {"MIG19P_T2_R_FUSE1", DECAL, "empty", true}; and {"MIG19P_T2_L_FUSE100", DECAL, "empty", true}; for further ahead on the hull or {"MIG19P_T2_R_FUSE100", DECAL, "empty", true}; and {"MIG19P_T2_L_FUSE1", DECAL, "empty", true}; to stand further back on the hull.