Search Results for 'n64'

[egutierg]

This is what I have on ./reicast/mappings $ controller-Xarcade-toGamepadDevice.cfg

[emulator]
mapping_name = Xarcade-to-Gamepad Device
btn_escape = 8

[dreamcast]
btn_a = 0
btn_b = 1
btn_c =
btn_d =
btn_x = 3
btn_y = 4
btn_z =
btn_start = 9
btn_dpad1_left =
btn_dpad1_right =
btn_dpad1_up =
btn_dpad1_down =
btn_dpad2_left =
btn_dpad2_right =
btn_dpad2_up =
btn_dpad2_down =
axis_x = 0
axis_y = 1
axis_trigger_left =
axis_trigger_right =

[compat]
btn_trigger_left = 294
btn_trigger_right = 295
axis_dpad1_x =
axis_dpad1_y =
axis_dpad2_x =
axis_dpad2_y =
axis_x_inverted = no
axis_y_inverted = no
axis_trigger_left_inverted =
axis_trigger_right_inverted =

All it does on the Dreamcast Emulator is the joystick works but none of the buttons works.

It is connected to a Raspberri Pi2

The Xarcade tankstick controller is used with retropie and emulation station to run NES, SNES, N64, Mame and PlayStation 1. Currently working as I want to. Wanted to add Dreamcast to the collection.

This is what I have on /opt/retropie/configs/all/Retroarch-joypads $ Xarcade-to-GamepadDevice.cfg

input_device = “Xarcade-to-Gamepad Device”
input_driver = “udev”
input_r_btn = “7”
input_save_state_btn = “7”
input_start_btn = “9”
input_exit_emulator_btn = “9”
input_l_btn = “6”
input_load_state_btn = “6”
input_up_axis = “-1”
input_a_btn = “0”
input_b_btn = “1”
input_reset_btn = “1”
input_down_axis = “+1”
input_right_axis = “+0”
input_state_slot_increase_axis = “+0”
input_x_btn = “3”
input_menu_toggle_btn = “3”
input_select_btn = “2”
input_enable_hotkey_btn = “2”
input_y_btn = “4”
input_left_axis = “-0”
input_state_slot_decrease_axis = “-0”

Any help will be greatly appreciated.

[mikeveli20]

Joy Mapping Stop = “J1B0/B3” in mupen64plus.cfg, but it doesn’t really matter what I change it to since no button combination is working. Those same buttons work perfectly to quit Retroarch and they worked without issue in Retropie 3.3

Edit: It seems when I launch a game it’s automatically reverting my mupen64plus.cfg back to default. I tried changing the Joy Mapping Stop = “J0B0/B3”, saved my changes, and re-opened the file to make sure the changes saved which they did. I then launched a game and once at the main menu of the game, I checked the mupen64plus.cfg file and it had changed back to J1B0/B3. Not sure if this is what’s causing the issue or not.

[maketheworldbetter]

A black screen is everything I got with the lr-n64-emu since months, whichever rom I took :(
However, I´ll now try to fix that with some different settings.

[gizmo98]

In lr-mupen64plus there is a core option for video plugins. Don’t expect to much. gles2n64 is broken since last june and glide shows a black screen.

[maketheworldbetter]

hi,
I’ve read weeks ago, that it now is possible to set individual videoplugins for every rom with N64-lr-core…but how?

Where do I find informations how to do that?

[Anonymous]

I think a super smash bros, n64 box art style with some of the characters would be cool, even though it’s not as retro as the ones you’re used to making

[mikeveli20]

Possible? If so, how would one go about configuring. I’m using a PS3 controller.

[catrinisin]

Thanks, I really appreciate all the info and I’m sure others will too.

In my case the unit I’m doing this with is a bartop arcade I built:

Large Bartop Arcade

I’m using an ipac controller that has a shift key option that allows me to have many different keyboard buttons available so it isn’t the end of the world if I have to reach over to the arcade controls to perform an action like bringing up a menu, etc.
I’m using the xbox controllers personally for every emulator but my kids use the arcade controls mostly. Originally I needed a controller for emulators like n64, psx, etc. but I love that I’m now going to be able to use it for all the older systems as well. I had no idea it could emulate a mouse!

[catrinisin]

In retroarch emulators, volume control works great. In the new default mupen64plus emulator (non-retroarch – retropie 3.3) volume control doesn’t respond even though I’ve configured a button in the mupen64plus.cfg file. The stop/exit emulator button works fine.

I read on github that sound control is still ongoing for the raspberry pi port of mupen64plus, but that comment was written over two years ago.

Has anyone gotten this working?

[mikeveli20]

Not sure if this is the right section of the forum for this so please move if need be.

I’m using Glide for Ocarina of Time as I feel it gives the best overall performance. There is a bug/glitch/whatever you want to call it on all 3 graphics plugins that causes a several second delay when entering the pause menu. This was apparently fixed in Glide and tested with mupen64plus back in April of 2015 as indicated here, but the problem still seems to exist. Anyone know how to get this fixed on the pi? The issue doesn’t exist in Majora’s Mask but I’m unsure if it was there to begin with.

[dankcushions]

But don’t we use https://github.com/gonetz/GLideN64 ? that’s what retropie references in the install scripts. in this repo it seems to indicate that there is an aspect ratio setting. eg:
– https://github.com/gonetz/GLideN64/issues/551

[gizmo98]

There is no aspect ratio setting for this plugin at the moment. Corn has created an branch with an aspect ratio option. We still use GlideN64 upstream which lags this feature. The only option is to tell your TV “don’t stretch video signal”. Most TVs have options like video format=smart/wide/zoom/normal and so on.

[mikeveli20]

Thanks for the reply. I checked the location you specified and there was a GlideN64.custom.ini file in there. I checked the contents but everything was related to custom game settings and there was nothing about aspect. In the mupen64plus.cfg file there’s a GlideN64 section which does have an aspect property, however, it’s already set to Force 4:3 which obviously isn’t working. I tried each one of the settings (0-3) but they all produced the same result.

[labelwhore]

[quote=114514]My issue with the xbox controller is also solved thanks to this great community. Thanks everyone!

My only issue left is trying to figure out how to get it to work with the new default mupen64plus emulator which doesn’t use Retroarch. (Retropie 3.3)

[/quote]
I haven’t played with that particular emulator, but if you’re having control issues, take a look at the xboxdrv documentation. There are some really handy features for the controller. (IMO the xbox 360 controller is hands down the best controller for the pi.) In particular, look into creating some extra config files and the --next-config option. The default behaviour of the xbox button is to change controller modes. I use this to be able to control atari 5200, 800, and ST, as well as c64 and Amiga. If you want more details I can provide some of my controller config files, and what you need to modify in rc.local to get that working.

http://pingus.seul.org/~grumbel/xboxdrv/xboxdrv.html

[catrinisin]

My issue with the xbox controller is also solved thanks to this great community. Thanks everyone!

My only issue left is trying to figure out how to get it to work with the new default mupen64plus emulator which doesn’t use Retroarch. (Retropie 3.3)

[dankcushions]

i think you need to be looking at the glide64.ini (or something like that) file in the /opt/retropie/configs/n64/ folder. i’m not sure of the exact setting you need, as i don’t have mine to hand, but it seems to be adjust_aspect=0.

[mikeveli20]

Currently trying to find the best settings for Banjo Kazooie and after trying the various gfx plugins and resolutions I’ve determined that GlideN64 at the recommended VGA resolution gives the best overall performance. However, the image stretches to fill the entire screen instead of displaying in the proper 4:3 aspect. I’ve tried the following resolutions:

CEA-1 (640×480 4:3, progressive)
CEA-2 (720×480 4:3, progressive)
CEA-3 (720×480 16:9, progressive)
CEA-4 (1280×720 16:9, progressive)
CEA-6 (720×480 4:3, interlaced)
CEA-7 (720×480 16:9, interlaced)

All of those stretch the image and 720p is unplayable anyways since it’s super slow. If I switch to Rice I can run it more smoothly at 1280×720 with the proper aspect, but there’s frequent audio stuttering which doesn’t happen with Glide. Any way to make Glide not stretch the image? Also, does anyone know what the “framebuffer res” setting does?

[catrinisin]

So I cheated and switched the default emulator to lr-mupen64plus and my controls work fine thanks to retroarch. But since version 3.3 now defaults to the better mupen64plus that does not use retroarch, no controls work. I thought I was fine with this until MarioKart64 didn’t work. It runs in the beter mupen64plus but not in the libretro version.

So I guess I need to somehow figure it out. Have you made any progress @jbounds286 ?

[catrinisin]

I have the same problem with Retropie 3.3. Can’t make sense of the InputAutoCfg file. In my case it is a wireless 360 controller and it works in all retroarch emulators but not the Mupen64plus for N64.

[k-bert]

Hey Herbfargus,

Sorry I didn’t see your post until after I posted my last one.

I am just using my pi for NES, nothing else. And I am mounting it in my dead NES with the goal of having it look and behave as close to an actual NES as possible.

As for your questions I’m not sure. Yes there is the nostalgia factor with using actual NES controller for a NES game, but the SNES also has all the buttons the NES would need. If I were to use my pi for NES and SNES I would just use the SNES controllers all the time (they are more comfortable after all).

According to the readme for the gamecon up to four controllers of mixed types can be used, so two NES and two SNES could be connected at all times and you can use either depending on what you are playing.

If I were building a multi platform emulator I would probably use PS3 controllers for everything but the N64 (I’m talking anything pre-Xbox or PS3), just because the N64 is a bit of a weird one. Also using PS3 would have sidestepped all of the headaches I just had trying to get this NES controller to work.

Cheers,
K-berg

[smithers]

[quote=113972]Hi Smithers

I used this latest build and have had no problems up until now.

My issue is there is only the libretro n64 emulator. The other emulator mupen64plus doesn’t seem to be there.

Is there any way to install this without having to start again?

Thanks in advance

[/quote]

Hi.

Yes, you can install any emulator you like from the normal RetroPie Setup Script. There is no change to normal functionality of RetroPie.

@skullmonkey – is your aim to completely start from scratch again or just to update RetroPie?

[epe9686518]

Fastest is completely game dependent…. Some plugins are faster on certain games than others….Sanfran Rush and Rush 2 have tons of slowdown on GL2n64 and Rice, and or lock up/freeze, but both run full speed with GlideN64 with minor issues.

Here is the rom compatibility list that we have put together thus far.

N64 Rom Compatibility List

As Corn Noted, you shouldn’t really even try N64 Emu on Pi with out a Pi2.

[sondrey]

Hi!

So i’m working on a project where i’m building a retrobox out of a defect Nintendo 64. I’m using the latest image of retropie on a Raspberry Pi 2. I’ve hooked up all the original console ports to the pi, using the suggested pins (3,5,7 and 29 if i remember correctly). So the status is now:

All ports works on the main menu, all ports are tested on 2 diffrent controllers.
In jstest, they are listed as:
Player1: js4
Player2: js5
Player3: js2
Player4: js3
They all give good values in jstest.

The situation and problem:
When i start up mupen64plus, it only detects player 3 and 4. In Mario Kart 64, i am able to select characters.

As you might understand from this, we can eliminate errors in wireing and the remotes themselfs, as they show up good in jstest, it might even be a matter of configuration. I’ve tried a lot, but can’t get it right. I was thinking maybe setting device number equal to the jsX number woud assign the jsX to player X, but still didn’t work.

If some of you can help me, and need more info, plz ask, i will get you what you need asap

Thanks a ton,
I’l might post something about the build when i’ve got it up and running :)

Sent fra min SM-G900F via Tapatalk

[mw99]

Is there anything else I can do? Most other emulators besides the N64 work fairly well, it’s just the SNES…

[orion]

Raspberry Pi 2, Retropie 3.3.1 Wheezy SD image download (no update performed).

I have a Logitech F710 wireless. It has a switch between 2 different modes: D (DInput) and X (XInput). Depending on the switch position it is seen as different devices (usb disconnects and reconnects when switching):

lsusb with DInput:

Bus 001 Device 009: ID 046d:c219 Logitech, Inc. Cordless RumblePad 2

dmesg with DInput:

[ 2555.058246] usb 1-1.5: new full-speed USB device number 12 using dwc_otg
[ 2555.167361] usb 1-1.5: New USB device found, idVendor=046d, idProduct=c219
[ 2555.167435] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2555.167470] usb 1-1.5: Product: Logitech Cordless RumblePad 2
[ 2555.167488] usb 1-1.5: Manufacturer: Logitech
[ 2555.178335] input: Logitech Logitech Cordless RumblePad 2 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:046D:C219.0008/input/input7
[ 2555.179747] logitech 0003:046D:C219.0008: input,hidraw2: USB HID v1.11 Gamepad [Logitech Logitech Cordless RumblePad 2] on usb-3f980000.usb-1.5/input0

lsusb with XInput:

Bus 001 Device 011: ID 046d:c21f Logitech, Inc. F710 Wireless Gamepad [XInput Mode]

dmesg with XInput:

[ 2505.718035] usb 1-1.5: new full-speed USB device number 11 using dwc_otg
[ 2505.828718] usb 1-1.5: New USB device found, idVendor=046d, idProduct=c21f
[ 2505.828746] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2505.828764] usb 1-1.5: Product: Wireless Gamepad F710
[ 2505.828780] usb 1-1.5: Manufacturer: Logitech
[ 2505.828797] usb 1-1.5: SerialNumber: 56E994A2
[ 2505.830708] input: Logitech Gamepad F710 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/input/input6

Using DInput the joystick works perfectly in emulation station, mupen64 and scummvm but is not recognised by retroarch.

Retroarch says when starting a game (snes, gba, gbc):

Logitech F710 Gamepad (DInput) (1133/49689) not configured

Now I have no idea where retroarch gets this joystick identifier (udev, SDL?). It does not appear in dmesg or lsusb.
I did a recursive find in /opt and /home/pi grepping files for the string ‘F710’ and there is no config file mentioning an F710 controller (in DInput it should be: Logitech Logitech Cordless RumblePad 2). The configured joysticks are:

pi@retropie /opt/retropie/configs/all/retroarch-joypads $ ls -lrt
total 16
-rw-r--r-- 1 pi pi 868 Jan 15 22:34 ACRUXUSBGAMEPAD8116.cfg.bak
-rw-r--r-- 1 pi pi 868 Jan 15 22:35 ACRUXUSBGAMEPAD8116.cfg
-rw-r--r-- 1 pi pi 878 Jan 15 22:44 LogitechLogitechCordlessRumblePad2.cfg.bak
-rw-r--r-- 1 pi pi 878 Jan 15 23:37 LogitechLogitechCordlessRumblePad2.cfg

There are also these same 2 joysticks in the emulation station config file.

I have tried copying the file LogitechLogitechCordlessRumblePad2.cfg to another file with the name of the joystick that appears in retroarch error message (without blank and special characters) and I also tried changing the name of the joystick inside the file. This was unsuccessful. Is there any documentation on how retroarch gets the joystick name (here: Logitech F710 Gamepad (DInput) (1133/49689)) and how I can map that name to a config file?

With XInput it is worse:
Not only do I get the very similar message:

Logitech F710 Gamepad (XInput) (1133/49695) not configured

but also emulation station GUI cannot configure all buttons in XInput mode (in XInput, lower R and L buttons are actually axis and when pressing one of them it triggers the configuration of 3 consecutive buttons with (axis-,axis+,not defined). It can be circumvented by editing the config file manually if only I could find a nice description of the config file settings).

I have read somewhere in this forum that DInput does not work, but according to http://linuxhacksandfixes.blogspot.de/2013/02/the-logitech-f710-gamepad.html it seems DInput should work fine on Linux. Also DInput works perfectly in emulation station, mupen64plus, scummvm (and with jstest /dev/input/js0) and also works on my PCs (also Linux but on Intel) so it could also work for retroarch (in the worst case by using xboxdrv to expose it as xinput).

I must say also that I seem to remember a week ago using this controller succesfully in retroarch snes or gba/gbc. I cannot say for sure, but this is surprising since I have not changed/updated anything except editing these joystick configs (only after the problem arised) and configuring mupen64.

Thank you.

[corn]

Fastest is the gl2n64 plugin but it will only work on some games. (MK64)
Second is the rice plugin which work on most games but it has some slowdowns in some games which I believe is due to the texture handling (see SSB yoshi map).
Third is GlideN64 which essentially only run well with VGA resolution 640×480 or possibly up to 800×600 and is one of the most accurate plugins with very few glitches.

Last but not least you really need a Pi2 overclocked to CPU/1GHz SDRAM/483MHz and GPU/500Mhz to get a reasonably smooth experience on most games.

[epe9686518]

The audio lagging is due to the emulator it self not the audio buffer on the pi. What I believe is happening is to get the games playable at a decent speed, the emulator is throwing the audio out of sync with the game. I am assuming it’s easier on the hardware if it’s not trying to keep the audio in-sync with the video. I noticed this with SanFrancisco rush, where there is about a 1 to 2 second delay on the audio. Other than that the game plays at full speed and works great. It’s a bit of a hack but it gets many games fully playable at great speed. Might can ask Gizmo, as he would probably better be able to explain what’s going on, but I don’t belive adjusting anything outside of the emulator would improve this. I got around 60 games that work great, either perfectly or close to it for N64. This is just how it is with N64 emulation on the PI, you really need more power to emulate N64 properly, but even on PC there are many games that don’t work or have issues still.

[kb0mmr]

I decide to upgrade the audio from the on board audio to an USB Audio devices. I am able to hear audio with the USB audio device with other emulators. Except when I am tring to run any N64 games using the mupen64plus emulator. When I move the audio jack from the USB audio port to the onboard audio port I can now hear the sounds from the game. I Need help in reconfiguring the emulator so that the USB audio is the defaulted instead of the onboard audio ports.

Thank -you
Frank (KB0MMR)

[gerd]

Same problem here. Mupen64plus behaves way better than the libretro previous version, but it still lags. I even suspect the audio part is the the main cause of the lagging, but I don’t know how I could prove it.

Somewhere I’ve read something about increasing the audio buffer, but in the config file in retropie 3.3 this audio buffer doesn’t appear to be there.

[cjohnstone87]

Thought I’d report back.

Figured out that v3 of retropie just has 1 folder for each emulator.

Pressed button 0 (select for PS3 as standard) while loading a ROM and changed the default to mupen64plus(gles2n64).

All ROMs tried so far working good!

[cjohnstone87]

Hi Smithers

I used this latest build and have had no problems up until now.

My issue is there is only the libretro n64 emulator. The other emulator mupen64plus doesn’t seem to be there.

Is there any way to install this without having to start again?

Thanks in advance

[cjohnstone87]

Hi all,

I am trying to setup and run N64 Roms but I only have the n64 libretro emulator. I appear to be missing the n64-mupen64plus

Is there anyway to install this into retropie without having format and reinstall a new image.

I want to avoid that as I have openelec all setup on a seperate partition.

Thanks in advance!

[klaxx]

I have a RP with RetroPie 3.3 on it and was wondering what would be the best way to use all my controllers. I have 2 USB nes, 2 USB sega, 2 USB SNES, and 4 USB n64 controllers. I have a wireless keyboard and a USB hub that has its own power. I really do not need to have all these controllers plugged in at once but I can if it poses and issue.

Any ideas?

[catrinisin]

Hi All,

I performed the upgrade using the Retropie menu and it seemed to go fine. Everything still works, but I noticed that the N64 emulator has changed to default to Mupen64PLus. The website says that this emulator will autoconfigure controls when I do the initial setup in Emulation Station, however it didn’t seem to work.

After the upgrade, Emulation Station did make me redo the controller configuration which I did, and it works in all RetroArch emulators. But no controls work at all in the Mupen64PLus. What is the easiest way to get this working?

I’m using a Raspberry Pie 2 with an ipac2 controller which just acts like a keyboard.

Any help is greatly appreciated, I hope I’m not just missing some obvious NOOB thing. Thanks!!

[jeffdamann]

Hi, I have a wired PS3 controller which works fine in every other area of emulationstation and retropie.

When I load N64 games however, my left stick will press buttons randomly. If I press left or right on the left stick, I get inputs from up on the left stick, and the up and right c-buttons.

The controller is configured correctly. I even tried using lr-mupen and using the retroarch controls, same thing. I tried manually adjusting the retroarch controls, but they were already set perfectly.

What could be the issue?