Thanks for this! I finally got some time to try this out and it's quite nice. ES feels better overall although I did notice some minor glitches. ES2 felt more like the original software rendering, i.e. a little sluggish around 20-30fps.
Is there, or could there be an easy way to switch between...
I'd like to request uoYabause - http://www.uoyabause.org/ I noticed it does mention GLES 3, but I don't know if that is a hard requirement or optional.
The fork is supposedly optimised to run on modest hardware.
The problem with just leaving the ini file there is that you get the black screen problem.
That's why I think deleting it before loading ES and copying it back before ES loads RA is the best solution unless someone cleverer than me figures out why the blackscreen occurs.
I think I have confused things for you by using variables in the paths. Check the megadrive run script again.
cp $ESSET/powervr.ini $ESPND/
core=$(zenity --list --radiolist --column 'Select' --column 'core' FALSE "$pico" FALSE "$genesis" --title="Megadrive")
It's not quite working with the powervr.ini. It loads ok but the powervr.ini is essentially doing nothing :/
Putting the powervr.ini in the root of ES app data folder fixes the tearing but causes the black screen as before.
I'm surprised you don't see any tearing - easiest way to notice in ES...
To the snes run script just before the zenity dialog is displayed and this does work around the black screen when using the powervr.ini.
However, I couldn't seem to get back to ES after, no matter what path structure I used in the call to the runES script or bin...
Yes I did try that, but the only place it appears to do anything is in the Base of the appdata folder for ES. Obviously with the previously mentioned blackscreen problems. In the .emulationstation folder, the tearing is there, although I'm not sure why.
Pretty neat. I've been trying this and found I couldn't get anything working...
It turned out that it was the powervr.ini that I had copied in the appdata to fix tearing. It fixed the tearing in ES but causes problems when launching roms. Sometimes it kicks you back to ES and sometimes it...
Well I think @canseco is currently porting releases of retroarch, so I would have a chat with him for a collaborative effort?
Doesn't stop you extracting the PND and getting things working in the meantime! ;)
It's only a guess but it sounds likely that Emulation Station is hogging the gl driver.
I guess in the launching process ES should be told to kill itself as it launches the emulator and started up at emulator exist?