Search Results for 'n64'

[tboheeren]

Hey all,

A couple of you asked me to do some more testing on specific games or emulators.
You can find them all here: https://www.youtube.com/playlist?list=PLShJegxSSfSJg59b_AIj4phMFrsK7x8Kl

gz

[shoothere]

As malacai said:

Overclocking the Pi2 to Pi2 setting made PSX games run pretty much flawlessly for me.

N64 is not so much a speed issue as an optimisation issue. If you turn down the resolution to 640×480/VGA the games getting that nice retro fuzzy look :) and also run rather smooth.

To check which emulator is best to use for which game (if it works at all) check this list:

https://docs.google.com/spreadsheets/d/1Wjzbu90l6eCEW1w6ar9NtfyDBQrSPILQL5MbRSpYSzw/edit

Hope this helps!

[malacai]

psx works both flav on a a rpi2 and a rpi3
n64 not that good in either system. but atm no emu is using the benefit of the new cpu.

[cooky069]

I got my pi3 up and running today . Psx is now running with enhanced resolution on, psp runs much better with less freezing. I’ve tried n64, still not impressed but it’s one system I only just started playing around with. Bluetooth sort of works but I have to manually reconnect my nes30pro every reboot , it works in game ok tho. Wifi connects to my network and I can update but don’t seem to be able to connect to the pi with putty or samba shares. However if I use my old dongles from pi2 it all works as before

[dbalkz]

The pi 3 has been out for a few days now and i’m not sure where to look around to see if anyone’s tested how well retropie runs on it (since from what i’ve gathered it’s not fully updated yet) and i’m also wondering for those who have gotten it to work: has anyone properly tested n64 and psx? i think this is really the only thing holding me back from purchasing the new pi. if it’s found that these systems play better than on the rpi2, i’d gladly upgrade.

[Anonymous]

Nice one. Whats the performance like for N64, PSP, Dreamcast? Did the built in bluetooth and wifi work atomatically? What version of Retropie are you running? Thanks

Mine is arriving tomorrow!

[cortex]

[quote=118490]I’d like to know how well the n64 and PSP emulators work Oh and maybe the Saturn one to Hehe

[/quote]

Oh yes, fullspeed or at least a really playable speed for all n64 games would be so awesome!
Please let us all know if you tested it :-)

[rafaelr]

Hello everyone!

I am a Brazilian fan of RetroPie project, I already made a small donation to thank and plan to collaborate again for this amazing project!

I have a little problem in the boot, on emulationstation loading, in versions 3.4 and 3.5 of Retropie.

I have the following collection of roms I use on my SD card:

Atari 2600: 772 roms
AdvMAME: 6.158 roms
Mame4ALL: 2.271 roms
Master System: 457 roms
Mega Drive: 1.502 roms
N64: 2 roms
NES: 1.345 roms
SNES: 2.883 roms

I use the “scraper” by SSELPH to download the covers in JPG and generate the “gamelist.xml” on my PC, and then move to the Raspberry Pi 2 (the scrap in RPi2 is very slow!).

In version 3.1 of RetroPie the boot was faster, some took more than one minute to load the system and emulationstation.

In versions 3.4 and 3.5, after it was used the “Jessie” version of Raspbian, the Emulationstation loading is too slow! After the system load (black screen with the letters passing), when it arrives on the screen “Loading Emulationstation” takes forever!!!

Compared the load times, in the moment you turn on the RPi2 until the system is ready for use in emulationstation screen emulators selection:

Version 3.1: 1 minute and 20 seconds.
Version 3.4/3.5: 3 minutes and 40 seconds!

It is almost triple(!) time with the same amount of ROMs!

I noticed that in versions 3.4/3.5 if I do not use the scrap files (JPG images and gamelist.xml files), using the “gamelist.xml” files blank, the system loads quickly! So it seems that the delay problem to load the emulationstation in versions 3.4/3.5 is related to the use of scraps, perhaps in reading the files “gamelist.xml”.

Does anyone have a solution to get around this?

I thank the attention.

Att .;

Rafael

[chamelious]

Brand new Rpi2, brand new install of newest Retropie build. Wired xbox360 controller. HDMi to samsung tv.

Problems:

Snes games are unplayable due to input lag. Feels like at least half a second.

N64 games are unplayable due to sound being all over the place. Actual games feel ok. Have tried uncommenting out the “hdmi drive 2” option.

Thanks

[Anonymous]

Agreed a bit strange how they just suddenly released this with no mention or hype. I only bought my Pi2 in December. Am ordering Pi3 from RS Online. At least i can use the case/fan from my Pi2.

I’m just hoping the built in Bluetooth will finally resolve everyones bluetooth problems, and just maybe the N64/Dreamcast emulator will be able to run smoothly for Goldeneye/Virtua Tennis! Fingers crossed.

@Floob will you be updating the Wiki for set up on Pi3? Is there any talk of building retropie with 64 bit architecture?

[wermy]

It would be awesome if you could report back on how well more demanding systems like N64 and Dreamcast run. :)

[jynxbone6986]

I figured out the n64 keyboard config. https://www.petrockblock.com/forums/topic/ipac-2-n64/
And u can use it without a joystick if u set the buttons in the joystick section. I cant get 2 players working though. If u just want to use controllers just configure that through emulation station. And each controller has to be in a different usb port on the pi.

[retroresolution]

Ordered mine from RS Components in the UK today, hopefully being delivered tomorrow.
Really hoping for full-speed 32X, enhanced resolution PlayStation on most or all games, and more playable n64 titles.
If I can help with testing, please let me know.

[dankcushions]

bought! pretty incremental improvement but i think a few things should be pushed over the line as most things we deal with are CPU-bound. i’m hopeful for powerdrive and afterburner type games running better/perfect, PSX at double-resolution mode with no slowdown, and N64 improvements (maybe even becomes ok to use GlideN64 plugin all the time?), but the lack of GLES3 is a shame. no vulkan or anything like that.

[InsecureSpike]

this may mean i’ll have to look into setting up the N64 tomorro to test, are there any vital topics/threads i’ll need to read up on?

[ronoh55]

The “safe” overclock for the pi2 is 1.0 Ghz, so my guess will be 1.3-1.5 will be the “safe” overclock for the pi3. I’m just hoping this helps big time with the n64 and psp emulations!

[smartroad]

I’d like to know how well the n64 and PSP emulators work :D Oh and maybe the Saturn one to Hehe

[catrinisin]

Yes Floob is correct, the default N64 emulator does not use the retroarch config. If you don’t want to use the lr version as suggested above, you’ll need to map your controls in this file:
/opt/retropie/configs/n64/InputAutoCfg.ini

[catrinisin]

Hi,

Yes, I did make progress by editing the file you mentioned. It took some trial and error but I did get it working with my wireless xbox controller. It actually works really well and I’m happy with it. I have not yet tackled getting a second controller working but will try that soon.

The ipac controller I was using for other emulators won’t ever work for N64 since this system requires the analog stick. PSX also has analog but is playable with the 8 way joystick that the ipac is connected to in my setup.

[Floob]

The file you edited is for retroarch emulation, but it looks like you are using the non-retroarch based emulator.

Try using the lr-mupen64plus
https://github.com/retropie/retropie-setup/wiki/Nintendo-64

Although to be honest the N64 is one of the trickier systems to get up and running as a lot of the games still arent that well supported.

Are you going to set it up with the arcade emulators?

[kazevil]

Dear all,

I just got a picade console and though I could make it run with a rasp pi2 and retropie.

I got everything built up and installed in just few steps but I’m now facing a controller issue.

At first boot the picade console (joystick + buttons) is not automatically detected. After holding a button it s seen as a keyboard and the keys mapping setup works fine.
Once in emulstation I can use it to navigate through the interface without any issue. Playing Doom works fine too.

I then try to copy som n64 roms and play with. Unfortunatelly in the game the button mapping is not working anymore… So I can’t do anything except exiting the game.

Looking to /tmp/runcommand.log, I could found such messages:

UI-Console: using Audio plugin: 'Mupen64Plus OMX Audio Plugin' v2.0.0
Input Error: Couldn't find config file 'InputAutoCfg.ini'
Input Warning: missing 'plugged' parameter from config section AutoConfig0. Setting to 1 (true).
Input Warning: missing 'plugin' parameter from config section AutoConfig0. Setting to 1 (none).
Input Warning: missing config key 'DPad R' for controller 1 button 0
Input Warning: missing config key 'DPad L' for controller 1 button 1
Input Warning: missing config key 'DPad D' for controller 1 button 2
Input Warning: missing config key 'DPad U' for controller 1 button 3

This looks like the key mapping is not recognized. So I went in /opt/retropie/config/all/retroarch.cfg and could see there my key mapping schema.
I tried copying following lines in /opt/retropie/config/n64/retroarch.cfg

input_remapping_directory = /opt/retropie/configs/n64/
input_player1_a = z
input_player1_b = shift
input_player1_y = ctrl
input_player1_x = alt
input_player1_start = enter
input_player1_select = escape
input_player1_l = space
input_player1_r = x
input_player1_left = left
input_player1_right = right
input_player1_up = up
input_player1_down = down
input_player1_l2 = s
input_player1_r2 = c

Unfortunately this didn’t help.
Looking again in the log file I could see this:

Input: 0 SDL joysticks were found.
Input: N64 Controller #1: Forcing default keyboard configuration
Input Error: Couldn’t find config file ‘InputAutoCfg.ini’

If anybody has some advice on the setup, it would be great :-)

Cheers

[jynxbone6986]

for retroarch in opt/retropie/configs/all/retroarch.cfg copy all the input_player1 lines but make them input_player2 and put the correct button mapping.
For mupen64plus id like to know too. Ive read that in /opt/retropie/configs/n64/AutoInputCfg.ini you do the same thing but put
__NextController:
inbetween first and second player controls. That didnt work for me though

[jynxbone6986]

Figured it out. For anybody using keyboard or ipac. It is the /opt/retropie/configs/n64/InputAutoCfg.ini file. If you dont have it plug in a controller and go through the controller config from emulationstation start menu and it will create one. Then change controls for the keyboard in that file. I found the keys from http://www.vizzed.com/boards/thread.php?id=79869

[jynxbone6986]

Im having the same problem. I think we need to edit /opt/retropie/configs/n64/InputAutoCfg.ini but we need the button id’s[key(102)] instead of “num1”. Have you made any progress with this?

[jynxbone6986]

I have arcade cabinet with pi2 retropie 3.5 and ipac2 for controls. Configured retroarch controls and mame fine but cant figure out mupen64plus. The InputAutoCfg.ini file wasnt there(im guessing because i havent connected a “controller”,just the ipac) but i put one in from another pi that i had connected one to. With that it gets input from a keyboard but not the right buttons. I cant run jtest on the ipac so how do i find the key id’s? ex. key(104)
Has anybody had success with ipac on mupen64plus?

[sito00]

[quote=118370]You can improve perforamce if you lower video resolution. A PI2 will never play the majority of n64 games without hiccups, lag and so on.

[/quote]

How do to lower the video resolution ?

[gizmo98]

You can improve perforamce if you lower video resolution. A PI2 will never play the majority of n64 games without hiccups, lag and so on.

[sito00]

Hello, I would like to know if there algona way to run well nintendo 64 emulator without the video or sound is cut .

No information meeting just because I am Spanish and I do not understand English .

I hope you can help me.

[Gnuku]

exactly same problem with 3.5 for n64
for gamepad: d-pad and left analog are reversed, and hotkeys don’t work (like “select + x” to access RGHU). Also new scrappers can no longer be memorized after saving for n64 only. Only n64 is like that

[somebody]

I agree that it is depending on the game. If you’re playing something with decent graphics like N64 or GC, i’d probably use smooth. Anything that takes it’s charm from being pixelated though, definitely off. For what I mainly do on my Pi, I’d prefer off. But then again, I don’t know how to turn it on or off…

[mw99]

[quote=118248]Just an FYI you won’t get great performance on most n64 games. The pi just isn’t up to the task of emulating most 3D systems.

You should be able to fix the audio output however. I imagine it’s most likely working, but probably being output on the HDMI jack as is the default as far as I know.

[/quote]
The actual game performance when using gles2n64 isn’t that bad. I have set the audio to go out the 3.5mm jack in the RetroPie setup and raspi-config. The sound works fine on other emulators.

[quote=118252]Use audio-sdl audio plugin and reduce screen resolution to VGA.

[/quote]
Would I switch that in the mupen64plus config? How would I go about changing the resolution to VGA?

Thanks!

[labelwhore]

Just an FYI you won’t get great performance on most n64 games. The pi just isn’t up to the task of emulating most 3D systems.

You should be able to fix the audio output however. I imagine it’s most likely working, but probably being output on the HDMI jack as is the default as far as I know.

[mw99]

RPi 2 Model B
Latest RetroPie image with everything updated
Audio – speakers via 3.5mm jack

When using mupen64plus-gles2n64/gles2rice/GLideN64 there is no sound output and the controls are not quite how I want them. lr-mupen64plus has sound output and proper controls, but in Mario Kart 64 the graphics are screwed up, the shadows in Star Fox are messed up, and Super Mario 64 is just plain laggy.

What do I need to do to get the sound working? I looked in the mupen64plus config file but didn’t see anything…

Thanks!

[herbfargus]

Not without some hardcore hardware skills, coding experience on the pi and a recoding of the n64 emulator

[jsawhi]

I had the same issue. While it can be done (I did it for my SNES case), I had to solder a couple of pins to the powerblock (see this post: https://www.petrockblock.com/forums/topic/snes-gpio-config-with-power-block/)

Using a different power controller would probably be your best best if you don’t want to solder or do anything like that (and if you live in the US will be cheaper and arrive faster than from overseas).

That said, I have a Mausberry power controller in my N64 conversion console. While it works, it seems a bit more no-frills vs the powerblock. It works, but it’s basic. no LED indication of what’s going on (power up or down), have to solder a pin in for the LED, not a service that runs, just an endless loop script that polls for the switch to send the shutdown command. I like the powerblock better (and it supports the project). The ATXRaspi is another power controller I have in my C64 conversion (yeah, I know) and I like it, but it only works with momentary switches so not a good fit for the SNES/N64 case.