MiSTer FPGA Forum

Hey guys! New to Mister!
I've been racking my brain for days trying to figure out my issue....
I have an analog I/O board with a VGA->Component cable connected to my Toshiba 20AF41 CRT
Most cores, such as NeoGeo, N64 output display perfectly via HDMI to my LCD and to my CRT
However, certain cores like MisterLaggy and Genesis do not work. Once the core is loaded, the CRT screen goes black and there's no video/audio; the LCD is still displaying the image.
Stranger yet, when I load the Master System core, there are no issues?!?!?!?!
I have tried modifying my .ini settings but to no avail
Current .ini settings I believe are relevant to this:

ypbpr=1
composite_sync=0
vga_scaler=0
vga_sog=1
direct_video=0
forced_scandoubler=0

Note that if I set vga_scaler=1 in my settings, the display on my CRT is garbled and unreadable in the Mister menu but does appear once a core is loaded. I have tried messing with my .ini settings for [Menu] but that has not helped.

I also cannot view the terminal screen when trying to edit my ini settings through the script. I get a message that says:
"If you see this , then you need to modify Mister.ini
Either disable framebuffer: fb_terminal=0
or enable scaler on VGA:
vga_scaler = 1"

Doing this does not help in fact when I disable fb_terminal I can no longer run the script to modify the ini

I am wondering if my TV is the issue????

Appreciate you taking the time to read and respond to my post.

Just a quick update, seems Genesis core and only a few of the Utility cores are doing this (no image)
Everything else seems to work fine
I tried modifying my ini settings but nothing worked.

It's possible that not all Utility cores are not made to work with CRTs or that maybe they have the same problem as the terminal. Genesis and the terminal should definitely work on a CRT.

Since you have already messed with your mister.ini (and maybe it's an old version anyway), best get a fresh one from here and then change "vga_mode=rgb" to "vga_mode=ypbpr", and possibly "vga_sog=0" to "1".

Guys, I figured it out with help from some other members.

The cores that aren't working aren't updated for the 24-bit I/O board.