Stella For Gp2x


Perhaps the SDL joystick reader is screwy?

There shoudl be no dead-zones from the joystick-reader; how you interpret the switches is up to the dev, but SDL interprets them in some specific manner; if SDL is reporting real dead zones, then its broken.

ie: I'd test that.. if the stick is reporting dead zones via SDL, SDL is broken.
I don't get it... isn't a 'dead zone' just where no joystick input is read?
 
Last edited by a moderator:
Perhaps the SDL joystick reader is screwy?

There shoudl be no dead-zones from the joystick-reader; how you interpret the switches is up to the dev, but SDL interprets them in some specific manner; if SDL is reporting real dead zones, then its broken.

ie: I'd test that.. if the stick is reporting dead zones via SDL, SDL is broken.
I don't get it... isn't a 'dead zone' just where no joystick input is read?


Yes but that dead zone can be inbetween directions as well as the center. If SW1 +SW2 was read as a "no input" it would also be a dead zone.
 
Last edited by a moderator:
In regular usage, there shoudl be very little dead zone .. ie: There shoudl almost always be some switch or another reporting (sometimes even the wrong one from my testing :) ..

.. and since we know iot works well in other apps, its almost certainyl a pure software problem of course..

.. so the problem is either in SDL, or in the interpreting of the SDL values, or in the emu core's interpreting of the suggested values.

Too many layers :)

jeff

I'd check out the code or convert it to minilib, but I'm pretty seriously used up right now :/
 
I reckon it's in the interpretation of the values, maybe the controls get JOYBUTTONUPed after they get JOYBUTTONDOWNed, and so nothing is being passed to the actual emulator. Just a theory.
 
In regular usage, there shoudl be very little dead zone .. ie: There shoudl almost always be some switch or another reporting (sometimes even the wrong one from my testing :) ..

.. and since we know iot works well in other apps, its almost certainyl a pure software problem of course..

.. so the problem is either in SDL, or in the interpreting of the SDL values, or in the emu core's interpreting of the suggested values.

Too many layers :)

jeff

I'd check out the code or convert it to minilib, but I'm pretty seriously used up right now :/


I've been using theoddbot's libs. Is there anything better?

EDIT: Maybe better wasn't the word. Are there any known SDL Joystick issues with theoddbot's libs?
 
Last edited by a moderator:
In regular usage, there shoudl be very little dead zone .. ie: There shoudl almost always be some switch or another reporting (sometimes even the wrong one from my testing :) ..

.. and since we know iot works well in other apps, its almost certainyl a pure software problem of course..

.. so the problem is either in SDL, or in the interpreting of the SDL values, or in the emu core's interpreting of the suggested values.

Too many layers :)

jeff

I'd check out the code or convert it to minilib, but I'm pretty seriously used up right now :/


I've been using theoddbot's libs. Is there anything better?

EDIT: Maybe better wasn't the word. Are there any known SDL Joystick issues with theoddbot's libs?

Going to theoddbot's libs actually *fixed* issues for me. I had been using some other version of SDL I found and some buttons didn't register and other stuff like that. Joystick input works fine in gp2xmess using the same library, so I'm wondering if maybe it's the emu's interpretation of the input itself.

~telengard
 
Last edited by a moderator:
It sounds like theoddbot is a pretty L337 dude, an "unsung hero".

You hardly hear from him or anything. He deserves alot of credit though.
 
Ok. Today was a bad day for my GP2X.

Story: I was in the process of debugging the current Stella code. I had my GP2X hooked up to my laptop, mounted, ready for transfer. I rubbed my hands together and the battery died. When I changed batteries, I turned the GP2X back on and now all I get are the colored lines. Bricked! <_< I'm ordering another one as we speak, but it's on preorder (that is unless someone knows how to recover from the colored lines...).

I'm looking for one (1 [uno | eins] ) beta tester who is articulate and willing to see the gritty underbelly of the latest build. If you are interested, send me an email to the address located in the readme. Please identify yourself by name and gp32x screenname, so I can put a voice to a name. Beta tester must be a patient person.
 
zansatsu posted on Feb 1 2006 at 09:37 PM said:
TelcoLou posted on Feb 1 2006 at 10:22 PM said:
:(

Very sorry to hear 'bout your mishap. I sent you an e-mail.

Position filled. Thanx Telco.

No prob. I'm glad to help :)
 
Last edited by a moderator:
zansatsu posted on Feb 1 2006 at 09:03 PM said:
Ok. Today was a bad day for my GP2X.

Story: I was in the process of debugging the current Stella code. I had my GP2X hooked up to my laptop, mounted, ready for transfer. I rubbed my hands together and the battery died. When I changed batteries, I turned the GP2X back on and now all I get are the colored lines. Bricked! <_< I'm ordering another one as we speak, but it's on preorder (that is unless someone knows how to recover from the colored lines...).

I'm looking for one (1 [uno | eins] ) beta tester who is articulate and willing to see the gritty underbelly of the latest build. If you are interested, send me an email to the address located in the readme. Please identify yourself by name and gp32x screenname, so I can put a voice to a name. Beta tester must be a patient person.

Man, I was testing last night and thought the same thing was going to happen to me. The batteries died and the game I was playing (Cavern Creatures) did the coolest fade out I've ever seen. Then I got the colored lines. Luckily mine booted again. Phew.

Sorry to hear it happend to you. :(

~telengard
 
Last edited by a moderator:
zansatsu posted on Feb 2 2006 at 05:26 AM said:
telengard posted on Feb 1 2006 at 11:19 PM said:
Sorry to hear it happend to you.    :(

~telengard


I don't understand how it could have happened, but GPH will hear from me. My one year warranty should cover this.


So the beta testing thing is filled. If you ever need anyone else please let me know. I am pretty good at finding things and joystick configs etc.

Sorry about the bricking, GPH needs to fix that buggy FW.
 
Last edited by a moderator:
OK.... *crosses fingers* I've posted a revision of 2.1 to http://archive.gp2x.de/. The joystick should be fixed now, along with an added feature (phosphor!).

Please give me any feedback you have. We suspect that PAL roms might hang, if anyone could confirm this let me know so I can add it to the documentation.

As usual, all feedback welcome.
 
remowilliams posted on Feb 6 2006 at 12:07 AM said:
I just tried it out and the intermediate diagonals are still hanging up quite badly here :(

Did you do a fresh install? Were the only files in your stella directory stella.gpe and stella.pro on your first run?
 
Last edited by a moderator:
zansatsu posted on Feb 5 2006 at 11:43 PM said:
Did you do a fresh install? Were the only files in your stella directory stella.gpe and stella.pro on your first run?
DOH - it must have been an old file hanging about that caused it. :rolleyes:

It's working BRILLIANTLY now! :D
 
Last edited by a moderator:
Back
Top