Wolfram_von_Thal: I've tested the game on Vista 64 and Win 7 64 and tried to use the mods as described above. On both systems it's the same error. The "vanilla"-hardware acceleration works without problems.
Yes, I'm experiencing the same issues. I know JKE is functional because I can run it with my god awful steam copy and even with my CD copy, permitting I give my CD copy a cross look and a stern talking to. But with the GOG version, it won't load the first level. I know the resources are working because I can load a multiplayer match.
I might have to dig back in to those countless years of my youth that I poured in to being a novice Jedi Knight mod developer.
EDIT: Been messing with it for hours. I think I'm just going to get my money back and take another 15 year break from this game. I don't think it's been in the closet long enough since it doesn't want to behave.
EDIT Again: I know it's exclusively a 64 bit OS issue, just doesn't make sense that it's ONLY JKE and ONLY with the GOG version. I can't figure out what's different about the GOG version that would cause a load fail conflict w/ JKE only on an x64 OS.
One more time with feeling: I won't be defeated. Time to dust off ConMan and take this bad boy apart.
Just a quick rough-and-dirty overview of my initial findings. I just straight up blew away the 3d objects folder. I had a hunch based on something I remembered from way back about load crashes occurring when the game was trying to handle an object with some kind of illegal vertex or maybe too many vertextes. It loaded the level, then crashed, likely because it was trying to load a specified object that had been removed. I anticipated this, so the crash wasn't a surprise. What is perplexing is that the x64 version would appear to contain the condition restricting vertex count in 3d models while the x86 version appears to have that restriction patched out. I know how to patch it out on a cd copy, but that method hasn't worked with the GOG version, not yet at least, I think because the method is tailored to an x86 executable, so the patcher is corrupting the application. Here's a thought. Going to restore JKE.gob and run JK.exe in compatibility. And.. no dice. That didn't work.
Another edit:
It's this issue here. Still, can't explain why we're only seeing this on x64.
http://forums.massassi.net/vb3/showthread.php?11113-Know-your-limits-in-JK JKE works based on some patching that removes or rather expands these limitations. I'm supposing that the GOG installer detects whether you're running x86 or x64 and uses an appropriate executable, also that the x64 executable lacks some of the patching that removes these limitations. This is assuming there's a different x64 executable included in the install package. Need to redownload the installer and look at the guts to be sure. The other possibility is that there's some kind of architecture change where the patching doesn't apply the same in x64. The latter is a bit more of a stretch, but still a possibility.
