Search Results for 'n64'

[brucem]

Awesome, thanks! I assume setup of n64 on arcade will always be limited, because you have fewer buttons and joysticks than on the n64 controller?

I never really used the original n64, anyone know which controls are least likely to be used in a game like mario64, I.e. which we could leave out of the key mapping and still start and play the game?

[dankcushions]

[quote=101987]With these settings, the overlay is being scaled with bilinear filter, which is blurring some of the scanlines and causing the moire effect you were describing. IMO this can be very distracting, particularly with vertically scrolling games.[/quote]
nope, it’s not being scaled. my overlays are 1080p, so if you set your retroarch video output to 1080p, no scaling takes place. i have scaled the scanlines ahead of time in gimp, but it seems to be a subtler effect, and not noticeable (to me) – see my screenshots.

the moire effect i’m describing is a feature of my TV (and others?) – i get it even when I’m using perfectly scaled 216 visible line games and 216 scanlines (5 x 216 = 1080 – I used a 1080p overlay of un-scaled 216 line scanlines, intiially), when the overlay opacity is too high. i think my panel doesn’t like concentric horizontal black lines and the brightness of them seems to waver (I have it set to ‘game mode’/post-processing off, of course).

i recommend folk fiddle with the setting to see what they like.

There are a couple incorrect assumptions you’re making, one of which is that most systems put out 224 horizontal lines of resolution, which is not the case.

…hence i’ve got the breakout section detailing the resolution of each system, as I check :) nes/snes, neogeo and megadrive are 224, which represents ‘most’ to me, but that’s my era I suppose.

[quote]If you’re losing important score/credit info, as you said you were at 5x scale, it’s likely because you are using 224 as the internal resolution instead of 240.[/quote]
nope, I was using 216 instead of 224, in the scenario I was talking about (this is the visible area you end up with when trying to 5x integer scale on a 224 line system). you can’t show 224 lines on a 1080p screen in a 5x integer scale (5*224=1120)

[quote]Also, regarding opacity, IMO you’re better off setting your display’s “backlight” setting higher to compensate for the loss of brightness. (This is not the same as the “brightness” setting). For example, with 4x scanlines at 100%, you would lose 50% light output, so you compensate for this by increasing the backlight by the same amount (eg., if your backlight is at 50%, you would turn it up to 100%).[/quote]My TV doesn’t have this setting :(

[quote]Also, regarding the dotmask shader, it will cause a drop in frame rate and input lag, but it is slight. I’m sensitive to these things, so it ruins it for me, personally.[/quote]Do you have a way of measuring this? None of the retroarch emulators seem to be able to display framerate for me.

[quote]With this said, could you please correct the misinformation contained in your post regarding the horizontal resolution of console systems? This kind of information can quickly and easily spread once posted, leading to more confusion and problems, and it works against the efforts of those who are working to preserve authenticity and accuracy. Thank you.

The correct horizontal resolution is 240 for NES, SNES, Genesis, PS1, N64, PC Engine. This can be readily corroborated by using Google and searching “internal resolution (system name)”

However, there are individual core differences and bugs where the internal resolution isn’t right, Picodrive being a notable example. So the correct resolution for a system may not be the “correct” resolution for an emulator.[/quote]sure, I’ve added a note on what I mean by ‘resolution’ in this guide

[patrickm]

With these settings, the overlay is being scaled with bilinear filter, which is blurring some of the scanlines and causing the moire effect you were describing. IMO this can be very distracting, particularly with vertically scrolling games.

I’ve detailed a way to get pixel perfect scaling at 1080p while cropping both the letterboxing (the black bars) and the overscan, so that the picture fills the vertical area of the screen and the scanlines line up perfectly without scaling artifacts, cf., “how to get perfect video scaling” and “how to get scanlines.”

There are a couple incorrect assumptions you’re making, one of which is that most systems put out 224 horizontal lines of resolution, which is not the case. If you’re losing important score/credit info, as you said you were at 5x scale, it’s likely because you are using 224 as the internal resolution instead of 240. What gets cropped at 5x scale corresponds exactly to the overscan area on an NTSC CRT TV. The remaining area is referred to as the “safe zone,” and game developers would always make sure that important game graphics were displayed within this zone (with a few rare exceptions), and they frequently made use of the overscan area to store information that the player wasn’t supposed to see (usually, to compensate for the variability in how CRTs were calibrated).

Also, regarding opacity, IMO you’re better off setting your display’s “backlight” setting higher to compensate for the loss of brightness. (This is not the same as the “brightness” setting). For example, with 4x scanlines at 100%, you would lose 50% light output, so you compensate for this by increasing the backlight by the same amount (eg., if your backlight is at 50%, you would turn it up to 100%).

Also, regarding the dotmask shader, it will cause a drop in frame rate and input lag, but it is slight. I’m sensitive to these things, so it ruins it for me, personally.

With this said, could you please correct the misinformation contained in your post regarding the horizontal resolution of console systems? This kind of information can quickly and easily spread once posted, leading to more confusion and problems, and it works against the efforts of those who are working to preserve authenticity and accuracy. Thank you. :)

The correct horizontal resolution is 240 for NES, SNES, Genesis, PS1, N64, PC Engine. This can be readily corroborated by using Google and searching “internal resolution (system name)”

However, there are individual core differences and bugs where the internal resolution isn’t right, Picodrive being a notable example. So the correct resolution for a system may not be the “correct” resolution for an emulator. I’ve saved you the work by providing a list of resolutions to use in “how to get perfect scaling.”

I haven’t tested Neo Geo, but I think it varied, with the most common being 264 with overscan (240 without)

[Jonathan Lundström]

Hey!

I managed to figure it out how to properly configure the N64 controllers for my iPac VE. The only thing missing is Z-support and D-pad, which I still don’t know how to configure.

I found the answer using this link in combination with the controller button reference.

I’ve posted my config below so that you can have a look at it as well. Keep in mind that plus is minus and vice-versa. The Y-axis is reversed.

# Keyboard player 1
input_player1_a = z
input_player1_b = x
input_player1_start = num1
input_player1_l = lshift
input_player1_r = v
input_player1_left = left
input_player1_right = right
input_player1_up = up
input_player1_down = down

# Keyboard player 1: Joystick
input_player1_l_x_plus = right
input_player1_l_x_minus = left
input_player1_l_y_plus = down
input_player1_l_y_minus = up

# Keyboard player 1: C-pad
input_player1_r_x_plus = "c"
input_player1_r_x_minus = "lctrl"
input_player1_r_y_plus = "space"
input_player1_r_y_minus = "lalt"

# Keyboard player 2
input_player2_a = i
input_player2_b = k
input_player2_start = num2
input_player2_l = w
input_player2_r = l
input_player2_left = d
input_player2_right = g
input_player2_up = r
input_player2_down = f

# Keyboard player 2: Joystick
input_player2_l_x_plus = g
input_player2_l_x_minus = d
input_player2_l_y_plus = f
input_player2_l_y_minus = r

# Keyboard player 1: C-pad
input_player2_r_x_plus = "j"
input_player2_r_x_minus = "a"
input_player2_r_y_plus = "q"
input_player2_r_y_minus = "s"

# Increases audio volume.
input_volume_up = num6

# Decreases audio volume.
input_volume_down = num7

I’ve also attached a photo showing a reference to which buttons and mapped to what in my layout as well as a photo of my build.

Hopefully this will help you configure your machine properly as well. Let me know if you manage to fix D-pad support! :)

Regards,
Jonathan

[Jonathan Lundström]

Hey mate,

I’m also using an iPac VE in my build and I’ve successfully managed to configure all keyboard buttons except for the ones corresponding to the joystick. I can’t figure out how to get “up, down, left and right” working. Have you got any clue?

So far, this is my config:

# Keyboard player 1
input_player1_a = z
input_player1_b = x
input_player1_start = num1
input_player1_l = lshift
input_player1_r = v
input_player1_left = left
input_player1__right = right
input_player1__up = up
input_player1_down = down
input_player1_l2 = nul
input_player1_r2 = nul
input_player1_l3 = nul
input_player1_r3 = nul

This is driving me crazy. And even more so because the config says:

Mupen64plus-libretro utilises RetroArch configurations. Add custom retroarch controls to the retroarch.cfg file in

/opt/retropie/configs/n64/retroarch.cfg
Yes, sure, but which custom controls?

Regards,
Jonathan

[doakey3]

I am editing /opt/retropie/configs/n64/mupen64plus.cfg

At the line that says:

Joy Mapping Stop = “”

I want to make a 2 button combo required to close the emulator. (having 1 makes it too easy to accidentally close the game)

I have tried
“J0B8+J0B9”
“J0B8 and J0B9”
“J0B8J0B9”

I can’t seem to figure it out. I don’t want to go through retroarch because it runs games with poor textures. Is this possible?

[herbfargus]

Under the experimental menu you can install one called mupen64plus testing- that has the best results for n64 games but even then they’ll still be hit and miss. I just stick with a PC for n64 games.

See this page:
https://github.com/RetroPie/RetroPie-Setup/wiki/Nintendo-64

Also each new release on the downloads page there is a changelog showing what has been changed/added since the last version. I also keep a page on the wiki updated as well: https://github.com/RetroPie/RetroPie-Setup/wiki/Changelogs

[herbfargus]

Your ROMs will still go in the n64 directory you’ll just have new options in the x or m menu as you load a ROM to choose those emulators. You can change the default emulator to your newly installed n64 emulator by pressing x or m as your ROM loads

[flexbt]

Using a Pi2B + Beta 3r4

I tried installing Mupen64plus and Mupen64plus-libretro via binaries and source. It appears like they are working when installed via source, the install goes on for a few minutes with a big ASCII “Mupen64″etc showing up, but the folders do not appear in \roms.

My questions:

Do I need to add them manually, or did my install fail?
How do you know which emulator is being used in the default \n64 roms folder?

[doakey3]

Thanks! I had considered just editing one of the already existing start up scripts, but I didn’t know which one to use.

In the end, I decided to use a different method of running my script. I learned that I could have the script called whenever I plugged in my controller by making a rule in the /etc/udev/rule.d folder. See

Mayflash N64 Controller Adapter

I was pretty disappointed though. I spent hours configuring my controller setup only to realize that n64 emulation is pretty bad. Most games run fast with the rice plugin, but for whatever reason, the menu textures are shot. I wonder if any future updates will correct these issues…

[polardude1983]

Howdy all,

I have 2 wii remote controllers connected to my raspberry pi. Both work and do connect. But most times when I try to play a playstation 1 or n64 game the controller seems to disconnect and I can’t reconnect it unless I turn off the system. This has happened very few times when playing a super nintendo game though. This happens even when I only have 1 controller connected and even took out the wireless dongle and just left bluetooth. Any ideas?

Pi Model: B+
RetroPie Version Used: 2.6 for Raspberry Pi 1
Power Source: input: 100-240V~50/60Hz 0.6a
Power Source: output: 5V—2.4A
Built From: SD Image
USB Devices connected: Bluetooth and wireless
Controller used: 2 wii remotes with classic controller
Error messages received: sometimes wii remotes disconnect when playing ps1,n64 games, or very seldom snes games
Guide used: the “An A to Z Beginners guide to installing retropie on a raspberry pi” Then used “wiimotes with classic controllers” guide from github
File: (File with issue (with FULL path))
Attachment of config files: (or use pastebin.com)
How to replicate the problem: How to replicate it for anyone else? unsure

[sekazi]

N64 is pretty much useless. It either runs too slow or the menus/gameplay is scrambled.

For MAME I have been filtering my set to be used with MAME4ALL, Final Burn Alpha and Neo Geo. I still have not messed with too many of the games but from the ones I did they seemed to run smooth.

[doakey3]

ok, with your controller plugged in type

lsusb

(That’s a lower cased ‘L’ by the way) This should give you the device info for your controller. for me there was a line that said,

Bus 001 Device 005: ID 0e8f:3013 GreenAsia Inc.

make a file by doing
sudo nano /etc/udev/rules.d/60-n64.rules

in that file put:

ATTRS{idVendor}==”0e8f”, ATTRS{idProduct}==”3013″, RUN+=”/opt/retropie/configs/n64/n64-config.sh”

replace the 0e8f and the 3013 for your device

now do

sudo nano /opt/retropie/configs/n64/n64-config.sh

and put:

#!/bin/bash
sleep 1
jscal -s 6,1,0,128,128,6882750,6627834,1,0,127,127,6882750,6795627,1,0,128,128,5592235,5592235,1,0,128,128,5592235,5592235,1,0,0,0,2147483647,2147483647,1,0,0,0,2147483647,2147483647 /dev/input/js0
jscal -s 6,1,0,128,128,6882750,6627834,1,0,127,127,6882750,6795627,1,0,128,128,5592235,5592235,1,0,128,128,5592235,5592235,1,0,0,0,2147483647,2147483647,1,0,0,0,2147483647,2147483647 /dev/input/js1

Now make that file an executable by doing:

sudo chmod 755 /opt/retropie/configs/n64/n64-config.sh

Now every time you plug in the controller, that script will be run and your joysticks will be recalibrated.

One gotcha is that the files need to be in unix format. I was writing the files on my windows pc and copying them over and ran into problems. To solve this I downloaded dos2unix for windows and converted them that way.

[doakey3]

I fixed this issue by typing

jstest /dev/input/js0 I observed the values of the joypads as I pushed them. I pressed ctrl+c to exit that and typed:

jscal -c /dev/input/js0

This allowed me to recalibrate the controller’s joypads. I ran

jstest /dev/input/js0

again and saw that the values had changed. I went to /opt/retropie/configs/all/retroarch.cfg
and edited the line:
input_autodetect_enable = true
and I changed it to false
For good measure I deleted my joypad’s auto config file by going to
/opt/retropie/configs/all/retroarch-joypads
and removed all files there.

I then went to
/opt/retropie/configs/n64
and edited the retroarch.cfg file there.

#include "/opt/retropie/configs/all/retroarch.cfg"
fast_forward_ratio = "2.0"

input_joypad_driver = "linuxraw"
input_device_p1 = "0"
input_player1_joypad_index = 1
input_player1_b_btn = 2
input_player1_a_btn = 1
input_player1_up_btn = 12
input_player1_down_btn = 14
input_player1_right_btn = 13
input_player1_left_btn = 15
input_player1_start_btn = 9
input_player1_select_btn = 8
input_player1_l2_btn = 8
input_player1_r2_btn = 7
input_player1_l_btn = 6
input_player1_r_y_plus_axis = +2
input_player1_r_y_minus_axis = -2
input_player1_r_x_plus_axis = +3
input_player1_r_x_minus_axis = -3
input_player1_l_y_plus_axis = +1
input_player1_l_y_minus_axis = -1
input_player1_l_x_plus_axis = +0
input_player1_l_x_minus_axis = -0 

input_enable_hotkey_btn = 14
input_exit_emulator_btn = 9
input_load_state_btn = 7
input_save_state_btn = 6

The important part about this file is to specify that you want the joypad driver to be “linuxraw”.

After doing this, link was able to run and I had no problems with the controls. Unfortunately, the joystick calibration will be undone at reboot.

You can use jscal -p to read the calibration settings.

Then call the function

jscal -s 1,6,128…..(a bunch of numbers) /dev/input/js0

ideally, you would have a script run at startup that would call this function for you, but I haven’t made it that far yet.

[doakey3]

I have a script that I’d like to run at start up, but for the life of me, I can’t seem to figure out how to make it happen. I’ve saved the file in /etc/init.d as
n64.sh and I did sudo chmod -x /etc/init.d/n64.sh

Now what?

#!/bin/bash
jscal -s 6,1,0,127,127,7354172,6710682,1,0,127,127,7158060,6627834,1,0,128,128,5,592235,1,0,128,128,5592235,5592235,1,0,0,0,2147483674,2147483647,1,0,0,0,2147483647,2147483647 /dev/input/js0

[doakey3]

I am using a mayflash n64 adapter with retropie 3.0 beta 4 for raspberry pi 2:

I have edited
/opt/retropie/configs/n64/retroarch.cfg
in order to create specific controls for the mupen64plus emulator (including hotlinks)

When I start Ocarina of Time in mupen64plus, all of my controls work, but when I push the joystick through it’s full range, link walks instead running. I have seen other threads where advice is given to edit
/opt/retropie/configs/n64/InputAutoCfg.ini

however, this file already contains a controller called [Linux: USB GamePad] and changing the AnalogPeak and AnalogDeadzone for my controller has no effect on the game (I don’t think the file is being used…). I don’t want auto controls anyway, I want to use the controls I have outlined in /opt/retropie/configs/n64/retroarch.cfg

I’ve also tried editing the ‘AnalogPeak’ value in /opt/retropie/configs/n64/mupen64plus.cfg but that hasn’t changed anything either.

Is there a way to adjust the joystick range for my mayflash n64 adapter? How can I make link run?

As a side note, I had this same problem with project64 on my pc, but in the controls window, there is an option to uncheck “Real N64 Range” and that fixed the problem entirely.

I have been at this for hours. Any help would be greatly appreciated.

[chooky536]

Hey People im just aksing what the best emulators are to use i dont care about 2 player support or anything like that just the best ones that run the games best.

1.Mame
2.N64

i have most of what i want running ok but with these two im having trouble booting roms mame runs extremly slow and n64 i think this video has fixed the menu issue for me https://www.youtube.com/watch?v=lh0n5PWN2lI but how he sets up the controllers for the non multiplayer emulator is that still how you need to do it, i just dont want to screw my install up and try again.

[Anonymous]

Are there any plans to upgrade mupen64plus to 2.5?

Also I’ve been using moonlight (previously limelight) version 2.0.1. It seems to work really well (I use it for steam games and also Dolphin by adding Dolphin to Steam). Not sure what it takes to move from experimental to stable but it seems quite stable to me :)

[fraybentos]

I have an RPi2 with Retropie that is working well. I use an XBOX360 wireless controller, but when playing the N64 games the N64’s trigger (Z) does not seem to be mapped to the controller

For example I can’t use powerups on Diddy Kong Racing, but other buttons seem OK.

I’m using the Mupen64Plus emulator for that particular game, whoch plays well

How can I fix the N64 button mapping for all N64 games?

Thanks

[brucem]

Hi there, I’ve done heaps of reading and can’t figure out the names of all the key bindings for retroarch.cfg – I’m currently using the libretro-mupen64plus, but could also use the non-libretro if need be?

I’m actually trying to set up an IPAC which shows up as a keyboard via USB, but any general help in keyboard bindings will help.

Thanks

[rasmushauschild]

Hi, So I actually got the thumbstick working, by copying and pasting the analog thumbstick code from a PS3 controller-config file. But when I try to walk around in super mario 64 he’s walking so slow. I think this is because my thumbstick is the same as you would find I a PSP (it’s very small compared to a regular thumbstick).
So how can I change the code, so retroarch knows the max value of the thumbstick (so that when I press it all the way the forward Mario will run (as if played with an original n64 gamepad) instead of walking very slow.
Thanks

[whonx]

I just received a Raspberry Pi 2, and I intended to use it as a PSX emulator. I already had a RP1 (model B 512MB) with retroarch (retropie-v3.0beta2-rpi1) running and configured. More or less everything worked properly. I even installed Kodi and some server tools. In short, it’s something that took me weeks to properly configure.

When the RPI2 arrived, I just swapped the microSD and it booted and everything seemed to work properly. However, despite the performance being somewhat better, PSX emulation is still choppy, and N64 emulation does not work at all (roms launch, I heard some sound but nothing appears on screen).

I realized that, in the download section, there are two images: one for RPI1 and another for RPI2. What is the difference? Maybe the performance issues may be related to this?

Please help!

[rasmushauschild]

Hi, I’ll try that config-file tomorrow.
Thank you so much, for putting this much effort into helping me out! :)

A very important thing for me is to have a full analog thumbstick, since I love n64 games. And I don’t think you can have that, if the Teensy is programmed as a keyboard, but I might be wrong?
In the directory “/home/pi/.emulationstation/es_temporaryinput.cfg” there is a configuration-file for my keyboard. i’ve posted a picture of the file here: http://minifactory.dk/test.html
Thanks again :)

[k3nni]

jfmanamtr: Were you able to successfully use the Logitech F310 controller to work on all emulators? More specifically MAME, NES, SNES, SEGA GENESIS, N64 & PlayStation?

[k3nni]

strawberrytau: I am looking at purchasing this controller. Does the Logitech F310 work on all emulators? -NES, SNES, SEGA, GENESIS, MAME, N64, AND PlayStation?

[sekazi]

I have been working on it as I have had time. There will potentially be 4 layout choices in the theme.

original
boxart + list
boxart + no list
classic es

I am going to see if I can get a hold of Florian Hurtaut somehow as I am basing the theme off of his and I use a few assets from his theme. His theme was for ES 1.x so it was not supported in the latest version. I have reworked the majority of the assets he had and I have made it look better at 16:9 vs his 4:3.

When I release the theme I will be including the asset files used so it can be easily changed by someone else if they so choose.

The emulators being themed are

atari2600
gamegear
gb
gba
gbc
mame
mastersystem
megadrive – genesis
n64 (maybe one day the emulator will not be useless)
nes
pcengine – turbografx
ports – doom
sega32x
snes
retropie

[dirkdigduggler]

With N64 perhaps you are using the 3.0 image? That’s what I am using and found that my N64 folders were different from his. I gave up on N64 anyway in the end, it’s just too janky to be worth messing with: stick with what Retropie does well :)

[callumhurley]

Okay so it turns out I just had to run the Retroarch autoconfig while connected to the Internet. My analog stick works for N64 too! Haven’t tested PS1 bur glad it all sorted. I have a bluetooth dongle too, would I be able to connect my DS4 via bluetooth?

[dragonjarvis]

Hello dear Forum :)

I freshly installed the latest retropie version on my raspberry Pi 2 and i updatet the script etc with help of this tutorial!

: Binary Tutorial

After that I followed another tutorial to get the psx emulator running.

: PSX Tutoral

HOWEVER after I followed the second tutorial my PSX section on emulation station was completly GONE!

I followed this tutorial carefully step by step.
I don’t know where I messed up and I hope you guys can help me out!
Primaly i want to play european and german psx n64 and dreamcast games.

Oh before I forget, i tried to follow this tutorial aswell!

: N64 Tutorial

But at 0:50 you see that this gentleman has 2 n64 emulatiors and I only have one.
This confused me so i did not follow that tutorial any further.

If you could explain me what I need to do or send me a guide/ tutorial which explains me step by step how i config these emulators properly you would be a HUGE help!

I am looking forward to your answers! :)

[herbfargus]

It will be updated eventually to include non-retroarch emulators but it may be a bit before that happens so until then You’ll need to configure them manually. (I.e. fba, mame4all, advmame, reicast, jzintv, mupen64plus, etc.)

[fleppi2001]

Hi guys,
I just started out with Pi 2 B, and Retropie 3 BETA 4.

I cant get N64 and NES games to work? SNES seems to work fine though.
Error message is “core couldnt load rom”.

Ive tried all 3 emulaters and different ROM’s…doesn’t make any difference.

Has anyone an idea what i should try to do?

Thanks so much already for reading

// PS1 works awesomly aswell

[callumhurley]

So I bought the Mayflash N64 Controller Adapter and it works perfectly fine in the menu (despite some analog stick issues), but the retroarch controller config does not recognise input whatsoever. Has anyone else had an issue like this and resolved it?

[poochie]

Hey guys,
i am configuring retropi only over ssh since i dont have an usb keyboard. Since 3.0 n64 emulators use the same rom folder. libretro emulator is set as the standard emulator and it can be modified pressing x or m on emulator start. Since i dont have a keyboard i cannot enter this menu. How can i change the settings over ssh. Or is there a simple way to access this using my laptop keyboard?

[petrockblog]

Overclocked ? Which emulators ? Don’t expect fullspeed n64 on the rpi1 though.

[herbfargus]

If you are interesting in using emulation station with more emulators that require more processing power like the n64, GameCube, Wii, etc you can get it setup on your pc. I created a video about it, I’m going to try and update it with more emulators this week or next.