Homepage Forums Search Search Results for 'n64'

Viewing 35 results - 1,051 through 1,085 (of 1,578 total)
  • Author
    Search Results
  • #88531
    fallersaur
    Participant

    Just in case you want to spend $35 on another Pi, I just tested the following SNES/N64 games on the RPi2:

    Note: I am using RetroPie 2.6.0 and am using the RPi2 overclock setting from within raspi-config. I also placed my roms in n64-mupen64plus to use that emulator instead (thanks floob for your videos on youtube!)

    Starfox – Runs really well now. I played it for like 30 seconds and saw no issues using this setup.

    Stunt Race FX – I will have to check if my rom is corrupt or if this game just doesn’t emulate well. I was able to do everything in the menu, but after entering a game it gave an error that it was unable to create my car. It failed to render any car/track upon entering a race.

    Super Mario 64 – Works very smooth. I only ran around for a bit, but it runs smooth and sounds great.

    Super Mario Kart 64 – Works very smooth. I did a test race with only 1 player and that went very well.

    Legend of Zelda 64 – I need to play around with this one. I attempted to load it and it never finished loading. I may need to try it on the other emulator, with a different rom, or play with some graphics settings within mupen64plus itself.

    Anonymous
    Inactive

    Hello All,

    Has anyone had any luck getting sound to work with Mupen64plus and a Hifiberry dac+ sound card? I cannot seem to get any sound when using Mupen64plus with Retropie v2.6.0 and a Raspberry Pi 2.

    In the mupen64plus.cfg file located in the directory /home/pi/.config/mupen64plus there are only two options for sound, “# Audio output to go to (0) Analogue jack, (1) HDMI.” I’ve tried both in addition to commenting out the subsequent line and still no sound. Does anyone know a work around to this or perhaps another audio plugin that may work?

    Thanks,
    Ryan

    #88513
    fallersaur
    Participant

    This is essentially why I just got my RPi 2.

    The problem with some SNES games like Starfox, Stunt Race FX, etc…is that those games used an FX chip. Unfortunately, those games do not run well on the RPi B+, but I have seen some reports that FX games work perfectly with the RPi 2.

    Same with most N64/PSX games. Although I have seen some users manage to get N64/PSX games “mostly” playable, the best bet is to go for the RPi 2. Again, I have already seen some people report much better performance with both of these.

    Either way…just like gizmo98 said, I would recommend overclocking to at least medium to get better performance out of the RPi B+.

    also Stunt Race FX gives a black screen checking for mode 7

    I think that is just a modded rom. I’ve seen the occasional “Mode 7” intro screen with certain roms and have seen forum posts where sometimes the modded intro screens can prevent some roms from running at all with the libretro emulators.

    #88501
    noobian
    Participant

    me too..having problems with Kirby,Starfox and Doom on snes…theyre just too sloowwww….also Stunt Race FX gives a black screen checking for mode 7 or somethin???..i havent yet overclocked my b+ and checked..

    you know sometimes these problems occur with emulators…try a different one and the same game might run perfectly smooth.

    Also i guess the only fix for n64 and PSX is to buy the new raspberry pi 2 quad core..the videos on youtube shows smooth gameplay..

    Anonymous
    Inactive

    Hi,
    I use the latest version of RetroPi. But the emulators has some performance problems – but not with all games, only with some ROMs.
    Example SNES (with and without overclocking): Lufia, Super Mario RPG, Super Mario World, Mario Kart, Donkey Kong works fine. If I try Kirbys Fun Pak, Tetris or F-Zero the game has lags that’s not very playful.
    Example N64: Without overclocking you can’t play anything. With maximum overclock, Mario64 has lags, Pokemon Stadium starts but if you start a game (“new game” in the game) I see only a black screen. Same with Mario Kart 64.
    Example PSX: Crash Badincoot runs with lags without overclocking. It runs well with maximum overclocking. Tomb Raider starts with and without overclocking, but if I start the game (“new game” in the game) I only see a black screen.

    I’m using an Pi Version B+. Tried both – install on a Raspbian system and used the full card image. Problems are the same.
    And I don’t understand it, the power of the RasPi should be enough for SNES games. And why are some working and some not?

    I’m glad to get some ideas to fix this problems. Thank you

    Greetings
    FluGar

    zersus
    Participant

    Hello everybody let me first say thank you to the head(s) behind this amazing retropi project!

    My problem is the mupen64 and mupen64plus.
    I have them both up and running on my Raspberry Pi 2 and, I’m using the 2.5 img (if I’m not mistaken). My linux knowlange is unter average, but as far as I can tell everything is up to date. I used the update option in the retropi-setup.sh as well as sudo apt-get update && sudo apt-get upgrade.
    The Problem in detail is, that the mupen64 can’t display the games correctly, the look all like this: http://imgur.com/Keg2JUp,TVWSzNZ

    The mupen64plus can run the games very well, but this emulator crashed on some roms for example when trying to run Zelda. The other Problem is, I can’t enter the RetroArch menu like here:http://imgur.com/Keg2JUp,TVWSzNZ#1

    Is there a way to make the mupen64 run the games like the plus-version AND enter the RetroArch menu? I’m to unsure in the linux world to start copy/past files from one folder in to another. And the problem is, I can only find the mupen64plus folder, but not the “normal” mupen64.

    I really tried to google this problem, but could not find any solution. Please help me to make the mupen64 up and running :).
    PS: I just register here very fresh, how is my avatar picture here all of the sudden?

    raymate
    Participant

    Trying to get N64 to run on my Pi2

    It seems to run at a OK speed (maybe a bit slow)

    But with Super Smash I see lots of the characters for some reason have no face details like now eyes, mouth etc.

    I see on youtube many people have the N64 working great, I can’t seem to get it run as well.

    Any tips?

    I have overclocked to 1GHz but thats it.

    #88452
    gizmo98
    Participant

    Already checked. mupen64plus-video-rice runs as good as mupen64plus-video-gles2n64. I haven’t tested the gln64 plugin now.

    Vanilla core, input, audio and video-rice are running atm.

    #88392
    clone206
    Participant

    As I was first looking into the mario kart 64 two player issue I submitted an issue for mupen64plus. Just today I got a reply that might be useful to the ricrpi maintainer(s). See the reply from today (Feb 20) at the below link.

    I wonder if the rpi 2 is powerful enough to handle the vanilla mupen64plus-video-rice and mupen64plus-video-gln64 plugins. I get the sense they’d be compatible with more roms.

    https://code.google.com/p/mupen64plus/issues/detail?id=641

    #88370
    Anonymous
    Inactive

    Okay thank you guys.

    It works with changing the default video mode via the Launch configuration tool (´X` during Game load).

    I use DMT-4 640×480 @ 60Hz, clock:25MHz progressive
    All other defaults are not working.

    In gles2n64.conf seems everything okay. Same resolution: 640×480 picture centered…

    It is only the sound that is not working in the emulator.

    23:30 Sound problem also solved.

    changed in mupen64plus.conf

    #Audio output to go to (0) Analogue Jack (1) HDMI
    OUTPUT_PORT=0
    (I have to active PC loudspeakers connected using the audio jack)

    #88359
    gizmo98
    Participant

    Modify gles2n64.cfg or use mupen64plus-testing (experimental module).

    #88355
    Roo
    Participant

    I found that Mupen64 will do that if you try to force its resolution too high. For example, if I hit ‘x’ when launching a game and try to set it to 1920×1080, I get the small window in the corner, but if I set it to 640×480, it launches full screen.

    Anonymous
    Inactive

    Hi all,

    i updated today my new Raspberry Pi 2 with the Retropie image v.2.6.

    Most of the emulators working fine.

    I only have some problems with the mupen64plus emulator. It running fine but only in a little square on downer right screen.

    If tried to add some Flags into the config file /opt/retropie/configs/n64/mupen64plus.cfg like:

    Fullscreen = True

    but no of these works. Also my (Video-General) section was empty?!

    How could i run those emulator in fullscreen?

    Sorry for my bad english..

    Thanks and regards

    MarcoCol
    Participant

    Hi,

    I’ve installed the build from approx. 6th/7th February, which “Buzz” has put there on the server.
    Thanks to Buzz for all of your work.
    So I’ve read, that the N64-Emulator maybe has some problems.
    But I didn’t use it.
    Also I read, that there can be done some updates?!
    So I want to ask if updates can be done or when there is a new version, if I must overwrite it each time on my SD-Card and configure all new.
    So if there is an update function, I can start with configuring the software.
    Or is there planed a fixed image in the near future?

    #88276
    whettingstone
    Participant

    Quake 3 or some PS game probably.

    Maybe some N64 game.

    #88222

    In reply to: N64 – Two Player

    phipli
    Participant

    Folks – I’ve been faffing around all evening and this is the best I’ve managed :

    Open file mupen64plus.cfg in nano using the command :

    sudo nano /opt/retropie/configs/n64/mupen64plus.cfg

    Go to the line ‘VideoPlugin = “mupen64plus-video-n64″‘ under [UI-Console] and change “n64” to “rice”.
    Save (Ctrl-x)
    Launch the emulator. Exit the emulator.
    Re-open mupen64plus.cfg in nano – there is a new section called [Video-Rice], change the line ‘ScreenUpdateSetting = 6’ to ‘ScreenUpdateSetting = 4’
    Save (Ctrl-x)
    Load up and play two player mariokart. Doesn’t seem to run quite as well – audio is a bit jittery, but that might be because of the two player…

    Also worth noting that the only place that seems to make a difference adding new controllers is the InputAutoCfg.ini file in the same folder. I was pulling my hair out for ages because guides on the internet all seem to point you to the wrong place… and there are two identically named files with the same content in my install. Hope this helps. To give credit where it is due, my final clue came from this page : http://www.raspberrypi.org/forums/viewtopic.php?f=78&t=6761&start=200

    #88144

    In reply to: Xbox One controller

    gonzo28
    Participant

    bigdrogba,

    I configured my xbox one controller with the retroarch-joyconfig command:

    retroarch-joyconfig for RetroPie 2.3 not responding to inputs

    Does anybody know how to get two controllers running in the n64 (mupen64plus) emulator?

    n64 works fine with the 360 controller. SNES works fine with both controllers (xbox 360 and xbox one). xbox one controller in the n64 is not recognized.

    #88102
    gizmo98
    Participant

    I have already a modified retroarch videocore context driver in the pipeline. I had no time to test it because of n64 stuff

    #88078
    clone206
    Participant

    @chdez77076 – Looks like the beginnings of one are here:

    https://github.com/ricrpi/mupen64plus/wiki/Game-Compatibility-List

    I’ve gotten a ton of roms to be very playable now between the default plugin and rice with these updated settings. I’m seriously neglecting important things in my life because of this!

    Also, I’ve gotten the default plugin to show both players’ screens in 2 player Mario kart 64 by setting “update mode=3” in gles2n64.conf, but the screen flickers so much it’s not really a workable solution. It’s a shame because it’s noticeably laggier with the rice plugin, to say nothing of the textures frequently being rendered incorrectly as black squares. There doesn’t seem to be much documentation out there on configuring the gles2n64 plugin. At least with the rice configs there’s heavy commenting.

    I have no idea what the numbers for “update mode” even correspond to!

    UPDATE: I figured out how to make the vast majority of the black boxes go away in mario kart 64 when using the rice plugin. This, in combination with the earlier changes to the settings I made, have got the rice plugin running pretty much on par with gles2n64 on the rpi 2. The trick was turning on texture filtering and using the “Sharpen” filter in /opt/retropie/configs/n64/mupen64plus.cfg under the Rice settings. So all of the relevant settings from that file are:

    [Video-Rice]
    ...
    # Frequency to write back the frame buffer (0=every frame, 1=every other frame, etc)
    FrameBufferWriteBackControl = 1
    ...
    # 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
    ...
    # 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 = False
    ...
    # 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

    I am one happy camper :)

    #88013
    chdez77076
    Participant

    Thats Awesome!

    Somebody should definitely set up a “working n64 roms” database with the specific video plugin + individual changes to the config.

    As more people try this emulator those setting could then maybe be setup as a default config for future releases.

    Win!

    Just a shower thought.

    MrCooper2012
    Participant

    So I’m trying to setup my new RPi2 to run retropie 2.5, but most of the emulators don’t seem to be working for me. I had already built one as a gift on a B+ using 2.3 and had no issues getting games to run and work with an Xbox controller. Yet now I can only get MAME working 100% (rom and controller), TurboGrafx and SNES will load but the controller does nothing.

    NES, Genesis, and N64 show up on emulation station, but when I select one it’s almost like it resets the Pi – or just kicks me back to the command prompt login (pi@raspberrypi or something like that).

    The controller is recognized by Emulation station and I have no issues using it to navigate that menu. I feel like there is probably some simple, but crucial, step I have missed somewhere along the line. Any ideas to get the controller working or the other emulators? I’m mostly puzzled by the emualator issue – I know there are other people with similar controller problems so I’m sure I’ll find a solution, but I foudn nothing regarding the loading issue. Could it be the SD Card (Sandisk UltraPlus 32g Class10) or is this just user error? I did use the default overclock to RPi2. Sorry if my terminology is off, still learning.

    #87953
    gizmo98
    Participant

    Zelda is working with rice plugin if ScreenUpdateSetting=5 (/opt/retropie/configs/n64/mupen64plus.cfg). But it is slow.

    #87946
    Roo
    Participant

    Not all games are working. I am able to play Super Mario 64 and Mario Kart 64 perfectly with both stock 2.5.0 and 2.6.0 images. 007 works too, but has slowdowns. Zelda games don’t work. That’s all I’ve tested so far.

    I know Floob has some videos about playing with the different video plugins, but I haven’t done any testing with that yet. The way I look at it, I’ll just wait for a better optimized build of RetroPie – I got enough other stuff to mess with that I’m not interested in tweaking Mupen64 settings.

    I have my Pi 2 set to “Pi2” overclock with a memory split of 384.

    rednas32
    Participant

    Hey all,

    I can’t get the Mupen64plus emulator to work. Everytime I try to load a rom it says the following:

    audio warning: audio buffer under run(0)
    audio warning: audio buffer under run(1)

    And the emulator freezes.

    I can still inject a reboot command through SSH but the keyboard and controller are both unresponsive at this point.
    I am using the latest 2.6 image for the rpi2 with a clean install, overclockt to pi2 settings and the memory split is at 192.

    Tried using older builds and differences in the memory split but nothing seems to work.

    Have tried different setting for the audio plugin but just can’t get it to work.

    When I change the config for Mupen64plus to run rice as a video plugin(so not changing anything about the audio plugin) the game does run and i have sound, but some screens don’t show. For example: playing zelda, MM or OoT, the start menu doesn’t show and the screen freezes. At this point I actually am in the start menu since i can hear the sounds in there, and when i exit the start menu the game continues like normal.

    Do you guys have a fix for either of these problems so i can play these wonderfull games again?

    Tnx!

    #87939

    In reply to: N64 – Two Player

    bowser
    Participant

    Same here. n64 / Mupen64plus: not able to get the splitscreen working for p2.
    Did an install from source 2 nights ago. Any help?

    ∆ + 0 / 9
    Participant

    Hi all,

    I’m pretty close to getting RetroPie working. I’ve got my RPI2, powered usb hub, controllers and a 16gb microsd card with RetroPie for rpi2 image installed on it.
    I’ve got around 5GB of nes, snes, N64 and megadrive roms ready to put on it but I’m not sure how to load them onto it.

    I’ve read that after plugging my external hard drive into the Pi when RetroPie is on, it should create a bunch of folders on my hard drive, I can then plug the hard drive into a windows machine and transfer my roms into the appropriate folders. Plug the hard drive back into the pi, boot up and retropi should transfer the roms onto the SD card automatically.

    I’ve tried this but when looking at the external hard drive from my computer there’re no folders to place my ROMS into.

    Can anyone explain why the folders aren’t being created on my external hard drive?

    A few possible reasons why this might not be working that I’ve thought of:

    – The external hard drive I plugged into the rpi2 already has a load of files on it, at the root there are 3 folders: Films TV Shows ROMS
    – This could be the name of the folder that’s automatically created by RetroPie already and is confusing it.
    – The hard drive is NTFS formatted. – My installation of RetroPie isn’t setup properly.

    If anyone has any suggestions that would be greatly appreciated.

    I’m wondering if anyone is able to provide me with the folder structures and names for my external hard drive and I’ll just manually create the folders and place them there myself?

    Thanks!

    gloob
    Participant

    Hello,

    I have running the N64 emulator without any problems with Mario Kart, but when I try to play it with two players, the lower part of the screen is just black. The controller is working without any problems but I get no screen.
    With only one user, everything is fine.

    I’m using the latest image from buzz.

    Any chance to get it working?

    Regards
    Stefan

    #87834
    juan9999
    Participant

    Ok, so I upgraded to 2.5 of the emulator, and it mostly fixed my first issue- now the two generic N64 USB controllers work (except for the analogue joystick) my retroarch.cfg got corrupted

    and the second issue was due to the wrong type of “quotes”

    – How can I get the analogue controls working? When I run the

    sudo ./retroarch-joyconfig -j 0 >> /opt/retropie/configs/all/retroarch.cfg

    Here is what was visible on the screen when I was programming the controller

    Up D-pad
    Joyaxis moved: Axis 1, Value -20945
    Down D-pad
    Joyaxis moved: Axis 1, Value 23002
    Left D-pad
    Joyaxis moved: Axis 0, Value -20174
    Right D-pad
    Joyaxis moved: Axis 0, Value 22745

    and here is what was added on

    input_player1_joypad_index = “0”
    input_player1_b_btn = “2”
    input_player1_y_btn = “3”
    input_player1_select_btn = “8”
    input_player1_start_btn = “9”
    input_player1_up_btn = “h0up”
    input_player1_down_btn = “h0down”
    input_player1_left_btn = “h0left”
    input_player1_right_btn = “h0right”
    input_player1_a_btn = “1”
    input_player1_x_btn = “0”
    input_player1_l_btn = “4”
    input_player1_r_btn = “5”
    input_player1_l2_btn = “4”
    input_player1_r2_btn = “5”
    input_player1_l3_btn = “7”
    input_player1_r3_btn = “7”
    input_player1_l_x_plus_axis = “+0”
    input_player1_l_x_minus_axis = “-0”
    input_player1_l_y_plus_axis = “+1”
    input_player1_l_y_minus_axis = “-1”
    input_player1_r_x_plus_axis = “+0”
    input_player1_r_x_minus_axis = “-0”
    input_player1_r_y_plus_axis = “+1”
    input_player1_r_y_minus_axis = “-1”

    #87823
    evilllama
    Participant

    It seems that there should be a way to do this.

    Anyone have a working n64 / Mame fix?

    The only problem is that when I found the mupen64plus configuration file, it only has about 60% of the lines listed under [CORE]. I assume that we can copy and paste the lines for [video], [input], [rice], etc., but when I changed the line

    frameskip = false, I tried “true”

    There was no change that I could see. Was it looking for a value? If so, is it basing it on skip per second, or maybe a ratio of frames:skips? Or maybe I found the file, but it is not the correct location to alter this because there is a file that is read after this one that alters the behavior I set?

    Just thinking of people who might want to emulate at 100% speed, but also don’t mind if there is a slight frame jump that is barely even noticeable. Pi 1 B+ can’t seem to hit 100% all the time even after (multiple) overclocking settings have been changed.

    #87796
    gizmo98
    Participant

    If you recompile both emulators you can test if neon optimizations speed up anything. Update RetroPie-Setup and open it with “sudo __platform=rpi2 ./retropie_setup.sh”. Select mupen64plus and mupen64plus-libretro under source based installation.

    #87770
    clone206
    Participant

    In case anybody is interested, I figured out that it’s actually quite easy to switch video plugins. mupen64plus has a –gfx switch that allows you to specify which plugin to use. Retropie 2.5 comes with two customized plugins, which happen to also be the plugins used in ouya, which is why ouya users also face the mario kart 64 issue. These plugins are named gles2n64 and gles2rice.

    In retropie 2.5 gles2n64 is the default plugin used by mupen64plus. It actually looks quite a bit nicer – at least for composite video out – than gles2rice, which I believe used to be the default in previous versions. The problem is that gles2n64 tends to lock up on a lot of roms, and in the case of mario kart 64, it can only display one of the players’ screens.

    In order to use the gles2rice plugin only for certain n64 roms, I created a separate folder in the roms directory. Then I created a new system in es_systems.cfg, and specified that plugin using the –gfx switch within the command tags. Note that you also have to explicitly set the gles2n64 plugin using the –gfx switch within the command tags of the original system, or the other system will cause gles2rice to be written into the main mupen config file as the default plugin. I’m guessing there’s a more elegant way to accomplish this, so sorry if I’m leading anybody astray, but it was the best I could do with the knowledge I have. I know you can also edit plugin settings on a per-game basis via config files too.

    Below is the relevant config code for using my method. The path to the roms directory has also been changed from the default because I keep all my roms on a usb stick, so you can’t just copy and paste this into your /etc/emulationstation/es_systems.cfg file. Also, I added a “sudo” before the commands as I also store save data on the usb stick, and if the commands aren’t run as root, mupen can’t write to the fat32 formatted usb stick. I’ve also read that running as root can give performance gains.

      <system>
        <fullname>Nintendo 64</fullname>
        <name>n64-mupen64plus</name>
        <path>/media/usb0/r0ms/n64-mupen64plus</path>
        <extension>.z64 .Z64 .n64 .N64 .v64 .V64</extension>
        <command>sudo /opt/retropie/supplementary/runcommand/runcommand.sh 1 "/opt/retropie/emulators/mupen64plus/bin/mupen64plus --gfx mupen64plus-video-n64 --configdir /opt/retropie/configs/n64 --datadir /opt/retropie/configs/n64 %ROM%" "mupen64plus"</command>
        <platform>n64</platform>
        <theme>n64</theme>
      </system>
      <system>
        <fullname>Nintendo 64</fullname>
        <name>n64-mupen64plus</name>
        <path>/media/usb0/r0ms/n64-mupen-rice</path>
        <extension>.z64 .Z64 .n64 .N64 .v64 .V64</extension>
        <command>sudo /opt/retropie/supplementary/runcommand/runcommand.sh 1 "/opt/retropie/emulators/mupen64plus/bin/mupen64plus --gfx mupen64plus-video-rice --configdir /opt/retropie/configs/n64 --datadir /opt/retropie/configs/n64 %ROM%" "mupen64plus"</command>
        <platform>n64</platform>
        <theme>n64</theme>
      </system>

    Now I’m going through all my roms, and when I find one that doesn’t work with the default plugin, I simply move it over into the alternate folder (specified with the above config code) and relaunch emulationstation. Now there are two nintendo 64’s listed in emulation station, one for the default plugin, and one for the rice plugin. Of course, some roms don’t work with either plugin, but sometimes I get lucky. Majora’s Mask and Banjo Kazooie are two notable examples of roms that only work with the rice plugin for me.

    I haven’t been able to test 2 player mario kart 64 with the rice plugin as I need my friend to come back over with his controller (unless I can figure out how to specify player two as using the keyboard), but I’m hopeful it’ll work, as it seems to work for ouya users based on the reddit thread in my previous post.

    All in all, n64 games run much better on my raspberry pi 2 than they did on my b+. And I finally have working doom, duke nukem 3d, and quake III arena. I’ll post my overclock and memory split settings as well. It’s been pretty stable at these settings, but if I try to go up to 1140 the pi seems to freeze up and I get locked out. And I believe it was also the cause of sd card corruption, which is why I store roms, save data, and backups of config files on a usb stick now.

    gpu_mem=64
    arm_freq=1100
    core_freq=500
    sdram_freq=500
    over_voltage=6

    UPDATE: I got two player mario kart 64 to work with the rice plugin! I had to tweak some settings in /opt/retropie/configs/n64/mupen64plus.cfg to get it to work. With the default config both players’ screens just freeze before the race even starts. This seems to have to do with when the screen is redrawn. Under the “[Video-Rice]” section of the file I changed the following parameters. This also had the effect of making things look nicer too (smoother frame rate)

    ScreenUpdateSetting = 7
    ...
    SkipFrame = False
    SkipScreenUpdate = False

    Edit: Lowered gpu memory to 64 for better performance.

    whywilson1
    Participant

    Finally figured out how to configure my controller for the N64, got a couple of games working too. MarioKart 64 looks pretty good, just some random black boxes here and there.

    whywilson1
    Participant

    [quote=87633]neighbourhoodnerd: Weird. I didn’t notice any significant improvement for n64 emulation using the “Pi 2″ overclock, that’s why I only use the “modest” one…

    whywilson1 : Did you try the 2.5.0 version? I just copied/pasted the n64 configs and emulators folders on my previous microSD, and did what I mentionned above, and some games work decently (Super Smash Bros for exemple).
    [/quote]

    Well I used Buzz img file, but then I updated the Binaries. And I have no idea what version of RetroPie I’m actually running now 2.5 or his version still.

    #87713
    whywilson1
    Participant

    @Floob Thanks for the info. Elgato seems pretty straight forward.

    @Roo. Before I came to this forum I DLed the 2.3 Img. THEN, I got it working because of Buzz img and Floobs help.

    Everything works fine except for N64.

    minimonk347
    Participant

    Actually, there are two rom folders for N64 in the 2.5.0 and buzz images. The only difference I have noticed regarding those between images is that the 2.5.0 retroarch emulator loaded Ocarina (terribly slow/choppy and graphically flawed), but the buzz image would throw out some illegible script (due to screen resolution), then return to rom selection.

    I feel ya on the individual plugin thing, though; it would be nice if the characters in SSB weren’t missing most of their facial features. Kirby was unaltered, strangely enough.

Viewing 35 results - 1,051 through 1,085 (of 1,578 total)