Search Results for 'n64'

[j2k15]

Thanks puck6t9.
I’ll follow your recommendation posted here :

N64 problems…

[eymano]

Hi, thx for your reply!:)

Hm ok, but the gfx problem only apears when im using the N64 emulator namned only N64 (when im extract all Roms in folder N64).
When im using emulator mupen64plus (add all the Roms to folder mupen64plus) the gfx works fine but then the controller doesnt work..

Do u think it can help to do the expermentall install anyway?.

Ok, i have tried both to copy the controller settings il get when im configurate my controller to retroarch (UBS_retroarch.cfg) to autoinput.ini.file.
Am also try to Add the controller information u wrote, but for my gamepad ofcurse. But nothing works.

Can anyone show me exactly what i have to add to autoinput.ini.file according to my snes controller? :)

[puck6t9]

[quote=93598]– For N64, I also use the RetroArch emulator in order to get benefit from all the standards (UsbGamepad.cfg). The problem is that Mario Kart M3 (E) ! rom is a mess on that emulator. Even the “press start screen” is buggy. Again, are there some settings that would enhabce the emulation ? I hope so because I never read elsewhere that someone had such an issue with that rom. FYI, this rom plays nicely on other emulators and on other platforms also.[/quote]

useing the expermintal mupen64plus package fixed that for me. Also if you will just add your controler to the autoinputconfig.ini in the configs/n64 folder it will see your game pad and remap it (with out using retrorarch i understand but it worked better.)

[gizmo98]

Please post your controller config so we can add your controller to the mupen64plus repo. I have seen it on the other thread.

[puck6t9]

no this is what i did.. Start the Pi when emulationstatin starts go to retropie then run retropie-setup.

then do a update retropie setup script.
then setup / configuration and the update APT packages (dont know if this is needed but i did it.

then go back a page and do experimental packages.
then on mine it was the second one “mupen64plus-testing”

it will then download and build the package. do a reboot when it finishes.

when emulation station starts back up go to Nintendo 64 click on a rom and as soon as the screen goes black hit X on the keyboard a window will come up where you can change the default emulator or set a emulator for just that rom. I changed the default to the mupen64plus-testing-rice one.

there is no mupen64plus folder in the beta 2 image. it only uses mupen64plus as far as i can tell so unlike the old one there is no need to install 2 n64 emulators. that’s what worked for me. so that means mupen64plus is already config to use the n64 folder.

after all that i had the edit the configs/n64/mupen64plus.cfg file to add a button the quit the game and add my joy pad button mapping the the autoinput.ini file in that same folder

[puck6t9]

try the expermental mupen64plus. you can install it from the retopie setup/source based installs. fix most all gfx problems i have on mine. as for the controller mupen64plus wont see it unless it is in the autoinput.ini file in the configs/n64 folder. i had to take the save file that retroroach made for my controller and add it to that INI file then mupen64plus used it. i had to add this to that file..

[Jess Tech GGE909 PC Recoil Pad]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
DPad R = hat(0 Right)
DPad L = hat(0 Left)
DPad D = hat(0 Down)
DPad U = hat(0 Up)
Start = button(9)
Z Trig = button(7)
B Button = button(0)
A Button = button(2)
C Button R = axis(3+)
C Button L = axis(3-)
C Button D = axis(2+)
C Button U = axis(2-)
R Trig = button(6)
L Trig = button(4)
Mempak switch = button(10)
Rumblepak switch = button(11)
X Axis = axis(0-,0+)
Y Axis = axis(1-,1+)

[danipoak]

Did you have to do something special on the source based install to get the experimental packages? When I did my sourced based install I ran the following:
sudo ./retropie_packages.sh mupen64plus
As far as the rom folder goes, did you just create a folder on your own called mupen64plus or was there automatically a folder with that name? I can create a folder easily enough but I don’t know how to tell mupen4plus where that folder is. I have been going through all the configuration files I can find for the emulator but I haven’t found any reference to a rom directory.

[puck6t9]

i got my problems fix… the n64 folder is mupen64plus. they changed it so you can push x or m at rom start to change the plugin used like Rice. more over do a source based install of the mupen64plus experimental packages then use the rice version. it run things a lot better. back up your config file like for your controller it will replace all settings back to default. also it seems that mupen64plus uses it own config file the mupen64plus.cfg i had to edit it i was getting no sound because i was using a HDMI to DVI converter to use a monitor and using the audio jack for audio even tho retro pie was using the jack mupen64plus was still trying to use the HDMI. also had to add my controller to the autoinput.ini file for it to see the joy pad. was alot more work then i thought for setup.

[danipoak]

I am having similar problems as you’ve stated so maybe a second post will get some more attention. I realized that the beta 2 image actually didn’t have mupen64plus installed, at least for me it didn’t seem that it was as there was no roms folder for it. Did you have a mupen64plus folder or just the n64 folder?

I tried doing a source based installation of mupen64plus but there is still no roms folder for it. I read through some of the console history and found this:
UI-Console Error: no ROM filepath given
So it seems that I should just be able to create my own folder but then I need to somehow tell mupen64plus where it is.

[genesisflux]

If I knew how to make screenshots I would to post.
I have my controls, and preferences set up on Mupen64Plus now and using the Rice plugin yields the best results, but the lighting is all very strange. In Super Mario 64 Mario is very dark, and there appear to be odd shadows everywhere. It certainly doesn’t look anything like the original lighting. Do I have a setting changed that I shouldn’t have?
The game is still playable, I’m hoping someone can help me iron this out though.

[eymano]

Hello!

I got som big problems N64 emulation on my retropie.
Im use the newest raspberry pi 2 (1gb) with retropie 3.0.

My problems:

1. If im using the emulator N64- mupen64plus everything works great except the controllers because it doesn´t work with retroarch controller settings.

And if I use the emulator N64 retroarch controller settings works fine, but all games are lagging so bad! I cant start any game or anything.

So my question is: Can someone help me fix the controller issues for N64mupen or the video problems for N64.

Im using a USB SNES gamepad (not the best for 64, i know, but it will work for now).

Plz Help.

[ziggy]

Hello everyone,
Just got my new RPI2 and it’s great.
Been fiddling around with it all last night, got most emulators up and running fine.

Unfortunately I’ve managed to mess up my retroarch.cfg file in the n64 folder, no roms are loading anymore.

I’d like to avoid reinstalling everything, is there any chance someone could hook me up with a working set of N64 config files for RetroPie 3.0 Beta 2?

Thanks in advance.

[xvyion]

My hope is that I can eventually play Legend of Zelda: Ocarina of Time. However, right now it is unplayable and I’m hoping the internet can help. I have tried two ways to get this working, one through RetroArch as the latest RetroPie comes configured to do natively. The second with just mupen64plus without retroarch on top. I’ve had different problems with both. And I’ve been Googling my problems for a week now with no luck figuring these things out. As a note, I have a retrolink USB N64 controller.

First, Mupen. This one is the simpler of the two to describe. My only real issue is that after playing for about 10 minutes, my controller becomes unresponsive. This happens with any N64 game I’ve tried, not just OoT. That makes it unplayable. I’m also having an issue saving (save states not working), but I haven’t really looked into that problem yet because of the controller issue. I haven’t found any reason for the controller issue to be happening yet, and the controller works just fine with any other emulator (played Doom for an hour without issues as well as other games). Oh, and the keyboard is fine and I can exit the game using ESC no worries. Then when EmulationStation loads up again the controller is still fine.

Second, RetroArch. The biggest problem I’m having is that the default controller configuration seems to be wrong. Now, I know that Mupen has it’s own configuration file. That isn’t the problem. Mupen’s controls are configured fine (I know this because as I described above I don’t have this issue when running with just Mupen). It even loads up and states the controller (Generic USB Joystick) that Mupen is using just like it does when I run the game with only Mupen. However, with RetroArch on top when I get to the menu the start button works correctly as does the joystick, but the left C button acts like it is the A button and nothing else has any effect. Also, the keyboard stops working correctly too. The enter button works as if it were the A button on the controller and that is all. ESC no longer exits the game. I’ve been able to reconfigure the controller with retroarch-joyconfig, but I haven’t found a configuration that actually makes the game playable yet.

Additionally for RetroArch, the graphics and sound are messed up. I can’t describe it better than that. Certain textures are a bit off and certain layers (health bar) don’t seem to be displayed at all. The sound crackles a bit at times though I haven’t gotten passed starting a new game thanks to the completely useless controller settings. This is all using the same configuration (for Mupen) as with just Mupen above (which doesn’t have any noticeable video or sound issues).

If anyone has any thoughts on either of these directions I’d be grateful. Ideally I’d like to figure out the Mupen only approach since it seems the least buggy so far, but I’d be happy with either.

[j2k15]

Hi Gaucho,

I configure my controllers by registering them as a retroarch one.

But I have not tried yet with N64 ones and don’t know the RetroArch mapping between N64 specific buttons and RetroArch controller ones (e.g. which key to press when I’m requested to press R2, …).

For the image, it has probably to do with the resolution that does not match with your monitor one.

Regards.

[killefer762]

I started out with the raspbian desktop and then installed retropie and updated by sources. Everything seems to run fine except there is no sound playing n64 using mupen64plus. Using retroarch n64 is the sound is fine. Any ideas why? I just didnt use the retropie image as I am dual booting with noobs with openelec.

[puck6t9]

you said you did setting for zelda majoria’s mask i can get it to load but it is missing textures. like the side of the buildings are just black. any idea how to fix it? i have tryed and changed every setting nothing works. here is my current rice settings

# Control when the screen will be updated (0=ROM default, 1=VI origin update, 2=VI origin change, 3=CI change, 4=first CI change, 5=first primitive draw, 6=before screen clear, 7=after screen drawn)
ScreenUpdateSetting = 7
# Frequency to write back the frame buffer (0=every frame, 1=every other frame, etc)
FrameBufferWriteBackControl = 1
# If this option is enabled, the plugin will skip every other frame
SkipFrame = False
# If this option is enabled, the plugin will only draw every other screen update
SkipScreenUpdate = True
# Force to use texture filtering or not (0=auto: n64 choose, 1=force no filtering, 2=force filtering)
ForceTextureFilter = 2
# Primary texture enhancement filter (0=None, 1=2X, 2=2XSAI, 3=HQ2X, 4=LQ2X, 5=HQ4X, 6=Sharpen, 7=Sharpen More, 8=External, 9=Mirrored)
TextureEnhancement = 6
# Secondary texture enhancement filter (0 = none, 1-4 = filtered)
TextureEnhancementControl = 0
# Frame Buffer Emulation (0=ROM default, 1=disable)
FrameBufferSetting = 0
# Render-to-texture emulation (0=none, 1=ignore, 2=normal, 3=write back, 4=write back and reload)
RenderToTexture = 3
# Force to use normal alpha blender
NormalAlphaBlender = False
# Use a faster algorithm to speed up texture loading and CRC computation
FastTextureLoading = False
# Use different texture coordinate clamping code
AccurateTextureMapping = True
# Force emulated frame buffers to be in N64 native resolution
InN64Resolution = False
# Try to reduce Video RAM usage (should never be used)
SaveVRAM = False
# Enable this option to have better render-to-texture quality
DoubleSizeForSmallTxtrBuf = False
# Force to use normal color combiner
DefaultCombinerDisable = False
# Enable game-specific settings from INI file
EnableHacks = True
# If enabled, graphics will be drawn in WinFrame mode instead of solid and texture mode
WinFrameMode = False
# N64 Texture Memory Full Emulation (may fix some games, may break others)
FullTMEMEmulation = False
# Enable vertex clipper for fog operations
OpenGLVertexClipper = False
# Enable/Disable SSE optimizations for capable CPUs
EnableSSE = False
# Use GPU vertex shader
EnableVertexShader = True
# If enabled, texture enhancement will be done only for TxtRect ucode
TexRectOnly = False
# If enabled, texture enhancement will be done only for textures width+height<=128
SmallTextureOnly = False
# Select hi-resolution textures based only on the CRC and ignore format+size information (Glide64 compatibility)
LoadHiResCRCOnly = True
# Enable hi-resolution texture file loading
LoadHiResTextures = False
# Enable texture dumping
DumpTexturesToFiles = False
# Display On-screen FPS
ShowFPS = True
# Use Mipmapping? 0=no, 1=nearest, 2=bilinear, 3=trilinear
Mipmapping = 2
# Enable, Disable or Force fog generation (0=Disable, 1=Enable n64 choose, 2=Force Fog)
FogMethod = 0
# Color bit depth to use for textures (0=default, 1=32 bits, 2=16 bits)
TextureQuality = 0
# Z-buffer depth (only 16 or 32)
OpenGLDepthBufferSetting = 16
# Enable/Disable MultiSampling (0=off, 2,4,8,16=quality)
MultiSampling = 0
# Color bit depth for rendering window (0=32 bits, 1=16 bits)
ColorQuality = 0
# OpenGL level to support (0=auto, 1=OGL_1.1, 2=OGL_1.2, 3=OGL_1.3, 4=OGL_1.4, 5=OGL_1.4_V2, 6=OGL_TNT2, 7=NVIDIA_OGL, 8=OGL_FRAGMENT_PROGRAM)
OpenGLRenderSetting = 0
# Enable/Disable Anisotropic Filtering for Mipmapping (0=no filtering, 2-16=quality). This is uneffective if Mipmapping is 0. If the given value is to high to be supported by your graphic card, the value will be the highest value your graphic card can support. Better result with Trilinear filtering
AnisotropicFiltering = 0

[gizmo98]

Mupen64plus.cfg button mapping looks like JxBy. J=joystick number, B=button If you have a ps3 controller as js0 and want to use ps button to exit the correct syntax is J0B16.

[puck6t9]

find your joystick config file. the name that come on in yellow writing when starting a emulator. then add that to the inputautocfg.ini file in the /configs/n64 folder. worked for me.

[puck6t9]

i fixed the first to by editing the the mupen64plus.cfg file and the InputAutoCfg.ini file in the /opt/retropie/configs/n64.

just when you edit the inputautocfg.ini file to remap buttons it does it for all games running that profile. just look in the file for the name of the controller your using and remap the keys the same as the retroroach.cfg

the last im still looking for has to do with changing the mupen64plus.cfg where it says

# Joystick event string for stopping the emulator
Joy Mapping Stop = “”

i like to know if you find what to put there.

[elektrosteve]

Hi everyone,

I managed to fix Mario Kart 64’s distorted menu fonts using dappsy‘s solution from here and the recommendation from mupen64plus’s compatibility list, which is switching the emulator/video driver by using the config wizard on emulator startup.

Unfortunately, doing so would cause follow-up issues:

• My system sound level (alsamixer) that has been respected before is ignored now, audio is put out at full volume.
• Xbox 360 controller mappings have changed and some buttons are not reachable from the gamepad anymore. While this is negligible as of Mario Kart 64 (I only cannot cycle through the different in-game HUD options anymore), it may cause problems with other games.
• “Start + Select” on the gamepad to exit the emulator has no effect anymore. The only way to kill the emulator is pressing ESC on a keyboard.

I’d be glad to hear any solutions or general advise where to look for the right config files etc.

Thanks in advance!!

—

Setup
Raspberry Pi 2
RetroPie 3.0 Beta from image
no further tweaks except the ones mentioned above
Xbox 360 Wireless controller

[gizmo98]

You can try to play around with frameskip settings. You can find all config files under /opt/retropie/configs/n64. mupen64plus.cfg has rice settings. gles2n64.conf has gles2n64 settings. If you have pal games use a display resolution with 50Hz (press x or m at game startup).

[chris-p81]

I assume you’re using the same one I am (Mayflash SNES controller adapter for PC).It’s quite straight forward to get the usb adapter to work, it’s just plug and play. You should first check if the RPi sees the device with lsusb. It should be listed as GreenAsia. You should now be able to use the controllers to navigate in the emulation station menu. Then configure your controllers for RetroArch. I used this video as a guide:
https://www.youtube.com/watch?v=OBloKEbBRAU
Unfortunately I can only get one controller to work, there is no response from the second controller in RetroArch.

[Anonymous]

Hi Guys

My 6 year old son and I just finished building out Porto Pi unfortunately we can only play 2 of the 3 preinstalled games and aren’t able to play any added roms :(

We are running Porta Pi with a Raspberry Pi 2 Model B 1GB and Porta Pi Image v4.5

All boots up well and we are able to play 2 of the 3 preinstalled games in the ports emulator (Cave Story & Doom), Duke Nukem doesnt want to work for us.

We followed the “Adding Roms” instructions on retrobuiltgames.com and can see the actuall roms when booting back into ES under the respective Emulators however not one single one actually starts. The main error that we are getting is the following:

/opt/retropie/emulators/uae4rpi ~
rm: cannot remove ‘df0.adf’ : No such file or directory
In: failed to create symbolic link ‘df0.adf’ : Permission denied
~n: failed to create symbolic link ‘df0.adf’ : Permission denied5 Segmentation faul

Games in the N64 Emu just show up a blue screen for a second then return back into ES without starting

When trying roms in the Atari 800 Emu I get the following error:
“Atari800/OS Emulation Halted
Copyright (c) 1997 David J. Firth
(c) 1998-2013 Atari800 Development Team

http:atari800.atari.org/

Sorry this program needs a real Atari/OS
Visit the Web pages to find more”

Please Please someone help us…
Your help in this matter would be greatly appreciated. My 6 year old son will thank you

[tireiron]

Updated it, all seems to work now except not I got to try and get the n64 and GBA emus working, Ill search for that.

[puck6t9]

I just got a pi 2 b and i downloaded RetroPie SD-card Image for Raspberry Pi 2 Version 3.0 BETA 2 put it on a card and got every thing running but n64.

My problem is this most of the games i run work fine but for example Mario kart 64 with the default stetting (lr-mupen64plus) the game loads controller works but the text on the menus are messed up. with a lot of searching i found that when starting the game if you hit X and change the emulator for the ROM to mupen64plus-gles2rice the menus show right but there is no sound and my controller does not work any more. I have to use a keyboard.

With Zelda majora’s mask using lr-mupen64plus i see the Nintendo logo but then a black screen. i can hear the game running and if i hit buttons on the controller i here the sounds like starting the game but the screen stays black. If i change it to mupen64plus-gles2rice video is good but i am back to no sound and controller not working.

same thing with Wave Race 64

but with Mario 64 every thing works with the default settings

I have updated the setup script. did a update even did a binary reinstall of mupen64plus. nothing has work.

Can some one please tell me what i am doing wrong and how to fix it. I have been searching all night and cant see to find anyone having the same problem.

I have a Pi 2
with a Philips controller with the same layout as a PS2. it works fine every where but in the mupen64plus-gles2rice emulator.

If you will just tell me what config files need to be posted or screenshots ill post it.

[brunchero]

In the libretro code there is a descriptor, which I’d expect explains the internal mapping, after line 70:
https://github.com/libretro/mupen64plus-libretro/blob/master/mupen64plus-core/src/plugin/emulate_game_controller_via_libretro.c

L2 should be the Z-Trigger then, and R2 could switch between “C-Stick” and “C-Buttons” (A,B,X,Y) mode.

Controls Default looks like to be what is configured. Should be on SELECT. Instead, Controls Alternate appears to define a ROM-specific mapping.

[gusgmb]

Hi.

I am trying to make my Retrolink N64 USB clone work under libretro n64, but I’m having some problems.

I copied retroarch.cfg from configs/all to configs/n64. I want to do a completely different configuration for n64. The problem is I can’t figure out how to setup the C-buttons or the Z.

There is not a input_player1_z_btn or input_player1_cdown_btn, and I don’t know if the emulator reads the c-butons as l2 or l3 or something like that.

Also, when I press B the emulator displays a message saying Control: Alternate or Control: Default and I can’t stop ir or disable control mode switching.

Any help?

[Floob]

[quote=94337]

Keys X and Y are not being recognized in any Retroarch emulator (tested with playstation and n64).

[/quote]

I dont have any N64 or PS1 games to hand, but I just tried this with SNES and Megadrive and it seems fine for me. I’m using an iBuffalo USB joypad.

[ceuse]

I think its a issue with the retropie v3 image. im running it sucsessfully on 2.6 and im hesitant to update at the moment.

i will post my retroarch.cfg later if you want ( i use 1 mayflash snes & 1 mayflash n64 adapter with 2 controllers each)

[resboyintl]

[quote=94741]Hi,

On a CRT, the graphics are perfect.

A solution if you want to use a LCD screen might be to use a upscaling box.

Like this one:

http://retrorgb.com/upscalers.html

[/quote]

Ok, so I don’t see how this makes any sense, so maybe you can explain this to me…

The Rpi is HDMI, so I couldn’t possibly use a CRT monitor without an adapter (and I don’t have a CRT monitor, anyway.)

I don’t see how I would benefit from a device that “upscales”.

Other emulator graphics, like snes, nes, and genesis have the appropriate graphics. I encounter issues with PSX, where the actual characters of the game are a pixelated mess. Also, the N64 has some graphical issues, where it doesn’t render some of the background (haven’t tinkered with that yet)

Thanks in advance

[mcbourne]

The MUPEN64 is working a lot better. Thanks for all who’ve contributed.

I’m trying to get a retropie setup ready for my son’s bday. I’m testing 4 player mario kart and the gles2n64 plugin runs too fast and rice runs too slow.

Is the best solution to do a frame limit on with gles?

If I try the experimental MK video plugin the ROM doesn’t load, just a black screen.

[kakas]

Don´t have any tips but a question, do you play Zelda with mupen-libretro och mupen64plus emulator?

[matthew]

So after soooo many tries i got everything configured on my RetroPie 3.0beta on my RPI2. I have the overclock set to RPI2 setting and i can run some n64 games perfectly. However i want to try to squeeze every drop of performance to get everything working well. So have you any tips for this old man on how to get some more juice or settings per rom i can adjust to get unplayable roms to work better.

i was thinking about adjusting memory splits and forcing lower fps for certain games. mostly conker’s bad fun day is the only one im having terrible performance with. both zelda’s work okay star-fox works great

[phrazelle]

I’m on the tail end of mine. Functional, but working out some software issues as well as adding a few other hardware elements like the main power switch you just mentioned and a dimmer on the marquee LED strip. Right now it’s running 3 wall warts to a power strip, but I’m flipping over to an ATX PSU before I’m done. Planning on writing a full instructables around it and will post when the dust settles.

All the buttons are LED and stay on constantly. The abundance of buttons allows for full N64 support, but I (as most others )haven’t got the N64 to run smoothly yet. The front triangle buttons are for exiting an emulator – more for show than anything.

[URL=http://s1261.photobucket.com/user/phrazelle1/media/cabinet/IMG_2771.jpg.html][IMG]http://i1261.photobucket.com/albums/ii584/phrazelle1/cabinet/IMG_2771.jpg[/IMG][/URL]

[czesiek32]

Hi there,

I’ve found issue related to version 3.0 beta 2 for Retropie 2.

Pi Model: 2B
RetroPie Version Used: 3.0 Beta 2
Built From: SD Image
Controller used: Rertolink SNES controller (worked perfectly with retropie 2.6 / raspberry pi 1 B+)
How to replicate the problem:

Keys X and Y are not being recognized in any Retroarch emulator (tested with playstation and n64).

I run ‘configure retroarch keyboard/joystick’ from ‘retropie’ emulation station menu a few times. Also I rebooted pi after that. No effect – only ‘default’ keys ‘A’ and ‘B’ can be used in games. ‘X’ and ‘Y’ can not be used. Running via command line (sudo ./retropie_setup.sh) takes no effect as well. As I see file /opt/retropie/configs/all/retroarch.cfg is not being altered by this command (I use ls -l to check modification date). I believe that script is not saving it’s result to this file.

Additional info:

Previously I was using Retropie 2.6 and 3.0 beta 1 on Raspberry pi B+ and it was working fine (the same gamepad) without any extra configuration (I didn’t even have to configure retroarch controller). I guess this can be related only to Retropie 3.0 beta 2 for Raspberry pi 2.

If you need more details please let me know, I’m happy to help as much as I can.

Robert