Chat
Discord
(07-03-2014, 03:04 PM)Blue Phoenix Wrote: as the float-type takes up more space than int (usually), so all kind of behind-the-scenes-magic would've to be adjusted as well).Not really. 'float' and 'int' both use 4 bytes, across all current systems.
Everything else you said is correct though, so if this is desired, the best bet would be to completely rewrite the engine from scratch (which would be way easier).
Also it would ruin the beautiful cinematic 30fps experience.
Also I think, I broke your fix for the [inv]-tag BP.
Damn you BP!
@bp: Pretty sure that LF2 just wouldn't work on a 16-bit processor, because it is compiled with 32-bit assembly.
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.