MoleUK

Good to know I don't need to reproduce a track if it's a known issue, cheers. Wonder if it's related to the spotting dots changing colour when against clouds sometimes as well. It has a similar look to it.

Pretty sure this has been around a while, but I may try and replicate this later in a track if it's not a known issue. Just stood out to me today as it noticeably changes from the as-expected black to bright blue when it's against the ground vs the air here.

Not so weird if it's the old LOS bug kicking in tbh. It was always hard to replicate it and it still pops up, albeit infrequently.

When I play the track there, he finds the targets. The target list is open with a list of Gaz-66 iirc, I can see you scrolling up/down it as you try and get Petro to re-find targets. I will say alongside the Fog problem, there is another bug that interferes with Petro's LOS sometimes resulting in him not finding targets. You might be running into that one, at least if the list of targets isn't appearing low down in the screen for you. The LOS bug is not as bad as it was a few patches ago, I would routinely run into that one in MP. It would require re-approaching the ground targets from a completely different angle, as whatever was blocking the LOS was not blocking it from '360, only certain angles. It's been suggested that it's some terrain bug, or dead units, or some other unit model blocking the LOS at times. I have never figured out what's doing it as it's not consistent. So next time it happens, just take note of what angle you're aiming from (the south/north etc) and move to another angle to see if he will pick up the targets again. Usually works, but not always. I don't know when this LOS bug was introduced, but it was a few months back. I ran into it again today so it's definitely still there, it's just not happening as often.

Yeah this one has been around a long time. The moving map mod doesn't open F10 at all, so it remains the best/easiest workaround for now. Keeping the F10 map centred on the aircraft by clicking the arrow means flipping to F10 and back doesn't require that the game load in too many extra assets afaik. I've kept it centred that way for a few years now, it does help keep it more responsive. If the F10 map is viewing somewhere entirely different from your aircraft, it will try and load in any air/ground assets around that area. Currently the F10 map is literally a birdseye view of the actual game/mission/server, rather than being a simpler stand-in/representation. If you zoom in far enough you can even see the trees sway. With a game as vram/memory heavy as DCS, that presents some problems.

It's not due to overheat issues, many users have reported this over on the ED discord. Seems to be limited to MP, and often doesn't show in track replays. https://discord.com/channels/542985647502393346/1301330515822903326/1323881862078267466 Also a thread on it here. But this is all seperate from OP's issue.

What is your LOD slider set to? Anything less than 1.0 can cause ground assets to not render until very close range. Example here: Because only 100 dots can be rendered, having LOD less than 1.0 will lead to ground assets trying to transition to a dot and instead just disappearing. Because it prioritises giving dots to ground assets that are the farthest away rather than the closest. And it does so with all ground assets in the direction you're facing up to 80km away, so it hits the 100 dot cap very quickly. Until that gets fixed, keep LOD to 1.0.

VD will correctly resume gameplay. For link/airlink, either use a bit of tape to cover the proximity sensor, or use sidequest/meta development hub to disable the proximity sensor entirely. Then set the headset sleep setting to as long as possible. You may need to disable the prox sensor after every headset reset if not using tape. If using tape it needs to be white masking tape to work right, as it must be somewhat reflective.

That one is a seperate problem, it's something only ED can fix. More commonly seen in MP atm, they are trying to figure it out. If you get it in a short track do send it to them.

Yea I do wonder if more tweaks were done in terms of transition points, feels great right now regardless.

Auto is not off. And several other of the most popular servers appear to be leaning towards letting users control it for now. What people did was incessently complain about DCS spotting being atrocious. Someone even got so fed up with it that they made a mod, that mod was eventually folded into the game. The spotting being awful for years is how we got here. Looking at all the feedback since the change (as early as it is), the vast majority seem happier with the new system.

What you aren't understanding is that the general MP playerbase simply doesn't agree with your position. Nor do the mission makers. ECW went as far as to disable IC entirely for over 6 months, just so people could continue using the spotting mod after ED realised it was being used. The population never wavered in that time. Groundpounders continued to groundpound. Fundamentally, most MP players don't want to be blind. If anything many of them would prefer to have even better visibility than is now possible. Disagreeing with them is fine, but that simply puts you in the minority. It doesn't change their minds.

I don't think it's bandwidth, but it could be. When a player joins a server that is using thousands of slots, I think it refreshes the entire list of slots and players for every single player simultaneously which can cause a freeze. If you leave the scoreboard or role select open you will notice every single time a player joins, disconnects or reslots, the ENTIRE list refreshes. Score board will scroll you back to the top, and you can see the list of spectating players flicker as it refreshes. This has been my observation over the past few years at least. ED recently did an optimisation pass on this aspect of the game which helped reduce the server wide freezing quite a bit, but it was a bit of a bandaid on a fundamentally flawed system imo. This sort of behavior was previously mostly limited to having role select open while in VR, but it's gradually built to the point where it's a problem for flatscreen players, and then to the point where it spilled over into general gameplay.

As others suggested, use the filter. It keeps the freezing down somewhat. This is an old problem in very busy MP servers. You would also see server wide stutters when players reslotted or joined/dc'ed sometimes. Servers that switched to only using dynamic slots got around it.

Yeah this is likely the best compromise that could have been reached. There is enough flexibility to account for various different setups, without being too over the top. Those servers who want to force them all off can do so, whilst also allowing for those players who want to have dots off for themselves to join any of the servers that allow user controlled dots. Which appears to be most of them atm. I'm especially happy to see quad view dots fixed, that was a huge problem.

Ghosting is a known problem with DLAA/DLSS/TAA. TAA tends to be worst for it. You can update the DLSS version that DCS uses, and switch the preset with DLSS tweaker for DLAA to F. This will help reduce ghosting a good bit. https://www.nexusmods.com/site/mods/550?tab=files https://www.techpowerup.com/download/nvidia-dlss-dll/

I was skeptical based on the changelog, but quad view spotting dots feel just right now. Had them set to auto while flying on ECW cauc mission, which is about the worst case scenario re: spotting. It's not making me blind anymore. Still capping object draw to 40k to try and avoid the dot cap. With the above changes and hopefully an eventual fix for the 100 dot cap, spotting will be in the best place it's ever been imo.

This has been a problem for years. The only thing that solved it for me was moving to a GPU with 24 gigs of vram, though I only ever play in VR. On an 8 gig GPU in particular it was a huge problem. In VR the problem presented the same way, once you hit that vram cap/problem, GPU usage would peg itself to 99% and the FPS would tank. If you actually looked at the frequency for the GPU and GPU temps, both would be very low despite showing 99% usage. Far lower than it actually gets when at real 99% usage. The reason alt-tabbing for a while can clear it is it triggers a vram flush, seems to release something that causes the performance degradation. Alternatively in VR on Quest headsets, sending the a headset to sleep for 30 seconds or so and waking it back up will also trigger a vram flush and fix it. Right up until you hit the cap again. The only other fix is restarting the entire game, which isn't really very viable. Even now I still use the blank hanger mod and keep the map position locked overhead at almost all times. I would highly recommend anyone on a GPU with less than 16 gigs use the recently created moving map mod as an alternative replacement, as a fix does not look imminent. This doesn't get around the problem entirely as on server join and role select it still opens up the map, but it's better than nothing. Alternatively you can lower the texture settings and use optimised mods to lower vram consumption. This will at best delay the problem a bit.

Here's another if necessary. It's happening with the non-remastered F-5 as well. I do not own the FC4 F-5, but I suspect it's worth checking if that also suffers from the new problem. If it doesn't, that might at least offer a clue to the source of the problem. disappearing F5 test 200.trk

Патч от 24 декабря уничтожил производительность F-5 (и оригинала, и ремастера), поэтому мои треки в F-5 теперь воспроизводятся с ужасной производительностью. Я заменил F-5 в треке 200 F-5 на F-86, чтобы было легче переигрывать. В идеале его все равно необходимо воспроизвести в разрешении 1080 с метками и точками. disappearing F5 test 200, f5 replaced with sabre.trk

If I owned it I would check the FC4 F-5, incase that doesn't exhibit the same behavior. Might help narrow down the problem if it doesn't.

It's not just the remastered F-5, this track shows the problem consistently in the old F-5 as well. Track replayed with a locked 72fps with lots of overhead before the patch dropped yesterday. Now it will dip below 20, showing a hard sim thread bottleneck. If I edit the track and replace the F5 with any other jet, no problem. Also remains happening when you move to external view. disappearing F5 test 200.trk

I managed to get time to double check, my cores are unparked. So it's not that, at least not on my system (5800X3D).

Special K suggested this was due to core parking not being disabled. While I disabed core parking quite some time ago, a windows update looks to have reset some things. I will check back later to see if it's still disabled, and if disabling it resolves the performance loss.

It's not an exploit, it's literally an in-game setting. You wanted an option to have them off, you have that now. Enjoy it.