Stupid phone...zlnes...argh i hat this...zones. 

Hey, that's a good idea: once you put your finger on the Fire button, any sliding you do with that finger should act as aiming, as long as you don't lift your finger (and you still keep shooting).


I've gotten a few crashes with Cache_MakeLRU: active link

I'm trying it out with a little bluetooth keyboard now, on fvf.servequake.com -- where everyone else should be trying it, since it's coop and you can sit around and chat if you want while everyone else kills the monsters ;) 

Probably a better option is to have a circle onscreen for a virtual joystick, and the movement is determined by your finger position within the circle.
I'm not one to stare a solid mobile version of Quake in the mouth (so to speak) but since Gunter has brought it up:

If there was this virtual thumb stick scheme I would play this on my phone often as opposed to just testing this out and playing occasionally. The current style of control is too difficult to get used to to play for long stretches.

I agree that this code should be brought into a repository as well for those who'd like to assist in development. 

Oh yeah, forgot was I was going to say about bluetooth controls: when you detect input from a bluetooth keyboard (or gamepad - do those work? I'll find out later), you should remove the onscreen control overlay, because it's not being used.... If someone touches the screen, then you draw it again until you detect bluetooth input.

... and you really need to disable the android Sleep mode, heh... While I wtas typing this, my table fell asleep, and Quake go bye bye. 

Is there any way to add original soundtrack? 

If I use 3 fingers on the left like I do on a keyboard, it's actully not bad. I still can't steer and shoot at the same time though. 

https://forums.libsdl.org/viewtopic.php?p=52442
https://stackoverflow.com/questions/6361966/exit-android-app-kill-all-processes

Android apps are not automatically unloaded even after the onDestroyed() callback, e.g. when they are in the destroyed lifecycle state. They will only be removed from memory if more recently started apps would require memory themselfes.

You cannot completely "exit" an Activity on Android (like on Windows or other OSes where exit() resp. return from main unloads the program from memory). Android will decide for itself whether and when to remove an Activity from memory.

Now I understand why I end up with an accumulation of several apps in the "Multitasking Screen" pic after I closed them.

The reason behind this design is the fast restart of applications (caching). 

@dudeq - Not yet, but it'll be coming.

@gunter - I have seen that happen on rare, I also know how to fix it.

As far as detecting a Bluetooth Keyboard, I don't know that SDL2 provides a method for that, but I think what would work just as well is that ...

1) opening the menu with the keyboard causes the in-game controls to hide

2) opening the menu by touch would unhide the game controls

After all is quite possible to not want to use the keyboard for playing, just entering console commands.

This scheme would satisfy all preferences and not require a setting, so it would be real convenient. 

What about using quaddicted? 

(UNSUPPORTED - BUILTIN QUADDICTED/QUAKE INJECTOR)

(Requires registered Quake and QuakeDroid doesn't check to see if registered vs. shareware)

In the console

1) type "install rapture"
2) type "game rapture"
3) Do Single Player->New Game

I have installed 6-7 mods with it -- things like (kinn_marcher, nihilore, rapture), but would prefer to test it more and think more about the structure on Android. Also johnny law provided me an example or 2 were unexpected file structure in a map jam confused the unpack a bit.

So "Should work, unsupported, use at own risk" because I want to exhaustively review it. 

Yeah that isn't a problem on iPhone, but you can't really mess with your own Quake folder on a iPhone, like put map from your hard drive on it. 

I guess the only solution for mappers for iphone would be to design with a controller in mind and release as normal. 

The controls leave something to be desired. As was said, it'd be nice if jump/attach were switched so attack is in a more naturally reachable position, maybe the ability to manually place the buttons.

Also the icons are a little faint, and the movement buttons are not very easy to use.

Any chance of a Quake-Touch type radius where on the left side is like a trackpad (like the aiming?)

As crappy as Q-touch is the controls are actually very natural and it's pretty easy to move around, whereas with this setup the individual buttons and binary movement make phone play much less enjoyable 

Here are my current thoughts on control options:

So you have possibly an onscreen graphic of a circle on both the left and right side of the screen. Left circle is movement, and right is aiming. Each circle would necessarily have a dead zone in the center, but as you move your finger around in the circle you would just measure the distance from the center and the direction of the line. These pretty much emulate analog joysticks. If you move your finger outside the circle it just reads as the maximum value which is the same as touching the edge of the circle, since you are noting the line from center to your finger position.

Ok, so left circle is move forward, back, left, right. Right circle behaves the same way for aim up, down, left, right. But if you double tap the right circle, you start firing and you keep firing as long as you don't lift your finger, and you can still aim using that circle while firing.


Just above the left movement circle there is a virtual Jump button, so that if you slide your finger up to it (outside the move circle) you keep moving forward and you jump.... These should probably also still be a virtual jump button above the right circle for tapping, because "jump while aiming up would not work well, but it could still be tappable if you aren't aiming.


Now you could get fancy, and not draw set cirle areas, but within a fairly large area on the left and right of the screen, you just detect the first place a touch occurs, and set that as the center of the circle (and then possibly draw it once a touch occurs). The movement controls would work the same as I described, just by measuring the distance and direction of the finger starting at that first touch point. When someone lifts their finger, you just forget the last touch start point and make a new one when they touch the screen again.

You may need a permanent jump tap button somewhere on the right to go with this scheme, but that button could also be dynamically relocated to just above the wherever the touch occurs and the circle is positioned when that happens.

The move circle could optionally respond to a double tap to toggle to walk mode, or to trigger a jump, or something else.


I also do think the weapons in the status bar do need to be touchable to select a gun (actually, to trigger impulse 1-9), abut if you swipe left or right along the weapon area, it will cycle weapons left or right. Touching the player face could activate messagemode. 

Any chance of a Quake-Touch type radius where on the left side is like a trackpad (like the aiming?)

Sure. I check that out and see the scheme there. 

I'm considering some of those kinds of concepts. I feel if I can just get the controls more tuned ... 

AD works great aside from that 

I have something in the works ;-) Might take a few days or perhaps I'll be very lucky and it could go faster. 

New Version :Just Reinstall
(Will show 1.92 in console)

New:

* Switched attack + change weapon position (everyone)
* Sepulcher support (pulsar)
* Underscore shows in on-screen keyboard (qmaster)
* Bluetooth keyboard use auto-hides in-game controls (gunter)
* Empty quake_command_line.txt doesn't hang. (qmaster)
* Water alpha vertical lines fixed (qmaster)

Looked into
* Immersive mode - Not seeing clear-cut SDL2 support in a stable SDL2 release. But will keep and eye on it.

Other issues/suggestions pointed out are on the list, I hope to get some more done in a new version in a few days.

Thanks for the feedback/suggestions/bug reports, Android is diverse in device variety and it has been greatly helpful! 

Hm, the onscreen control overlay doesn't seem to go away when I use my bluetooth keyboard(s). The overlay does vanish when I'm using messagemode though.


Change
Jump
Attack

is not a good layout. Your default finger position is on Attack. Other buttons should be within one button of that finger position. With Attack all the way at the bottom, it's a large motion to get all the way up to that Change button. That's why I think it should be:

Jump
Attack
Change


With thumb resting on or over the Attack button, it's easy to get to either Jump or Change.


So, it seems many mini bluetooth keyboards (like mine) have no Escape key. I can bind some other key to togglemenu, but it doesn't work like Escape, in that it won't cancel messagemode, for example. Luckily you have the little top-left triangle that acts just like an Escape key.

My little bluetooth keyboard has tougher problem though. Pressing Func+Up or Func+Down should give me PageUp or PageDown. But this keyboard is some weird generic thing (I have a different one that does work correctly in this regard), and instead it triggers Windows+Up and Windows+Down, so I can't scroll up and down in the console. So how about allowing me to swipe up and down in the console? A tap on the console should obviously trigger the onscreen keyboard, buy an up or down swipe could instead trigger PageUp/PageDown to scroll the console.


I also have a almost full-size Mircosoft bluetooth keyboard, and while it does have an Escape key, it doesn't even have Functionable PageUp/PageDown, yet it has Functionable Home/End.... So no console scrolling with this onn either. Though if I were going to use a large keyboard, I may as well just use my XP Netbook, heh. 

Looks like I needed to provide more detail.

Do you have a tidle/backquote key? That will trigger the console and cause the keyboard to hide.

Let me know.

Working on game controls come takes time, I did not have time to do anything with control. 

Oh, maybe we are talking about a different thing.

I had suggested that the onscreen control overlay be completely hidden in-game if a keyboard is being used.

Yeah, I can effectively use the tilde key and pull down the console -- the onscreen overlay doesn't show on top of that.

I'm wanting a way to hide the overlay during game play. Like if input is being detected, but no screen touches are being detected, that should indicate that someone is not using the touch screen controls, so the overlay can be hidden. 

Yeah, probably so but that thought didn't cross my mind at the time, haha.

So for now, press tilde and it will hide the touch controls. ESC to the menu will cause them to reappear.

Next time, I'll have any keypress hide the controls. 

Underscore on console touch keyboard works great!
Empty command line file fix confirmed. (I like to keep it empty for vanilla.)

BUT water alpha no longer works. I tried different values of r_wateralpha but no luck.

Bug report:
When the player camera is looking too far up or too far down past about +/- 80 deg, the turn direction flips and rotates the view the opposite way. Expected:slide thumb right looks right, slide thumb left looks left. The wierd part is that it only seems to happen if I make one continuous thumb swipe that looks up/down and to the side in a sweeping thumb arc such that the view moves past a certain threshhold angle for pitch and only then does the yaw reverse. If I make quick single swipes it works correctly regardless of view pitch. 

Very excited for this, but when I run it I get a blue screen tint to the screen as the opening demo plays. I can't access any menus at that point so the demo keeps playing with a blue tint to everything. I am testing with a Galaxy S9- any ideas? Thanks and congrats to Baker.