Forum Replies Created
-
AuthorPosts
-
petrockblogKeymasterYou can install it on top of raspbian – you can install just single emulators even
see the readme
petrockblogKeymasterDo you mean video_vsync for the first option btw – that should be enabled by default.
Setting “video_threaded = false” can also help with latency (at the cost of performance)
petrockblogKeymasterJust to note : Video hard sync is not used on the RPI.
petrockblogKeymasterI thought we had fixed the button limit already with 3.3.1 – however for now maybe you can try advmame or a libretro core if it doesn’t work.
petrockblogKeymasterwhich mame ?
petrockblogKeymasterThere are new images available now yes. However you can do the manual fix listed above which would save time than downloading again.
petrockblogKeymasterThat’s fine. It was a specific issue with that file caused by me interrupting my image building script.
petrockblogKeymasterProbably related this issue – https://github.com/RetroPie/RetroPie-Setup/issues/1141
If you rewrite the image again, make those editos to /etc/fstab and then resize it should be ok.
petrockblogKeymasteryou can do “git log” in RetroPie-Setup folder to see the commit log with changes.
petrockblogKeymasterThere is no internal version number, we just tag the script for each release, but that’s just the script – not the binaries etc. However if you update now, you basically get retropie 3.3 with a few additional fixes. the binaries would be the same as the 3.3 release, but in a few weeks I may update some, so if you updated then, you would get new binaries etc.
petrockblogKeymasterRetroarch.cfg won’t be overwritten, but the main ES config will be, which will cause it to prompt for joypad configuration again – which is a good thing since there are new input configuration scripts that need to be run.
mame settings won’t be overwritten.
Always backup configs first.
petrockblogKeymasterNew images being created now – but in the meantime please edit /etc/fstab and make sure it contains
proc /proc proc defaults 0 0 /dev/mmcblk0p1 /boot vfat defaults 0 2 /dev/mmcblk0p2 / ext4 defaults,noatime 0 1it will be missing the last 2 lines. Then /boot will be populated after a reboot with the config.txt and the rest of the files from the boot partition.
petrockblogKeymasterit is an old bug and the version in Wheezy should be fixed, so it’s either come back, or there is a bug in another package dependencies causing something similar.
On Raspbian Jessie it seems fine.
You installed RetroPie on top of jessie running under Noobs ? I am referring to our prebuild Jessie images, or if you manually install retropie-setup on Jessie Lite etc.
petrockblogKeymasterHow is your RPI powered. Please give details about power adapter.
Please post the output of “dmesg” command (ssh into retropie from another machine)
petrockblogKeymasterThose talking about the freezing etc – have you all tried changing the “IO Timing method” in the system settings (with standalone PPSSPP) ? By default it is set to “Fast” which it says can lag on slow storage.
petrockblogKeymasterYou can’t use the core updater etc with RetroPie.
We don’t ship with any cheat files, and I have never tested it, but I guess you need to install some cheat data somewhere, and then use “quick menu” -> “core cheat option” and “cheat File load”
Cheats are available here – https://github.com/libretro/libretro-database/tree/master/cht
petrockblogKeymasterit happens due to some dependency issue with a package required by scummvm – this is a Raspbian wheezy issue though rather than a retropie issue.
You can’t for example install these together
sudo apt-get install sonic-pi libfluidsynth-devhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597265
if you need sonic-pi – reinstall it, but scummvm may not work. Alternatively you can try the Jessie image where this should be fixed.
petrockblogKeymasterare you the same user with a thread open regarding this on reddit – because I don’t want to be responding to the same person in two places.
petrockblogKeymasterplease update retropie-setup again, then disable and re-enable xboxdrv (will remove and recreate the launch configuration).
petrockblogKeymasterThe dispmanx backend for SDL1 is unrelated to the RetroArch dispmanx driver (apart from the fact they both render with dispmanx api). It can actually decrease performance due to the way it forces double buffering. (There is a newer dispmanx backend for SDL available we don’t have yet that should have better performance).
Using the dispmanx backend for SDL1 can help some stuff which is unstable when using framebuffer directly, and can stop tearing as it forces vsync. It will allow rendering to a smaller resolution and then scale automatically. Although the framebuffer has hardware scaling also, it requires modes to be set up first and can have problems with some resolutions.
petrockblogKeymasterAdjust “input_player1_joypad_index” setting for each system (configs/system/retroarch.cfg)
so input_player1_joypad_index=0 is first usb port. input_player1_joypad_index=1 is second etc.
see
petrockblogKeymasterSorry – cmdline.txt not config.txt – updated post.
petrockblogKeymaster[quote=112158]
I have even done a fresh image, installed custom kernel and added line. NOTHING!! I must be doing something wrong???? I even have to Xin-mo boards and cables just to make sure nothing is faulty.
[/quote]
please post me your actual cmdline.txt via a site like pastebin.com so I can check it. thanks.
petrockblogKeymasterSwap the USB ports around.
petrockblogKeymasterIt works yes.
petrockblogKeymasterIt’s not possible unless perhaps you ran ES under X server. There is no software way I know of of capturing the graphics that are directly rendered to the screen/framebuffer without hardware like a capture/tv card etc.
petrockblogKeymasterLikely due to me accidentally rebuilding that when I had the Raspbian mesa EGL libraries installed. I’ve rebuilt – please can you reinstall.
petrockblogKeymasterWhen it’s done. Maybe an image to test soon.
I still need to do more testing – you can see progress of development on the github repository.
Downgrading is not really possible – you can backup / start with a new image.
petrockblogKeymasterI have updated retroarch binaries. Please can you reinstall just retroarch from binary and let me know if it works for you. thanks.
petrockblogKeymasterI also wouldn’t recommend updating to Jessie yet. Jessie support is still a work in progress.
petrockblogKeymasterBTW if starting from the 3.2.1 image, after downloading you shouldn’t need to update retropie-setup and re-install from binaries. Doing so will give you a snapshot of where we are at currently, but there can be problems sometimes, especially when close to a new release. Best done after we have just released a new version, as things will be more tested then.
petrockblogKeymasteroh right, yeh don’t re-install from binaries at the moment, I am preparing a new release, and have been rebuilding some of the binaries. I just rebuilt retroarch and I need to revisit it (It’s possible I may have accidentally uploaded the jessie release to wheezy), so until it is fixed you can recompile it from source.
petrockblogKeymasterhmm no-one else has reported this with the last images. Which image are you using ? are you doing any updates after writing etc ?
petrockblogKeymasterDon’t think the joystick buttons are configurable without a recompile or if it supports your joystick mapping
https://github.com/RetroPie/snes9x-rpi/blob/master/readme.rpi
But I’m surprised if that emulator supports something snes9x-next doesnt as it’s not using a newer snes9x core.
Please give me an example of a game which doesn’t work? Which version of retropie are you using ?
-
AuthorPosts
