Posts made by mc9625

It's a gift for the son of a friend of mine. He is 10 but I'm sure he will like it... He's father will for sure!
https://youtu.be/-9LSVi9XVn0

The version is the 4.0 stable on a Raspberry 2. The emulator is IMAME4ALL

I'm sure it has been asked thousand of times, don't flame me, but I really can't find the answer on the forum. Probably I can't think to a clever words to search for, I've tried with game info, ok screen, disclaimer, and so on.

How can I get rid of the game info when mame starts a new game?

How can I change the default settings for mame? I've tried to follow the instructions in the wiki but adding the mame.configfile= ... seems not useful. Any help?

@paradadf HK means?

I see. Actually I think that I took all that screenshot by mistake, pressing some weird key combo. Probably the only way could be to remap this combo to other keys in order to make it "impossible" to make it by mistake (for instance by pressing the UP and DOWN on the stick, or something like this). Unfortunately it's not very easy to find documentation on such feature.

Thanks for your advice, I will keep looking.

I would like to disable the screenshot keys combo, and also remove the screenshot menu item. How can I do that?

Thanks

Is there a way to add the boot animation I saw on some 4.1beta to a 4.0 final ?

You are absolutely right! Actually it seems non that easy to find info about this item. Anyway this is a description of how it works:
"As long as a touch (e.g. from a finger) is detected, the AT42QT1010 keeps the output line high. Otherwise, the line is kept low. You just need to provide a power source (1.8V - 5V) and ground for the AT42QT1010 to work."

In the project that inspired me, the author says:
"Since the cap-touch sensor (connected to GPIO23) is active-high, the code needed to interpret it differently since all the other GPIO inputs are active-low. Otherwise, the coin-drop will constantly retrigger. Replace line 226 with the following code:

if (io[i].pin == 23)
pinConfig(io[i].pin, "active_low", "1");
else
pinConfig(io[i].pin, "active_low", "0"); // Don't invert"

Of course it refers to Adafruit retrogame.c but I hope that makes sense for you anyhow.

Thanks.

Massimo

this is the product
https://www.adafruit.com/product/1374

I'm trying to use the AT42QT1010 capacitive touch module. The inspiration came from here: https://elecdrome.com/icade-raspberry-pi-mod/
But I can't understand how I should wire the module to the GPIO. I've used the ground and GPIO21 as described in the recalbox wiki for GPIO controller, but probably I still miss something.

I've got a big issue when I connect via SSH (from my macbook). I can't write in VI (opening NANO result in an error: error opening terminal: xterm-256color) because the arrows key will print numbers instead of move the cursor, and there's no way to write, the keyboard report wrong characters.

sorry I don't get it. I would like to have the PI automatically turn off the screen instead of the screensaver (simply dim it or go black without turning the screen off).

Nope, sorry I wasn't clear. I've attached the Raspberry PI to a VS Display LCD controller via HDMI, the controller is attached to an iPad2 LCD display.

Now, since I have the PI, could you tell me how to turn off the screen?

Thanks for your help.

@paradadf my tv? Actually I am using an IPad 2 screen with a controller. I will try with another monitor.
BTW Could it be possible to turn off the monitor when in standby rather than simply dim it or turn thr screen black?

I've noticed a strange behaviour on my recalbox (rasp 2, latest beta) when I leave it alone it enters standby but periodically (I would say every 10minutes or so) it wakes up (the screen turns on) for a minute and then goes in stand by again. How can I find what causes this?

little beyond my skills!

Thanks anyway

Hi, is it possible to map a key combo (lets say select+joy up or select+joy down) to control audio volume during play? I would like to avoid phisical buttons only for audio setting.

Yes, you're right. The 360 controller was the culprit. Now I've detached the USB wireless adapter for the 360 controller. Did you manage to fix this issue some how?

i have just installed the last beta. When I start kodi, I can't control the menu. I have both a wireless keyboard, that has always work with every other release, and the CEC system (in a Samsung TV). They both work, but the menu always return back to the first option (image) so quick that basically I cannot choose anything else. I have tried disabling the CEC remote or the keyboard but can't fix this. The keyboard works fine in emustation. The problem seems kodi. It's The  first time I see such behaviour in kodi. Any suggestion?