Topic on Talk:Sonic Adventure 2

This is mostly commenting on this edit and my edit after that.

So basically game was designed to run at solid 60 FPS, on consoles game would then slow down when too much stuff was happening instead of dropping frames. The way developer ensured this on PC was forcing vsync on, so with regular 60Hz monitor game would run that 60 FPS. This just means that vsync does indeed work, but they just though that every monitor is 60Hz so that they could use it as capping method. They left it at that, meaning that with over 60Hz monitors there will be speedup issues and some sort of cap has to be set in place, even if sonic is about the speed.

Easiest way to do this will be setting refresh rate to 60Hz, but this has some nasty negative impacts (which other high refresh rate owners may know about) which include visual things like flickering effect which gets really annoying as well as colors getting bit washed out (which is why I hate the games forcing refresh rate change), then not to mention that setting monitor to 60Hz every time before launching the game. It's still solution, yes, but far from perfect one and thus I feel like completely wiping note about frame rate capping and telling user to change monitors refresh rate instead isn't good. I made section about frame rate capping into frame rate article, but forgot to update it here. (If you meant games launcher option to set the game 60Hz, it simply doesn't work and always uses monitors refresh rate anyway.)

Now for Nvidia Inspector, when I tested the frame rate issues I was using mainly Dxtorys capping, but Nvidia Inspector worked absolutely fine and it's basically best solution for frame rate capping as it's automatic and game specific. Now I tested it again, I was using this profile as an test and it worked just fine, so I would like to see some more information that somehow Inspector would be the reason for the game to crash - or forced FXAA or other AA method.

However what I did notice was that any sort of in-game overlay would make the game flip over and crash on launch. Also that PC has hard time Alt+Tab ↹ as well as Alt+f4 not working at all. Rebooting the game after initial launch or setting hook delay made it launch just fine though.

I tried very similar settings to you and could only get the game to run if my monitor's resolution was actually at 60 FPS, in a window.

You can't change monitors resolution to 60 FPS, only to 60Hz and I haven't seen any game crash because of "incorrect" refresh rate. Even those games which tend to force 60Hz refresh rate in exclusive fullscreen mode work just fine when manually changing refresh rate back to 144Hz or forcing use of highest possible refresh rate from nvidia control panel - some games simply need 60 FPS capping after that.

But that's unrelated issue to the speedup issue. Speedup issue is fixed with 60 FPS cap of some sort and that's basically that. Changing refresh rate to 60Hz and letting vsync do it's job is one of the methods, so link to frame rate capping methods should stay there.

I would like to learn more about general crashing on games startup. As I said in first post, game crashed for me as well with dxtory enabled or if starting the game first time after reboot, so I would assume there's something other related to this issue than monitors refresh rate. Also looking at forums, tons of people are having problems like that and most say even windowed aren't helping. 13 pages on steam community alone, most of them saying windowed and borderless windowed helping a lot.

What I'm saying is that I'm fairly sure issues aren't tied into monitors refresh rate or nvidia inspector, but more to game in general, so instead of changing FPS notes, making it it's own seperate issue would be smarter. You did mention rivatuner, you sure you didn't use overlay and that would cause crashing instead? There was mention back in 2012 that game will crash with Dxtory as well if delay hook (delaying overlay inserting) wasn't used.

You can force any form of AA without issue with inspector. Just not FXAA

Using Inspector's Framerate limiter is also a VERY bad idea as it is very low quality and does not stablize frametimes at all.

You are better off just using inspector to force Vysnc instead with testing the amount of pre-rendered frames from 1-3. (As that CAN have an impact on frame time stability).

If you have a greater than 60hz monitor or a Gsync monitor. you are just better off setting your monitor to 60hz mode.

So first of all, game have forced on Vsync, because developers are using that as capping mechanism, so basically 60Hz monitors already work just fine. As you can imagine, over 60Hz makes frame rate then higher, like stated in the article. It's just that Thaumasurge edited that information to 60 FPS field for some reason. Maybe I should've just reverted those changes instead...

"you are just better off setting your monitor to 60hz mode."

You haven't seen image quality decrease in these things when set to 60Hz? Even if it is the best solution from gameplay standpoint, I would rather not have really washed out and bit flickering image with already bit washed out looking TN-panel. Also have tested that not only Nvidia Inspector works, but so does Dxtory, so limiting frame rate externally without changing refresh rate does work. To me, it just seems like game has really nitpicking way how it crashes for people for ridiculous reasons, some can't launch the game in fullscreen at all even with all the extra overlays and such disabled and seems like for some reason Thaumasurge came to conclusion that anything other than 60Hz refresh rate is unplayable, which isn't entirely true.

The game speed is tied to 60hz. Setting to 60hz mode is the best option IMO. If you have a VRR Monitor for example, then it shouldn't be much of a problem since it will be the same as being a 60hz native monitor.

Whether this still lets you use something like ULMB I don't know, I don't have a VRR Mon. Backlight strobing at 60hz doesn't bother me much though considering I still use a CRT television for old low res consoles and 480i consoles (Which flickers way more than 240p/480p60)

If DXtory works without any issues that don't crash the game. Then that's worth noting.

I think Nvidia's built in limiter in the drivers is utter shit. And I refuse to use it.

DXTory, I didn't like how it performed in the brief time that I used it.

There is also GeDoSaTo's limiter you can try!

Honestly feel free to make any edits you feel are necessary to inform people of other solutions as long as you don't remove other important information.

With setting 60Hz mode, you mean GPU panel? Because I only see options for using games value and highest possible, which in both cases use 144Hz for me. Setting desktop to 60Hz every single time when starting the game is just pita. Games own launcher gives only 60Hz values for some reason, but that doesn't change anything at all and game uses desktop refresh rate any way. If game did use 60Hz then this wouldn't be that big issue and merely minor complaing.

Also, no VRR monitors, bought the model before G-syncs and freesyncs were a thing.

Dxtory and nvidia have served me well enough even though they aren't perfect solutions. I did see GeDoSaTos update, that's why I added it in to FPS article, but haven't gotten around to test it. Blog post about how that thing works compared to other cappers was intriguing though.

Yes, by 60hz I mean via the GPU panel. Honestly it's no different than if you used custom resolutions AND DSR at the same time. Having to toggle between the two when needed. Which I do constantly. Which doesn't bother me at all.

If your Monitor doesn't list 60hz as a selectable RR, you may be able to create a custom resolution of your native at 60hz instead. (It might be worth trying to see if it supports it at all perhaps? It might or might not. Two of my PC 60hz monitors won't go below 50hz for example. )