SharpeXB

Check out the Downloads / User Files section on the DCS website. That will have what you’re looking for.

With a 144Hz Gsync monitor you should set the Frame Limiter in DCS to off (all the way to the right) then in Nvidia CP set a frame limit of 144Hz to match your screen or perhaps 2-3 fps lower if you still see tearing. Turn Vsync off in DCS and NCP.

I’m not sure how that helps the problem above. It’s inevitable that there will be distortion at extremely wide FOVs. Such as with a 32:9 screen.

Yes! It’s annoying to zoom out and get that fish-eyed effect. It would be great to be able to just set a limit for that.

The zoom view feature in the game is functioning as intended. I can’t quite understand what you’re suggesting.

There is. Set the zoom as you like and then press Atl+Num0. You need Snap View Saving enabled in the options. Then the “zoom normal” command will reset this FOV

I don’t think that will be achieved… if the dots were so small you can’t notice them then what’s the point? If the dot is bigger than the aircraft model it will be too big and hide it. If the dot is smaller than the aircraft model there’s no point in using it. See there’s no way to win except get rid of the idea altogether.

But VR users often use supersampling, not the native setting. Monitor users tend not to although that’s possible as well. If the dots are only sized for the native resolution that’s problematic. It also leaves the possibility of exploiting the system by just lowering the input resolution. The accounts from VR users seem to indicate that changing pixel density settings affects the dot sizes. If this system was done correctly I don’t think that should happen. Making a “per HMD” configuration makes as little sense as trying to create a “per monitor” one. What’s needed is a “per resolution” system. Honestly I don’t think the whole idea makes any sense but it’s also not being implemented well either.

I’m curious what “headset specific” settings means since all HMDs can have different resolutions based on the pixel density setting. And I believe is usually set outside DCS so how would the game know how to adjust this?

If the game is trying to keep the dots the same size independent of resolution then the 4K dot would need to be 4x the pixels of the 1080p dot. Now I don’t think the whole idea makes sense at all, just pointing out what it would need to do if that’s the goal. Yes, the model will be visible and smaller than the dot and a 1 pixel 1080p dot is gigantic so it obscures the 3D model. And the system shouldn’t be exploitable by lowering the resolution. Which it appears to be now. I think v2.8 used a single pixel in 4K which was effectively invisible. Selecting Spotting Dots Off (which enables v2.8) basically removes the dots in 4K. The more you try to analyze this the more you realize how little sense it makes.

I think high quality voiceovers are a given for DLC campaigns regardless of what DCS core can do. Yeah this is a bug at the moment. But if it was working I think hardly anyone would use it or pay attention to it regardless.

I thought this new solution was supposed to be resolution agnostic. As such I suppose it would indeed have to use the selected resolution (ie supersampling) and not the native res on either an HMD or screen. So in simplistic terms if you select 1080x1920 in the game you get a 1 pixel dot and of you select 3840x2160 you get a 4 pixel dot (never mind that both those examples are too large) If it’s possible to change the dot sizes by simply selecting different resolutions then the exploit is open to just lower resolution and see bigger dots. I thought the whole idea was to get rid of that since this was the problem with v2.8. The problem with this too is I think such resolutions can be set outside the game and so DCS isn’t going to know how to scale the dots. And it’s still going to be possible to hack or exploit the system.

I feel like any improvement to ATC would only really be appreciated in the context of a dynamic campaign so getting this before that seems premature. I can’t fathom MP gamers actually using authentic ATC procedures and the DLC campaigns already have this. It’s only something I imagine being used in the core SP game modes, again like a dynamic campaign if there was one.

There will always be negative feedback. You can’t please everyone. And they do actually listen.

This issue has nothing to do with “spaghetti code” or what any other games do.

If you’ve heard the expression “Perfect is the enemy of good enough” I think that may entirely be the case here. This has been built up in the minds of the players to such a degree I fear they’ll never feel it’s good enough. I’d settle for a good enough DC now rather than a perfect one in five more years.

Seeing this on Syria link to track file: https://www.dropbox.com/scl/fi/4tpegtniz6nfern0l8i86/SPS-Contention-Syria-20241112-163504.zip?rlkey=zwkz1pg2jthu3qfnzkzjx8a6x&st=7yz3m1ga&dl=0

I don’t think this can ever be resolved for VR because aparently it’s affected by the pixel density setting and not just the native resolution of the HMD. So there are infinite variables to account for and trying to tailor this to each headset is futile. People with the same headsets either can’t see the dots or claim they’re too large. At least monitor users can’t just turn these off but then you’ll be at a disadvantage online. The whole idea is a gigantic mess and should just be scrapped IMO.

That’s a funny thing to say. It’s not a matter of luck whether or not your hardware functions correctly.

Sure there is. DCS is open to modding. There is a user files section for these on the official website and a forum section. You’re confusing unofficial mods with licensed third party content. And DCS has a great amount of that. Besides this difficulty the chief reason people avoid unofficial mods is the problems they can create. Having easy access to these doesn’t solve that issue. Most players aren’t going to want to use these no matter how easy the access is.

You don’t seem to understand anything about unofficial mods in DCS. Again the fact that they’re made without the SDK or the ability to test them with a preview build of the game or any internal testing by ED meant they’re inherently problematic. Even if they might seem worthwhile superficially, they have the potential to cause all sorts of bugs and problems. This is why very few servers use them.

You keep missing the point that unofficial mods cause problems in DCS because they’re not tested. Most people aren’t going to want to use them no matter what the “benefit” might be. And that’s why very few severs would ask players to download them. They’re just going to screw up your game and cause you a big headache.

I think you are missing the fact that DCS unofficial mods are unofficial. They aren’t tested with the game builds nor created with use of the SDK. Bottom line they can cause a lot of problems and are best avoided if you want the game to run well. Hardly anyone would want these downloaded into their game automatically. And very few servers use unofficial mods.

Huh? We do not want servers automatically installing unofficial mods onto our machines! These cause a lot of trouble in DCS

If the pixel density setting affects the dot size then the whole idea of trying to make these equal across headsets seems like sheer folly. There is such a variety of possible resolutions and HMDs