dutchili

This occurs even with a high-end PC, especially in VR. Sounds like a classic programming issue where the graphical representation is linked to the actual work (getting server data). If the latter is delayed, so is the UI en 'user input'. The gameplay has the same issue (so it seems) where FPS and 'mission complexity' are tightly coupled.

I was indeed I was pretty successful in limited the stutters with DCS, Windows and Nvidia settings, but i can't fix scenary stutters over populated areas. If you watch the recorded stream you can see that the houses etc on the edges of the screen are not fluidly moving backwards. The FPS indications in DCS are not 100% representing what we actually see. In general, in my case, the ground/scenery stutters are the result of the CPU not being able to produce enough frames. It occurs mostly when turning while taxiing, looking sideways more than 45 degrees or when flying low-level over cities. The more complex the weather, the more stutters. With my reference to settings, i primarily mean that the game is unable produces enough frames in all scenario's regardless the settings.

Check yesterday's livestream by Waggs on the Germany map. 2d and continuous scenery stutters. I advised him to remove all unofficial mods. No seriously, I don't think you can fix it with settings.

Does anybody know how to fix the following: - i can't add ground units contained in the VPC Aifield equipment mod. - but for mission already having units from that mod, they show fine. - in the attached picture i copy/pasted a unit into a new miz, and then it shows. But the other available units from that mod do not show in the dropdown list.null

The latest NVidia drivers seemed to have an impact, but about the time it was released we also had a DCS update. Before that, it was near perfect. Some threats are not tuned to the capacity of the CPU core they run on, resulting in all of us being "CPU limited", which is actually 'limited by insufficient load balancing'.

@BIGNEWYCan you address this topic to the correct team?

non moded units do not land either. The error is known in another map too, until it was fixed.

I rather not. Just make Bodo Blue, put a red unit in front of the airport, have it land (waypoint). It won't. Or place a civi (civilian aircraft mod) on the airfield (you'll get the error)

Civilian airplanes cannot be placed with waypoint 'Takeoff from ramp'. The error pop-up mesage reads "error set to airfield. No free airport." I tried this with A330, A320, while KC-135 and E-3A work perfectly. Additionally, AI traffic does not land on Bodo. Instead they divert to Andoya. This was tested with F-18, F-15 and F-16.

When the contrast on the mfd is changed and then the user selects a different sensor on that same mfd, the entire mfd goes black as a result of maximal contrast. When clicking the contrast button the issue immediately resolves itself.

No units positioned, just scrolling and zooming. All of a sudan de mouse pointer becomes laggy and than the entire system hangs. CTRL-ALT-DEL does not respond. Last entries of dcs.log: 2025-02-22 08:36:44.473 ERROR_ONCE DX11BACKEND (15472): texture 'splineAtlas.Splatmap5.1.roof.tif' not found. Asked from '' 2025-02-22 08:36:44.476 ERROR_ONCE DX11BACKEND (2828): texture 'pointAtlas.Splatmap5.1.roof.tif' not found. Asked from '' 2025-02-22 08:36:44.483 ERROR_ONCE DX11BACKEND (2828): texture 'default.mr' not found. Asked from '' 2025-02-22 08:37:39.770 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2025-02-22 08:38:11.955 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] 2025-02-22 08:38:16.441 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2025-02-22 08:38:29.308 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] dcs.log DxDiag.txt

Haha, I didn't know that.

Documentation on what all actions, tasks etc do.

Then I suggest you build your own test mission(s) to enable regression testing on actions, triggers and conditions. Perhaps write some documentation too.

Tanker have weird behavior too. After completing the left-hand racetrack, then weave to the right before starting the next lap.

let's not discuss windows or hardware settings. We 'all' noticed this since the last update. The root cause is in the (full and complete) change log. Something for ED to figure out.

I think this graphics card will not deliver better performance until the 'CPU overload' is fixed (by spreading the frame generation and other workload over more CPU cores /make it more efficient). In VR: the final FPS is mostly limited by the rendering process in the CPU, not the GPU.

Indeed. There was a good exchange of public documents behind the scenes on this topic. Yet I agree with the original poster that it ...well...sucks. But DCS is a simulation, not a game, so we have to live with what we know about the real world and hope that the real pilots received more useful software in later blocks/MLUs.

DM sent

@BIGNEWYCan you link the public unclassified evidence for the current implementation?

Like the topic starter said: it is so strange that the pilot initiating the search is not getting the result. Please consult a subject matter expert.

Had multiple crashes in ME and one while trying to run a simple flight. Only found this at the end of the dcs.log: 2024-12-15 18:35:12.549 WARNING ASYNCNET (Main): Ignoring duplicate request to imageIRAQ_terrain while one is already in flight. 2024-12-15 18:35:12.551 WARNING ASYNCNET (Main): Ignoring duplicate request to imageAFGHANISTAN_terrain while one is already in flight.

Yes, and: waypoints created while flying (mark / TGP lase) have the wrong elevation too.

This issue still excists, bump! @BIGNEWY It is hard to hit a bridge. The object height seems not be added to the ground altitude. In this example mission, the ME lists the altitude equal for the water and the bridge (which cannot be right). Also, the elevation of the water as displayed by the ME differs significantly on different area's of the lake, suggesting that the water depths are also ignored. During the miz, the TGP points at the water below the bridge. When lasingBridge strike test.miz the road on the bridge, the elevation is different from what the ME reads and the actual elevation of the road. Out of 5 tests, at least one bomb misses the road by underflying or overflying the target. For GPS bombs, waypoints create in the ME or on the fly are far from exact.

see topic title @BIGNEWY