Bargas / kwaak3

Automatically exported from code.google.com/p/kwaak3
0 stars 0 forks source link

Suggestion for how to handle further modifications for android. #103

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. no issue, just a suggestion below
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
newest test release, Android 2.1, Droid X

Please provide any additional information below.
I used to do a small bit of modding for Quake 3, and I feel many of the issues 
faces by putting quake 3 on a mobile device can be overcome via a custom mod 
for android phones.

This would be a pak file that gets loaded in addition to quake 3 (you'll have 
to add that to the code, to load all pk3 files present in the quake3/baseq3 
folder). Anyways, th einterface is completely changeable, and I think, through 
the loader, and via remapping to a joystick input, we could get multitouch 
input working. And the mod could include a onscreen dpad that is directly 
hardwired to our fake joystick input.

Anyways, it's a long shot, but at the very least, the menus of quake 3 could be 
made completely from scratch, to show options that matter to the android 
version, and perhaps bigger buttons for easier touch input. This is an 
illustration of my ideal view of the game on my droidx:

I think double tapping on the on screen dpad could be jump too, but switching 
from 1 to 2 fingers that fast probably would glitch out the aiming.
(btw, the dpad graphics I just swiped from zenonia)

Let me kno what you think. At the least I know the menus are possible :P

Original issue reported on code.google.com by WACOM...@gmail.com on 14 Aug 2010 at 8:35

Attachments:

GoogleCodeExporter commented 9 years ago
And for some reason I hid the layer when I saved out that showed the touch with 
right thumb is still used for aiming.

If we could somehow box off the screen (probably separate from the mod, 
probably have to be in the code, and make any touch in the area of the On 
screen dpad be sent as joystick, and anything outside be mouse (when not in 
menus anyways) then that would clear up the majority of issues with tapping on 
the dpad messing up aiming. (it may still drift, but no hardcore glitches I 
think)

Bear in mind this is all speculation....

also with a custom mod, I wonder if we would still easily be able to play 
online with regular copies of the game.

Original comment by WACOM...@gmail.com on 14 Aug 2010 at 10:32

GoogleCodeExporter commented 9 years ago
I have been working on some input changes, I might post a test build today or 
else tomorrow. I'm not an artist, so initially the joystick would be something 
basic but that's good enough for testing ;)

Original comment by roderick...@gmail.com on 15 Aug 2010 at 1:04

GoogleCodeExporter commented 9 years ago
That is great to hear! If you need any UI art or anything, I will gladly offer 
my services. Any chance of having the :load all paks in the baseq3 directory" 
feature in this build? rather than the "load pak0-8.pk3" like it is current? 
I'd love to help by starting a UI mod that'll be a bit more usable on android.

Original comment by WACOM...@gmail.com on 15 Aug 2010 at 1:07

GoogleCodeExporter commented 9 years ago
There is a new test build with an initial joypad (see bug 1 for a little more 
info).

Later on it should become prettier (I might be able to use your services for 
that). I'm not sure yet how to proceed with UI modding. I don't really know how 
that stuff works. If we decide to modify it, I don't think we would be able to 
use the original UI since it is proprietary. If you can provide more details 
that would be great and how difficult is it to create a basic UI from scratch? 
(or what parts did you want to modify)

Later on I would like to do as much of the configuration on the android side 
(and get rid of the control overrides on the quake3 side) and the same perhaps 
for some other settings.

Original comment by thunderb...@gmail.com on 17 Aug 2010 at 6:39

GoogleCodeExporter commented 9 years ago
Hmm, as far as UI modding goes, I only see two ways to go about it. the nice 
thing about using quake3's built in modding setup is that its pretty well 
documented, and you would be able to test most of it out on a PC.   Also the 
mod can be a separate file from the game pk3s meaning no infringement.  I have 
done modding in the way of maps and textures, but none on UI,  though I'd be 
glad to learn if it means I can help out on the porting of one of my favorite 
games.  :).    Modding the game from here android specific code may be harder,  
but I have no idea to be quite honest.  i'm sure a little of both will be 
needed to get this thing polished.   Anyways, I tested your new version,  an 
while it still needs work to be useful,  you definitely figured out how to make 
a control UI on screen when in-game.  On screen controls will really only be 
useful though if you can find a way to implement multitouh, simmilar to the 
many emulators that do things that way (like nesoid, gameboid, psx4psx4droid 
etc).   Anyways Im sure the in game menus would be easiest tthrough a pk3s mod, 
 so I'll start researching that in hopes that it will come useful. 

Also,  unrelated, when you set jump to mouse 1, aka touch,  it doesn't work.  :P

Original comment by WACOM...@gmail.com on 17 Aug 2010 at 7:59

GoogleCodeExporter commented 9 years ago
The current hacky code should support multi touch. Try to rotate/shoot while 
you walk using the joypad. Though it depends on the device if there is real 
multitouch though. On my Nexus One I can receive two touch spots.

Original comment by thunderb...@gmail.com on 17 Aug 2010 at 3:13

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I'll test that again tonight, I guess by default it isnt set up correctly in 
the quake 3 contraols? On my DX it was making me aim whenever I'd drag the 
joystick, and no difference when off of the joystick.

Anywho, I took some of my free time and made a mock-up of what sort of 
interface Id try to build for you if I get to it.  This would be the 
replacement for the loader, not the in game graphcis. This is using quite a bit 
of original textures from quake 3, so I'm not sure if that's 100% kosher, If 
not I can do something from scratch.  What nice though is this is all made of 
easily script-able elements. Mostly tiled images, and only 4 sections.

Let me know if you like this. I have enough android coding experience to try to 
make the layout work, or if you'd prefer I can give you the elements or PSD 
file if you choose to go with this.

Original comment by WACOM...@gmail.com on 18 Aug 2010 at 7:04

Attachments:

GoogleCodeExporter commented 9 years ago
Hey there, I am very excited about these prospects! I know nothing about code, 
but have a fair bit of experience with gimp (free photshop replica) I would be 
happy to do design element and graphics for hud or menus.. please feel free to 
send me picture requests! On a secondary note, please fix the issue of the alt 
key so using the terminal works on my droid2 so I can find my fps, thanks!

-Spencer

Original comment by sadamsr...@bwscampus.com on 19 Oct 2010 at 6:08