BJ55

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

16GB of RAM? My installation uses 18GB just in mission editor... Try with MSAA set to 2x or TAA, SSS off, civ. traffic off, water medium, SSAO off, SSLR off, heat blur off, forest and scenery detail factor 0.8, terrain object shadows set to flat, aniso filtering 16x, cockpit global illumination off, also check to have a fixed pagefile size of 32768 (or the double, since you're low on RAM). If this doesn't help reduce textures to medium and resolution to 1920x1080.

Next time attach also the ..\Saved Games\DCS\Logs\dcs.log , from your .crash I suppose a grafic driver issue, see https://forum.dcs.world/topic/356816-one-day-one-or-two-freeze-and-crashes/#comment-5509622 and https://forum.dcs.world/topic/218023-acces-violation-crash/#comment-218492 , first try to rool back drivers (if NVidia don't use versions after 552.44). @silverdevil : the effects2.dll crash was due to exhausted resources, with the current DCS release I've also had occasional big memory leaks and performance drops previously unnoticed, since they're already investigating...

In some Sinai areas I'm having the same issue, the only way for me to avoid stutters is flat shadows w/o AA and LOD<0.8, so I suspect that it's mainly a DCS graphic engine issue (last patch has big memory leaks).

Thanks for the input, I will try your suggestions.

With the A-10C II I've had my first crash when the AGM hit the target (TTI Sinai 2.5.0a, track disabled, TGP + MAV feed). The only change made to the system was NV drivers, from 551.86 to 552.44, in NVcp I've set max performance and Vsync on (60 FPS). W10 error: Faulting application name: DCS.exe, version: 2.9.7.59263, time stamp: 0x66c380d4 Faulting module name: Effects2.dll, version: 2.9.7.59263, time stamp: 0x66c37b2f Exception code: 0xc0000005 Fault offset: 0x0000000000034927 Faulting process ID: 0xb64 Faulting application start time: 0x01daf95cabf3d02a Faulting application path: E:\sim\DCS World\bin-mt\DCS.exe Faulting module path: E:\sim\DCS World\bin-mt\Effects2.dll Report ID: 2598bd3f-556e-4e45-9b9d-7f782951d69c Faulting package full name: Faulting package-relative application ID: Recently I've noticed that smoke effects have a huge impact on FPS, really noticeable when firing rockets with choppers, could this be the cause of the crash or maybe shaders/fxo compilation took too much? dcs.log-20240828-153913.zip

Maybe ask to Nvidia/AMD/M$ if their updates caused performance issues? Here with W10pro 19045.3086 and NV 551.86 I've not had any performance decrease, stutters or CTD's since last year.

I have the same impression, the Moon is too small, almost impossible to see any surface detail even at max zoom (min FoV). Right now I'm downloading Stellarium, to compare dimensions with the same 70° FoV on a 2560x1440 screen. Edit: WT ? Ok, time to order a 64" curved monitor.

This!

That folder only contains the CEF user profile, so it will be recreated at first hbui restart. In order to prevent unwanted connections you must set "offline" in "HB UI Online Access" within the F-4 special options. The CEF executable is contained inside main DCS folder and cannot be deleted. Since that folder must be excluded for detection because of false positives, the best thing to do remains blocking all network requests to untrustworthy corporations globally! (expect web breakage since The Four Horsemen tentacles are everywhere)

All default RB missions are unmaintained, so expect breakage.

"Can't move D:\DCS World\_downloads\bin/WorldGeneral.dll to D:\DCS World\bin/WorldGeneral.dll: (225) Operation did not complete successfully because the file contains a virus or potentially unwanted software" Add DCS folder to antivirus exclusions, sync system time and try again.

Install a good security sw with an advanced firewall and hips, enable windows event viewer dns logging, use LiveTcp and Wireshark (or other sw) to monitor your connections... Then you will discover that those dll's don't make any kind of network requests.

The HUD was in night mode?

Note that not all the map has been optimized, there are some areas that still cause a FPS drop. Forest and scenery detail factor together with terrain object shadows make a lot of difference in this very demanding map and Marianas map (GPU and VRAM usage), also check if NVCP power management mode is set to prefer maximum perf. I see a lot of stutters/F10 reports in the VR Bugs subforum, so maybe it's only more evident with this map?

I'm using linear axis and the maximum stick displacement speed seems quite spot on, really like it! (without FFB it's easy to exceed real life displacement speeds)

At least I've understood why the FARP was causing issues, quick start mission has unchecked AC types:

I've removed the FARP, put single helipads and saved the mission, now it works.Mi-24P_CAUC_IA_Weapons_Range.zip

Maybe you're askin' too much from your rig? Smooth as silk in 2D.

Not tested 560 yet, so thanks for the info, you made me spare a lot of time. Every driver after 552 is causing me multiple issues (massive tearing, CTD's, etc..) with almost every program, I have a suspect: are they next to release the RTX 50 series?

https://forum.dcs.world/topic/353420-f-14b-afterburner-problem-with-dcs-29657650/#comment-5478867 You must click on the right side of the bar and use arrows to change deadzone, be aware that any setting >9.9 cause issues. https://forum.dcs.world/topic/353370-speedbrake-retraction-bug-with-new-detent-option/#comment-5479849 ...We must wait for the hotfix!

+1 , something's wrong with the new AB detent and deadzone special options.

The situation is worse than expected, did some tests and noticed that special settings have no effect on AB detent, also, after loading a quick start mission, if deadzone >9.9% when pushing to full AB fuel goes empty, after restarting the mission tanks are empty from the beginning and I have to restart DCS! Edit: even with 0 fuel the engines keep running and pushing! dcs.log

1- noticed this as well, the only way to move the slider is click on the bar and use keyboard arrows. 2- no issues here with AB detent at 90% and deadzone at 1%. 3- not sure what you mean.