Flappie

OK. So it's not something in the Saved Games folder, and it's not the screen either (I have a 3440x1440 display as well). Please try a DCS cleanup then a DCS repair (link).

@Grindmetal Do you have MSI Afterburner installed on your PC? @jnr4817 Browse to "Saved Games\DCS\Scripts\Hooks", then rename "gunner_export_hook.lua" to "gunner_export_hook.lua.bak". This is part of the OH-6 mod. Its creator says this file can cause performance issues. See if you keep having issues after the renaming of this file.

Pages 1-97 to 1-99 of the real F-5E manual make it very clear: The DIM/BRT switch should work for "Warning, Caution and Indicator lights". Warning, Caution and Indicator lights include: FIRE, gear unsafe, Master Caution, Arrest Hook, gear position, AOA indexer and caution light panel. Which means it should be possible to dim the AOA indexed lights. EDIT: it already does in DCS.

I agree. Thanks for your feedback. I don't know if the AoA indexer light can be dimmed in the real aircraft, and whether it's currently accurate or not. I'll see if I can find some reference material. While testing all this, I've found what looks like a bug: when the Flight Instrument Lighting knob is set to 0, the Warning Lights state is automatically changed to BRT (but the switch does not move).

Good! We're going somewhere. Try this folder: "Saved Games\DCS\Config\View" And these files: Saved Games\DCS\Config\appSettings.lua Saved Games\DCS\Config\imgui.ini Saved Games\DCS\Config\MultiplayerDialogsPositions.lua Saved Games\DCS\Config\VCPosition.lua

Issue reported. What are you calling an automated server restart? How do you achieve it?

Hi @rob10. This is what I believe is correct when it comes to VHF/UHF bands: And this is what I observe in the ME for the Hornet and A-10C: VHF-FM "lo band": 30 to 87.995 gives FM (correct) VHF-AM: 118 to 135.9 gives AM (almost correct, it should extend to 136.975) VFH-FM "hi band": 136 to 173.9 gives FM (almost correct, it should extend from 137 to 174) UHF (AM) 225 to 3999.975 = AM (correct) The Viper AN-ARC222 radio should only be able to emit to these frequencies: FM : 30-87.975 AM : 116.000-151.975 In the ME, the Viper also can emit between 152 and 155.975 MHz, which is incorrect. -> already reported internally EDIT: I found this from the manual: This means: AM should be made available from 136 to 155.9 MHz. FM should be made available from 225 to 399.975 MHz. I'll report this.

@twistking This is what I get. I understand what you mean. The question now is: do you expect these gear/caution lights to be brighter than they currently are when switch is on "BRT", or do you want them to be dimmer than they currently are when switch is on "DIM"? (again, it would be great if someone could find reference images/footage of the cockpit night lighting) F-5E_warning lights dim-brt.trk

@Bowie Thank you for the track. Have you seen this issue elsewhere than at Lymington AB?

Waypoint 1 was too close to the airbase. I moved waypoint 1 a bit to the south and it made them attack the Hawk SAM. жд-узел_fix.miz

Hi @Zyll. I used your options.lua with my track, and I still cannot reproduce your issue. This might be caused by some custom file in your "Saved Games/DCS" folder. Try this if you want (do NOT delete anything, only do renamings): Browse to "Saved Games" Rename "DCS" (or DCS.openbeta) to "DCS.bak" Start DCS, log in, run the track and see if you can still reproduce the issue. Once the test is over: Exist DCS. Browse to "Saved Games" Rename "DCS" (or DCS.openbeta) to "DCS.test" Rename "DCS.bak" to "DCS" (or DCS.openbeta)

Most SAM missiles in DCS still have an old flight model. It was "good enough" back in the days, but not anymore. I'm not sure what prevents the missile from going faster in the old flight model, but the graph below shows the facts: in DCS, the Hawk MIM-23 missile accelerates until it reaches ~2100 kph, where it hits an artificial "speed wall". The real MIM-23 missile is able to reach Mach 2.4 (~3000 kph). More info here:

An update is planned for legacy missiles affected with the "speed wall" issue, but it seems the Hawk missile needs it first since it's unable to hit a plane 10 000 m high. Issue reported.

@104th_Money@felipesm@AKULA_OPTIMUS@VampireNZ@MoleUK Hey, I've been talking to SpecialK who's been helping a lot of people over here and on Discord. He's pretty sure the MT issue was fixed for good when it comes to W11 users, because he has helped a number of them get rid of stutters. He showed me an example and it was 104th_Money's case. @104th_Money Can you please confirm your P-core issue is gone for good? If you gents keep having performance issues caused by a core stuck to 100%: If you have Windows 10 and an E-core CPU (Intel 12th, 13th or 14th gen), upgrade to Windows 11 (Microsoft will stop supporting W10 by October 14th 2025). If you have Windows 11: Ensure Core Parking is completely turned off ; see link If you still have issues, please attach your DCS log (Saved Games/DCS/Logs/dcs.log) AND your dxdiag log.

You should open a support ticket: Log into DCS website. Click Support. Click Create a new ticket.

I cannot reproduce your issue. Please attach a DCS track. Afgha_Hind.trk

The last time I saw someone with a DCS setting changing on its own, it was caused by an external app:

I've just bumped the report.

A fix was issued in ED internal version. So far, I can't reproduce the issue with this fix (while I keep having the issue from time to time in Release). This fix should be part of the next core update.

I don't experience this issue. Replay this track and tell us if you can here the BOOM. bombing.trk

The thread will be moved, but without a track (without mods of course), I'm not sure devs will be able to identify the issue.

@mousepilot The fix should be part of the next update. Please note that the "All spawn/parking slots are occupied..." popup will be displayed whenever the client tries to jump into a forbidden aircraft.

No, it's a completely different bug. It is related to fog manual settings in missions (the crater texture bug appears when vehicle explodes). I've just tested a fix for this black veil bug, and it works. The fix is not merged yet.

@Hotel Tango Many vehicles will get the "smoke fix" with the next update. I was told some issues couldn't get fixed: AAV-7, Tractor M4, T-72b3 optic (glass parts will still be visible though smoke) MTLB, MLRS, PT-76 (very old models - tracks will still be visible through smoke)

You have a few mods (A-4E, BRONCO, Hercules, UH-60) but I don't think these ever broke JTAC radio dialogs. I've found these error messages: 2025-02-21 01:48:37.191 ALERT WRADIO (Main): Error in wMessage::buildSpeech(), event = wMsgLeaderCheckIn:: [string ".\NATO.lua"]:333: attempt to call global 'isHeavyAircraft' (a nil value) ... 2025-02-21 02:08:47.717 ERROR Lua::Config (Main): Call error findGSByLOC:[string "Scripts/World/Radio/BeaconTypes.lua"]:96: assertion failed! Maybe they have to do with your issue. Try another DCS cleanup and repair just in case.