GumidekCZ

AIM-7 Sparrow not guiding when target is at bottom or low half of 12° FLOOD circle. (DCS OB update 2.8.4.39731) null AIM-7_FLOOD_tgt_bottom_circle_BUG.trk Tacview-20230510-234818-DCS.zip.acmi

As title says. After pressing FLOOD mode ... AIM-7 will fly straight, not guiding anymore and will everytime miss. (DCS OB update 2.8.4.39731) AIM-7_manual_FLOOD_BUG.trk Tacview-20230510-233243-DCS-AIM-7_FLOOD_BUG.zip.acmi

Please, never steal other artist work. Somebody made Ukrainian camouflage based on my stolen livery. Was reported and his files deleted from ED userfiles page. I will do that Ukrainian livery myself as soon as I will find some time to do that. My: https://www.digitalcombatsimulator.com/en/files/3318869/

Where is the FLOOD mode pushbutton?, cant se it.

@HILOK AZ/EL is not top-down radar view, but something like radar first person view. Borders should change only by changing scan elevation, azimuth, #bars. NOT distance.

So strange that except two people here in forum, nobody else including admins, nobody cares how major part of fighter defensive CHAFF countermeasure works and is treated in DCS high fidelity simulator. I have to admit that I expected more than just single user reply. That's just sad.

So far No evidence found to be presented or unreliable. ATFLIR Laser ranging is continuous = BUG, which is wrong and IRL will give enemy warning about your presence and that you are targeting them. On top, if terrain will appear between your ATFLIR and target, firing computer will take this shorter range into your selected weapon to calculate balistic trajectory - this will totaly spoil any AUTO(CCRP) bomb delivery from behind the terrain cover. Also according to A1-F18AC-746-100 ATFLIR MANUAL, the LASER should work only if Laser Target Designator/Ranger (LTD/R) Switch is set to ARM - in DCS, the ranging Laser operates even if swith is SAFE (which inhibits the Laser) = yes another BUG It should rather work this way - which is decribed for other detailed Hornet simulation, which I cant mention here: The ranging function of the Laser FLIR is used to determine the ground altitude at target for weapon delivery. The ranging function happens automatically immediately after target designation (or anytime pressing TDC button). The ranging burst lasts for 2 seconds and only occurs when a compatible weapon (Maverick or LGB) is selected and the LTD is in the AUTO mode. LTD/R appears and is flashed in the HUD and LTD DDI formats while the laser is firing.

AAA have wrong WEZ calculation, faster detected target inside of WEZ are miscalculated as not interceptable by AAA shells. In attachment I have add two ACMI file for comparism between targets flying M0.6 and M0.8 speeds. AAA_FLAK_Gun_aiming_tgt_M0.6.zip.acmi AAA_FLAK_Gun_aiming_tgt_M0.8.zip.acmi Track file: KS-19_with_SON-9_Bug_tgt_M0.8.trk I guess that same issue is present also with other AAA (S-60) guns - best if ED team check it. The target flying at 30k feet is on the very endge of WEZ ... I added it only for my check.

If you ask anyone who knows about flares something ... he will just confirm my words, that physical SIZE of the flare have least effect on resulting countermeasure effectiveness among other parameters, like time and intensity of burning, radiated wavelengths, direction and speed of ejection ...

So sad that mil-sim like DCS is getting so low priorities on very important problems like this one. DCS - one of best sims of its kind in the world, with best simulated combat aircrafts, is nowdays still based on just 20 years old simple core (one human generation, cars went to electric propulsion, PC are 10000x more powerful,...), where CHAFF and FLARES are just lottery game, FLAREs only big or small - nothing between, affected only by sun but nothing else from nature environment... That just sad. to have nice polished aircrafts, but behind that shiny mirror we have just guess game - so nicely shown, how ED treats InfraRed world in DCS, just on base of pictures and user reports, not on base of real physics and calculations.

By adding custom_args, we were able to solve partialy this problem since day one. Not needed to delete all old cript lines. But font shown on Hornet will be the default one, not able to set Left or Right font I think.

I have just changed date to 15th (instead of 13) of March and weather to "Scattered 1". The resulted NVG visibility allowed me to wipe out entire speed boat group.... of course with some difficulties and 1-2 times lost tally on them and needed to search by radar again. Also very useful thing is to decrease brightness of HUD to be just barely visible and declutter it. Play with NVG brightness a little before every attack. High zoom cockpit view from longer range (4 and more) make visibility even worse. Zoom out at distance, and zoom in for shooting in close range.

As title says, after destroying APC and outpost, Venom is calling the decision to evacuate via last ship in harbour, but the team is just staying in front of grey warehouse on street, but not moving an inch. I didn't had any message about snipers. DCS OB (not MT) Just found same problem found in past. https://forum.dcs.world/topic/312208-mission-09-trigger-bug

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.