Flappie

I feel inspired tonight.

Precisely, because he cannot turn his sight to where the AI helper points anymore. Because the gyro is borked. As you can see, when the gyro is borked, there's an offset between the AI helper logo and the periscope view. As a consequence, when you say "look over here (cross on the orange disc), Petrovitch will look over there (cross on the blue disc). If you want to make sure of this, switch to the CPG position, look into the periscope and try to find your target. You wont be able to center the periscope on the target. Solution : ask Petrovich to go Observ. off before you make your turns. This way, your gyro will stay aligned.

If you want us to help you with that, we'd need the latest zip file from your "Saved Games/DCS.../Logs" folder.

No, it doesn't. I asked because I wanted to be sure Alt+Tabbing was from your initiative, not from some program. Another user is seeing fast Alt+Tabbing in DCS and he does not know what causes them (and I have no idea either). Pleas ensure your Windows power plan is not set to an eco mode. Choose normal or high/ultimate power plan and see if things improve.

This guide will help you: https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/ In your case, I recommend these values: Init size: 32768 (32GB) Max size: 32768 (32GB) Windows uses a pagefile in order to relieve the system fast memory (RAM). The more RAM a PC has, the less page fle it needs. Your PC has 16GB of RAM, and DCS can very greedy when it comes to memory. A bigger pagefile might help, as long as the drive hosting the pagefile is fast.

Ok. Ensure your Windows power plan is not set to an economic mode.

Thanks for the heads up. The issue is clearly visible in the Yak-52 and the I-16 (2-blade), as well as in the Bf-109 and the Fw190 (3-blade). I could not spot the issue in the Spitfire, the P-51 and the P-47 (4-blade). Strangely, I could not spot the issue with the Mi-24 either (5-blade), nor with the Huey (2-blade). Maybe helicopter blades are simulated differently. Issue reported.

Let's use videos taken from the deck, because as @Micr0 underlined, photographers "cheat" with longer exposure. Videos don't cheat as much. Here's some footage from CVN-69 and CVN-70 (Nimitz class): CVN-78 here (Ford class): Back to the Nimitz class with CVN-72: According to these videos, this photo does not cheat: Here's a last one from CVN-76 (Nimitz class), with what looks like a longer exposition, but it's very useful to locate the spotlights: null A few observations: In most videos, the lower part of the island appears to be lit in yellow. This light comes from spotlights pointing downward. These spotlights are never lit in DCS. In all videos, the middle part of the island stays dark (they don't seem to use the top yellow lights very often). In DCS, the blue/teal lights are always turned off, while the top yellow lights are always turned on. In the last video, many lights are off. I assume it's a wartime configuration. In DCS, there's no such thing.

The next time it happens, please record the track when you exit the mission, then attach it here.

Glad you solved your problem!

I've just found this in your log: 2024-04-22 08:59:25.731 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 09:00:21.679 INFO LUA (Main): Lua: States: 683, CPU load: 0.4%, Mem: 525.6 MB 2024-04-22 09:00:23.304 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 09:08:55.525 INFO APP (Main): Device unplugged: [PCI] Intel(R) Ethernet Connection (7) I219-V 2024-04-22 09:08:56.255 WARNING LOG (19264): 1 duplicate message(s) skipped. 2024-04-22 09:08:56.255 INFO APP (Main): Device plugged: [PCI] Intel(R) Ethernet Connection (7) I219-V 2024-04-22 09:08:56.317 INFO INPUT (Main): created [TrackIR] 2024-04-22 09:08:56.819 INFO APP (Main): Device plugged: [PCI] Intel(R) Ethernet Connection (7) I219-V 2024-04-22 09:10:16.641 INFO APP (Main): Device unplugged: [PCI] Intel(R) Ethernet Connection (7) I219-V 2024-04-22 09:10:22.279 WARNING LOG (19264): 1 duplicate message(s) skipped. 2024-04-22 09:10:22.279 INFO APP (Main): Device plugged: [PCI] Intel(R) Ethernet Connection (7) I219-V 2024-04-22 09:10:22.345 INFO INPUT (Main): created [TrackIR] 2024-04-22 09:10:22.808 INFO APP (Main): Device plugged: [PCI] Intel(R) Ethernet Connection (7) I219-V 2024-04-22 09:11:25.045 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 09:11:38.752 INFO LUA (Main): Lua: States: 683, CPU load: 0.4%, Mem: 475.6 MB 2024-04-22 09:13:34.523 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 09:13:44.123 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] Were you unplugging/plugging your Ethernet cable or is it something with your PC? I also see a lot of Alt+Tabbing here: 2024-04-22 07:51:26.218 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-04-22 07:52:32.068 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 07:52:38.720 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 07:53:32.898 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 07:53:34.557 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 07:55:04.017 INFO LUA (Main): Lua: States: 683, CPU load: 0.4%, Mem: 477.7 MB 2024-04-22 07:56:56.394 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 07:57:25.399 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 07:58:14.017 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 07:58:31.345 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 07:58:31.662 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-04-22 08:07:52.125 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:07:58.509 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:10:44.962 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:11:18.241 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:13:32.003 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:13:43.818 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:13:43.833 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-04-22 08:13:55.042 INFO LUA (Main): Lua: States: 683, CPU load: 0.4%, Mem: 493.7 MB 2024-04-22 08:13:59.255 INFO INPUT (Main): created [TrackIR] 2024-04-22 08:17:52.666 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:17:54.932 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:19:22.339 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:19:24.156 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:24:42.276 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:26:16.902 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:27:28.294 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:27:29.345 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:29:54.220 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:30:00.916 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:30:01.157 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-04-22 08:31:32.961 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:31:55.512 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] 2024-04-22 08:32:37.907 INFO APP (Main): wcTanker::onEvent:0 2024-04-22 08:32:37.917 INFO EDCORE (Main): (wcTanker)enterToState_:2 2024-04-22 08:33:57.722 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2024-04-22 08:33:58.840 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3440, 1440] Was it you?

Your GPU is getting old for DCS. 2024-04-22 14:03:41.053 INFO DX11BACKEND (13808): ATI Adapter Radeon RX 570 Series And you should try and set a bigger pagefile if you have a fast drive with enough free space: 2024-04-22 14:03:29.678 INFO APP (Main): CPU cores: 6, threads: 12, System RAM: 16332 MB, Pagefile: 12800 MB Also, feel free to try these steps:

Thanks gents. Issue reported.

Is your PC connected to a surge protector?

Can you confirm the freeze happened while you were performing AAR? 2024-04-22 12:03:32.978 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-04-22 12:11:09.233 INFO LUA (Main): Lua: States: 690, CPU load: 0.4%, Mem: 521.3 MB 2024-04-22 12:11:15.472 INFO LUA (Main): Lua: States: 690, CPU load: 1.3%, Mem: 530.6 MB 2024-04-22 12:11:47.260 INFO LUA (Main): Lua: States: 690, CPU load: 0.4%, Mem: 532.3 MB 2024-04-22 12:15:19.294 INFO Dispatcher (Main): Stop 2024-04-22 12:15:19.694 INFO APP (Main): wcTanker::onEvent:5 2024-04-22 12:15:19.694 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:6 2024-04-22 12:15:19.694 WARNING LOG (19264): 1 duplicate message(s) skipped. 2024-04-22 12:15:19.694 INFO EDCORE (Main): (wcTanker)enterToState_:3 2024-04-22 12:15:19.694 INFO APP (Main): wcTanker::onEvent:5 2024-04-22 12:15:19.694 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:6 2024-04-22 12:15:19.694 WARNING LOG (19264): 1 duplicate message(s) skipped. 2024-04-22 12:15:19.694 INFO EDCORE (Main): (wcTanker)enterToState_:3

I assume you don't have a track for this?

Thanks for your feedback.

Thanks for the precision. Issue reproduced and reported.

As long as you believe the issue is not on your side, we won't be able to help. Do you have Riva Tuner installed?

Designers should have the choice between scalable text and fixed-size text. For now, we only get scalable text. Draw tools improvements are low priority right now, which means fixed-size text won't be implemented right away.

The crash comes from a "Virtual Desktop Streamer" dll: 2024-04-21 11:47:59.187 INFO EDCORE (17404): try to write dump information 2024-04-21 11:47:59.191 INFO EDCORE (17404): # -------------- 20240421-114800 -------------- 2024-04-21 11:47:59.191 INFO EDCORE (17404): DCS/2.9.4.53707 (x86_64; MT; Windows NT 10.0.19045) 2024-04-21 11:47:59.192 INFO EDCORE (17404): C:\Program Files\Virtual Desktop Streamer\VirtualDesktop.LibOVRRT64_1.dll 2024-04-21 11:47:59.192 INFO EDCORE (17404): # C0000005 ACCESS_VIOLATION at 00007ffe8e98aa86 00:00000000 2024-04-21 11:47:59.193 INFO EDCORE (17404): SymInit: Symbol-SearchPath: 'F:\SteamLibrary\steamapps\common\DCSWorld\bin-mt;', symOptions: 532, UserName: 'user' 2024-04-21 11:47:59.193 INFO EDCORE (17404): OS-Version: 10.0.19045 () 0x100-0x1 2024-04-21 11:47:59.194 INFO EDCORE (17404): 0x000000000000aa86 (VirtualDesktop.LibOVRRT64_1): (function-name not available) + 0x0 2024-04-21 11:47:59.194 INFO EDCORE (17404): 0x0000000000006fc2 (VirtualDesktop.LibOVRRT64_1): (function-name not available) + 0x0 2024-04-21 11:47:59.195 INFO EDCORE (17404): 0x0000000000046459 (virtualdesktop-openxr): (function-name not available) + 0x0 2024-04-21 11:47:59.195 INFO EDCORE (17404): 0x0000000000047671 (virtualdesktop-openxr): (function-name not available) + 0x0 2024-04-21 11:47:59.195 INFO EDCORE (17404): 0x00000000000ab9d2 (virtualdesktop-openxr): xrNegotiateLoaderRuntimeInterface + 0x58742 2024-04-21 11:47:59.196 INFO EDCORE (17404): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14 2024-04-21 11:47:59.551 INFO EDCORE (17404): Minidump created.

No, it's OK: The search engine is broken in this part of the forum (reported here). It took me 5 minutes to find the other thread I knew about. Threads will be merged.

It happens when the track starts when the server starts. Check the mission time.

@Rene Coulon As discussed in PM, I checked all terrains: I found that Normandy has this issue with civilian traffic. I could not replicate the issue with other terrains. It's now reported as a Normandy terrain issue.

An issue has been reported a few days ago: Does that matches your issue?