Well it works, but I don't like it...

[Old Duck]

I tried the trick of unlocking framerate to speed up POI scans in the FSS, and it does speed it up. It's still a bit slow, but nowhere near as bad as when FPS is locked to monitor refresh.

However, I really, strongly dislike the screen tearing and stuttering artifacts this creates. I'll take a locked 60 fps VSync-on over 200+ fps VSync-off any day. Not only does it look WAY better to me, it also uses a lot less power! Obviously I don't have a FreeSync monitor, otherwise I'd not be complaining about tearing. The one silver lining is that I tend to spend more time in FSS when exploring in this way than I do looking out my window (queue ADS vs FSS debate), and I care a bit less about screen tearing inside the FSS. If I find something extra appealing that I want to visit and see, I can pop out and enable VSync before setting off.

If nothing else, this seems to prove that POIs can be resolved way quicker if the code that does so is moved off the main thread. So Frontier, why haven't you done this yet?

 

[Jethro49]

Thanks for bringing back this old bug into the light... That one is really annoying : scanning volcanic bodies is as funny as watching grass growing.

I hope we can get a solution soon (note the contradiction between "hope" and "soon", in the context of bug solving).

 

[Stigbob]

This seems to confirm the issue is caused by you messing with the settings.

 

[Riverside]

This seems to confirm the issue is caused by you messing with the settings.

Best way to learn

 

[Old Duck]

What are you people on about?

 

[Stigbob]

What are you people on about?

I was implying it was pebcak in a tongue in cheek way.

Try dropping everything to the pre-set that works best then increasing one setting at a time to identity the one(s) that don't agree with your system.

Takes ages but works.

 

[photomankc]

This seems to confirm the issue is caused by you messing with the settings.

What?

 

[photomankc]

I was implying it was pebcak in a tongue in cheek way.

Try dropping everything to the pre-set that works best then increasing one setting at a time to identity the one(s) that don't agree with your system.

Takes ages but works.

It’s not a thread about screen tearing. It’s the long delay in getting FSS results for volcanic systems being a product of screen update rate.

That issue is not caused by our settings.

 

[Stigbob]

What?

How ?.

 

[nosleepdemon]

If nothing else, this seems to prove that POIs can be resolved way quicker if the code that does so is moved off the main thread. So Frontier, why haven't you done this yet?

Jolly good sir, we'll get right on that! One extra special thread coming up just for you, sir. Ah, there we are, almost ready! Tell me sir, while we wait for the handle, do you know a great deal about spinning up threads willy-nilly and the challenges of designing asynchronous software?

 

[Old Duck]

Tell me sir, while we wait for the handle, do you know a great deal about spinning up threads willy-nilly and the challenges of designing asynchronous software?

Actually, yes. But if you think it's too difficult, there's always Plan B, where Frontier displays the existence of POIs (which is likely a variable set on the server) rather than the procedural-generated count of POIs, the latter being the computationally-demanding cause of the very long scanning delays.

 

[photomankc]

How ?.

That's a good question. "How" has he caused the FSS Geological POI delay by messing with his settings?

 

[Old Duck]

No no, I fixed the POI delay by messing with my settings. I caused the POI delay by fixing my settings. It's the inverse of what I want.

 

[Morbad]

However, I really, strongly dislike the screen tearing and stuttering artifacts this creates.

Turn off vsync in game and enable fast sync in the NVIDIA control panel.

 

[Old Duck]

Turn off vsync in game and enable fast sync in the NVIDIA control panel.

Doesn't this require my LCD to support it?

 

[Morbad]

I agree. Removing framerate limiter (or the most obvious and straightforward v-sync) is a very bad idea, in many regards. One of the unwanted side-effects will be the heat increase of your video card. Who wants that, just for "fixing" a trivial bug?

There are advantages to uncapped frame rates as well, even well in excess of display refresh rate, namely with regard to input latency.

Doesn't this require my LCD to support it?

No, but if your display supports it, you should enable G-SYNC as well.

Fast sync is just vsync with an uncapped internal frame rate, where the driver selects the most recent frame to send to the display on it's vertical refresh. There will be no tearing and nearly uncapped fps.

 

[Old Duck]

No, but if your display supports it, you should enable G-SYNC as well.

There's no option for Fast Sync - only On, Off, Application Controlled. I guess my hardware doesn't support such fancy things.

 

[Old Duck]

Also, why do I have to jump through 20 hoops to fix something that should not be an issue in the first place? You PC gamers have been abused for so long that you can't even recognize it. On console, it works or it don't, and if it don't, you give the company what-for until it does. Unless that company is Frontier, then you spend silly money for a PC and it still doesn't work...

 

[Riverside]

There's no option for Fast Sync - only On, Off, Application Controlled. I guess my hardware doesn't support such fancy things.

There is more you can do with a PC (compared to a console) but there is more you have to do too. Make sure you have the latest drivers, the option for 'vertical sync' in the Nvidia Control Panel gives 'on', 'off' and 'fast' options. Personally mine is off, but I don't suffer from the issues you describe.

 

[Morbad]

There's no option for Fast Sync - only On, Off, Application Controlled. I guess my hardware doesn't support such fancy things.

Fast sync should be supported on any Maxwell or newer NVIDIA GPU. Your 1660 Ti is certainly compatible.

What driver version are you using? Did you get it from Windows Update?