Thanks for the help guys. I'm not using Retropie at the moment, I'm using Mupen64plus-next on Lakka. My old Pi3B+/Retropie setup wasn't overclocked so I didn't use N64 much. Mariokart 64 and Rouge Squadron are my go to games for trying to judge resolution. Rogue Squadron has been covered and Mariokart has slight graphical glitches in anything above 320x2xx which leads me to think that it ran in low res.

@KN4THX Thanks to you, too. Most (all?) Linux graphical desktop environments can output their screen on multiple outputs with different resolutions. With the oldest and (still) most common X.org display server, this can be done in shell scripts by the xrandr tool*. But Retropie comes without X.org or similar display server, and I also remember reading somewhere in this forum that the Pi 3b's hardware can't output different pictures at the same time (e.g. via hdmi and composite). * edit: I don't know if tvservice can do anything similar on the Pi. In addition to these obstacles and unknowns, I would prefer an external solution to free the Pi from any additional cpu or gpu stress, and (with less priority) to be future-proof from significant changes in the hard- and software. That said, if there is a software solution for cloning the output with different resolutions without slowing the Pi down significantly, I would be happy to try it. :)

Thanks @mitu thats kinda what I needed to know, I'm a bit clueless when it comes to pc monitors and pi's.

@ohmycommodore From what I've tried out, systems where the resolution is the same as ES (probably 320x240) are fine, it's only when the resolution needs to switch that the problem occurs. You can definitely try it out and just send that command to clear out the frame buffer if you get stuck at any point. The one or two N64 games I tried worked really well, as well as psx games with enhanced resolution and the older systems with one or two frames of runahead. I'd be interested in seeing how RT works with Pi4 and Lakka though. I haven't used it much as I have all my PSX games in chd and didn't really want to change them all over.

@jamesfarnhamlong said in Retrotink U - Higher res ES and PSX games: The 450x270 looks best, but I was wondering if it was possible to run one @ 720x578 to improve the picture a little. I know the TV supports this as I have an old Apple TV that uses this revolution. How do I write the hdmi_timing to make this work? Is there a calculator or something I could use? Try this - http://eightvirtues.com/lakka/hat/RPi HDMI Timings Calculator and Core Docs.ods (courtesy of https://www.youtube.com/channel/UCtF_2HGXXPlUi1J0Euw1Qrw). Is it possible to adapt this to run at 2x resolution so I can use the enhanced graphics in psi-rearmed. Is there a way to have this only affect psx game launching? Or would it then throw out all the other systems? Is there much point? Maybe if you use the calculator linked above you can derive the correct HDMI timings to use. As for the effect on the other systems, you'll have to ask the author of those configs.

@BuZz Ah, I see. Guess that was easily solved :D

Thanks for the answers and the suggestion of new theme. I will look into it. I did, that's where I got suggested to change the integer scaling, that didn't change anything.

Thanks for the tip @dankcushions. This was driving me insane. I'll update from source when Mario Kart 64 misbehaves from now on :)

@sirhenrythe5th Thanks for the detailed answer!

@mitu - Not a big deal but shouldn't Core Providedfill the screen on the x or y axis but not necessarily Integer Scaling which would be more of a whole number multiple of the original resolution less than the display resolution or am I reading that wrong?

@delirium_cordia RetroPie (and the Raspberry PI and other SBCs) are all about tinkering and learning new things. No need to rush things if you're not in a hurry - ask away in the forums if you cannot find the answer in the Docs.

@mindfieldx Yes, it's part of the 4.5 release: https://github.com/RetroPie/RetroPie-Setup/commit/47035624de6e26b52a9c0d7529926c307440a6f5

I think I found the solution. In mupen64plus.cfg you can find the overscan options. Need some fiddling around with it but probably this is what I was searching for. Though I don't know why the standard resolution (640x480) doesn't need overscan and higher resolutions need this to be able to fill the whole screen. Any one know why?

@canispeaktodave that makes sense. once you use overscan you're not using the native resolution, so blurring/artefacts. i believe the overscan settings are based on pixels, so assuming overscan_left=-12 overscan_right=15 overscan_top=-30 overscan_bottom=20 you can work out the post-overscan resolution by applying the left and right numbers to the width (480), and the top and bottom numbers to the height (320) it's a bit confusing to me that you have positive and negative numbers in your overscan settings, though. that would seem to shift the image when normally you'd want to shrink it, but it's been a while since i played with that stuff.

@mitu its working . I modify only the mode and group as you said . Thanks alot mate , all good !

I am using an HDMI to DVI cable. Will try tvservice now. Thank you for trying to help!

Huh. Now that's weird. I tried what you described (thank you very much for that!), and while the script works like a charm, for some reason fbi fails to load the 1920x1200 splashscreen. It literally returns a black screen with /home/pi/RetroPie/splashscreens/retropie-extra/rookervik-pixel-16x10.png: loading FAILED written at the bottom. The weirdest thing is that if I run sudo fbi -T 2 -once -t 20 -noverbose -a -l /etc/splashscreen.list >/dev/null 2>&1 after start up, mimicking the syntax in /opt/retropie/supplementary/splashscreen/asplashscreen.sh, the image is shown normally! So close, yet so far! Any ideas? EDIT: UN-FREAKING-BELIEVABLE! That was happening because I’m using USB auto-mount for loading roms into the system. For some reason, that option also overwrites the splash screens directory, but the pendrive is only mounted AFTER the splash screen is actually shown on startup. Hence, when I moved the stretched image into the directory, I was actually moving into the pendrive, which is ignored by the Pi on startup! All I had to do was unmount the pendrive, copy the file into the SD card and it worked! 😁 Thank you very much once again for all the help!

@granderjoree In retroarch you can adjust the fullscreen width and height, this will change the resolution of the app, It may help none in performance. The aspect ratio is the part that scales the emulators output, to fit in your screen, you can do whatever you want with it, pressing the start button on an option sets it to its default value, you can save options for individual games, in the games quick menu and then under options, save game options. The run command when you start an emulation gives you some control of the hdmi output, you can change to Monitor modes, or HDMI, some of the modes will not work, You can even change to a 50hz refresh rate. There are additional configurations for individual emulators outside of retroarch, in these config files you can usually change the emulators rendering resolution. You can access the configs through the network share, if you set-up samba on the PI.

@CursedLemon Its going to vary by game, some games can run playable in 720p with the right emulator. But some games, like the zelda games, are not going to render above the n64's native res. You may get better performance overclocking the gpu but it wont effect the resolution. I'll take a look at what mine does with the framebuffer and get back.