CrazySpence
commented
2 years ago -Switched to windows -Tried od2 I compiled on debian: immediate crash -Installed visual studio 2012 -loaded makeodt solution --allowed it to update the solution -Built -Compiled planet.wrl: client can load it -Compiled the wrl I was trying to use yesterday: client can load it
So on windows it appears it can work, should try a newer VS and see if it's the age of the compiler or the platform (win vs linux)
I have tried to compile a couple VRML 1.0 files and makeodt appears to work correctly however if I load these new od2 files with: load object (somemadeupclass) file thefilename.od2 type ship_1 or load object (somemadeupclass) file thefilename.od2 type ship_2
The game loops forever and crashes
So then I used makeodt to compile the planet.wrl file in the tools folder, which should produce the same planet2.od2 that we already have in parsec_root/client
Game loops eats all the memory and crashes
NOW here's the fun part
If I use the planet2.od2 made back in 2013 with the same commands, it loads correctly. I was even able to use the shipclass command, shipdesc and a tiny planet ship popped up in the ships menu exactly as the original tutorial says should happen
So this means theres something wrong with the way makeodt is making od2's all of a sudden. This code hasn't changed since we made the planet2.od2 so that makes it extra weird? Using a 32bit Debian VM to make the files so I don't think 64bit weirdness is coming into play