Search results

Hey buddy The repo just reuse your login on the boards. So if you wanna connect to the repo, you'll be redirected to the boards login form

There's doc on the wiki, use it : https://pyra-handheld.com/wiki/index.php?title=Using_SDL2 :P You probably wanna add export CFLAGS="-I/opt/omap5-sgx-ddk-um-linux/include" LD_FLAGS="-L/opt/omap5-sgx-ddk-um-linux/lib" before building and then export SDL_OPENGL_ES_DRIVER=1...

"enculé" it is :P the close relative "enfoiré" have no equivalent in english either (as far as I know) I mean, the closest I know would be a**h*le, which, translated back to french would mean "trou du cul"... But that's at least 2 order of magnetude bellow these 2

Sorry for being that long, life can be a bitch :P 1.2.1 is up in the air fixing the infamous issue ;)

Bennr01 already have submitted a fix for this. I just hasnt had time to package the new version over the weekend

On my pyra, xev says when pressing [fn]+[n]: KeyPress event, serial 38, synthetic NO, window 0x2c00001, root 0x3af, subw 0x0, time 22506832, (-466,100), root:(612,154), state 0x0, keycode 49 (keysym 0x60, grave), same_screen YES, XLookupString gives 1 bytes: (60) "`" XmbLookupString...

The physical hardware are several separed devices : - left nub is one joystick (having no buttons, no giro, no rumble, only 2 analog axis) - right nub is an other distinct joystick - the gaming buttons (shoulders, d-pad... everything around the d-pad) form a keyboard - the letters keys...

https://dev.pyra-handheld.com/packages/funkeymonkey-pyrainput/-/blob/master/pyrainput.cpp#L91 This code block might help too ;)

Then, ship it to : DragonBox Shop OpenPandora GmbH Asternweg 5 85080 Gaimersheim Germany With return information and a description of your issue (your nickname on these boards might/will help).

Loll ! So what ? Because you said so nobody will make it happen ?

Clearly not sold out, but since pre-order are now closed and not all delivered (yet). Normal order are not yet opened. But will, no worries. Software are availables on the dbp repo (check the menu, or my sigs :P). But this is only the beginning imho. Most games are waiting for the dev to get...

Arf, indeed. Just delete the old versions. A fix while not impossible (far from it) might takes sometimes, since i'm short on free time

good to know that my latest change on pyrainput works as intended (added force-feedback during the new year holidays :P)

aTc said on discord: https://pyra-handheld.com/boards/threads/issues-with-updating.99611/#post-1701189

my bad : I should have tested more in deep. Like I did for this batch of changes you sent :) In between all the code quality improvements from you, you've also added a way to report for progression. So I added the UI for theses pieces. Version 1.2.0 is out. - Fixing issues reported here (update...

Isn't the wiki enough ? if not adding the missing piece there sound like a plan.

Version 1.1.0 is up on the repo. Look like I found a co-maintainer for this one. Thanks bennr01 for his works. There's no real user-facing change here (see his MR for details), mainly bug fixes. But his work is the base for many improvement to come (hopefully)

Document yourself on the mess that happened because of gpsp being open-source. There's not a single chance Exo open this one.

I dont get your question. If the dbp is available on the repo, it will show up in the available tab. If it is installed and accepted by dbpd, it will show up in the installed tab. This doesn't start any dbp ; when they have been made is irrevelent. Beside, version 1.0.0 is out which strike the...

a shmups Beside, version 0.5.3 is out : package upgrade support. dbpInstaller.sh -Uu will magically upgrade all your installed dbp. There's an entry in the menu too.