dutchili

I experience terrain stutters when looking sideways, approx. from a 45 degree angle compared to 'straight ahead'. The stutters disappear after a second or two when their are not many objects to show in my field of view. (but the issue is reproduceable even in de Nevada desert) It is very reproduceable and not something new in the latest release. I wonder: why is the 'system' working differently from a specific viewing angle? Anyway, it might be a clue to further performance improvements. @BIGNEWY

@BIGNEWY

I checked the tacview. Distance between the two helicopters was 1000 ft

Difficult to see in this VR screenshot, but: - with LOD set to 0.3, the center of the Apache disappears at a center distance. - the apache in the front is fully visible. - the one in the rear only shows the rotor and two (gear?) elements.null I was expecting to see the entire Apache at distance, though will less detail.

Pressing DMS left will change the displayed sensor on the left MFD. The newly shown sensor is not made SOI. I can see the logic in that if you just wanna have a quick peek using another sensor without losing 'the lock', but i don't find it intuitive. I change the sensor deliberately to use it. I do not have declassified information that this behavior is wrong. I also don't have documentation that this is right. My wish is that the newly selected sensor is made SOI automatically. (no track file and dcs log will be provided)

Could have been DCS not handling exceptions with local internet.

16:54: both server and client are working again. Next dcs server entry is ASYNCNET (13684): Login success. I guess there was a authentication issue

dcs.logserver dcs.log@bignewy: here is you crystal ball

Yes, but also 2d is not starting @BIGNEWY (Yesterday everything was fine. No changes to drivers or other system changes. So i suspect something with data connection to Steam/ED.)

Currently unable to start DCS (steam edition) nor dedicated server. Both just quit during loading without an error message. Last entry in dcs.log: 2024-02-16 14:38:58.657 INFO APP (Main): options.graphics = Last entry in dedicated server log: 2024-02-16 14:38:49.143 INFO APP (Main): CPU cores: 24, threads: 32, System RAM: 32535 MB, Pagefile: 38912 MB === Log closed.

I checked the solution offered by @Lord Vader. The Cursor Zero feature is indeed available on the AGR (no sub-mode) MFD page and resets the diamond to the selected steerpoint location. Thanks!

Are you sure CZ is available in AGR? CZ is available in the TGP sensor, but that was not loaded on this flight. I tried to TMS down in AGR but without the CZ effect. I don't a OSB button for CZ. Is there another button/command to CZ?

To quickly show the issue, i did the following in the track: - hot start with 2 dumb bombs - set CCRP - create radar lock on sub-mode GMT - see the POI with JHMCS - switch back to CCIP (now the AGR does not show GMT anymore) - drop bombs - unable to undesignate as GMT is no longer available - switching back to nav does not change the POI cannot undesignate.trk

I'll get you a track asap. I think i missed out one important step to reproduce: get rit of the bombs before trying to undesignate.

As the title says. Only way to back to the nav point is by undesignating through the TGP, which is annoying if you haven't loaded one. Reproduction: - prep Miz with one steerpoint - Load bombs -take off - designate any location with AGR/GM - try to undesignate

Hi @Lord Vader, Replication steps: - cold start - load TGP - take off - master mode A-G - ISSUE: radar cannot be set to AG modes In NAV mode you can select the AG radar modes, but you can't see the locked items (FCR or TGP) in the JHMCS. I don't know if this is 'correct' or incorrect', but if feels wrong as it does not support recon flights.

Hahaha, how did you find out that?? Great tip, thanks.

In the Viper, having no weapons loaded, the Air To Ground radar is not available in A-G mode. I cannot select AGR modes. I can select those modes in NAV mode, but won't see a diamond in the HUD for whatever targe i lock with the AGR nor the TGP.

even if you have enough VRAM, you will still have stutters.

I guess we all want our beloved simulator to work flawlessly. Even in Wags' video's we see the ground stutters. So i would not spent too much time on optimising your own. Just enjoy the sim as much as you can. I feel it is not up to us to solve this issue nor find the root causes. I would highly appreciate a response from ED from a technical perspective on the root cause(s) and when they expect to fix it (or not). It should not be too difficult to debug the frame-time and understand which feature causes it to extend the target set by a certain FPS.

Only after setting list/dlink/gps time to OFF and then ON again i can see 'some' units, but not all, including the Awacs itself. Both multiplayer as single player (same mission)

In this track you can see that the mark points set with HUD or TGP don't last. After making a mark point, setting it the active waypoint and pressing CZ on the TGP, it does not point to the same location as where the markpoint was made. Second issue. WLastMissionTrack.trkhen mountains are in between the target and the TGP, the data given to GBU-31 bombs in PRE mode is wrong (bomb hitting mountain.

Same in multiplayer. I could not get it to work. I locked a SA-6 radar via the HAD page, TMS left long to send it to my human wingman. I got the TDOA HUD symbology. Wingman got 'data received' audio message and TDOA HUD symbology ("- - >") pointing towards the target. However, the lines on the HAD page were not showing. We did sometimes see a solid white line from own ship to 'nowhere' or a blue dashed line from master to target. But never the expected white dashed line from slave to target. Wingman was unable to lock the target. Neither ever got the TD-M or TD-S indications. @BIGNEWY Seems broken.

Somehow only my windows app shows v.59 while the headset still has .57. I do have all those new options (for a week now). The battery-life is hugely improved, even without setting that power mode. I drained the battery in about 1.5 hours before at 90hz, now it is 'not a topic'.

These guys did die, but kept hanging in the air (at the original top of the building?)