Flappie

The trick will work: I tested it. But you are right: these files might get replaced by a future update. Since the Caucasus terrain is free of charge, I'm not sure why you would want a refund, but you are free to try. Why not install the Caucasus terrain?

Thank you! Issue reported.

I checked the mission files: two missions happen over Caucasus (13 and 14), and one happens over the Channel ("Channel bonus"), but this last one is not "listed" in the campaign, which means it won't cause you any trouble in case you don't have the Channel terrain installed. In case you won't or can't install the Caucasus terrain, here's what you need to do: 1. Move these two files away from the campaign folder (.\DCS World\Mods\campaigns\P-51D The Blue Nosed Bastards of Bodney): BNBOB - 13.miz BNBOB - 14.miz 2. Now, make two copies of "BNBOB - 01.miz" and rename them using these names: BNBOB - 13.miz BNBOB - 14.miz

Thank you, @Livers. Unfortunately, I'm still unable to reproduce the issue. I see you're using Upscaling (=0.66). Can you disable upscaling in DCS and see if messages are still clipped?

No, it shouldn't cause any issue.

Actually, "bin-mt" and "bin" folders now contain the exact same thing. ED hasn't removed the "bin-mt" folder yet, but it will be removed at some point.

I ran an old track of mine and I can see several issues, especially with the S-3B (for all planes) and also with the Tomcat desperately trying to get fuel from a KC-135 MPRS. There's an internal request to lower maximum AOB for tankers doing circuits/racetracks, from 25° to 15°. Hopefully, this action will solve current issues.

The crash comes from the F-15E dll. This is a module-related crash. The thread will soon be moved to the F-15E subsection of the forum.

In this video of an A320, we can see it's still raining when the aircraft takes off. The rain is still seen gliding on the glass at 4:50 (speed is not indicated). In this other video, the rain stops being visible on the canopy at about 230 knots:

Hey @draconus. I've read the other thread (which has NO track by the way, just like yours ) then tested by myself. Some observations: I've just tested both settings (low and high rain droplets) and I agree it's very hard to see any difference. I plan to report that the "low" rain droplets setting is not different from the "high" setting. It should be lower than it is. In DCS, the rain effect on the canopy ceases once airspeed reaches ~460 knots. In the Youtube footage, it ceases when the main gear is lifted off the ground (let's say 175 knots). BUT, it looks like it's not raining anymore in the footage. We need another video showing a takeoff in heavy rain. Hornet_rain_takeoff_LOW.trk Hornet_rain_takeoff_HIGH.trk

We need a short DCS track, please.

Can you please attach a short DCS track?

Please attach your options.lua (Saved Games/DCS.../Config/options.lua).

The simplest way to check whether other players experience your issue is to post a DCS track. How to make a track? Run your mission, wait for the issue to happen, make sure it lasts at least 30 seconds to 1 minute, so players have time to check their FPS. Exit the mission, then click "Save Track". Exit DCS, then attach your track here (the file is named something-something.trk).

Wow, that is some quality post! Once the Combattante II smoke is fixed (a.k.a once ship smoke thickness variability works in DCS), please ping me here so I can review all ships and make the appropriate reports to devs (black/white smoke and transparency). Thank you.

I tried both, plus the Minigun one.

This is how it looks like: 2025-01-25 19:01:14.149 WARNING LOG (19392): 2 duplicate message(s) skipped. 2025-01-25 19:01:14.149 ERROR_ONCE DX11BACKEND (16032): texture 'MAP_AH64_PLT_R' not found. Asked from '' 2025-01-25 19:01:24.158 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2025-01-25 19:07:24.344 WARNING LOG (19392): 4 duplicate message(s) skipped. 2025-01-25 19:07:24.344 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-01-25 19:07:31.256 WARNING LOG (19392): 1 duplicate message(s) skipped. 2025-01-25 19:07:31.256 ERROR DX11BACKEND (22436): Can't map structured buffer. 2025-01-25 19:07:31.256 ERROR DX11BACKEND (22436): Failed assert `0` 2025-01-25 19:07:31.257 INFO APP (Main): Device unplugged: [HDAUDIO] NVIDIA High Definition Audio 2025-01-25 19:07:31.259 ERROR ED_SOUND (8928): IAudioClient::GetCurrentPadding failed: 0x88890004 (AUDCLNT_E_DEVICE_INVALIDATED) 2025-01-25 19:07:31.432 WARNING LOG (19392): 1 duplicate message(s) skipped. 2025-01-25 19:07:31.432 ERROR VISUALIZER (22436): xrEndFrame failed with error: XR_ERROR_RUNTIME_FAILURE 2025-01-25 19:07:31.433 ERROR DX11BACKEND (22436): DX device removed. Reason: 0x887A0006 2025-01-25 19:07:31.458 INFO APP (Main): Device unplugged: [HDAUDIO] NVIDIA High Definition Audio 2025-01-25 19:07:31.775 WARNING LOG (19392): 2 duplicate message(s) skipped. 2025-01-25 19:07:31.775 INFO APP (Main): Device unplugged: [SWD] ASUS VA24E (NVIDIA High Definition Audio) 2025-01-25 19:07:31.813 INFO APP (Main): Device unplugged: [HDAUDIO] NVIDIA High Definition Audio 2025-01-25 19:07:32.041 WARNING LOG (19392): 3 duplicate message(s) skipped. 2025-01-25 19:07:32.041 INFO APP (Main): Device unplugged: [SWD] Pimax (NVIDIA High Definition Audio) 2025-01-25 19:07:32.078 INFO APP (Main): Device unplugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(ASUS VA24E) 2025-01-25 19:07:32.117 INFO APP (Main): Device unplugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(G236HL) 2025-01-25 19:07:32.193 WARNING LOG (19392): 1 duplicate message(s) skipped. 2025-01-25 19:07:32.193 INFO APP (Main): Device unplugged: [HDAUDIO] NVIDIA High Definition Audio 2025-01-25 19:07:32.272 WARNING LOG (19392): 1 duplicate message(s) skipped. 2025-01-25 19:07:32.272 INFO APP (Main): Device plugged: [HDAUDIO] NVIDIA High Definition Audio 2025-01-25 19:07:32.652 WARNING LOG (19392): 5 duplicate message(s) skipped. 2025-01-25 19:07:32.652 INFO APP (Main): Device unplugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(ASUS VA24E) 2025-01-25 19:07:32.723 WARNING LOG (19392): 1 duplicate message(s) skipped. 2025-01-25 19:07:32.723 INFO APP (Main): Device unplugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(G236HL) 2025-01-25 19:07:32.862 WARNING LOG (19392): 3 duplicate message(s) skipped. 2025-01-25 19:07:32.862 INFO APP (Main): Device plugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(G236HL) 2025-01-25 19:07:33.028 WARNING LOG (19392): 3 duplicate message(s) skipped. 2025-01-25 19:07:33.028 INFO APP (Main): Device plugged: [DISPLAY] @System32\drivers\dxgkrnl.sys,#303;Generic Monitor (%1);(ASUS VA24E) 2025-01-25 19:07:33.068 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2025-01-25 19:07:33.071 INFO ED_SOUND (Main): Opening default audio device. 2025-01-25 19:07:33.071 ERROR DX11BACKEND (14128): Failed assert `false && "failed to create texture"` 2025-01-25 19:07:33.071 INFO EDCORE (14128): try to write dump information 2025-01-25 19:07:33.071 INFO ED_SOUND (Main): Speaker layout: auto 2025-01-25 19:07:33.072 INFO ED_SOUND (Main): Driver reports 2 channels with mask 0x3 2025-01-25 19:07:33.072 INFO ED_SOUND (Main): Using 2 channels at 48000 Hz 2025-01-25 19:07:33.072 INFO ED_SOUND (Main): Channel layout: Headphones/Stereo 2025-01-25 19:07:33.089 INFO EDCORE (14128): # -------------- 20250125-190733 -------------- 2025-01-25 19:07:33.102 INFO EDCORE (14128): DCS/2.9.12.5336 (x86_64; MT; Windows NT 10.0.26100) 2025-01-25 19:07:33.120 INFO EDCORE (14128): C:\Program Files\Eagle Dynamics\DCS World\bin-mt\GraphicsCore.dll 2025-01-25 19:07:33.122 INFO EDCORE (14128): # C0000005 ACCESS_VIOLATION at 00007fff3a6514a2 00:00000000 2025-01-25 19:07:33.123 INFO EDCORE (14128): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World\bin-mt;', symOptions: 532, UserName: 'genea' 2025-01-25 19:07:33.136 INFO EDCORE (14128): OS-Version: 10.0.26100 () 0x100-0x1 2025-01-25 19:07:33.167 INFO EDCORE (14128): 0x00000000000614a2 (GraphicsCore): render::RenderGraph::reset + 0x2352 2025-01-25 19:07:33.168 INFO EDCORE (14128): 0x0000000000058037 (GraphicsCore): render::RenderGraph::createRenderablesCollection + 0x887 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x0000000000054e96 (GraphicsCore): render::RenderGraph::bakeGraph + 0x1D6 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x000000000001e854 (SceneRenderer): DCSSceneRenderer::bakeRenderGraph + 0x34 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x00000000001570d5 (Visualizer): smCamera_Implement::getClipRegion + 0x1E555 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x0000000000047a89 (edCore): ed::SyncTaskQueue::push_task + 0x14449 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x0000000000046f87 (edCore): ed::SyncTaskQueue::push_task + 0x13947 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x0000000000048833 (edCore): ed::SyncTaskQueue::push_task + 0x151F3 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x00000000000323b1 (edCore): ed::thread::_get_current_thread_id + 0x71 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x0000000000014ea0 (ucrtbase): wcsrchr + 0x1F0 2025-01-25 19:07:33.169 INFO EDCORE (14128): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-01-25 19:07:33.286 INFO EDCORE (14128): Minidump created. The relevant line is here: 2025-01-25 19:07:31.432 ERROR VISUALIZER (22436): xrEndFrame failed with error: XR_ERROR_RUNTIME_FAILURE Ensure you don't have any remnant of the Open Kneeboard in Windows registry:

Do you mind sharing your script so I can quickly reproduce the issue?

Hi @franx. Please check this thread and tell me if it helps:

Some modules can only display 2 digits (Mi-24P), or an association (the P-47 has one digit, the roundel, then 2 digits), because they were coded that way, influenced by the main users of the real aircraft (e.g. Russian Mi-24 have only 2 digits). The "real" issue here, as stated by @rob10, is the change that was operated in 2023. More explanations here. I couldn't reproduce the Gazelle issue: my Gazelle does not display any number. Can you please attach the mission you used?

At first, I was all alone, so I didn't think about reporting this issue. I'll report it.

It could, yes. According to what I read, this setting has various results depending on the game and the PC. I had a brain fart about parking/unparking cores. Simply ensure you let Windows run your CPU as usual, especially if you had to tweak Windows when that messy MT bug was around. You are right: High Performance power plan means no core-parking. Anyway, now that your DCS runs fine, don't touch anything. Come back here if the issue returns.

A dev says the Combattante II smoke thickness cannot be tuned because of a bug in the code which enforces max smoke thickness. Hopefully, the reason for the Kilo smoke thickness is the same, which means it would smoke less once the Combattante II bug is fixed. I've just bumped the Combattante II internal report. We'll see. About the smoking/non-smoking matter, I have a proposition: maybe we can ask devs to make the Kilo stop emitting smoke whenever its depth is less than 0 feet. This way, mission designers and Combined Arms users will be able to choose whether the sub emits smoke or not. Would it work for you, gents?

I don't see anything obvious in your DCS log, but this: 2025-01-25 04:49:33.113 WARNING EDCORE (Main): hypervisor is active ... 2025-01-25 04:49:33.113 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) Warning 1#: Check this thread (and don't forget the second page). Warning #2: Try unparking all of your CPU cores The former MT bug with modern CPUs is no more. If you had tweaked your CPU because of this bug, try the previous, normal, setting. Your DxDiag log shows several blue screens. You might want to check your RAM.

Please attach a DCS track, a screenshot or two, and your custom board so we can give it a try.