Custom Resolution Utility (CRU)

[ToastyX]

(12-05-2024 05:07 PM)lyndonguitar Wrote:  Hello, I am trying to create a shortcut for CRU's restart64.exe via Stream Deck. It works good, but for the prompt window that appears after "Graphics Driver Restarted, Restart Again, Recovery Mode, F8), can it be disabled? is there a command prompt switch perhaps to be made on a bat file so it won't appear?

It's in the first post:

(09-07-2012 09:06 PM)ToastyX Wrote:  

• restart.exe/restart64.exe:
  • /q - Restart without prompting (or rename the file to restart-only.exe)
  • /r - Activate recovery mode without prompting
    

[korisnik2007a]

(12-05-2024 10:09 PM)ToastyX Wrote:  

(12-05-2024 09:13 PM)korisnik2007a Wrote:  However, when I use CRU to make any kind of adjustments to my settings, and I try to reboot my pc my screen goes blank and the system is not responsive, I have to restart it.

I have noticed that if I physically unplug my second display (the HDMI HP one), the problem goes away and everything works fine. I've tried different driver versions (newer ones), and they all acted the same.

It's an NVIDIA driver bug. Their driver is hanging on boot when an EDID override is present with multiple displays connected, but it doesn't always happen. You should report the issue to NVIDIA.

Thank you for replying! I'll try to report it to them. Once again thanks for the app!

[LoveTilapia]

Hello friends,

I am trying to test if my cable is good quality. I am on an AMD 7900xt. If I set CRU to the following settings, will this properly disable DSC and run the full 3840x2160 144hz 10bit @ 40gigabit to my display? Is there some way to check if DSC is running on AMD ?

I know my display can handle the 48gbit on hdmi 2.1.

[ToastyX]

(12-11-2024 02:31 AM)LoveTilapia Wrote:  Hello friends,

I am trying to test if my cable is good quality. I am on an AMD 7900xt. If I set CRU to the following settings, will this properly disable DSC and run the full 3840x2160 144hz 10bit @ 40gigabit to my display? Is there some way to check if DSC is running on AMD ?

I know my display can handle the 48gbit on hdmi 2.1.

Delete the max chunk total as well. That should disable DSC, but I don't know how AMD handles DSC since I don't have the hardware myself. I don't know a way to get the DSC status either.

[LoveTilapia]

(Yesterday 12:55 AM)ToastyX Wrote:  Delete the max chunk total as well. That should disable DSC, but I don't know how AMD handles DSC since I don't have the hardware myself. I don't know a way to get the DSC status either.

Thanks ToastyX

How do people normally check for DSC?

[Vikto0r]

Dear forum users.
My question is, is there any way to give the exact frequency with cru?
Example (2 pc stream setup with capture card. Passthrough .) :

-240hz gamer monitor almost 240hz cru exact using https://ibb.co/9ZKCPdq
-60hz stream pc : 59.997601hz --> exact using cru. with other options 60.000360 etc. never accurate

I want 240.000000 and 60.000000hz, is this possible?

Why?
When streaming. when recording. there is periodic choppy stutter in the recording and in the stream too. in my opinion, my guess is that the hz differences cause this.

important: note. obs 60fps, game 60 fps . no dropped frames or overload. checked

Thanks in advance:
I would be grateful if you could help me with this, I have been suffering with this for years and have already gone through a million tests and settings

[ToastyX]

(Yesterday 11:57 AM)Vikto0r Wrote:  Dear forum users.
My question is, is there any way to give the exact frequency with cru?
Example (2 pc stream setup with capture card. Passthrough .) :

-240hz gamer monitor almost 240hz cru exact using https://ibb.co/9ZKCPdq
-60hz stream pc : 59.997601hz --> exact using cru. with other options 60.000360 etc. never accurate

I want 240.000000 and 60.000000hz, is this possible?

Why?
When streaming. when recording. there is periodic choppy stutter in the recording and in the stream too. in my opinion, my guess is that the hz differences cause this.

important: note. obs 60fps, game 60 fps . no dropped frames or overload. checked

Thanks in advance:
I would be grateful if you could help me with this, I have been suffering with this for years and have already gone through a million tests and settings

"Exact" is mathematically exact, but hardware timing and measurements may not be. That wouldn't solve your problem anyway. The monitor's refresh rate is different from the game's frame rate which is different from the recording's frame rate. Even if the monitor's refresh rate were exact, how can you guarantee the game's frame rate and the recording's frame rate are also exact? Even that's not enough because they all have to be perfectly synchronized with when the GPU has a new frame ready, not just have the same rate.

If you are using vsync, that alone can cause stutter if the game's frame rate is also capped to the monitor's refresh rate. Vsync should be used without frame rate caps since it already acts as a frame rate cap, but that might not be possible for games that only support 60 FPS. If you are using G-SYNC, that will synchronize the monitor's refresh rate to the game's frame rate, but the game might have fluctuations that would mess up the timing. That's just for synchronizing the monitor's refresh rate with the game's frame rate. The recording would also have to be perfectly synchronized to avoid stutter, and the video player would also have to be perfectly synchronized to play it smoothly. There's just too much that has to go right for this to work perfectly, and I'm not sure it's possible unless the recording software has some way to synchronize perfectly with the monitor.

If you want to reduce stutter, the best way is to not try to synchronize everything. Run your monitor at the highest refresh rate (240 Hz I assume) and avoid vsync, but you can use G-SYNC. Cap the game's frame rate to something higher than the recording's frame rate, like 90 FPS. If you want to use vsync instead, then you'd need to use a refresh rate like 90 Hz instead of using a frame rate cap. Those options wouldn't be as smooth as a perfectly synchronized recording, but that would avoid the periodic stutter you're seeing, except for games that are stuck at 60 FPS. In that case, maybe recording at 50 FPS would help.

[ToastyX]

(Yesterday 05:49 AM)LoveTilapia Wrote:  How do people normally check for DSC?

They don't unless the monitor has a way to report if DSC is active.

[Vikto0r]

(Yesterday 04:20 PM)ToastyX Wrote:  

(Yesterday 11:57 AM)Vikto0r Wrote:  Dear forum users.
My question is, is there any way to give the exact frequency with cru?
Example (2 pc stream setup with capture card. Passthrough .) :

-240hz gamer monitor almost 240hz cru exact using https://ibb.co/9ZKCPdq
-60hz stream pc : 59.997601hz --> exact using cru. with other options 60.000360 etc. never accurate

I want 240.000000 and 60.000000hz, is this possible?

Why?
When streaming. when recording. there is periodic choppy stutter in the recording and in the stream too. in my opinion, my guess is that the hz differences cause this.

important: note. obs 60fps, game 60 fps . no dropped frames or overload. checked

Thanks in advance:
I would be grateful if you could help me with this, I have been suffering with this for years and have already gone through a million tests and settings

"Exact" is mathematically exact, but hardware timing and measurements may not be. That wouldn't solve your problem anyway. The monitor's refresh rate is different from the game's frame rate which is different from the recording's frame rate. Even if the monitor's refresh rate were exact, how can you guarantee the game's frame rate and the recording's frame rate are also exact? Even that's not enough because they all have to be perfectly synchronized with when the GPU has a new frame ready, not just have the same rate.

If you are using vsync, that alone can cause stutter if the game's frame rate is also capped to the monitor's refresh rate. Vsync should be used without frame rate caps since it already acts as a frame rate cap, but that might not be possible for games that only support 60 FPS. If you are using G-SYNC, that will synchronize the monitor's refresh rate to the game's frame rate, but the game might have fluctuations that would mess up the timing. That's just for synchronizing the monitor's refresh rate with the game's frame rate. The recording would also have to be perfectly synchronized to avoid stutter, and the video player would also have to be perfectly synchronized to play it smoothly. There's just too much that has to go right for this to work perfectly, and I'm not sure it's possible unless the recording software has some way to synchronize perfectly with the monitor.

If you want to reduce stutter, the best way is to not try to synchronize everything. Run your monitor at the highest refresh rate (240 Hz I assume) and avoid vsync, but you can use G-SYNC. Cap the game's frame rate to something higher than the recording's frame rate, like 90 FPS. If you want to use vsync instead, then you'd need to use a refresh rate like 90 Hz instead of using a frame rate cap. Those options wouldn't be as smooth as a perfectly synchronized recording, but that would avoid the periodic stutter you're seeing, except for games that are stuck at 60 FPS. In that case, maybe recording at 50 FPS would help.

Dear ToastyX.
Thank you for an honorable and meaningful answer. I will consider what you have written.

[LoveTilapia]

I am pretty sure those clock gens are affected by temperature as well. So they might cycle a little faster or slower after it warms up.

---

(Yesterday 04:21 PM)ToastyX Wrote:  

(Yesterday 05:49 AM)LoveTilapia Wrote:  How do people normally check for DSC?

They don't unless the monitor has a way to report if DSC is active.

Thanks for the help ToastyX, Damn this DSC world we live in.