Urbi

Hello folks ! I find the whole discussion inappropriate. The simulation of the damage to the model is realized via the damage model. This is as unrealistic as it can be. With the destruction of the nose wheel steering by ED just to make it easier to find the line to the Kattapult on the carrier, the model only has a fixed reference point to the ground. This is the value Maingear in the model lua for the damage model. It's the left side. Why isn't there this value for both sides? If the calculations of the two points nosegear and maingear for the load during landing (old) were divided (calculation on the model side), everything is now placed on the left maingear. In the pictures the left main landing gear is affected because the right side does not have a fixed point on the ground. The chassis on the right side is only simulated synchronously.

Hello lee1hy! You are using specular textures in your package for the AIM-9P and AIM-9P5, which makes absolutely no sense since ED has Roughmet textures in its zip for these models. these are automatically replaced with Specular. Even an entry as false will not display your texture. The roughmet is loaded from the zip. There is a way to load your textures as standard in exchange for the originals without breaking the IC and having to create false entries in the desciption.lua.

I have to agree with you. You should always use dds. save these in BC7 and with MipMaps. Furthermore, you should make sure that the use of terms (.dds; .png, etc.) is no longer allowed in the description.lua. A key reason is also when using textures that have a different aspect ratio, as they often have a rectangular shape. It should be the width that corresponds to the standard in pixel size (512-1024-2048-4096 and also 8192), so that no black textures emerge. you simply change the width when the height is automatically changed. The errors in my textures were caused by incorrect compression, which I believe had to do with the release of the F-14, as their textures were saved with the Intel tool, which could not be opened with PS. You can easily fix this error by opening these textures with an image editing program and then simply saving them again. NetPaint also supports pixel sizes of 8192x8192. When saving vo bmp; jpg and png no MipMaps are created. This should also be taken into account.

The Tu-95MSM BKC all have the RuAF star. For the Tu-160M2, all BKCs except the newly manufactured and technically overhauled ones have the RuAF star. Red Star : (BKC 02 RF-94102 ВАСИЛИЙ РЕШЕТНИКОВ; BKC 06 RF-94105 ИЛЬЯ МУРОМЕЦ; BKC 07 RF-94106 АЛЕХАНДЕР МОЛОДЦИЙ; BKC 20; BKC 21 RF-66017 ВАЛЕНТИНА ТЕРЕШКОВА and BKC 22 МИНТИМЕР ШАЙМИЕВ)

A note to lee1hy! I downloaded your last liveries in user download. These were packed with the “.rar” program. ED only supports win-zip or the packing method provided by Windows 11, so that your liveries when packed with a ".rar" file will not be displayed in the MV and in the game.

Hello Matt Wags! I can't quite follow your call to create liveries for the countries mentioned under points 1-5. All countries listed there do not have an F-15C Block 50. Not even an F-16C. Excerpt: https://www.f-16.net/f-16_versions_article9.html (Production Production of the block 50/52 totals 813 airframes up to now. Manufacturing started in 1991 and is still ongoing. Block 50 aircraft were delivered to the USAF, Turkey, Greece and Chile, whilst Block 52 aircraft were delivered to the USAF, South Korea, Singapore, Greece, Poland and Israel. Of the total number of Block 50/52, still 260 are waiting delivery to the customer (July 2003).) All of these countries had/have F-16A variants. When I see in the uploaded user lives, 70% are not F-16C Block 50/52. Next comes the no longer existing realism, as these A variants are armed with the C. Special specialists among the users then further falsify the weaponry. The discussion taking place here gives me the rest of my incomprehension.

Read it properly. ED's announcement is dated February 23, 2024. the update to 2.9.3.51704 occurred before this date(22.02.2024). The A-10A_2 and Su-25 have newer textures, with those of the Su-25 being from December last year. The cockpit shapes except those of the Mig-29 also have a more recent date.

It is once again a misinterpretation of the facts. The model of the Ka-52 is by Tim Samedov. The mod is from Currenthill. However, the quality of the cockpit would allow it to be used by cutting it out to create a full-fledged virtual cockpit. Currenthill is an animation specialist. It shouldn't be difficult for him to animate all the switches and levers, as well as the control sticks. The other team could then pass their clickable commands for the virtual cockpit. But it is not an easy task.

Nobody is forced to do their work. Either you do it or you leave it alone. Those who complain here about something where there is nothing to complain about basically only use the templates from ED. Ultimately, liveries created should have a practical and, above all, historical character. Works of art should be offered in art shops. The term Liverie Police is presumptuous and does not reflect the facts. P.S. whether “Livery Policy” or “Livery Police”, the difference is not that far apart. Unfortunately there was a translation error.

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.