BJ55

Weird, I'm having wrong releases in any mode other than DT.

Well, that one is funny: I followed your suggestion, mem usage was the same but with the AH-64, over high density areas and video feed turned on, GPU usage went from 100% to 80% and stutters are gone. DCS 2.9.3.51704 "Terrain scenery performance: optimized instancing and improved and optimized streaming." could be the cause of more RAM needs?

Naaah, no need to SFC with winupdates and drives scheduled optimisation disabled (the two more probable cause of corruption), if the console reports no errors it's better leave the ugly beast as it is. I see little difference with textures set to low: 8GB less usage, same long loading time, same 60 fps, lower quality. What's eating all the RAM? Maybe I should refresh .Net and C++ libraries?

@Kanelbolle : SP , this is mission https://www.digitalcombatsimulator.com/en/files/3331362/ , or any DCS "create fast mission" with medium-high units and with this settings Since the last updates I've had to lower preload radius from 80km to 50km, shadows from default to flat and MSAA from 4x to 2x, but still huge memory usage with high number of units... And stutters when they explode! It doesn't crash because of a big pagefile.sys, but often it hangs for minutes, even while generating fast missions.

I look at the process memory usage and free RAM left from any source than windows 10 useless task manager (that displays wrong values https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/task-manager-display-incorrect-memory-info ) , reaching 50GB while standing C&D is a bit too much, don't you think?

This! I reach 58GB with TTI Sinai SP, 35GB with fast mission (med. units) , memory and disk usage is out of control.

I was able to reproduce with quick mission Caucasus C&D, with both automatic startup and manual startup no steady alignment light. Edit: pilot error, forgot to set Nav Comp to stby.

The website is misconfigured. Direct link: https://www.digitalcombatsimulator.com/en/products/planes/m2000c/

Can you tell me the source of that info? Reticle depression knob has no effect in A/A mode.

Found: automatic entries in AC weight with the reload button don't affect mils depression value, only manual input of AC weight is effective. But still can't explain why at low altitude (TGT 200ft) with default fuze settings it's always a miss, while in Nevada (TGT 4500ft)... Wrong AoA value in the calculator because of unpredicted CG shift and air density?

I've made a test with system managed some time ago and the result was more stutters/instability, maybe because of my PC configuration, but with the CAD-CAM workstation I always used a fixed (really big) pagefile to avoid unexpected crashes. Little OT: with the last patch 64GB of ram are on the low side: AH-64 @ Sinai (only two units) 40GB usage, AH-64 @ TTI-Sinai (multiple units/scripts) 59GB usage.

No, it's not, a big swap file is always needed, especially when the software isn't optimized or has memory leaks. Set the pagefile at 32GB, check the cause of "2024-09-16 02:00:37.928 INFO EDCORE (Main): IO cores: {}" , also there are plenty of reports regarding instability of 560.70 drivers, give a try the 552.44.

Other modules have other issues: F-18 https://forum.dcs.world/topic/350516-issues-with-cluster-bombs F-16 https://forum.dcs.world/topic/349405-cbu-97-inaccuracy-ccrpccip/ https://forum.dcs.world/topic/355618-f16c-bomb-interval-bug (the funniest one) F-4 https://forum.dcs.world/topic/357226-laydown-cbu-87-falling-long The main problem is that AV-6B is not maintained anymore, so the introduction of fuze settings added more issues to the already existing ones.

Yes, CBU's are having problems and this is happening on most modules. No issues here with ripple in CCIP/CCRP DMT single/multiple (tested with both CBU-99 and Mk-82 SE with default settings, because of: https://forum.dcs.world/topic/351882-the-fuze-option-for-multiple-bombs-per-rack-is-not-available/ ).

SA342.

All default RB missions are unmaintained, so expect breakage. Download Chuck's guide and use it for learn startup procedure and other tasks.

Tested all possible combinations, this time with max fuze delay so only HoF is used, always the same result. The CBU's ripple is problematic with other aircrafts too, only the A-10 seem unafected.

i5-4690K 4 cores, see here: https://forum.dcs.world/topic/357198-fps-drops-when-enemy-aircraft-present/#comment-5514870

2024-09-04 17:05:11.415 INFO EDCORE (Main): common cores: {2, 3} 2024-09-04 17:05:11.415 INFO EDCORE (Main): render cores: {0, 1} 2024-09-04 17:05:11.415 INFO EDCORE (Main): IO cores: {} Your CPU doesn't have enough cores to handle all the data... Set resolution at 1920x1080 and disable all the eye-candy, I see that motion blur, canopy reflections, shadows, chimney Smoke Density, clouds, etc. are still enabled or set too high for your rig. Limit FPS at 60 or 30, better if with Adrenalin. Also try this: https://forum.dcs.world/topic/355693-huge-sp-performance-degradation-with-29758923-and-29658056-compared-to-dcs-29555918/page/9/#comment-5513022

If you're low on RAM you get stutters because it have to constantly load resources from disk, but loading from pagefile is faster than from installation folder. Are DCS folders excluded from AV real-time scanning? Could you upload the dcs.log after starting and quitting DCS? btw: DCS RAM/VRAM/disk usage went out of control.

Yep, right! Today I'm a little confused... So only remains the fuze settings, I will try with the default 1500.

Have you tried the special option "lower hbui refresh rate"? To me it made a huge difference, now I can use 8x sim speed without killing my PC.

@HB_PainterEdit: added track and mission. @Zabuzard I depress the button when aim dot is on TGT and speed/alt/att/dist are within parameters, also I check both altimeters: What I've noticed is that with the bombing calculator in L mode speed and bomb type don't affect mils, so if I fly at 400TAS I hit the target, any other speed is a miss. Edit2: I also change fuze settings, usually with the CBU-87 I set 1200 for >2000AGL and 900 for <1500AGL, that could also be part of the problem, since bombing calculator don't have an airburst altitude field. (btw: lower hbui refresh rate had a huge impact on performance, now I can run at 8x simulation rate without big stutters, thanks a lot!) F-4E_laydown_sinai2.miz F-4E_laydown_sinai2.trk

Did some more tests... 01 L CBU-87: 450TAS (indicated +-5), run in 2000 (+-100 AGL), IP 4nm, TA 0, 91 mil - bombs released when target was aligned the center of the radar display, hit after target. 02 L CBU-87: 450TAS (indicated +-5), run in 1500 (+-100 AGL), IP 3nm, TA 0, 89 mil - bombs released when target was aligned the center of the radar display, hit after target. 03 L CBU-87: 450TAS (indicated +-5), run in 1500 (+-100 AGL), IP 1nm, TA 900 (fuze), 39 mil - dropped at button press, hit before target. 04 L CBU-87: 450TAS (indicated 453), run in 2000 (+50 AGL), IP 3nm, TA 0, 119 mil - hit after target. 05 Direct CBU-87: 450TAS (indicated +-5), RA 2000 (+-100 AGL), TA 0, DA 20°, 118 mil - on target. 06 L MK-20: 450TAS (indicated +-5), run in 1000 (+-50 AGL), IP 2nm, TA 0, 91 mil - on target. Then I thought, what if Jesta is missing something? Aaand yes, drag coefficient remains unchanged (1.02) for every bomb type.

Today I was testing the CBU-87 in L mode, all fell long after the target, I've also tried with 0 release advance and was the same. Release speed (450) and height (2000) was not precise, but in DL mode bombs hit the target. Am I doin' something wrong? Is it a bug? F-4E_laydown_sinai.trk