|
Post by redangel121 on Apr 29, 2014 3:35:06 GMT -5
Found it in the play store a while back. Thought you guys should know. They all work great with the campaign/expansions and online. The controls are fairly well designed and customizable. It just requires your base files transferred to your device and everything else is good to go. The same guy that made the Q2 port also made... QI4A <== Quake 1 QII4A <== Quake 2 QIII4A <== Quake 3 DIII4A <== Doom 3 RTCW4A <== Return to Castle Wolfenstein
I played all sorts of maps and gamemodes to test them out. The only thing I can't do is play Q2 with bots (still trying to find a good work around, lemme know if somebody figures that one out).
|
|
|
Post by knightmare on Apr 29, 2014 14:09:54 GMT -5
You'd need to get his source files for Q2 to see how he compiled/ported the game DLL for Android, and then do the same to an open-source Q2 bot, like 3ZB2 or ACE bot. Porting the Eraser bot is unfortunately not possible due to its closed-source navigation/node code.
|
|
|
Post by redangel121 on Apr 29, 2014 14:34:07 GMT -5
I tried to get in contact with him a while ago but he never got back to me. Now that I know eraser bots are not compatible I'll try to use the others you just mentioned.
EDIT: I tried just using 3zb2 on my device but it comes up with several "doesn't have a spawn function" errors when I load any map. The exact same thing happened when I used eraser. Do you have advice that doesn't mean I have to learn heavy coding?
|
|
|
Post by knightmare on Apr 29, 2014 20:38:41 GMT -5
They're ALL incompatible with any Android port. The Eraser bot is just impossible to make compatible without some serious reverse engineering that's beyond me.
Quake2 mods are Win32 DLLs, and won't run on anything else like Quake1 mods do (and they even break when you add certain new features to the engine). You have to do a porting job on the bot's source code, there's no way around it.
|
|