VFA41_Lion

External nav lights definitely don't bloom that painfully in real life. Nose gear landing light on the other hand, could use a tune up...

ok, yes, I see they're in singleplayer. However I've watched hours of AI fighting it out in Liberation missions and in the sim, the launch animations appear smooth and fluid to me. No weird jerking around or anything.

if you run tacview, suggest turning that off. also hosting it on a dedicated server if you can will greatly increase frames but Syria is absolutely terrible on performance right now, so running a full map is

This looks more like network lag causing a rubberbanding or bouncing missile than actual missile launch animations.

Recommend joining the Discord server for more readily and speedily help that might otherwise get lost in the ED forums: https://discord.gg/YUwuyapT

Bump.... A/G radar unusable when target designated via HUD/HMD. Seems kind of major to me :music_whistling:

Also the Hornet has a permanent red light on at night when viewed far back enough.

The A2G MAP EXP mode screens flicker rapidly and are unusable if you designate a TGT via the HUD or HMD after today's patch. Designating from anything else works fine. hmd designation break radar.trk

I haven't tried it but you could try a temporary fix by changing the smoke lifetime values in the relevant .lua files to something super short and see if that fixes it. And then learn to enjoy DCS without smoking wrecks <_<

The crazy nav lights bloom at close distance however is gone which imo was the major issue ;)

Unfortunately this has not been fixed as of the NOV10 update. The light still bleeds through the wings and tail.

This is a mission designer issue. It is supposed to represent known fixed SAM sites. Hidden on map will set them to invisible in the editor.

Then you will have to practice your situational awareness if you need to absolutely know where your TPOD is looking at all times without a target designated.

Its not working is by design - ED hasn't (yet?) coded the EXP mode to work with "unrealistic" TDC slewing like they did for the Maverick.

did you have a specific issue or did you just wanna vent?

If you are deselecting a target, then no target diamond will appear, as you have un-designated a target. You also won't get a symbol in the HUD to show where the TPOD is looking at.

Use this binding in the sim to remove whatever you have designated as a target. If a target designation exists, your MavF will be slaved to it when you uncage it. If you have a FLIR pod on, the MavF will be slaved to whereever its pointing and locked on to. If you tap undesignate twice (default key S) it will cycle between FLIR pod modes, snowplow (fixed look down angle of 8 degrees) or it will be boresighted to your flight path marker. As for your MPCD reflections, set your canopy reflections to none in the special tab in options: And then adjust brightness with the GAIN rocker:

Press undesignate once to clear your target designation. Press it twice to switch the FLIR between snowplow mode or velocity-vector slaved mode. Uncaging the Mav-F will slave it to whatever is designated as the target (TGT), or boresighted if no designation exists. 65F with the FLIR on will be slaved automatically to it. As for MPCD, use the rockers on the lower left of the display to turn down brightness in daytime.

https://forums.eagle.ru/showthread.php?t=283532 Read this thread. It's been in the sim for 1.5 months now.

every time a patch rolls out, you can count on someone posting a thread here saying "hey i think the flight model changed"

AI F-14B has wings swept back when spawned via runway start, starts takeoff roll, rotates, and then the wings magically un-sweep themselves and the plane tilts over and blows up on the ground. Track attached. f14b ai runway spawn blowup.trk

I can confirm that I got the red IC break shield the first time I ran DCS with the mod, but after I exited and restarted it was working again. Seems like it needs to be run once for DCS to recognize it or whatever.

Eh, i'd say anywhere from five to ten minutes is reasonable considering view distance and time in the area of a crash.

Heyyy seems like you mighta missed this question earlier? Probably because we posted at around the same time. Just gonna bump it here again :thumbup:

Mention of this functionality died after the June 2020 roadmap was released.... just checking in to see if ED forgot about this :music_whistling: