<no subject>
Re: <no subject>
Yeah Photex engine was definitely advanced for its time but also an incredible spaghetti code. Partly it is also the fault of coding standards back then, they had to do a lot of workarounds to get stuff working and those workarounds add another layer of difficulty in porting the code over to newer render software.
Re: <no subject>
To give you an idea... there's some legacy HB code inside the MTM2 codeKmaster wrote: Mon May 04, 2026 8:48 pmNice timing! I was using terminalFury (the classic one) yesterday to debug JTraxx TV/F3 level support. So you took F3 code and basically added ground box support. Makes me wonder how much of a mess is the HB code.StrikerTheHedgefox wrote: Mon May 04, 2026 3:15 pmBeen wanting to reply to this for a while now. Funnily enough, TerminalFury actually has some shared origins with your project.Kmaster wrote: Fri Jul 11, 2025 12:46 am
That looks quite promising. I hope he reads this, we're all willing to help!
Terminal Fury. Hmm.. bring backs memories, I called my TV windows port using the Fury3 engine the same way https://www.youtube.com/watch?v=8DI4EQ43HeA
Before I got the source code to Terminal Velocity/Fury3/Hellbender, it started as a reverse-engineered patch of Terminal Fury, done in IDA Pro, to bump it up to 640x480 resolution, and add support for higher sample rate sound effects. Then, once I got the source, I applied those same changes to the actual source in a modified version of the Fury3 codebase. Then eventually, I ported Hellbender back into Fury3's CyberUI interface (since the Hellbender MFC one is a spaghetti code nightmare that's hard to compile), and the name just kind of stuck, because it fits considering it supports all of Terminal Velocity, and the Fury series (Fury3/Hellbender aka. Fury6 in code).
Also, I am definitely looking for some help, because I'm currently stuck with some things, main thing is getting everything ported over to OpenGL world space and getting the rotation/translation/scale all working on the GPU instead of having Photex handle that all before uploading to the GPU polygon by polygon (which is incredibly slow).
Took me forever to understand it doesn't apply to MTM. I kept wondering what is the purpose of it until I finally realized it belongs to a different game.