OpenBOR v3.0 Build 4682 (Android/PSP/WII/WINDOWS)

Status
Not open for further replies.
Hey WhiteDragon, I've tested the latest build - 5484 - and the touch bug is gone, finally!
Thanks for your hard time.

Also, I noticed that the OpenBOR app doesn't starts in fullscreen anymore. You can set the mod to fullscreen (stretching to the screen) and it works, but the OpenBOR itself, before the mod runs, won't stay stretched to the screen like it was on the past.
Its a minor issue, sure. But it would be good if we have it back.

There is something happening with the non-touch controls. I've brought a IPEGA 9021 controller, which works great in every emulator, but no in OpenBOR.

Since you changed the SDL version, you can't map an bluetooth controll anymore. The engine detects random button press like a crazy clown, lol. You can't map anything because it keeps detects one of the axis mutiple times or even the other buttons.
When I tried with my old build - 4432 - it works.

By any chance, do you think you can fix this?

Edit: Also, this is a long time issue - if you have a controller pluged into your pc and something happens with the connection, OpenBOR won't recognize it anymore and you have to close the engine and run it again.
 
Ok, so please open SDLActivity.java and see public boolean onKey() method.
Try to change and test key mapping and compile.
Help me about this because I have not Bluetooth devices.
Thanks

Ps. Fixed aspect ratio.
 
I suppose that the issue is on method:
public boolean onKey() in SDLActivity.java file
in old SDL uTunnels mapped keycode because there was no support..
Maybe we need to changethis mapping...
So help me because I can't test on bluetooth controller (I have no one).
Go into engine\android\src\org\libsdl\app folder and check for public boolean onKey() method.
Then try to change keyCodes, compile and test...

BTW try this private version without old uTunnels mapping:
https://www64.zippyshare.com/v/9jV7sOQ9/file.html

Big thanks for your time and your helo guys!!
We are a wonderful team!!  ;)
 
I tested both and they dont work with usb gamepads, when im setting up controllers then p2 axis 3  is pressed , so it actyally is like on autofire and i cant setup any other button because p2 axis 3 is being used all the time, gamepad is not faulty, works fine on pc, even on old openbor version pre video playback ability enabled one had gamepad right away working but only with directional keys, i could still not use other buttons of gamepad which is weird.They actually dont register anything when you press them and p2 axis 3 is not pressed all the time like in these new openbor builds i just tried.
Not much info but maybe someone else has bluetooth gamepads.


--
I see you uploaded 2 new versions, ill test them and let you know.
No controller manager and that other version api 19 still have p2 axis 3 on autofire , so it wont let me to set anything else , so maybe if this will be taken care of then something will move forward, it even shows p2 axis 3 when no gamepads are connected
 
ON windows there is no such problem, what it is on android and im 90% sure is accelerometer/gyroscope sending its data and openbor captures it when configuring controls, you would have to ignore this data , i remember utunnels had this issue as well.
 
bWWd said:
ON windows there is no such problem, what it is on android and im 90% sure is accelerometer/gyroscope sending its data and openbor captures it when configuring controls, you would have to ignore this data , i remember utunnels had this issue as well.
Click to expand...

Big thanks bwwd, next test is disabling accelerometer
 
I think the accelerometer should be used to flip the landscape view depending on which way up you hold your phone but if you have to disable it to fix this issue so be it.
 
WhiteDragon its worth to read this thread where utunnels developed android version, i suggested looking up sourcecode of mame4droid which is open so you could see how he did android controls cause theyre great in this emulator.
http://www.chronocrash.com/forum/index.php?topic=160.30

Also i disabled gamepads and p2axis doesnt show up anymore but also i cant remap gamepad, openbor is not recognizing any buttons.
 
Disabled accelerator, please test it and report which version work..
https://www107.zippyshare.com/v/hH4jvg6r/file.html
https://www107.zippyshare.com/v/mVyD4Cwc/file.html
Thanks for all you support!!
 
"OpenBOR-noAccByActivity.apk" worked perfectly.

"OpenBOR-noAccByC.apk" still has the bug.

There is a new issue when setting gamepad buttons they are not applied right away.  So setting gamepad up and down will disable up and down with touchscreen controls and gamepad up and down will not work until you select ok. So you can get stuck on the menu.
 
Now remapping works a bit but i cant configure all controls, just left/right is detected and other up/down is called unknown, also none of the buttons work, like theyre not detected, im using generic gamepad like this , maybe i could help and find some info about it you need to make it work ? Maybe run some software on android to see whats happening when i press buttons?
11601-6aca6fb4c07f2321363c6c6d4ca97530.jpg

Gamepad works nice in emulators , i found source for nesoid, maybe you can lookup how they did input controls
https://github.com/huzongyao/AndroidNesoid/tree/master/Nesoid
Another android emu
https://github.com/def-/nimes
 
Everything worked fine on this build but a reason i could not reproduced the error was due to the directional controls working by default.

@bwwd

Did you delete you openbor saves folder before you tested ?
 
yes, i remember this gamepad did not work even in old build utunnels created, only DPAD was detecred and none of the buttons but in emulators all buttons worked.
 
I think there is a app game keyboard or something like that it makes your gamepad inputs the same as keyboard inputs so its more compatible but that is not a real fix to this issue.

what make is your gamepad ?
 
My moga hero power works on the old builds with default settings and I have the same problems as bwwd with the last one posted. In some of these test builds all buttons work but the dpad/stick has not worked in any of them.
 
msmalik681 said:
Everything worked fine on this build but a reason i could not reproduced the error was due to the directional controls working by default.
Click to expand...

So for you is this the good and one release to commit?
 
Status
Not open for further replies.
Back
Top Bottom