sonic_NO

In game test:

Testing panel line widths, rivets and weathering for scale, hopefully it illustrates the level of detail I'm aiming for. Again, with the original file for comparinson:

Thnx! Currently working on the engine cowling/nozzle, here's a comparison to the default 1024x1024px skin VS 8K. Because of the lack of detail in the 3D model I have to make an illusion of depth/3D that is not necessarily 100% realistic, but I think its better this way:

Thnx for the feedback guys, this started as a remake of an existing skin for the old model with a lot of the main panel outlines in place. However, as work progressed, I have pretty much redone all the panels and rivets as well as weathering and adjustment of the skin file so it aligns as much as possible with canopy openings, landing gear bay door animations etc. Its a tedious and time consuming job and I’ll share more as work progresses. It’s important to note that the goal is not to be photo-realistic, but to create a high degree of similarity to the real plane within the constraints of the 3D model and available graphic files. @Urbi Not sure I understand what you mean by “proper working labels”, you mean text markings on fuselage?

With the Cold War map released I figured it was time to give some much needed attention to this ancient AI model skin. Very much work in progress/test phase, but the goal is to release a high res (8K) template with weathering, panels and rivets etc. Starting with an East German skin, the 3D model has a few shortcomings (one sided tailplane amongst others), but I hope this can be a nice addition to the Cold War map:

Incoming, hopefully soon available in userfiles.Thnx @Eight Ball and @Neo47

Had a similar issue. As posted there is a problem with duplicate TACAN channels on this map. I think I found a fix for it: If you navigate to: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\terrains\Sinai (or wherever you have your main DCS install) and open the beacons.lua file in a text editor you can see alle the beacons. I altered the "96" value on Hatzerim to the correct "100" that caused a conflict because "96" was also used on Wadi al Jandali. The section to look for is: display_name = _('Hatzerim'); beaconId = 'airfield7_0'; type = BEACON_TYPE_VORTAC; callsign = 'BRA'; frequency = 114900000.000000; channel = 96; position = { 131543.724991, 208.862773, 329208.708252 }; direction = 104.503260; positionGeo = { latitude = 31.234946, longitude = 34.679870 }; sceneObjects = {'t:361406851'}; In the section above, change channel=96; to channel=100; Hatzerim TACAN will now be displayed correctly in the hornet (and any other aircraft that use tacan I presume) I don't know if duplicate TACANs on this map affects all TACAN use, but its worth a try. Tested in both multiplayer and singleplayer.