Flappie

BIGNEWY won't be here next week. I relayed your message on the internal report.

Canopy issue reproduced in SP and reported too. Thanks!

Thanks for the heads up. Issue reported.

This thread will be moved to the proper section soon.

Issue reproduced and reported.

I watched the video 4 times in a row but I still can't understand what you mean. Some footage of the real thing:

Hi @Gault05. There are clear signs in your log that DCS is having a hard time with your CPU: 2025-03-29 01:17:25.446 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:29.171 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-03-29 01:17:29.492 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:36.499 WARNING LOG (7736): 11 duplicate message(s) skipped. 2025-03-29 01:17:36.499 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-03-29 01:17:36.736 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:37.499 WARNING LOG (7736): 3 duplicate message(s) skipped. 2025-03-29 01:17:37.499 INFO SCRIPTING (Main): TTI: Debug - Detecting active Mission: [Convoy Mission], [10] units remain, threshold is set to [0] 2025-03-29 01:17:39.579 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-03-29 01:17:39.628 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:45.089 WARNING LOG (7736): 16 duplicate message(s) skipped. 2025-03-29 01:17:45.089 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-03-29 01:17:45.313 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:47.204 WARNING LOG (7736): 8 duplicate message(s) skipped. 2025-03-29 01:17:47.204 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-03-29 01:17:47.505 INFO SCRIPTING (Main): TTI: Debug - Detecting active Mission: [MR8], [11] units remain, threshold is set to [3] 2025-03-29 01:17:47.811 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:49.000 WARNING LOG (7736): 1 duplicate message(s) skipped. 2025-03-29 01:17:49.000 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-03-29 01:17:50.329 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:56.142 WARNING LOG (7736): 6 duplicate message(s) skipped. 2025-03-29 01:17:56.142 INFO SCRIPTING (Main): TTI: Debug - Running Main A2A Constant Detection! Alive status: [true] 2025-03-29 01:17:56.142 INFO SCRIPTING (Main): TTI: Debug - A2A_CONSTANT-#001 is still alive! Respawn skipped... 2025-03-29 01:17:56.649 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:57.630 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-03-29 01:17:57.681 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:17:59.051 WARNING LOG (7736): 1 duplicate message(s) skipped. 2025-03-29 01:17:59.051 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-03-29 01:17:59.312 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-03-29 01:18:02.816 WARNING LOG (7736): 7 duplicate message(s) skipped. ("ANTIFREEZE ENABLED" all over) Furthermore, DCS noticed at the beginning of your log that you're having parked cores. 2025-03-29 00:42:22.125 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores) 2025-03-29 00:42:23.588 INFO EDCORE (Main): Platform Timer Resolution: 2.01ms 2025-03-29 00:42:24.128 INFO EDCORE (Main): Created boot pool: n:12 2025-03-29 00:42:24.130 INFO APP (Main): Command line: "C:\Program Files\Eagle Dynamics\DCS World\bin/DCS.exe" --restarted 2025-03-29 00:42:24.130 INFO APP (Main): DCS/2.9.14.8394 (x86_64; MT; Windows NT 10.0.19045) And I see you're still using Windows 10. You should upgrade to Windows 11 which handles E-cores better.

This was reported before. I'll bump the internal report right away.

Yes, we know, but they are supposed to be stuck together. One should not be able to move without the other. One question remains: can they be moved without power? I think they can, but we might need some proof. I'll report it nonetheless and we'll see what we get. Maybe ED has some interesting docs about this radio.

Thanks. The error is even logged (twice): 2025-03-28 07:34:19.774 ERROR DXGUI_EDGE_RENDER (Main): Texture [missioneditor/data/images/countries/bolivia/awards/bol-08-caballero.png] not found! 2025-03-28 07:34:19.774 ERROR DXGUI_EDGE_RENDER (Main): Texture [MissionEditor/data/images/countries/Bolivia/awards/BOL-08-Caballero.png] not found! Issue reported.

Hi @T4buk. Can you please attach your logbook.lua file? It will help me reproduce the issue. The file is located in "Saved Games/DCS/MissionEditor".

At this point, we know what actions cause it (large bombs released on dirt can cause the bug, no need for a destroyed vehicle). We just don't know why the bug appears (many servers are not affected).

Warning lights go blink.

Thank you. I've added this to the report.

Thank for the heads up. Issue reported.

Issue reported.

Great news. Thanks for your feedback.

Hi @Pju I tried to reproduce your issue step by step, from the ground, with my MS FFB2 stick. FFB special option is set to Instant Trim. Key 1 : Pilot view. Trim right and aft like in hover: Control helper shows trimmed position. Physical FFB stick follows. Key 3 : Chief Engineer view: Control helper shows stick centered but FFB stick does not follow: it's still trimmed right and aft. Key 1 : Pilot view. Control helper shows trimmed position and FFB hasn't moved (right and aft). Key 3 : Chief Engineer view: Control helper shows stick centered but FFB stick does not follow: it's still trimmed right and aft. Key 1 : Pilot view. Reset trim button: Control helper tim position does not move (right and aft). Gently move the stick toward the center: Control helper shows trimmed position. Physical FFB stick follows. And I don't see any difference if I stay in Pilot view the whole time. Have you tried a DCS cleanup then a DCS repair yet?

@Aphrodite51503 Please attach your dcs log (from Saved Games/DCS/Logs).

The previous thread was locked because the issue was global, it was well identified by devs, and the fix they issued proved successful. And also because a user answered the thread with a completely different issue. Feel free to open a new thread. (but you told us your issue was fixed)

@Gunfreak I tried your track in Release and it looks fixed. Can you please confirm this is OK for you?

Feel free to send him a PM.

I tested a lot of messages but could not test them all. I could not hear these: messages[25] = {wMsgALMAZ_Null + 25, false, 1, 2.41 } -- Minimum fuel. ("FORWARD 110" / "BACK 110") messages[13] = {wMsgALMAZ_Null + 13, false, 2, 2.32 } -- Danger engine vibration. ("HI VIBR LEFT ENG" / "HI VIBR RIGHT ENG") messages[46] = {wMsgBettyMissile3Low + 0, false, 1, 2.43 } -- Missile 3 low messages[47] = {wMsgBettyMissile3Low + 1, false, 1, 2.43 } -- Missile 3 high messages[48] = {wMsgBettyMissile3Low + 2, false, 1, 2.43 } -- Missile 6 low messages[49] = {wMsgBettyMissile3Low + 3, false, 1, 2.43 } -- Missile 6 high messages[50] = {wMsgBettyMissile3Low + 4, false, 1, 2.43 } -- Missile 9 low messages[51] = {wMsgBettyMissile3Low + 5, false, 1, 2.43 } -- Missile 9 high messages[52] = {wMsgBettyMissile3Low + 6, false, 1, 2.43 } -- Missile 12 low messages[53] = {wMsgBettyMissile3Low + 7, false, 1, 2.43 } -- Missile 12 high They are now reported. EDIT: "missile low/high" messages were used with simplified avionics, but this was removed from DCS.

Hi @Akiazusa and sorry for the huge delay. I'll report this today.

@SturmVogel ED devs answered. The Mistral missile is coded as an air-to-air missile, and DCS air-to-air missile model does not allow attacks of ground targets. They want to change this in the future, but it's not planned yet.