First post, by superfury
When I compile it for Windows etc., I end up with (1000000000/1190000)(=PIT frequency), ending up with a variable (which is calculated when compiling) containing about 800(the amount of nanoseconds for a PIT tick). But instead, the application ends up with a number about 1.728413e-306, which causes an insane amount of PIT ticks to be handled, instead of just a few, on the very first instruction executed. This causes the application to crash after it's very first CPU instruction is executed, and the PIT starts ticking it's supposed ticks for that instruction.
Is this fixable? I've used the SDL2.0 build with the Android NDK(Createn using the tutorial at http://lazyfoo.net/tutorials/SDL/52_hello_mob … ndows/index.php ).
Anyone?
https://bitbucket.org/superfury/unipcemu.git
Edit: Can it be fixed by moving the relevant formula inside executable functions (e.g. leave the global variable global, but move it's assignment of it's value to a normal function that's always called when the module is used)?
So, like:
double abc=(1000000000/(1.0/2.0)); //Example
Becoming:
double abc=0.0; //Example
void initModule()
{
//Initialize our timings!
abc = (1000000000/(1.0/2.0)); //Example
}
Will this work for the Android NDK(on windows, using SDL2 based on the tutorial on lazyfoo: http://lazyfoo.net/tutorials/SDL/52_hello_mob … ndows/index.php ) and all used android devices(I've changed the compilation architecture to the 'all' option, compiling for all possible Android targets)?
Author of the UniPCemu emulator.
UniPCemu Git repository
UniPCemu for Android, Windows, PSP, Vita and Switch on itch.io