[gizmo98]

It’s slower as glesn64 and rice but more compatible. Use VGA resolution and GLideN64 should be fast enough.

[gizmo98]

Use github and fork retropie-setup. Modify https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/system.sh. Add a platform for ux4 and try to use something like ‘if ux4 ,then…’ in modules. Then start retropie setup with ‘__platform=ux4 ./retropie_setup.sh’.

[gizmo98]

Press PS button once.

[gizmo98]

Please update your retropie-setup script and install mupen64plus from source. For best performance use RPI2 Overclocking, VGA resolution and a good power supply.

[gizmo98]

Try the experimental mupen64plus-testing emulator. After installation select experimental emulator at game start. Press x or m and select mupen64plus-testing-rice.

@deadherring
There is “no plugin for all games”. Some games run flawless with rice, some with gles2n64. Gles2n64 is most of the time faster but there are major stability issues with games like zelda OoT. Some games are not playable at all.

[gizmo98]

Increase audio output buffer size. (mupen64plus.cfg)

[gizmo98]

It is not software compatible. It has an allwinner H3 with four Cortex A7 cores and a MALI GPU. Don’t know if there is a debian image with good gpu support. I doubt it. Linux sunxi based allwinner images are not as good as raspbian. Bad GPU support. Bad full HD performance. No resolution switching during runtime. X must run to get GLES support. Bad default settings and so on.

So you have a cheap board with no software support best used for headless tasks like file server or router.

[gizmo98]

Last time i have checked this plugin there was no gles support and android port was in progress. The plugin looks really good if you have a pc. I have no time at the moment. I will check it later this month.

[gizmo98]

There is no upscaling if display and render resolutions are equal. Be aware your display resolution could be some pixels smaller if overscan (config.txt) is enabled. So if render resolution is 1920×1080 and your display resolution is 1910×1070 (overscan) there could be scaling artifacts.

If performance is ok i would recommend render = display resolution. If performance is to low (shaders, emulation speed) a mix of hardware upscaling and lower render resolutions should be used. Hardware upscaling is for free and needs no processing power.

I have not seen any input lag with hardware upscaling. Thought threaded video causes a small input lag.

[gizmo98]

You can set “any” vertical resolution (0-1080) in your retroarch.cfg. For example you could set something like 1080/2=540 or 1080/4=270 to get integer scaling. If the aspect ratio of your render resolution differs from your display resolution horizontal resolution will be recalculated. You can try to get the best fit for performance and visual appearence. Render resolution upscaling is for free (hardware). If render and display resolution is equal software integer scaling is used (performance penalty). It is also possible to modify the hardware upscaler to your needs: https://github.com/raspberrypi/firmware/issues/104

As i have said default visual settings are not optimized for rpi2 at the moment. If we find better defaults we can at them.

[gizmo98]

640×480 default is set because higher resolutions will slow down rpi1s. In the past display resolution was switched which caused flickering and was not compatible with all screens. Rpi2 and 1080p should be fast enough if you use no shaders. Rpi1 and two share the same default configuration at the moment.

If you have a 16:9 screen resolution and 640×480 render resolution retroarch will increase your horizontal resolution to 853×480. So there should be no unequal pixels since Retropie 2.6 or 3.0.

[gizmo98]

Try it out. I have no dialog after doing it once. Keyboard can be removed then.

[gizmo98]

Dear fellows,

If you use RP3 B2 please check out the reworked ps3 module: https://www.petrockblock.com/forums/topic/ps3-controller-on-bluetooth-anyway-to-save-the-emulation-station-settings/#post-96127

If a bluetooth dongle is present and you connect a ps3 controller over USB the controller will be paired instantly. Remove USB cable from PS3 controller, press PS button and have fun.

Open issues:
-Bluetooth dongle + wired PS3 controller is not possible at the same time. Remove bluetooth dongle to get wired connection working.

[gizmo98]

If you start game there is this “press x or m” message for a short time. Select gles2n64 for MK64 because it should be the fastest and best looking plugin for this game.

[gizmo98]

1. There should’t be any big difference between our mupen64plus and mupen64plus 2.5. We compile core, ui, and some other plugins from current vanilla source. If you open retropie_setup and install from source you should have mupen64plus 2.5.

2. Game specific settings must be setup in different locations. Video Plugins store these settings in two files:
/opt/retropie/configs/n64/RiceVideoLinux.ini
/opt/retropie/configs/n64/gles2n64rom.conf
One is for rice plugin, the other for the n64 plugin.

Global rice settings are stored in mupen64plus.cfg. N64 settings are stored under gles2n64.conf.

@olapaulakoski use another emulator or plugin

Anyone got n64 Mario Kart working?

[gizmo98]

You are using mupen64plus-libretro with rice plugin at the moment. Use another emu or plugin. Press x/m at game startup and select another one. MK64 + RetroPie Beta 2 runs fine with:
mupen64plus-libretro + gles2n64 plugin
mupen64plus + rice plugin
mupen64plus + gles2n64 plugin
mupen64plus-testing + rice plugin
mupen64plus-testing + gles2n64 plugin

Mupen64plus-libretro + rice is default because it does not crash your pi with certain games and uses retroarch controller setup. Mupen64plus standalone should be faster but needs more effort to setup unknown controllers and hotkeys.

[gizmo98]

As i have written in some other thread please setup your keyboard as a emulationstation input device and the message should not pop up anymore.

The “Can’t register ps3 controller. Buttons are to sensitive. ” issue should be resolved now. If you use the newest ps3 driver module sbuttons (sensitive buttons) option is disabled.

How to update:
1. Close emulationstation with two F4 key presses.
2. Type:

cd RetroPie-Setup
sudo git pull
sudo ./retropie_packages.sh ps3controller

[gizmo98]

With the next retropie release you should see the same behaviour.

[gizmo98]

Press ps button for 10s and your controller will disconnect.

[gizmo98]

You could also do a source update of mupen64plus and mupen64plus-testing. Both rice plugins use your native resolution now.

[gizmo98]

Do you mean the doom.sh script? There should be a “retropie/roms/ports/Doom 1 Shareware.sh” script. This script always tries to open “retropie/roms/ports/doom/doom1.wad”. Copy and rename this script and add the path to your new wad file.

[gizmo98]

Disable threaded video.

[gizmo98]

roms/n64 is the only n64 romdir now. Select a emulator with x/m key press if you start a game.

[gizmo98]

It’s a new 3.0 option. A binary update should bring the new option as well.

[gizmo98]

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

[gizmo98]

No.

[gizmo98]

@all
Could you retry this again? I modified sixad source code. register controller shouldn’t be necessary anymore.

[gizmo98]

It’s for rpi2 as well. Actually most rpi1/2 settings are equal. You can modify the render resolution of libretrocores at startup with x/m key press.

[gizmo98]

Try to use experimental rice. Runs and looks much better with zelda games.

If this does not work please post your ricevideolinix.ini. Could be you use a not supported rom file.

[gizmo98]

@all check if your video_fullscreen_x/y settings are 0. Otherwise your resolution will be upscaled. Hardware upscaling should be default enabled for rpi1 performance reasons.

There will be a performance drop if you use a HD resolution with shaders.

[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.

[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).

[gizmo98]

Ok. I think i know what you all mean. We have autoconfig files for ps3 controllers. These files do not work with sixad “out of the box” because sixad modifies the controller name. Retroarch can only test vendor id and product id for usb devices. So it is necessary to register every bluetooth paired ps3 controller. You could also copy vanilla ps3 controller autoconfig file and add your ps3 controller name.
I try to get vid pid detection fixed for bluetooth devices.

[gizmo98]

Ohh this issue…
Please setup your keyboard as an input (setup ES Controls) and try again.

[gizmo98]

Actually it looked like your captured picture on a CRT. Ok. there is also a high res core option for PCSX_Rearmed. Open RGUI and select “Options/Core Options”. There is a performance drop if you enable this option.

[Author]

Posts