CRTswitchres doesn't work on CRT TV Windows 10
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Use CRTswitchres on 15khz TV with a standard VGA to component transcoder on windows 10. I'm using a gtx 980 with DVI-I to a VGA transcoder going to the CRT TV. Sending a a custom resolution of 2560x240 through the VGA transcoder produces working CRT video with this set up
Expected behavior
TV screen should change to a super resolution mode based on the requested core resolution; ie 2560x240 for 240p.
Actual behavior
Insanity; either it doesn't sync, or it doesn't go scale to the screen properly, or go on the correct screen, etc, switch res is so broken that it's hard to reproduce consistent behavior with it. which is well attested by others in the CRT gaming community. Behavior will often change between reboots. The most common recommendation is the use a custom, single video mode per core with a switchres.ini but that often encounters the same issues.
Steps to reproduce the bugs
Set up retroarch for 240p with RGUI, 2560 super resolution
Boot retroarch. It won't go to the correct screen even if you tell it to, so use win+shift to move it over to your CRT
This is most often where it fails, usually logic fails to get you a working output in favor of voodoo magic. I genuinely have no clue what the right settings for view ports could even be because nothing works consistently; settings that work this time break on the next boot. Not touching view ports also prevents the screen from filling the CRT TV correctly.
Then, if you hit the full screen button enough you might get a picture, usually it freaks out a few times first.
Try to play an SNES game, there's a good chance, if retroarch doesn't crash, that the picture won't scale correctly, or will stop scaling correctly, or go out off sync, or get squished into the middle...
This and more has been happening with all retroarch versions I've ever used since 2022.
I'm taking a break for now because there's tons more broken behavior to describe. I plan to document everything I encounter them; I hope I don't have to say that from an accuracy standpoint, not being able to output to CRT TV is genuinely awful, critical issue; it shocks me switchres is in this- utterly unusable- state.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the CRTswitchres behavior on Windows 10 with the stated GTX 980, DVI-I-to-VGA transcoder, 15 kHz CRT, 2560x240 output, RGUI, and switchres.ini setup. Narrow the inconsistent failure to a specific screen-selection, synchronization, scaling, or mode-switching case, then define a reproducible expected result before investigating a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100