@soda-inc said in How do I enable force feedback / rumble?:

Also, I found some old posts which indicated that the Retropie Kernel might not be setup for controller vibration support.

There's no RetroPie kernel and there's no special configuration that disables controller vibration support (as you've noticed with N64).

When starting a PS1 game, check if you have 'Enable Vibrarion' in the Core settings and also set the Pad 1 Type to Dualshock.

@Nakynaw

My quick question is, since the 4.6 official image is a couple of months old, if I really want to make sure to start from the best basis, does it suffice to run the «update packages»?

i would, but generally you shouldn't update unless there's something specific you want. and, as always, take a backup.

Does it covers everything there is to update? And are there things worth updating from source to get latest improvements (especially if regarding n64 performances)?

see https://retropie.org.uk/docs/Updating-RetroPie/#binary-vs-source-updates

the best thing for n64 improvements is patience. some good improvements should be in the coming weeks/months.

@dankcushions I just changed the resolution and frequency. Ignore my last comment about it not being horrible. It looks sooooooo much better now. Thanks again!

I've only had it happen on my 3B+ setup with the lr-genesis-plus-gx emulator. And it wasn't unique to megadrive games. I has some Master System ROMs also do it.

Hope they can resolve this in an update before long.

@mitu Sorry, for whatever reason it suddenly started to work. I didn't change anything and it's the same games that I tried before. Weird to say the least. But thank you for your time and help.

@goldug said in Runcommand messes up resolution for some reason:

because I hadn't changed anything, but yes, it seems there is now for some reason.

You added something, there is nothing in stock RetroPie that creates those files automatically.

@mitu I've tried both .bin and .zip, the hash file for astrocde says .bin files as well as all the BIOS files zipped in the roms directory as well as being in the main BIOS directory. Still no dice.

@Darksavior said in lr-daphne:

@shavecat Nope. Read what I said.

Lr- Daphne sucked the last time I tried it on my pc. No audio, compatibility was bad, weird folder structure, and crashes a lot.

@AdamBeGood Daphne Singe only plays certain games. My post that I linked to has the list. The dev also has his own Daphne port but I'm not sure that it's arm compatible.

It's arm compatible, and has singe support built in, but doesn't run roadblaster on retropie...

@Parabolaralus Looks like it can be kernel related.
I made it work yesterday on older RetroPie based on Debian Etcher. However, the system was a few years old and I decided to make a fresh install. And it was a mistake because nothing was wrong with an old install, I just wanted to clean up the system garbage after several years of usage...

After re-install I have top heat instead of dpad left e.t.c.

I also tried Batocera, Reacalbox everywhere it looks the same.

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.

@8Ataco For N64 not all games run good.
As for DreamCast try:
over_voltage=3
arm_freq=1750
core_freq=600
v3d_freq=750

You must just edit the conig.txt file. So take out the SD card, insert in a Mac card reader or slot and edit the file in any txt editor.
You must place this above mentioned lines under the line with the text:
"#uncomment to overcloak the Arm. 700Mhz is default"

@riphead77 I've merged your 2 topics - I've split your previous post in an old topic to a new one. For your issue - see the answer above.

@mitu Here's the text that came out after the commands:

AP///////wBMLe4NAA4AAQEbAQOAeUR4CiOtpFRNmSYPR0q974BxT4HAgQCBgJUAqcCzAAEBBHQA MPJwWoCwWIoAUB10AAAeAjqAGHE4LUBYLEUAUB10AAAeAAAA/QAYSw9RHgAKICAgICAgAAAA/ABT QU1TVU5HCiAgICAgAToCA0/wU18QHwQTBRQgISJdXmJjZAcWAxIsCQcHFQdQPQTAVwcAgwEAAOIA D+MFAwFuAwwAQAC4PCAAgAECAwTjBg0B5Q5gYWVm5QGLhJABAR2A0HIcFiAQLCWAUB10AACeZiFW qlEAHjBGjzMAUB10AAAeAAAAAAAAAAAAAAAArQ==

Additionally, after hours of messing with this, when I plugged it in today it was magically working. I had just rebuilt the box after an issue with SSD corruption. I'm still willing to pull data/test to help anyone else who has come across this issue. I also plan on rebooting a few times to see if this is a fluke.

@mitu I need to read a lot of documentation. Thank you !

Sorry for the spelling mistakes but I cannot edit the post anymore (Askimet spam mark).
Pi Model or other hardware: Pi4 2gb
RetroPie Version Used: 4.6.7
Built From: NO BUILD (I added the roms by myself from buid by Ghostware and Damaso and some form CDROM site)
Error masseg: GDD_ERR_TOUT (and other hangout and crashes)
Controller Used: Esperanza wireless Gladiator GamePad (with USB dongle)
Guide used: no giude, installed redream form binary in retropie
USB Devices connected: wirless airmouse with keyboard (I cannot fins the model name, but its quite old), wireless second gamepad (TY-G103D) with dongle (but the pad is switched off)