I'm bumping this because I found a solution. It's not the best possible thing to do but seems to have solved my issue.

I edited my .cfg file on /opt/retropie/configs/all/retroarch/autoconfig and added

input_l_y_minus_axis = "-1"
input_l_x_plus_axis = "+0"
input_l_y_plus_axis = "+1"
input_l_x_minus_axis = "-0"

in order to set the digital inputs as analogue (in addition to keeping them as analogue too).

It appears that the current fba core accepts only analogue (thumb)stick inputs for arcade machines that used analogue hardware such as wheels, joysticks, pedals, etc, something that wasn't a case previously and still isn't on MAME.

For anyone having the same problem (and doesn't use analogue sticks) this seems to be the only solution currently but I'm not sure if this will interfere with anything else.

@waltwhitman6969

You can view the commits that are made to the setup script here. A little investigation work is sometimes required to know exactly what all the changes mean though. Otherwise, everything is really only listed at a major version release as you noted.

@Sano

/facepalm

Yeah I missed that. I read all my information from an old issue of MagPi. I did find that same info elsewhere.

wget -qO - http://archive.itimmer.nl/itimmer.gpg | sudo apt-key add -

Thank you both for all the information. Surprised that the performance hit is so pronounced. Will report back

@picogame So, while the utility was running, were you moving the joystick, pressing buttons etc? And while you did, was the screen changing?

The idea is to make sure that the system responds with some indication on-screen that you are manipulating the joystick. If it does, that means AdvanceMAME is capable of seeing the inputs, and the joystick number shown on-screen that is changing obviously corresponds to the joystick you are manipulating.

This is something I don't need to do with arcade controls, so someone else might chime in here who has done it--but with the above results, you should then be able to use/edit the index number for a device in the advmame.rc file. For example, you might verify or add the line device_joystick_0 raw and perhaps device_joystick_1 rawto the .rc file. Or, instead of "raw" you could try using the "event" driver which may be more appropriate. You can read about drivers in the dev documentation for advmame. My thought is that once the device is properly defined, you should be able to press TAB on a keyboard while in a game, and navigate through the menus to map keys for all games or specific games using the joystick to map buttons etc. A successful test using advj proves that advMAME can see the device, so this is just an exercise to expose it so you can map inputs.

Of course, you could map all inputs manually by editing the .rc file using details here, but that would be extremely tedious.

@mediamogul said in Help getting Brutal Doom campaign hellonearthstarterpack + Duke3d expansions to work:

@megafacehead

Give those demons hell on earth.

Fixed that for ya

I run my Pi3s at stock clock speed and have no speed issues with SNES or NES games. I don't bother with N64. A Pi 3 can barely handle it. When you get into overclocking territory the whole system starts to become unstable.

I also get that error on Ubuntu 16.04 x64. The issue is described here:
https://github.com/libretro/parallel-n64/issues/441

After installing libclang-dev and adding /usr/lib/llvm-3.8/include to the include path I had this error:

In file included from /usr/lib/llvm-3.8/include/clang/Basic/DiagnosticOptions.h:13:0, from mupen64plus-rsp-paraLLEl/jit.cpp:3: /usr/lib/llvm-3.8/include/clang/Basic/LLVM.h:22:34: fatal error: llvm/Support/Casting.h: No such file or directory

So I installed llvm-dev and then I could compile fine.

Any chance to get this incorporated into RetroPie?

@rulfen First, a riddle.

What's black and blue, yet hardly ever read?

Hint: ˙ǝƃɐd ʎɹǝʌ sᴉɥʇ ɟo doʇ ǝɥʇ ʇɐ s,ʇI

[Riddle's credit goes to @mediamogul .]

We need more info about your setup to try to help you.

@the496rocket please, try to fill the form in the read this first post.

There must be something wrong in your setup. RetroPie on a raspi3 with decent peripherals can run smoothly any game from the 8/16-bit era without any tweak. Just install, config input, put your ROMs and play.

[Footnote: OK, maybe 3D games, like StarFox (SNES) and Virtua Racing (Mega Drive), can stutter a bit. But the games you mentioned should work just fine.]

@razinx if you really want to hide the bios files, you can open the zip and add the contents to the zip for the game that requires that bios.

So the contents of pgm.zip could be added into kov.zip, and you wouldn't have that bios showing up in ES. Now of course this will make your roms bigger and so your set will be bigger.

@RedBatman you should read this post: https://retropie.org.uk/forum/topic/2859/how-to-use-mame-with-retropie-help-guide

And, of course, the official docs too: https://retropie.org.uk/docs/Arcade/

hey guys!

so i managed to get this to work to some capacity but few things are a tad wrong and was hoping for your help.

when i power the NES on, the push button is OUT when the unit is on and when i push the POWER IN, it turns OFF.
is there something anyone can think of to reverse that? I've tried moving cables around and can't seem to get it.

how does one get the LED to work with the unit if its built in on the board? should it just not turn on and off if i ave properly tapped into the power?

thanks everyone

@kmickelow You could start by telling us a few things about where you DID get your image. Is it the RetroPie 4.2 image?

Then, tell us all about your setup by following the link at the top of every page here.

@jmperez

More information about your setup will probably be necessary. The required information can be found at https://retropie.org.uk/forum/topic/3/read-this-first. Also at that same link, take note of the part detailing how to format your posts for log entries.

@simonster I had totally forgotten that I used a USB to transfer the last time and not the SD card. This should fix the problem. Thank you!

Hi chipsnblip
Yes u possible can do it with that d3scription in ur link. I'm wondering if anyone has successfully burnt a big gig pi image with games and boxart tge lot onto an external drive and it worked.

I've been chatting around on forums for past few weeks and talking about this and alot of people have said no u can't boot the image off ex hdd u need a 64gb 128gb or 250gb sd card. As it's not possible to run it off external.

Just done it myself in about 5 simple steps. With help and info from Internet of course

Just wondering as I've made my own image with games art and stuff put it on external and plugged into pi and powered on and it booted up and works.

Has anyone else tried it instead of going the long way round and inputting lots of data into the pi terminal to format scan re partition and to auto mount the usb drive.

Okay folks, I've written up a script to handle this exactly the way I described before.

It runs from the autostart.sh and watches /dev/shm/screen_manager.cfg for updates.
That way any other system process can create/modify that file and this script will respond by either starting the rom, or starting the dashboard.

Cheers!

https://github.com/coderkevin/mini-nes/tree/master/screen