So… I did patch 1.34, which had a bunch of minor stuff that was fairly urgent, and immediately everything went wrong. I’ve\u00a0 moved to Windows 7 on 64 bit, and that meant a new PC, and thus nothing worked. I needed to install the Microsoft Directx sdk, which is fine, but the old version I used would not install on W7. That meant getting the new version, which took 2 days to download (grrr), but installed, so I could actually debug my games again….<\/p>\n
But it also meant that when I recompiled the game for a patch, it got automatically tied to the latest d3dx dll, which is weird because I havent changed any graphics engine code at all. It seems Microsoft defaults to requiring the latest of everything. Cheers guys.<\/p>\n
And here it gets annoying. Because the machines I test on all have the SDK installed, I had no idea that I was suddenly needing a new (not normally installed) DLL until I released the patch and got complaints. Eeek!. I’m 99.99% sure this is fixed now with 1.35. I couldnt get the stupid-ass directx redist installer to actually install the new files, so I just recompiled the game forcing it to use includes and libs from the older SDK.<\/p>\n
What a pain!<\/p>\n
In other news the ‘spot the feature’ is that missile trails are going above the ship that fired them. They never used to do that. Nobody even notices when I point it out. Bah. Also, multiple-rockets now split apart in a more convincing way now, and tons of really minor stuff is now fixed. Hurrah!<\/p>\n","protected":false},"excerpt":{"rendered":"
So… I did patch 1.34, which had a bunch of minor stuff that was fairly urgent, and immediately everything went wrong. I’ve\u00a0 moved to Windows 7 on 64 bit, and that meant a new PC, and thus nothing worked. I needed to install the Microsoft Directx sdk, which is fine, but the old version I<\/p>\n