I suppose the feasibility of this would depend on the
tightness of the 30 FPS's relationship with the game
logic (i.e. whether the game speed would increase
proportionally with the FPS) and the difficulty of
untangling them.
The whole engine revolves around a fixed tickrate of 30fps.
Changing it would be a major pain, change the actual game
experience, and particularly affect netplay.
There's an alternative... David Olofson calls it "tweening,"
the idea is to calculate the frames and then "tween" between
them graphically. Kobo Deluxe does this. Still a major pain
to implement, though.
I think it's pretty safe to say neither of the above is
going to be implemented in Aleph One, even if only because
it would be hugely complicated for a fairly minor return.
-:sigma.SB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
I believe its tied to game physics. It wouldn't be Marathon
if it didn't give you headaches. ;)
Logged In: YES
user_id=810548
The whole engine revolves around a fixed tickrate of 30fps.
Changing it would be a major pain, change the actual game
experience, and particularly affect netplay.
There's an alternative... David Olofson calls it "tweening,"
the idea is to calculate the frames and then "tween" between
them graphically. Kobo Deluxe does this. Still a major pain
to implement, though.
I think it's pretty safe to say neither of the above is
going to be implemented in Aleph One, even if only because
it would be hugely complicated for a fairly minor return.
-:sigma.SB