qrack for android? how?

[Phenom]

I like and am most familiar with qrack by rook.

Downloaded quake touch off google play store. It comes with 3 engines: darkplaces, FTEQ, and vanilla GL. It also supports controller use. Phone I tested it on was Galaxy S4 active, which is still considered powerful.

DP ran like ass, fteq and gl ran pretty much perfect. The galaxy has a 5 inch screen and quake feels really good on it.

So how would one go about getting qrack up and running for an android phone? Is this possible?

#1 - Track R00k down
#2 - Kidnap R00k in any fashion possible as long as he's alive (you want Qrack for Android right?)
#3 - Place R00k in a cool environment such as a highly secure locked basement
#4 - Entice R00k with such offerings as alcohol, or alcohol.

Let me know how it turns out! I heard he's quick so make sure you bring some tranquilizer darts and some night vision goggles.

[Spike]

simply? no...
changing sensitivity might help.
vid_conautoscale 5 or so definitely makes the menus more usable, and should help with selecting the right weapon via touching the hud too.
m_touchmajoraxis 0 will let you strafe+move forwards at the same time.
m_slidethreshold will configure how far you need to move for it to do that instead of shooting. bigger values make it easier to spam attacks.

alternatively you can add a few showpic commands like the following into your id1/autoexec.cfg file:
showpic "gfx/face1" "bfwd" 0 0 0 64 64 "+forward"
showpic "gfx/face2" "bbck" 0 64 0 64 64 "+back"
this will give you a couple of on-screen buttons. add your extras as desired.

[Nato]

fte help

Im teying to use ftedroid on my device and the controls are giving me freive anyway to change them simply?

[OMacKnight]

fun fact, fte is my goto for quake 2

[MadGypsy]

You seem like a master at this stuff already.

Naaaaah, Spike is just practicin'

---

In all reality though you should probably beg him to help you. Tell him he is awesome a whole lot, he likes that. He is also the author of FTE ({random} which I believe means Future Thought Entertainment)

fteq and gl ran pretty much perfect

[Seven_Force]

Amazing post. Ty for info.

You seem like a master at this stuff already.

Gonna start researching.

I thought qrack source code was part of download? I'll have to look.

[Spike]

you don't need rook's permission, as qrack is GPLed. getting his permission is a good idea though, if only because it implies you might also get his help. source is definitely required.
try and keep your changes self contained, this makes it easier for him to adopt your changes in his version (if he does, this means your fork doesn't go stale quite so easily as it becomes merely a port instead of a fork).

android sdk Android SDK | Android Developers
android ndk https://developer.android.com/tools/sdk/ndk/index.html
I won't link qrack's source, last time I tried it was an old version...

you have four options.
1: SDL (either 1.2 or 2.0).
2: native-activity.
3: from scratch.
4: 'steal' from another project (like FTE).

SDL ports are perhaps the easiest route, if only because you can write it on your desktop then 'assume' that it'll work just fine on a phone. this means you're not stuck with trying to debug things from android's quite frankly pathetic stack traces.

the native-activity is an api and/or example within the android ndk. using this there's no requirement to use java, but you'll need to write the sys_ etc stuff yourself.

from-scratch means writing your own android program that invokes the engine via the ndk. egl stuff within java invoking C code where the actual gl calls are used.

stealing from another engine generally means that you can benefit from already-written code that is already derived from a quake engine. generally it already has all the functions and events that you're likely to need.
beware though, other engines often have additional expectations, like fte's code assumes that input and audio are safe if the events/mixing happens on a separate thread.
there'll still be a lot of renamed things.

here's some useful stuff that I use from batch scripts when debugging.
to see the output of the ndk's __android_log_print function:
c:\pathto\android-sdk\platform-tools\adb logcat FTEDroid:I *:S

to capture a stack trace from the device and display it
C:\pathto\android-sdk\platform-tools\adb logcat | C:\pathto\android-ndk-r7\ndk-stack -sym C:\pathto\engine\debug\gl_droid-armeabi

good luck.

[Seven_Force]

Well, my friend and I want to learn how to do this stuff.

Sooooo, I need to port qrack and rewrite it? Do I need rook's permission? I need source code for qrack I assume? Yes I am a noob.

[Spike]

you'd need to port it first. this can take a while... especially as you would need to rewrite enough of the renderer to support gles, as well as all the system code.

if you're willing to do all the coding, you can supposedly do it purely via the ndk now, or via sdl2, both of which would avoid needing to use multiple programming languages.

[Seven_Force]

I like and am most familiar with qrack by rook.

Downloaded quake touch off google play store. It comes with 3 engines: darkplaces, FTEQ, and vanilla GL. It also supports controller use. Phone I tested it on was Galaxy S4 active, which is still considered powerful.

DP ran like ass, fteq and gl ran pretty much perfect. The galaxy has a 5 inch screen and quake feels really good on it.

So how would one go about getting qrack up and running for an android phone? Is this possible?