Yeah ... mh and Spike's comments.
I don't want to add "bot-like" behavior and cannot control what a server uses for settings or QuakeC.
Ok, here is a demo that shows the weird centerview behavior near the end. I don't know how long the whole demo is, but it starts out in e4m7, when I reconnected with the software version because the hardware version had just crashed with that cache error. Centerview kept working fine, until we got to e1m3 at about 18 minutes in, right as we were about to exit. But around 25 minutes into e1m3 there are some good examples of me testing it and saying when I was pressing the button, then I'd wait, and then my view would be centered like 15 seconds later without me touching anything. I'm not positive I was tapping the correct button a few times before that when it didn't seem to be working at all (small android keyboard) but the other guy on the server experienced the same issue at the same time I did.
Oh yeah, additionally, I find that gl_overbright 0 causes things like doors and ammo boxes to... uh... get extremely blurry to the point where it looks like they are textureless.
saying when I was pressing the button
This one has my curiosity. I don't know how long it will take to develop some sort of plan, but an interesting bug and what should be enough evidence to trap it, is kind of like a 4D Rubik's cube.
With pq_moveup 1 set, if you go in the water (I was in waist-deep) and tap jump, you just keep furiously bobbing even after you release jump. It only stops if you actually tap a +moveup key.
In android, r_bloom 1 causes a huge black square to appear and take up almost half my screen. Yeah, I know: experimental feature in development?
gl_flashblend 1 is causing many things to appear with a blue lightball instead of orange.... Watch the start demo and see the ogres and scrags glowing blue.
Tapping the power button on android (normally this would cause the screen to go to sleep) kills QuakeDroid and HARD NUKES all configs. It even erased my name, colors, and social security number. All default controls were set to ??? (nothing), and I had to delete the config.cfg file to even get those back.
I should start holding all my bug reports for ransom.... "Deliver OGG support to the dumpster outside of the Slipgate Complex, or you'll never see your precious bugs again!!" >:D
Uhhh, In the Mark V thread, Baker said:
Gunter, I just want to point out that it is impossible to play ogg on Android or an iPhone (without unacceptably chewing up metric shit tons of CPU -- hence the frames per second would be absolute trash --- because it is an obscure format and hence does not have hardware decoding in the processor)
Soooo, I just happened to be browsing the File Explorer on my Android device, and in the "Recent" section, imagine my surprise when I found (because I had been adjusting my alert sound): "hangouts_message.ogg"
I tap that and it opens right up in a Google Play Music popup right there on my screen....
So... yeah... it seems Android is FULLY CAPABLE OF PLAYING OGG FORMAT, and at least one Google app includes sound effects in OGG format....
I guess it remains to be seen if it would actually affect the frame rate, but it seems that QuakeDroid does not yet include any music support anyway -- at least I can't get it to play the MP3s.
Though with Google having OGG support built in and used in some of its major apps on Android... I'd suspect it would not be a CPU-killing format on Android... otherwise... why did Google chose to use such an "obscure" format?
Since This Is A Good Place For Quake For Android Questions....
Quake For Android [EDIT]
Posted by Reyond on 2018/05/29 21:29:46
Hello. I have a question about running my quake mod on android devices. Of course, I can launch quake on android using qi4a port. After that I can replace original ID1 folder with my one.
But what should I do if I decide to distribute my game? How can I add my quake mod to Google play? Is it possible to make .apk file with my mod?
#1 posted by Spike on 2018/05/29 22:01:04 spam
Depends on the engine as to whether it already works. I implemented it into FTE, where it was really handy for touchscreen widgets etc, so maybe it'll work in qi4a(aka dp) already - check the path command to see.
apks and pk3s are basically the same thing so the bulk of the code is already there. Just remember that if you're nesting pk3s or paks inside an apk then be sure to NOT use compression when adding that file to your apk, otherwise seeking gets expensive. This is no great loss - other files can still be compressed, and any files inside the pk3 will still be compressed, just avoid paks).
#2 posted by Reyond on 2018/05/29 23:47:38 spam
Thanks for respond! I will try to do that with Qi4a. However, fte engine is my favorite quake-based engine but it has complicated and not really handy controls. I would like to use fte if it had handy control system. For instance I like how it is made in quake touch
#3 posted by Reyond on 2018/05/30 02:21:40 spam
Also, in FTE port movement buttons and rotating does not work at one time.
#4 posted by anonymous user on 2018/05/30 04:42:05 spam
"QI4A is broken for good I'm afraid. I know this because I had to fix the issue it has in order for QVR (Quake VR) to work correctly. Basically the problem is Android 5 introduced some security checking on calls to snprintf, which means a null string is returned if it detects invalid characters in the input string. As Darkplaces uses certain characters in its netcomms code, it is failing on starting the game on Android 5 and above and is unable to go any further."
So, I acquired a USB OTG cable from ebay for under $1 (great option as long as you don't mind ordering directly from China and waiting weeks for it to arrive... and I'm a cheapo who hasn't upgraded his WinXP netbook, so that works for me!).
I hooked up a USB mouse, in an attempt to make my teeny tiny Quake device ( http://www.fvfonline.com/forum/viewtopic.php?f=4&t=3810
) as much like a teeny tiny PC as possible.
Well, mouse control obviously hasn't been considered in QuakeDroid, but it does function at a system level in Android (just like OGG decoding! XD ), and shows a mouse cursor on the screen.
It thinks my screen on QuakeDroid is rotated 90 degrees to the left though (same with the softkeys being along the right side of the screen), so when I move the mouse up, it moves left on the screen, moving the mouse right moves the cursor up, etc.
It acts as a "touch" rather than functioning as actual mouse1 or other mouse motions. If I hold down mouse1, then I can "drag" the screen around just like with touch aiming. Double-clicking makes it fire, and I can click through the menus (sideways...).
And if I use the mouse cursor to press any of the onscreen controls, it activates that control, just like a touch.
So actual mouse controls might be viable, assuming the mouse can be separated from touch controls. But I'm not sure how possible that is....
I have never seen any app for android, where the mouse does more than stay a cursor. Mouse is probably not supported in a way that would enable FPS Gaming.
Though in PUBG Mobile, there are people ”hacking“ which means Android emulator users from Windows using Keyboard and Mouse. Those are not supported by the actual game and are very unfair for other players.
relative motion requires android 7.0, and even then I've no idea how to hide the cursor itself.
android just wasn't made for mice...
Hm, there do seem to be some methods for distinguishing mouse input: https://stackoverflow.com/questions/12705117/handle-all-mouse-events-in-android
At the very least, perhaps the mouse could still operate the menus, if QuakeDroid and Android could agree about which direction was "up."
Feature Request For Your Next Coding Season
I'd like to play in ”full immersive“ mode, without the black Android navigation bar with the gray triangle, circle and square (see scr.)
Also, I am unable to play mp3s. My CD-Rips are mp3s at 256kbs, because I have enough space for good quality.
Do I need to lower the bitrate? Which bitrate is recommended? 192kps? Or even lower?
How to compile quakedroid?
i got this error
executing external native build for ndkBuild
Compiling QuakeDroid ...
Assumes you have quakedroid_gl_source_20180508.rar downloaded ...
For source folder named:
Open folder C:/quakedroid_gl_source_20180508/Android_GLQuake
// 1. "make_symlink.bat" may need admin privledges to create the symlink ...
make_symlink.bat (double click me ... you need only do this once to build folder reference)
// 2. Compile ...
gradle_assembleDebug.bat (double click me to compile!)
// 3. Install on your phone with USB cable connected otherwise having your phone with ADB development mode available
// Which may require drivers
adb_debug.bat (double click me me to install on your phone!)
Android development can be cruel and brutal.
Android NDK (C/C++ code like QuakeDroid) is several times as cruel, as Android is geared towards Java and support for C/C++ code is awkward.
It is best if you do several Android tutorials before stepping on to this playing field to get your phone setup right and get a handle on the basics!
Finding adb drivers for your phone might be a challenge or it may go easy ... for my phone finding the drivers was moderately difficult and it was a minor nightmare finding them for my phone model.
Every phone has a different manufacturer and tons of models, etc.
ericw compiled without guidance, so I think I did a pretty solid job making it as easy to compile as possible.
May fortune ever be in your favor!
I found the problem,that was whitespace in Program Files (x86),dumb error:)
another problem in
Error:(47, 19) SDL.h: No such file or directory
SDL.h: No such file or directory
See #2 above "make_symlink.bat (double click me ... you need only do this once to build folder reference)"
I tried,its show this:
C:\Windows\system32>rem cd "C:\androidprojects\SDL\app\src\main\jni"
C:\Windows\system32>rem we are in C:\Dropbox\quakedroid_source_20180401_controllerus_functional2\SDK\SDL2-2.0.8\android-project
C:\Windows\system32>rem need to nav to app\src\main\jni
C:\Windows\system32>rem sym to here C:\Dropbox\quakedroid_source_20180401_controllerus_functional2\SDK\SDL2-2.0.8
C:\Windows\system32>rem Kill the fake folder
C:\Windows\system32>rmdir /s /q app\jni\SDL2
The system can not find the path specified.
The system can not find the path specified.
Forget about all this:)
just done that commands in cmd
local path: C:\quakedroid_gl_source_20180508\Android_GLQuake\app\build\outputs\apk\QuakeDroid-GL-debug.apk
Issues With Arcane Dimensions
I tried to run AD in this, used the command txt file to select -game ad, and it loads the menu correctly, but touch controls no longer work at that point. Is this a known bug?
@arfink - AFAIK Should Work (screenshot) @brassbite/@gutner
To the best of my knowledge, it worked for me during testing ...
AD 1.5 QuakeDroid screenshot
I mostly only checked if it loaded, walked around the map and admired the view and then moved on to the next thing on my list when I was testing.
You might uninstall AD and then reinstall it -- maybe you have a file that only partially copied or something? If you continue to have the problem after a delete AD15 and then reinstall AD15 and especially if others say they do, I'll add it to the list of items to investigate when I code next which is probably around Christmas.
@brassbite - Didn't get around to adding the soundtrack support to QuakeDroid because I ran out of time -- every time I was trying to do it someone discovered something during testing that needed immediately attention.
So adding soundtrack support in is #2 or #3 on the list for when I code again around Christmas.
I was using 1.7 fwiw. I can try with 1.5.
Oh yeah, and it might be an AD 1.7 thing anyway since the mouse driven menu from regular ol PC Mark V also doesn't work with 1.7 either.
Just tried AD 1.7 and then 1.71. Not able to replicate your issue. Mouse driven menu works fine. I also opened AD's 1.71 quake.rc file to see if it contained something unusual ... it didn't.
Obviously you have something going on, but I wasn't able to cause anything unusual to happen.
/Delete config.cfg and autoexec.cfg?
Replicated your issue.
Sometimes when the config.cfg is being written, for reasons I don't understand the config file gets truncated and it doesn't write the whole thing. Must be some sort of "Android NDK thing".
Delete your config in ad folder.
When I do an update next around Christmas either I'll do some research and find out why Android NDK may sometimes write incomplete files or have QuakeDroid ignore an incomplete config by writing a checksum into the config header.
Android is known to arbitrarily terminate applications whenever it likes, which means verifying the file wrote completely wouldn't work if that is what is going on.
But one way or another, when I do an update around Christmas, I'll make this problem impossible. (Especially since it is very annoying.)
/Excellent bug report!
I deleted config files in AD and id1, as well as autoexec, and it didn't seem to help. I'll putz around with some other stuff too.
You must be logged in to post in this thread.
Website copyright © 2002-2019 John Fitzgibbons. All posts are copyright their respective authors.