Pete...
Long time since I used B3D, but Mark's code, ripped from the Castle Demo was what I used (no idea if this is the same as the code in the archives), and it ran perfectly for me. I also tried delta time on the same project. Problems included:
1) 'Lurching' - the assumption that this frame will take the same length of time as the last is not always a good one
2) Physics is a no-no. I was writing a crazy golf game, and with different time-steps using it on different machines, the distance travelled up a slope by the ball varied wildly. You would need to have a fixed time steps for the physics, giving extra complication.
3) The pain of adding all those *dt's
Long time since I used B3D, but Mark's code, ripped from the Castle Demo was what I used (no idea if this is the same as the code in the archives), and it ran perfectly for me. I also tried delta time on the same project. Problems included:
1) 'Lurching' - the assumption that this frame will take the same length of time as the last is not always a good one
2) Physics is a no-no. I was writing a crazy golf game, and with different time-steps using it on different machines, the distance travelled up a slope by the ball varied wildly. You would need to have a fixed time steps for the physics, giving extra complication.
3) The pain of adding all those *dt's