@sirhenrythe5th ahh sorry about that. I must have missed that part. Thank you!

I solved the problem. It was easy. An update from the lr-Atari800 emulator helped.

@accio-brain

The forum has a search option !

Have a look here :
https://retropie.org.uk/forum/topic/32069/retropie-wont-boot-up-start4-elf-not-compatible

@sleve_mcdichael

Thanks ! Will give it a try and post result after a couple of tests...

@folly Thank you, it is working now!

Please forgive me for replying in an older topic, but I just had to thank barbudreadmon for his explanation on "how to use cheat codes with FBneo." I've been on youtube, tons of forums and could only get .cht's to work but not the .ini files. Some very smart folks here....... Thank you so much :D.

I don't know the technical details, but the impression I got from reading discussions is that the NAOMI issue is due to something with RetroPie specifically and is currently being investigated.

The Virtua Cop 2 issue with freezing upon firing with a lightgun is isolated to the libretro port of current Flycast, and it doesn't seem that the issue is being investigated.

Thanks guys, this was very helpful. I just ordered the
I-PAC2. =)

Hi Guys.
This might be more complicated than expected. I have read something about autoconfig, but I think it doesn´t fit this case.
So, right now I am trying Plan B which is made a .cfg file for each 3 button game to override retroarch.cfg and have a 3 button game config.
Now the hard part of this is to find a list with all the 3 button games, or at least to able to filter down my roms to know which ones are "3 button game"
but so far I haven´t been able to find a list or find a method to filter down my romset.
Just the museum arcade have an advanced search with 3 button layout option, but it only show me 150 results .
Any idea?

@dankcushions

Sorry I am replying so late; I have been running an experiment and got to the bottom of all my issues. Its the audio drivers that are causing my screen tearing. Currently I am running Alsa sound driver, ZFAST curved along with some pretty fancy overlays (As I stated prior I ran everything without them still with issues). I am noticing 0 performance drops. No audio drops or screen tearing. I just couldn't believe how well its running with the load placed on it. I have tried my other pies and low and behold; Alsathread was the cause of all my issues. I know you said Alsa is slower but I have been testing the most graphically intense PS1 games on playstation (Duckstation) and I am experiencing no performance drops. I actually just beat Final Fantasy 8! I know you had mentioned something about a driver stack which is probably the cause. Now I didn't try the n64 cores and probably wont as I will wont be playing those games on my pie.

Hi all, so I'm trying to test openlara on a pi zero 2 w and have brought Tomb Raider 1 from gog as it's on sale. But it's an exe file and I don't have access to a windows machine. Is there any quick and easy way to extract the files from my pi? Or i'd need to install wine etc?

OMG, for some reason I never received a notification concerning the two replies ... I'm so sorry! Really do not want to come across as a snob hahah ... and here my replies 2+ years later ... (I'm blaming Covid)

@mitu - So yes, APB was developed in Free Pascal using the Lazarus IDE 😊

@hiulit - Thanks 😊

I've tried downgrading my Steamlink version to 1.1.68.170 but the issue still persists.
I've also tried a Steamlink PC game and that also didn't work.

Within my config.txt file, I've allocated 256MB of RAM to the GPU via gpu_mem=256, however the screen still remains blank. I'm on a 5GHz wireless connection.

Is there any specific host or client settings I should set from Steam to help resolve the issue? Is there any config.txt settings that would cause this issue?

@mitu Sorry for the late response!

There were indeed no events when I tested with evtest.

I completely removed the keyboard again, rebooted and started Pixel. I again paired the keyboard, and made sure it worked in Pixel. Then I rebooted into ES again, again no keyboard..... some kind of weird inspiration made me go to the Retropie Config (you know, where the setup.sh is started) and, much to my surprise, I found that after a few button pushes the keyboard started working! I have no idea what went on and why it worked, because apart from opening setup I did nothing differently from the first time. After leaving the config I started evtest again (via the remote console) and actually this time around the events were showing up! The keyboard actually started to work!

Soooo happy now, as after adding the proper event source to the moonlight config I actually have full keyboard support there as well!!!

Thank you again for your help and patience @mitu !

@spaceblaze Just to confirm the above code change does work.

I reexported all the videos at 480p and now have control over the size.

As it turns out, the end result is not that great a user experience so I'm reworking the layout a bit.

Will post a video once I'm happy with it.

What @Ashpool suggested seems to have worked for me. In case anyone is interested, here's what I did...

First, with the RP up and running and the TV screen displaying correctly, I queried for the HDMI mode used:

$ tvservice -s state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive

From this and the RetroPie documentation on HDMI Mode I learned that in /boot/config.txt I had to set

hdmi_group=1

(for CEA) and

hdmi_mode=16

(for 1080p at 60Hz and 16:9). I also had to add

hdmi_force_hotplug=1

After rebooting the RP, the issue was resolved.

Thanks again, @Ashpool!

This has now been fixed in the latest version of carbon-2021

@linuxxp said in Strange colors on NES:

The problem persist on both emulators and only with NES games. I don't use shaders.

Are you sure you don't use shaders ? The image you posted looks like it has a smoothing shader applied. Which game is it ?

EDIT: have you changed the palette options for the NES system ? I know Nestopia has the ability to change it from the core options.