Cognition, Unity and non-SSE2 processors.

[ningo]

Having downloaded and installed the game (episode 1) without issue, I saw the dreaded Unity logo. I know I'm one of a vanishingly small number of users, but I still use an athlon XP processor, which does not have SSE2 instructions and which Unity quietly dropped support for midway through the v3 development path.  There are ways of patching v3 webclients to still work on non-SSE2 processors (see http://forum.unity3d.com/threads/142411-Error-Launching-Unity-Player/page4).
I know you guys are busy, but is there any chance of a patched client version for us dinosaurs? Regardless, it would make sense to update your system requirements page.

[wilco64256]

Can you get me the results of running DxDiag on your computer? Just save the information it comes up with and email it to me via weldon at postudios dot com.

[Oldbushie]

I'm rather puzzled because we're not using the Unity Web Player at all for the game. That is a different beast compared to a self-contained executable. Though it is certainly possible that pre-SSE2 support was dropped from the entire Unity Engine in general, I am having trouble finding that information.

[ningo]

My issue is now probably moot as my trusty radeon 3650 is no more, and I've had to stick an old(!) nvidia 6200 in to tide me over.  Time for a new machine, methinks.
As regards the problem, I didn't actually mean the problem was webplayer-intrinsic, I just linked the thread because it has the cause of the problem there, together with the only statement you will find on the Unity site that support for non-SSE2 processors has been dropped.  As per the discussion thread, "SQRTSD" is a SSE2-only instruction.  I opened the memory location where cognition was still running after throwing up an error in a hex editor, and SQRTSD was present, so I think this is a issue with the Unity engine from v3.2 ish onwards.

[br305893]

The non-techie over here is like...