Pandora Cube 2 Engine On The Pandora?


** Important info on Cube 2 **
sauerbraten / cube 2 doesn't like big maps on older videocards.

why?

sauerbraten NEEDS hardware occlusion queries, otherwise, loads of rendering time is wasted on surfaces "behind" the walls around you. If occluders are included in the pandora hardware, Cube 2 should run a treat presuming that map loading etc and other demands aren't too high.

however, Cube 1, being essentially a 2D-mapped-into-3D style engine like DooM and the like, does occlusion on the CPU, with a system of "solids": cubes(co-ordinates on the 2D grid) that are 100% wall, from ceiling to floor. the player cannot see through them, so it works =]

Cube 1 and hence Actioncube runs on virtually anything, so it should fare well on the Pandora for sure =]
There are even experiments with porting to the GP2X, see the "Yeti3D" port on the 2x archive. Yeti3D is based on the cube engine, designed for low-power devices such as the GBA.

GunPei2X said:
BenT said:
[*]Whilst the game part of Cube 2 is easily converted to use the dpad & analog sticks (or should be); there will be difficulty in porting the map editing functionality. This would be really worthwhile as cooperative editing via WiFi on the handset would be just awesome!
(apologies in advance if I am misunderstanding) Can you convert the mouse input to touchscreen? With that and the keyboard, editing should be a breeze.


yes, true. map two keyboard buttons to act as mouse scroll (push and pull cubes), say set a modifier key like A such that A+L=leftclick and A+R=rightclick, touchscreen for mouse movement, and there you go!
 
Last edited by a moderator:
CC_machine said:
Cube 1 and hence Actioncube runs on virtually anything, so it should fare well on the Pandora for sure =]
There are even experiments with porting to the GP2X, see the "Yeti3D" port on the 2x archive. Yeti3D is based on the cube engine, designed for low-power devices such as the GBA.

yes, true. map two keyboard buttons to act as mouse scroll (push and pull cubes), say set a modifier key like A such that A+L=leftclick and A+R=rightclick, touchscreen for mouse movement, and there you go!


Damn I must have missed Yeti3D. Thanks for the heads up CC :)

Maybe the volume control can be used for mouse scroll (when in the editor), as we won't be needing the sound?
 
Last edited by a moderator:
Tripmonkey_uk said:
CC_machine said:
Cube 1 and hence Actioncube runs on virtually anything, so it should fare well on the Pandora for sure =]
There are even experiments with porting to the GP2X, see the "Yeti3D" port on the 2x archive. Yeti3D is based on the cube engine, designed for low-power devices such as the GBA.

yes, true. map two keyboard buttons to act as mouse scroll (push and pull cubes), say set a modifier key like A such that A+L=leftclick and A+R=rightclick, touchscreen for mouse movement, and there you go!


Damn I must have missed Yeti3D. Thanks for the heads up CC :)

Maybe the volume control can be used for mouse scroll (when in the editor), as we won't be needing the sound?


As far as I know, the volume control wheel does volume limiting via hardware, not software, therefore you can't map it to anything.
 
Last edited by a moderator:
Could use an anaologue stick for mousewheel, or even Dpad -- L/R to toggle left/right mouse button, and U/D for wheel mouse.
 
Back
Top