[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/vr/ - Retro Games

Search:


View post   

>> No.9888084 [View]
File: 485 KB, 1392x484, durrrr.png [View same] [iqdb] [saucenao] [google]
9888084

ooookay
custom resolutions lesgooo
AMD's own driver application sucks. It sucks. No. I don't wanna hear otherwise, what the fuck is this barbarism CCP wuz better and it pales in comparison to NVCPL zoomers begone.

The custom resolutions not having a limit's pretty neat tho (or I've not reached it yet), and I'm not sure how it's doing it but it's nice to not have to use CRU but I've found that using it gives me different results even when using CVT for timing in the auto calculator and sometimes the results are less favourable.

So I'm guessing the best way's gonna be use CRU as a calculator for temporary resolutions etc and then punch the numbers into the AMD drivers to get it to work.
I can see some of the obvious stuff and where it goes like the sync width/front porch. The H. timing and V timing I'm guessing come from the total column but the blanking & back porch I'm not sure about and if I'd get those numbers from back porch/blanking or if I need to use another calculator for this instead?
CRU's been great for getting me as close to 30kHz as possible for some stuff and pushing the higher limits but the detailed resolutions being limited to 4 has been hurting.

Is there a better way to use both of these that I'm missing?
I'm used to using CRU with flat panel technology for weird refresh rates more than I am this stuff so sorry for being shit at it.

Navigation
View posts[+24][+48][+96]