Worked great for me. Ran art of rally at 120. It was at low settings but it all appeared to run well.
I was trying to find this yesterday. 😅. I hope i remember tonight
All of a sudden people now clamor BOE as the superior panel, lmao
All because a few highly upvoted posts had dead pixels lmao.
Yall gonna break ya shit
Does not work on Samsung oled, everything becomes completely garbled at 100hz (first I’ve tried). Any way to uninstall it? Thanks!
Just out of curiosity long as you don’t push frame limiter up it won’t push monitor harder yeah?
Looking forward to anything VRR related would be absolutely huge if its possible
I did change how 90Hz mode works slightly [I manually tuned all 80 modes from 40hz to 120Hz] so using this will push BOE OLED panel controllers slightly more at 90hz than stock would, but it should still be well within expected panel tolerances. I would not expect any harm to come from that.
Modes that will drive BOE panels at rates higher than stock: 46-48, 50, 53-54, 58, 60-63, 65-64, 68-69, 75-79, 82-83, 86, 89-120
All other modes will drive BOE panels at rates lower than stock.
For SDC, all modes from 45 through 90 will drive panel at stock rate, for 40-44 they’ll be lower than stock, 91-120 will be higher than stock.
For LCD decks, only 61-70 would push panel harder, but there’s very little risk comparatively there, especially given many, including myself, have run LCD decks at 70hz for extended periods without issue.
Speaking of my external LCD monitor, it’s an old one now. What I have observed about it is that even though it will accept and display higher refresh rates, it is actually dropping frames.
Not saying that is happening here, but further testing is required to confirm that frames are not being dropped.
In the case of embedded displays rather than external, dropping happens to be quite rare due to having increased directness of control of a panel. I have already confirmed that no dropping occurs on either my BOE OLED or LCD decks, but no clue about SDC OLED decks.
In external displays, there can be additional processing happening between receiving a signal and displaying an image, that would be where frame dropping most commonly occurs.
Heads up: maybe posting this at midnight in the US isn’t the best. I know other time zones exist but it seems most active when it’s day in the US. And something like this getting buried would be sad.
USA! USA! USA!
This is why people laugh at Americans.
Posting at a time in a place most active at a different time always carries more risk of being buried.
I’m American and I laugh at dumb shit like this. It’s amazing how entitled some of us are.
This wasn’t entitlement bruh, he was giving a suggestion to reduce it from getting buried.
Nah, assuming you are the center of the universe and expecting a non American to post when Americans are awake is peak entitlement.
Why would a post about the LE, a specifically American product, be best posted at a time where Europeans are awake and not Americans? Also even if it wasn’t about the LE, the united states and Canadian time zones make up over half of reddit users. Someone was just giving advice that might help someones post not get buried. There has been plenty of times useful posts get buried while shitposts are at the top of the subreddit.
Once again you are expecting a European to wake up in the middle of the night to make a post because you assume that Americans are the prime users here. Peak entitlement. There is plenty of activity on this sub at all times, if the post is worthy it will get up votes and it will be seen.
Making a post at the time most of your target audience will see it is called being smart.
While good to point out, morning in europe also tends to be fairly active and I feel that should stuff be genuinely cared about, there would not be that high of likelihood of getting buried even should things be posted during slower times.
someone remind me when Samsung panel is tested
I wouldn’t be touching something like this until Steam officially enables it.
There was a comment replying here saying something like “I wouldn’t touch this until steam officially enables it” and I had typed out a response only to get a message saying that comment was deleted when I went to actually post my response, so here’s that response anyway.
I mean, aside from that being very unlikely, it would be quite silly to think Valve would enable an overclock by default :p
They might fill in those missing refresh rate options though, somewhat hoping someone from Valve contacts me to help with that so I could contribute a pgp-signed commit into gamescope’s repository.
Regardless, anyone is free to inspect what changes I have made and/or compile things for themselves, https://git.spec.cat/Nyaaori/gamescope/commit/d39000aa9f53d1bd3c6fa993fdaeb6cc99ad4ae0
Hard part was manually tuning and testing timings for BOE panels over several hours, code part only took like 5-10 minutes.
Why lower limit is 40fps/hz when you can go to 30fps/30hz ?
So how do I know if my LE has a boe?
From everything I have heard, all LE decks have BOE panels. That being said, if you run
xrandr --verbose | grep MHzfrom desktop mode and the first [or only] value you see is close or equal to102.00MHzyou have a BOE panel but if you see a value close or equal to133.20MHzyou have an SDC panelAren’t those numbers backwards? On your git you state “BOE limit ~133Hz, SDC Bandwidth Limit ~100Hz” With the Deck resolution at ~1Mpix, that should be about the same in MHz?
SDC at 90Hz uses ~133MHz of bandwidth while BOE at 90Hz uses ~102MHz of bandwidth; Valve’s MIPI converter seems to begin struggling at roughly ~147-148MHz which is where those numbers come from.
I do not know if SDC can be made to use narrower timings to reduce bandwidth usage or not, and given I currently only have a BOE deck I can not currently test for that.
Since I don’t know a whole lot about timing signals, if the BOE is using less bandwidth, does it somehow have a lesser picture quality? If the quality is the same, why would the SDC panel require more bandwidth to display the exact same picture?
Signal padding, there happen to be empty/blank pixels sent which make things easier for display controllers when detecting timings, historically those blank pixels were there to give time for CRT electron beams to move to where the next line or frame began.
For BOE panels at 90hz, they receive frames which happen to be 858x1320 pixels in size, with an active area of 800x1280, while SDC panels use frames which are 1128x1312 in size, also with an 800x1280 active area.
So…
for BOE: 858x1320x90 = 101930400; ie a clock of ~101.93MHz; though in reality the panel runs at 102mhz so has a refresh rate of ~90.0615Hz.
and for SDC: 1128x1312x90 = 133194240; so a clock of 133.194mhz; but they run at 133.200MHz instead which gives a refresh rate of ~90.004Hz
Reducing how large of a padding area gets sent may be possible, but without having an SDC panel deck myself I’m not able to test to which degree, if any, that would be possible.
Thanks for the detailed answer, that makes more sense! So it all comes down to the controller and how much padding it needs to make sure it has the right pixels in the right area of the screen. Depending on the speed/sensitivity of the controller, it determines how much extra padding or bandwidth is used to make the same picture. That makes sense on a CRT due to the physical limitation of an electron gun only being able to move so fast. I’m surprised that some modern day controller chips would need so much extra padding!
By the amount of dead pixels. Badum psh. I’m here all evening.
hello when i enable 120 hz with a BOE panel the contrast gets boosted very high and looks washed out.
How do I uninstall this script to be safe ? Thanks - Hank
On OLED panels, gamma curves relate directly to how long pixels are driven, so when you increase refresh rate you end up with reduced resolution in darker colours.
I left removal instructions in another comment here, but if you do not use the higher values than your panel will not be driven at those higher values. Gamma curves being off should not in of itself cause issues for the display.
I’m going to be real salty if it turns out that only the BOE panel on the LE deck is the one that can do 120hz, which of course sold out officially this morning…
I do not have a deck with a Samsung panel currently so unfortunately I can not perform manual timing tuning like I was able to do with a BOE panel deck (which was quite annoying to get given they only shipped LE ones to US&Canada, luckily I had access to an old secondary steam account and could order from that, got kinda worried with shipping but despite the box being a bit wet given it was left out in the rain briefly, everything turned out okay)
If I do end up receiving enough donations to buy a second OLED deck than I intend on ordering one so that I can hand-tune Samsung panel timings. Without one though, it looks like SDC decks will be limited to ~98hz for now.
I will likely update my code to handle SDC and BOE decks separately to avoid enabling modes SDC decks can not function at.
is 70hz on the LCD noticeable? or waste of battery?
I think the most notable change is being able to set a 35fps limit on 70hz refresh rate on games that you cannot quite sustain 40.
Also classic Doom! That always ran at 35FPS at 70Hz, so if you’re a purist who doesn’t wanna use a modern engine that runs at 60 (like if you’re using Chocolate Doom like I usually do), then it’s great for that to avoid judder
that is a pretty good feature I didn’t realize that
Depends. If you’re playing a FPS and can do higher than 60 fps as a minimum rate in the game, then running at 70 Hz could give you 10 extra fps.
For a visual novel, a waste.
At 60Hz, each frame is shown for ~16ms, while at 70Hz each frame gets displayed for ~14ms.
2ms is not nothing… But it’s below the treshold for human perception. While LCD screens have a little bit of a blur as the time for each subpixel to transition is somewhat long, the change from 60Hz to 70Hz amounts to nothing but a placebo.
But it’s below the treshold for human perception
Not exactly true, depending on which sense and , humans can perceive differences down to amounts quite small, even tiny values like 5-10 microseconds for hearing frequencies are noticeable.
For input-visual response time, differences down 0.5-1 milliseconds can be perceived by those sensitive to it and/or trained for it, 2 milliseconds happens to be well above that, though on average 4-6 milliseconds would be an expected threshold without knowing what to expect.
When using gyro-to-mouse input, difference between 60 and 70hz is perceivable, though a small change and not immediately noticeable, often it would be to enough to throw off my inputs for timing-sensitive things should I forget about increasing refresh rate.
Motion inputs often have significantly higher sensitivity to response time variation, adding say, 2msec extra latency into a VR headset and you would be far likelier to end up feeling nauseous after/during use.
109HZ seems to be the spot where the colors/gamma dont get shot up. Anything past that it gets brighter and you lose color.