it still desyncs an incredible amount more than the other build that I provided. .
The person who provides that blogspot, smasherx explained before on the blogspot the difference from the modified 0.13 and the original 0.13 compiled back in 2003.
I remember specifically, PJ64kVE, 7E, all of those versions are done using a hex editor to change the GFX plugin to Jabo8. They also use Resource editors which then recompile the exe and that definitely causes desynces. His version specifically was/is the onyl one to use ASM modifications which prevent any expectations that may occur using hex editors or resource editors. He knew how the program worked and modified it accordingly.
I've used that blogspot because its the first link off google. I've never had desync problems with it like I actually have using the links provided here on smashboards. One of the copies would auto-crash my old computer and give me a BSOD even... So I don't really care what you have to say unless you can provide evidence like he did a long time ago. I'm going to keep using the file I know is safe, and works 100% correctly.
Thanks, I advice you gather some evidence on these things before making wild accusations. Yesterday I played nearly 20+ minutes in a single game without desync. I've also never had any virus that was notable besides regular cookie malware that gets caught by malwarebytes.
Here is my suggestion: Download your copy then download the regular copy. Compare the two on two identical systems. Just go into game and start pressing the CPU/Player button and see which one DSes first. Do this 3 or 5 times and you have your self a scientific theory stating The blogspot link is corrupted (which I know for a fact your version is corrupted by the name of it).
Update: I tried your link, as expected it did EXACTLY what I remember it doing. I'm not even going to try emulating with ti in fear my computer will BSOD (I knwo for a fact this happens withj faulty pj64ks and the original one that they were suppose to fix).
Take note: I deleted all registry of PJ64 as seen in the begging. This means all cache/data was relieved of the emulator. This is how someone who has never used pj64k will see the emulator. Your PJ64KVE doesn't load the audio or input plugin. The GFX plugin is force set to Jabo8 which has many graphical glitches compared to Glide64 or GLideN64.
Update2: I just attempted to use your emulator, It turns out you can ONLY USE Jabo_Direct3D8.dll you cannot use the Glide64 final version plugin ON KAILLERA. This is something
www.blogspot.com explained how to do back when it was an actual blog!!! Your pj64k copy is faulty!
Here is proof