- SCUMMVM CONTROLS ANDROID INSTALL
- SCUMMVM CONTROLS ANDROID ANDROID
- SCUMMVM CONTROLS ANDROID CODE
- SCUMMVM CONTROLS ANDROID BLUETOOTH
- SCUMMVM CONTROLS ANDROID TV
However, you show no interest to do anything on your own. A lot of people got into open-source projects because they liked some feature added or some bug fixed, even vastly more complicated issues than analog stick support. You then even go on to show your complete ignorance by trying to make it sound ridiculous that a "newcomer" would be able to fix this issue. What is really just bad behavior is that after people politely point out that nobody is looking at this right now and the likelyhood is small that someone will, you show an attitude which is makes people question what your parents taught you when it comes to manners. You just rant, your statement about "project management" just makes you look impolite, and will definitely not increase your sympathy rating with anyone. However, you do a miserable job at motivating people to do so. It seems you want to get someone from us to look into fixing your issue.
SCUMMVM CONTROLS ANDROID ANDROID
The people who worked on the Android port in the past are either busy right now or not active anymore. And of course we focus on bits which personally affect us, what we want to see fixed ourselves, first. I am pretty sure you have no idea how a project like ScummVM works. (Maybe a newcomer could fix our mouse emulation code. They dont even see them as devices worth the effort - but still maintain the android build as part of their core three development platforms. SIGH They missed the start and uptake of an entirely new product category and now find it - reasonable - to bring those devices in - to a playable state - whenever. So on top of your sigh (that may still be valid). With reporting on the issue and probabilities I have done what I am able to to address this. HINT - most of those Android settop boxes/sticks will never get connected to a mouse/keyboard and TVs dont have touchscreens. While you are offering an Android build for the device category with the highest uptake in years - that is literally broken. You are "flagging this low priority" - because WAYNE.
SCUMMVM CONTROLS ANDROID BLUETOOTH
SCUMMVM CONTROLS ANDROID CODE
SCUMMVM CONTROLS ANDROID TV
Android TV boxes/sticks arent going away. Right now, the Android built doesnt even have controller mappings for "toggle mouse cursor speed", while some of the console ports in the past had. When you get away from a "people only use us on their phone - touching the screen" standing, maybe start looking into how people will use you on android set top boxes - because its a growth market.
SCUMMVM CONTROLS ANDROID INSTALL
So may I ask from you, that you first look into the generic implementation of your Controller Mouse Emulation - because its very, very likely that it breaks there.Īlso - the Fire TV Stick right now is the Android settop box (/stick) with the fastest sell through and install base out there. And they all have to use different implementations. (Allthough it is unusable because of another implementation bug (resulution scaling vs mouse emulation speed.))įurthermore - NO emulator, or game (sideloaded, not downloaded from an Amazon store) I have EVER tried on the Fire TV (Stick) has EVER shown any problems while the Analog stick is used. Retroarch (another multi system emulator) for example doesnt even know the Fire TV controller (not even the mappings), but after you do the mapping for it - it works with their ScummVM core (which is based on the nightlies), without it showing the problem.
Id say it has something to do with your implementation of mouse acceleration - because even when you hold it halfway down, you get movement, but then it force stops after a few inches, until you change direction. And the problem has to be reproducible with many controllers out there. I'd say your controller integration is botched. But it is definitely reproducible with one. It is highly unlikely, that this is an issue with only the Fire TV Controller.
0 kommentar(er)
