codyw1996 Posted August 3, 2015 Report Share Posted August 3, 2015 I am trying to run the game on my dual processor Pentium III windows XP machine, but it immediately crashes.Is this game compatible with the 686 architecture or does it require the sse2 instruction set?When I try to run the program pyrogenises.exe from the folder c:/../../Application Data\0 A.D. alpha\binaries\system\ I see an immediate message box that says "The application failed to initialize properly (0xc000001d)Click ok to terminate the program."My PC is powerful enough to run the game, but I'm not sure if this game requires the sse2 instruction set.PC specs:CPU(s): 2x 1.5ghz Pentium III processorsGraphics: Radeon HD 4670 with 1 gigabyte of vram.RAM: 3 gigabytesOS: Windows XP SP3 Quote Link to comment Share on other sites More sharing options...
Lion.Kanzen Posted August 4, 2015 Report Share Posted August 4, 2015 Now is fixed and will be avaible for the next release. 1 Quote Link to comment Share on other sites More sharing options...
codyw1996 Posted August 4, 2015 Author Report Share Posted August 4, 2015 Now is fixed and will be avaible for the next release.What's a rough estimate of when the "fixed" release will be made available?A few days maybe?A few weeks?Never...? Quote Link to comment Share on other sites More sharing options...
Lion.Kanzen Posted August 4, 2015 Report Share Posted August 4, 2015 What's a rough estimate of when the "fixed" release will be made available?A few days maybe?A few weeks?Never...? in the next release, months may be. Because in developer version is fixed now. 1 Quote Link to comment Share on other sites More sharing options...
codyw1996 Posted August 4, 2015 Author Report Share Posted August 4, 2015 Okay thanks. I'll mark this as solved then.Just out of curiosity, what exactly was causing the crash? Quote Link to comment Share on other sites More sharing options...
FLHerne Posted August 4, 2015 Report Share Posted August 4, 2015 Was fixed in response to your ticket, by removing a build flag. You could compile the current release with SSE2 disabled if you don't want to wait for the next release.I'd prefer that was left enabled, to be honest - the vast majority of pre-Core2 boxes will never run 0ad playably in any case, so reducing performance for everyone else doesn't seem like a good trade-off. Quote Link to comment Share on other sites More sharing options...
Stan` Posted August 4, 2015 Report Share Posted August 4, 2015 Was fixed in response to your ticket, by removing a build flag. You could compile the current release with SSE2 disabled if you don't want to wait for the next release.I'd prefer that was left enabled, to be honest - the vast majority of pre-Core2 boxes will never run 0ad playably in any case, so reducing performance for everyone else doesn't seem like a good trade-off.Actually It was only used on windows so, not everybody else Quote Link to comment Share on other sites More sharing options...
leper Posted August 4, 2015 Report Share Posted August 4, 2015 I'd prefer that was left enabled, to be honest - the vast majority of pre-Core2 boxes will never run 0ad playably in any case, so reducing performance for everyone else doesn't seem like a good trade-off.Which might have been a no-op, since VS2012 changed the default to use SSE2. Someone actually testing the latest autobuild might help, else we'd need to add /arch:IA32 to prevent it from generating SSE2 instructions (which also disables SSE which might need explicit enabling then). There aren't a lot of doubles in the code, and even floats aren't used in a lot of places. So the benefit of SSE2 on performance might not be that huge (if at all). Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.