@mitu
Ok. All clear now. Thanks for the clarification.
I'm not a dev guy, so it's beyond my knowledge to modify the source code. I guess I have to prepare two set of config.txt, and reboot into the proper video mode when needed.

@sharkytowers Your issue is not related to this topic.
For RetroArch Windows issues you'd better ask in the libretro forums - forums.libretro.com, which seem to be down at the moment - or on their Reddit forum over at reddit.com/r/retroarch.

You can try with a different hdmi_group/hdmi_mode until you find one that works (240p modes maybe ?).

To anyone having the same issue, I needed to cut the HSYNC trace on the vga666 board for the csync to be strong enough to control the PVM

@dankcushions

Ah sorry missed read that - that makes more sense - ok good so it is doing nearest neighbour!

Updates!

I have gotten somewhat of a picture to have display (IGNORE THE MESS 🤣)

https://i.imgur.com/uCDczXZ.jpeg

This was achieved using the following modelines in the config.txt

hdmi_ignore_edid=0xa5000080 config_hdmi_boost=4 hdmi_group=2 hdmi_mode=87 hdmi_force_mode=1 hdmi_timings=1024 0 48 104 152 768 0 3 4 23 0 0 0 60 0 88509090 1

It's still obviously very distorted but what is odd that the pixel clock I'm using, 88.5MHz was the only way to get some semblance of an image. However according to the manual for my display it should be a pixel clock of 64MHz for 1024x768 60hz (resolution I'm using rn) and a pixel clock of 108.18MHz for 1280x1024 60hz

Any reason why the pixel clock is so off? Is my code still wrong? Ultimately I think this will boil down into me opening up the CRT and messing with the sync pots but I'd like to avoid that if possible.

Any further guidance or help is greatly appreciated 😄.

@mahoneyt944 said in Retropie video output to G07 Electrohome crt:

Is there a way to set rgb manually or change palettes? G07 is considered standard res /low res monitor.

Not sure if there's such a thing as a 'palette' for an analog signal, but no, have no idea. You may want to ask in the raspberrypi.org/forum forum and provide some pictures.

Righto, here's the solution for everyone who wants to let RetroPie handle NTSC/ NTSC progressive modes but then switch to the PAL60 equivalent:
Put this into runcommand-onstart.sh:

(sleep 15 && sudo /home/pi/tweakvec/tweakvec.py --preset PAL60) &

If it doesn't work for your Pi, try sleeping a bit longer. On my Pi3, 15 seconds seems like the sweet spot.

@solidshook not an expert, my understanding is that tvservice is used heavily in CRT guides/scripts, and this is only partially functional on pi4, since it is a call to the fkms firmware layer that is being depreciated.

raspberry pi are instead moving to the open source driver stack, which aims to be a more standard KMS offering, where the way to use custom modes is via DRM modesetting or xandr, the latter of which relies on X which retropie doesn't use by default, and i believe the former might not have enough flexibility.

still, an approach should be possible, with some work.

@jedcooper Sorry, never got around to fixing it. My menu widgets are already disabled, but the issue persists. I'm assuming that it's a similar issue to the one people are reporting with widgets, but not sure what more to do with that information unfortunately.

My other approach.. has been to emulate SNES on my Wii, haha. For an unrelated matter, I'm getting a VGA666 board in the mail some time. I don't expect that it will make a difference with this particular issue, but I'll give it a try anyway and report back if it makes a difference.

Besides the pictures and the seller's page, there's no much info about VGA666RGBs. They say it's compatible with Raspbian/RetroPie/etc., so I assume it works similarly to other GPIO analog video add-ons, using the standard vga666 'driver'.

For RGP-Pi, I remember it outputs RGB via Scart, so it might not be the first choice if your monitor has no Scart inputs. Not sure about the driver, though.

@busywait Thanks for that, I added "composite=1" to the "dtoverlay" line in config.txt, and it has had some change, but the screen is still blank.

Now when I run modetest, the connector "composite-1" shows up, but its status is "unknown", and it has no associated encoder id.

The list of encoders has also changed to include TVDAC, but it has a crtc of 0.

TBH I'm not sure how connector, encoder, and crtc interrelate, and/or whether it's possible to fix the relations (assuming that's all the problem is).

@buzz I've tried this before, but I've tried again just now, to make sure.

overscan_top=40 overscan_bottom=40 overscan_left=40 overscan_right=40 overscan_scale=0

While this does add the overscan on the console, it also adds it to EmulationStation and RetroArch while emulating.

Probably yes, but you could ask the author of the RetroPie CRT Ed. for confirmation to know which systems it supports.

@planetdune Does the TV have a front RCA video input ? Try that and see if the signal works. Also, check to the /boot/config.txt has enable_tvout=1 added (should have been added by raspi-config).