@mitu Actually it turned out all I needed to do was edit ES_SYSTEMS.CFG and it all just worked. Weird, I thought I'd already tried that.

@AwesomeKingClem don't remove your posts, makes the replies you got seem out of place and breaks the topics. That's not how a forum works.

@Lord-Vek said in Trying to run Commodore plus/4:

What it would do if I wasn't the owner?

per the previous post:

Do check if /opt/retropie/configs/cplus4/ is owned by user pi (ls -l on that folder), else do as root: chown pi: cplus4.

Are you talking about the vice libretro core or the standalone emulator ? RetroArch input combos do not apply to the standalone emulator.

@yserra Hmm, shoot. I wonder if I have a greater issue. I did as you instructed for the C64 and the keyboard is still having the same issues. FWIW, the same issue exists when I connect a straight up PC USB keyboard. I also notice the Scoll lock made no difference.. then again I test that after I edited the cfg, so maybe it doesn't work because I set it to "nul".

@bkumanchik It's working now?? Maybe I just needed to restart it - don't know.

Just me thinking that, works great now! Thanks!

Now the only thing not working is sound on the VIC-20, weird sound is working on the C64 side of things.

@mitu

@mitu Hmm, that booted up with a Super CPU bootscreen, but then just did the same as running in lr-vice (testing it with Metal Dust, which goes through the intro then gets to an options screen then just dumps you back to the C64 OS when you hit Return to start the game, whichever options you choose).

@a1eg said in Joystick not working for Commodore emulator VICE in some games:

@pscotto1234 THANK YOU
That did the trick!

You saved me perhaps a weeks time. I would have been playing around with this, reinstalling the RetroPie image, starting from scratch, trying this that and everything. Then maybe if I was lucky I would have come up with the answer.

Thank you for saving my time and giving me the answer!
I wonder why some games are for Joystick 1 and some for Joystick 2.

I found a lot of help in this forum. I'm very happy when I can help someone else ;)
Enjoy!

@dankcushions I'm going to do a full update and reinstall of as much as I can right now.

@billydent no problem. Glad I could help.

@mbrett You can use lr-vice instead and use RetroArch's built-in Save State function to accomplish the same thing tho.

lr-vice is maybe slower than standalone, I dunno, but on my Pi4 I can't see a performance difference.

@mitu Thanks for your reply. I'll give it a try.

Looks like entering an empty file name for the log doesn't work. You can set it to /dev/null with

LogFileName=/dev/null

and the file will not be created.

@jalbarracin welcome :-)

@CrazySpence did you update RetroPie-Setup first? That dependency was added recently.

Sorry the quality is so bad. Hopefully you can see the signal blanking out as I switch between the menu and the running system. The monitor's HDMI2 input notification appears in the top-right each time this happens.

The output resolution is 1080p@60 in both the system and the menu (I tried to show this but it's hard to see the monitor's OSD).

It feels more like the SDL window(?) is being recreated as I switch between the system and the menu.

With the FKMS driver, the monitor never blanks out and switching between the running system and the menu is instant.