GumidekCZ

Make always sure that you did reset TACAN by turning it off and on. Sometimes get stuck with wrong number, that's common in DCS Hornet.

Just played this mission without this fault. Try it once again and you will see.

@baltic_dragon I think that everyone who played this mission have same problems as described here. I know that we can't change ED things. But can we change the weather and size plus position of the moon ? It would help a lot. I can try to find some optimum for you if you want.

4 years later, and ... ???

This is how my cockpit inside of Spit look like, when sun is somewhere in front of me. I can barely read instruments. I HATE IT, no other WWII DCS planes have such crazy reflections like I have in Spit. (There is no connection between Cockpit Global illumination set to ON/OFF) Also, the black instrument panel is faulty textured to be glossy, same as all instruments behind round glasses - yes they are also very glossy. - ALL should be textured in matt colors. On top of this, various Errors can be found when dcs.log checked. Like this one (someone from ED just accidently deleted last letter "t" from its name in Lua): ERROR_ONCE DX11BACKEND (3876): texture 'spitfireix_cpt_glass_diff_roughme' not found. Asked from '' ERROR_ONCE DX11BACKEND (11328): texture 'SpitfireIX_DIF_flir' not found. Asked from '' or this one: ERROR_ONCE DX11BACKEND (4376): texture 'spitfireix_ref_chrom' not found. Asked from '' The RW cockpit picture, I know that its not original, but surely someone did good job in authentic replacement by new things):

I have already made corrections to my all 62 user skins, was not an easy taks from start without any help from ED side. But I did it even for same Campain skins like Raven One:

When pressed, the priority track is automaticly designated as L&S. This is bug, the automatic high threat L&S designation shold be initialized only by activation of TWS from RWS as last update notes write: "Upon entering TWS", the priority 1 target was not automatically set as the L&S. Not even manual mention something about auto L&S when RESET is pressed: TWS_Reset_BUG.trk

Unfortunately purpose of this topic isn't to show our modifications to ED team, but show them how OFF the colors of NTTR map are. Your picture is much better than is in DCS, but still posses green vegetation of grass, bush, trees.

VERY NICE SET OF NTTR PHOTOS: https://www.thedrive.com/the-war-zone/32951/pilots-rare-trip-around-area-51-includes-pics-of-range-targets-drone-bases-ufo-legends Dog Bone Lake from above linked gallery: In DCS - red-brown hell:

Beware, the mission will give you only small amount of flares, be sure to LOAD FULL FLARES! At low pass, be at very high speed, but not on burners, release flare preemptively as CH4Pz said.

I was told to do CASE I departure with 1minute separation. --- No info about rejoin, which altitude, speed and formation like briefed in MSN04 (" We’re taking off behind Blade and Psycho, and let’s join on the 040 at 20, angels 5.") I have in my KB WP1 as 20k feet, so I fly this and #2 went RTB because I didnt joined him. Why? Because he was flying down at 5k 10nm in front of me. Why he didnt made a climb to 20k, because mission editor WP is set to 5k! We are supposed to conserve fuel, no burn it fast at low alt, me trying to catch SMOKE at his 350KTS, me burning fuel at 0.9 Mach. Also Question is, why the 1 minute separation betwen flight members cat launch? BTW I so sad that even today at 2023, the DCS AI still cant do proper CASE I departure (climb and turn only after 7nm from carrier) Also, every CAS, CAP, .. whatever mission the pilot have, he will have good maps in his KB of to AO area. We have only the VERY poor ones - high scale, poor resolution DCS maps! Would be nice to have some better ones in mission KB made by @baltic_dragon. On top of that, the DCS ground textures there at IRAQ are so washed, so you can barelly recognize any road, so instructing CAS flight by JTAC with roads talkon, is here not very lucky idea! I would expect some better way of pointing at target location on these DCS map washed outskirts. CAS mission always requires FULL catridge of Flares. In mission we have only 28 from awaylable 60. Oh, and the last patch messed with Hornet skin Lua, so now the Raven look like this: - someone from Baltic team will have to fix Lua for Hornets skins. FLIPs skin Lua file edited by me and attached to this post. At the end, the mission was good. Ingress and egress is quite boring if you have not at least some music with you. I recommend to players to prepare some mp3 before mission and enjoy it! Adding battle damage checks and Fence-out checks by Baltic into mission would be nice - to spend some time on boring egress. description.lua

When Lua edited and put in original DCS provided texture like for example "FW-190_01_Stab IIJG 6_s.dds" (FW-190D9_Black 4 of Stab IIJG 6), the camouflage colors not fit rest of plane textures. FW-190D9_13.JG 51_Heinz Marquardt: FW-190_01_s_Heinz-Marquardt.dds FW-190D9_IV.JG 26_Hans Dortenmann: FW-190_01_s.dds Please correct the textures or remove them.

Do you like this type of camouflage?

I just wonder who is responsible for not even inform DCS user's about this change in last patch. Did the person behind this change realized, how big problem he made and how many players are affected by it? Now all the user skins on ED have wrong Lua. I expect that only minor number of skins will be corrected there by it's creators. And all this for what? Can the guy behind this change tell us, what we gained by this? I think that the answer would interest most all of DCS players... Almost everyone have Hornet and likewise everyone have some user skins. A small apology would be nice, if nothing else. No offense to anyone, but I would like to see some sorry word here for all the trebles we have with it.

It seems that "f18c1_number_F" is for foregin bort numbers (Kuwait, Australian, Finland, Switzerland). As can be seen on screenshot where all custom_args were set to 0.0 to enable them to show. {"f18c1_number_F", 0 ,"F18C_1_VFA-105_DIFF",false}; {"f18c1_number_F", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c1_number_F", DECAL ,"132_494_Hi_bort_number_LEFT",false}; - I did put different font (the yellow one) here just for this demonstration. Flaps are defined as "f18c2_number_X" Vertical Left and Right stabilizers: "f18c2_kil_right" and "f18c2_kil_left" null

Both ATFLIR & LITENING pod when Auto Level Gain (ALG) button unboxed - gain should be souly manual, but because of bug, both pods are still adjusting gain auctimaticaly. ATFLIR moving sensor partialy into cloud - we can see if any targets there, unable to designate. LITENING same wrong behaviour as ATFLIR: ALG_LITENING_pod_BUG.trk ALG_ATFLIR_pod_BUG.trk

Did you checked the 1 (hide) and 0.0 (show) at the custom_args ? Also numbers where "{"f18c1_number_F", DECAL ,"empty",true}; " is defined will not show.

Dont forget these lines: But honestly, I dont know what are these for? custom_args = { [27] = 1, -- Tail change of type of board number (0.0 -default USA, 0.1- ) [1000] = 0.0, -- Flaps [1001] = 1, -- Nose [1002] = 1, -- Kuwait Squadron [1003] = 1, -- Australian Squadron [1004] = 1, -- Finland Squadron [1005] = 1, -- Switzerland Squadron [1006] = 1, -- Blue Angels Jet Team }

Not a bug, but unfortunately the feature NOT mentioned in Changelog. The Lua code for definig bort numbers changed today. Because of that, I have many many skins broken Now it look like this: {"f18c1_number_nose_right", 0 ,"F18C_1_DIFF",false}; {"f18c1_number_nose_right", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c1_number_nose_right", DECAL ,"empty",true}; {"f18c1_number_nose_left", 0 ,"F18C_1_DIFF",false}; {"f18c1_number_nose_left", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c1_number_nose_left", DECAL ,"empty",true}; {"f18c1_number_F", 0 ,"F18C_1_DIFF",false}; {"f18c1_number_F", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c1_number_F", DECAL ,"empty",true}; {"f18c2_number_X", 0 ,"F18C_2_DIFF",false}; {"f18c2_number_X", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"f18c2_number_X", DECAL ,"empty",true}; {"f18c2_kil_right", 0 ,"F18C_2_DIFF",false}; {"f18c2_kil_right", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"f18c2_kil_right", DECAL ,"empty",true}; {"f18c2_kil_left", 0 ,"F18C_2_DIFF",false}; {"f18c2_kil_left", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"f18c2_kil_left", DECAL ,"empty",true};

I was not suggesting use of all the physics in DCS directly. Non of user PC would handle that. But rather than to use proper physics simulations by dev team to get proper results what we should have see in our FLIRs. Level of simplification should than cover most of the variables present nowadays/ or in future DCS missions.

It is really stupid idea to create FLIR textures on base of some pictures or video records. What we need is to implement some physics laws of nature into DCS. Like different materials properties of heat reflection, emission and absorbtion. Put into math the power of Sun rays during the Year and Day cycle. At the end of equation, add factors of precipitation, clouds, dust or smoke, sunny or shady side of object. Also darker matt material absorb heat much better than glossy bright paints. Small/thin objects heat up quicker than large/thick ones. Tracks of moving heavy tank warms more than light tank and much more than tires of wheeled vehicle. Everything not corresponding to above well known physics is not realistic. In DCS I'm sure this is impossible, but we can get very close to it. If Devs will not focus on pictures, but rather than to physics... than we can get reasonable FLIR simulation here. Getting FLIR image of static tank in the middle of grass field at summer noon, where you can't recognize it even if Gain and Level is adjusted is just nonsense. Speaking of Level and Gain, AT-FLIR auto Level-Gain at Hornet is still bugged since the release. It will adjust even if it's not boxed.

As name of report says if armour plates are not equiped, the MBIENT_OCCLUSION texture is set to wrong texture, which results in not very nice shadows an all liveries in DCS. {"mi_8_tex1", AMBIENT_OCCLUSION , "mi_8_tex_1_ao", false}; mi_8_tex_1_ao.dds

More than year, No fix, not designated as bug or commented. I have same experience with mine reported bug which are not module specific

Any progress there behind the doors? We started flying Tomcat in 2023 with this issue still unresolved. Still unable to refuel at pitch black night because of poor refuel light.

null@BIGNEWY Please, re-open this bug report. There is for 100% bug in blind evelevation areas inside of scanned box.