maemo.org - Talk - ioquake3 Engine Possibilities

maemo.org - Talk (https://talk.maemo.org/index.php)

- Games (https://talk.maemo.org/forumdisplay.php?f=12)

- - ioquake3 Engine Possibilities (https://talk.maemo.org/showthread.php?t=46718)

Re: ioquake3 Engine Possibilities

Most likely the bugs you're seeing in ioquake3-maemo6 are due to the QVM support, also the optimization flags changed and the input code was reworked (again to allow for QVM support, but I did this rather quickly.)

I'll try to take a look at it most probably over the weekend. Sorry if this is causing you guys problems, but for now, as mentioned, you can use maemo5.

Re: ioquake3 Engine Possibilities

Is there a way to disable the accelerometer?
________
Anal Plug

Re: ioquake3 Engine Possibilities

Quote:

Originally Posted by nax3000 (Post 656529)

Is there a way to disable the accelerometer?

Yes, you can set accel_sensitivity to zero by editing /home/user/baseq3/autoexec.cfg:

set accel_sensitivity 0

Currently there is no button combo to toggle the accelerometer on/off. Is this a feature you'd like to have?

Re: ioquake3 Engine Possibilities

Quote:

Originally Posted by omcfadde (Post 656951)

Yes. I can't seem to get even one shot at the AI with the accelerometer..
Also I though this was the regular quake 3 thread woops hehe..
________
Design host

Re: ioquake3 Engine Possibilities

Is it possible you add mouse and joystick support? It would be good to play with Dualshock 3...

Re: ioquake3 Engine Possibilities

Quote:

Originally Posted by nax3000 (Post 657062)

Yes. I can't seem to get even one shot at the AI with the accelerometer..
Also I though this was the regular quake 3 thread woops hehe..

Just install the older version! auto aim is way more fun and playable.

Re: ioquake3 Engine Possibilities

Quote:

Originally Posted by omcfadde (Post 656406)

It is good to see that you are back and that Quake 3 hasn't been abandoned. Now that the N900 GL libraries have been updated, can you make versions of Quake 1 and 2 that are GL accelerated? No rush or anything but it never hurts to ask eh? :o

On a final note, while you are checking, are you able to correct the lighting in Quake 3. It appears that it is showing as Vertex Lighting even though it is set to Lightmap. They ambience and shadows are missing. Even the N82 version has the correct lighting. Also, the game crashes if I change the graphical settings. The PC and other mobile versions close upon changing the settings and then they relaunch with the new settings. It appears that the N900 version forgets to relaunch.

Re: ioquake3 Engine Possibilities

To me autoaim feels like cheating, can this game be updated we can aim with the accelerometer?

Quote:

Originally Posted by slender (Post 652146)

Quote:

Originally Posted by megaexer

See accelerometer control, to me it's easy!

http://www.youtube.com/watch?v=Yl91gQikaog - skip to 2:28

YES. There is many ways to implement it and in that video it´s implemented in good way. Some keys to success

- Accelcontrol only turning (towards,backwards from keys)
- Give user access to sensitivity
- Also put some inertia to turning so that it doesn't react to too little turns but still reacts so that you do not have to tilt whole screen sideways

So....Do we have ANY game right now on N900 that can be installed pretty easily and has optimized accel.controlling taking account of list.

Also I agree with the lightmaps and hardware accelerated Quake II part.

Re: ioquake3 Engine Possibilities

Quote:

Originally Posted by megaexer (Post 657302)

Is it possible you add mouse and joystick support? It would be good to play with Dualshock 3...

Yes, it's possible. It's a bluetooth controller, however I'm not sure how much work is involved in supporting it on the N900 (kernel drivers, etc.) I have actually though about doing this already... I think it could make the game a lot more fun for PlayStation owners.

I don't have the PS3 controller though so it's not currently on the immediate todo list.

Re: ioquake3 Engine Possibilities

I am looking at improving the input, and fixing the issues discussed already (performance regression, input bugs, etc.) Actually I did a little work on it this morning, so maybe something this weekend. :)