From: Solra B. <sb...@te...> - 2016-08-15 06:32:55
|
I'm surprised at how easy it was to get this far. I only started working on it four hours ago, and I already have working (partial) 60fps support. It only tweens the player's view and the positions of objects, but this alone makes a huge difference to the experience. In its current state, it's a step up from the non-30fps support that Halo for PC had; Halo only tweens the player's view. If you leave the framerate target setting at the default 30fps, nothing will change. Only if you change that setting does the new timing and rendering logic even apply. (Note that the built-in framerate measurement has always been wrong. I made it less wrong, but it still seems to be _slightly_ wrong, and I'm not sure why.) Film, save, and network compatibility are not affected, but netplay and non-realtime film playback are likely to be hilarious jitterfests in the current version. For now, set the target to 30fps when doing those things. Depending on how hard it is to fix those, I may end up forcing 30fps in either or both circumstances. Interested parties who can build Aleph One from source can check it out on GitHub: https://github.com/SolraBizna/alephone Make sure you check out the 60fps branch before building. P.S. It's ironic that, almost exactly 10 years ago, I was dashing someone's dreams for silken Marathon, insisting that implementing it would be "hugely complicated for a fairly minor return." |