@mitu so i just mapped it in ES ( after re-enabling auto save) and then i had to quit ES and i did a system shutdown, performed a reboot and it is WORKING! so far, yes!! i think before, i wasn't exiting ES correctly and it kept remapping the r1 to only the start button as the "y" button. and it was showing up as a keyboard input. I REALLY appreciate your help. thank you!
I ended up trading my ps4 controller with a friend that had one that came with her console. Kinda sucked because I really liked the Electric Purple color but I'd rather have a working wireless controller than one that's just a paperweight. I wonder if Sony changed something slightly with their controllers that kept it from connecting to Raspberry OS. I guess this topic can be closed now since it's technically resolved.
You can copy the drastic.sh version from that repo to your own RetroPie-Setup installation (overwriting $HOME/RetroPie-Setup/scriptmodules/emulators/drastic.sh) and then re-install drastic.
Do note that replacing the scriptmodule with another version will make updating the RetroPie-Setup fail, since you modified the file locally.
I get much faster boot times with my bluetooth (8bitdo) controllers turned off. Since that's an acceptable workaround for me, I haven't dug in to figure out what's wrong. My expected boot time is around 30 seconds on a 4. I'm only running retropie.
I've just upgraded to a Pi 4 and performed a fresh install of the latest Pi 4 install file (md5: 9154d998cba5219ddf23de46d8845f6c). I know this is still a beta, but I've experienced a couple of quite big issues. Is it the build or something I'm doing?
WiFi search initially found about 8 of my SSID name (for some reason). I couldn't connect to any, but now it can't find any SSIDs at all
Retropie has crashed on a few occasions (with 'Retropie has crashed' message)
Can't change resolution from 4k to 1080p because I can't get into the resolution menu - it just stays at the same menu level
Have I somehow got the wrong image or copied it to the SD card incorrectly?
I had similar issues
WiFi - I created the file pre setup so didn't have this, however did notice a lot of repeats in Bluetooth when setting up my sixaxis for PS3.
Didn't get crashing
Raspi-config resolution... I couldn't get into this either although I did get a workaround which helped.
I used FlyCast and it .... worked.... One of the emulators crashed on me but I don't recall which one. I'll try ReDream again as it did load but seemed a little goofy but that's probably due to my inexperience with it. Took me a few minutes to realize the mouse was working and had to exit using the commands and not through RetroArch. I'll give it another whirl.
Part of the problem is not really having anything off the top of my head that I would specifically play on Dreamcast. Nearly everything over the years that I had has either aged terribly and not worth the trouble or has been updated or remade on better systems.
PSO has been redone and done better, Skies of Arcadia is on GameCube, etc.
Okay, there is some problem with the onboard bluetooth. The documentation already mentions that the case interferes with 2.4 GHz wifi. The same is true for bluetooth, and I added a USB bluetooth adapter to mitigate that.
Just for context, here is a comparison of uncached read performance:
Could this issue be fixed by making customisations to the /etc/emulationstation/es_systems.cfg directly rather than creating a copy or would that put the customisations at risk of being overwritten & lost?
The system file (in /etc) is maintained by the RetroPie-Setup script, so it might get changed by an update, so it shouldn't be used for custom systems.
@mitu ok good to know, i'll blow everything away and start from scratch. i must have glazed over the part about it not being supported on a DE. Also i was never planning on using vnc for it and figutred it would never work, was just using it for troubleshooting and setting up other things unrelated to retropie, im just to lazy to switch the input on my monitor :P
thanks for the info to you both, much appreciated.
To bring this thread to its full conclusion I finally got round to modifying my copy of Gloom Deluxe.
I made an HD floppy disk image file and used Workbench to copy the contents of both disks to this file. I then modified the s/startup-sequence file to boot straight into the game without loading the setup program. I used ED from the AmigaDOS Shell to do this.
I now have a single disk version of Gloom Deluxe that works perfectly.
I had read that the 4k60 flag is supposed to increase the clock by ~10%
The 4k60 flag increases the GPU core freq from 500mhz to 550mhz. It shouldn't affect the CPU freq. I have gotten weird readings in the past where it reported much higher CPU frequencies than is possible. Im not sure what causes it, but I believe it's a false report.