@Mrakobijes said in trying to use KMS driver yields no composite video output (Raspberry Pi 4):

dtoverlay-vc4-kms-v3d-pi4,composite=1

This looks like a mis-spelling, it should be just:

dtoverlay=vc4-kms-v3d,composite=1

and you should start with stock config.txt, instead of the one you're using, which has too many overclocking options which may conflict.

Note that this configuration is not fully supported by RetroPie yet and for the KMS driver is recommended to use an up-to-date Linux kernel/firmware.

You

The font in the message blurb is not set by theme, it's the default EmulationStation font - the size is not configurable.
It would be nice if the size would be bumped on smaller resolutions, could be a nice addition.

@dankcushions

can you give an example? fmv in PS1 games used pretty brutal compression. it's typical to see constant ugly colour banding on real hardware.

Not an FMV, but I believe it's a 24-bit color scene. Comparison between a screenshot and the screen. Some of the grays in the photo aren't completely gray.
SLUS-00922_2022-02-02_14-28-04.png
IMG_20220202_153105.jpg

what did you add?

I used hvs_set_dither=0x210

@mitu , correct. The script makes all the calculations and applies then with tvservice. My apologies about some misspelled words, english is not my native language. Feel free to make some correctins if you want.

Unfortunely, I don't own the Pi 4. I would like make the scripts also compatible with that model as well. But unfortunely this kind of eletronic, lastely, has become more and more expensive here in Brazil.

@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.