1. osu! forums
  2. osu!
  3. Development
show more
posted

rodrigez_BCL_ wrote:

It's on your future plan implement an online mode?
We (me and euphyy) had a chat about this a few months ago. tl;dr of what he told me then: it would be pretty complicated to do. Although if a lot of people are willing to help, we can figure something out.
posted
On opsu! android version, there's no hitsounds
i cant provide any logcat sorry.
Currently running CyanogenMod 12.1 (Android 5.1.1) Sprout8 (Android One) Official Nightlies.
Sorry 4 my bad english XD
posted

Xerath Solo Top wrote:

On opsu! android version, there's no hitsounds
i cant provide any logcat sorry.
Currently running CyanogenMod 12.1 (Android 5.1.1) Sprout8 (Android One) Official Nightlies.
Sorry 4 my bad english XD



Fix for no hitsounds on CM12.1 / Android 5.1.1,
Go to Settings>Developer Options and find the option "Use AwesomePlayer (deprecated). Activate that then reboot.
Tadaaa~~~~ Problem Solved! (Don't forget to set the option "Disable All Sound Effects" to "No" on Opsu! Android.)
Hope it helps
Sorry for very bad english hahahaha
posted
@WasuraretaKioku thank you! This actually solved my problem! You Rock XD!
posted
how can i play streams? (android)
posted

Hot Loli wrote:

how can i play streams? (android)
*facepalm*
just tap as fast as you can (or use a keyboard if you phone support USB On-the-Go)
posted

chong601 wrote:

Hot Loli wrote:

how can i play streams? (android)
*facepalm*
just tap as fast as you can (or use a keyboard if you phone support USB On-the-Go)
ok, i'll rephrase my question. how can i stream with 2 fingers, not one. I tryed to play using one finger like a pen and two for tap but it didn't work. you advice me to play streams with 1 finger? mb you will advice me to play only mouse in pc version then?
posted

Hot Loli wrote:

chong601 wrote:

*facepalm*
just tap as fast as you can (or use a keyboard if you phone support USB On-the-Go)
ok, i'll rephrase my question. how can i stream with 2 fingers, not one. I tryed to play using one finger like a pen and two for tap but it didn't work. you advice me to play streams with 1 finger? mb you will advice me to play only mouse in pc version then?
If you've got a screen big enough, you can try doing this.
posted

Hot Loli wrote:

ok, i'll rephrase my question. how can i stream with 2 fingers, not one. I tryed to play using one finger like a pen and two for tap but it didn't work. you advice me to play streams with 1 finger? mb you will advice me to play only mouse in pc version then?
well only if you have big screen, then you can use 2 fingers to stream (7+ inch minimum, 10 inch recommended) or use a keyboard attached to your phone
Keep in mind because opsu-android have limitations that it only can register only one input at a time because ospu-android emulates touch input as mouse for now.
posted
Well then, i don't have tablet, just phone 4.7 inch. Waiting for another input method.
posted
I love this project.
Personally, I think you should drop desktop support and focus only on the Android version. Too bad it's almost impossible to play streams on a touch screen. D:
posted

gintoki147 wrote:

I love this project.
Personally, I think you should drop desktop support and focus only on the Android version. Too bad it's almost impossible to play streams on a touch screen. D:
I think you got the point wrong here. There is one guy working on the PC version, which is opsu! itself, and another one who is working on opsu! for android. I think euphyy (the creator and mantainer of the PC version) would rather carry on working on it for the PC version, while leaving everything related to the android version to fluddokt, the guy working on the android port.
posted

Howl wrote:

gintoki147 wrote:

I love this project.
Personally, I think you should drop desktop support and focus only on the Android version. Too bad it's almost impossible to play streams on a touch screen. D:
I think you got the point wrong here. There is one guy working on the PC version, which is opsu! itself, and another one who is working on opsu! for android. I think euphyy (the creator and mantainer of the PC version) would rather carry on working on it for the PC version, while leaving everything related to the android version to fluddokt, the guy working on the android port.
It seems that fluddokt has been even busier than I have lately, which is why the Android version hasn't been getting as many updates. (I don't blame him, since porting my changes can't be very interesting...) But it's all open source, so really anyone can take over if they want to.

A technical issue is the way the Android version is written. To actually get the program running on Android, fluddokt had to switch the game engine from Slick2D (simple, dead, and desktop-only) to libGDX. But instead of porting the source code, which would've taken a very long time, he's "faking" the Slick2D API and replacing the implementation of all referenced methods with libGDX code. It works, as you can tell, but comes with these large problems:
  1. If someone updates the Slick2D code and calls Slick2D methods not yet "faked", all of those methods need to be rewritten as well (which isn't always easy, or even possible).
  2. If anyone continues developing the libGDX code with pure libGDX calls, the source code will be a mess of mixed Slick2D/libGDX and merging changes from the Slick2D code will get significantly harder.
  3. Some desktop code needs to be rewritten to work at all on Android, which makes things even more complicated.

The only two choices I can see are to rewrite the project completely in pure libGDX (which nobody wants to do) or continue developing in Slick2D and porting the changes (which anyone can try to do, if they're up for it).

A more practical problem is that I don't actually own an Android device, so I'm not easily able to test anything for it.
posted

euphyy wrote:

It seems that fluddokt has been even busier than I have lately, which is why the Android version hasn't been getting as many updates. (I don't blame him, since porting my changes can't be very interesting...) But it's all open source, so really anyone can take over if they want to.

A technical issue is the way the Android version is written. To actually get the program running on Android, fluddokt had to switch the game engine from Slick2D (simple, dead, and desktop-only) to libGDX. But instead of porting the source code, which would've taken a very long time, he's "faking" the Slick2D API and replacing the implementation of all referenced methods with libGDX code. It works, as you can tell, but comes with these large problems:
  1. If someone updates the Slick2D code and calls Slick2D methods not yet "faked", all of those methods need to be rewritten as well (which isn't always easy, or even possible).
  2. If anyone continues developing the libGDX code with pure libGDX calls, the source code will be a mess of mixed Slick2D/libGDX and merging changes from the Slick2D code will get significantly harder.
  3. Some desktop code needs to be rewritten to work at all on Android, which makes things even more complicated.

The only two choices I can see are to rewrite the project completely in pure libGDX (which nobody wants to do) or continue developing in Slick2D and porting the changes (which anyone can try to do, if they're up for it).

A more practical problem is that I don't actually own an Android device, so I'm not easily able to test anything for it.
Well, to be honest, I would support the choice to rewrite the entire game in libGDX.

Reasons are because of libGDX are targeted at making games on any platform as well as cleaner code base (as long we don't do much of editing and mucking around)
From my view, most of the game (map parser, objects, states (need confirming, yet to reach that part), sounds) itself can be retained as is, but the drawing part must be rebuilt to use libGDX platform.

Also, by changing to libGDX, the performance issues on opsu-android may be possible to be handled since there's no API faking going on everywhere as well as the desktop version which seems still have room for more improvement

For the part of rewriting, I might able to offer my help but because of my Java skill limitations (and the fact that libGDX documentation is quite lengthy, so it takes time for me to understand how the whole platform works for now), I might unable to handle the project on my own and have to keep up with RL stuff.
posted

chong601 wrote:

I don't think there'd be any significant performance gains because opsu! isn't very resource-intensive anyway. There's also a lot of Slick-specific code in the states and audio, so there's more rewriting required than you'd expect. I'm not discouraging you from porting the code, but if you're willing to do that much, it might really be more worth your time to help fluddokt merge changes over to his fork. (Though the new slider rendering code might be a pain to move over there...)
posted
ummm is the spinner glitch for opsuandroid fixed? (using tablet btw) laggs for half a second
posted

gintoki147 wrote:

I love this project.
Personally, I think you should drop desktop support and focus only on the Android version. Too bad it's almost impossible to play streams on a touch screen. D:
Don't download 1/4 beatmaps then. Is that hard?
opsu! could need specific beatmaps for it, like osu! stream
posted

XinCrin wrote:

gintoki147 wrote:

I love this project.
Personally, I think you should drop desktop support and focus only on the Android version. Too bad it's almost impossible to play streams on a touch screen. D:
Don't download 1/4 beatmaps then. Is that hard?
opsu! could need specific beatmaps for it, like osu! stream
im not a fan of touch screen osu but what about having bottom right corner of screen for tap overlay keys.
posted

Agrrox wrote:

im not a fan of touch screen osu but what about having bottom right corner of screen for tap overlay keys.
tfw opsu!-android have no support of multitouch
posted
Play streams is not fun in a touch screen imo.
show more
Please sign in to reply.