BSPC creates different AAS files on win32 and linux x86_64

[zturtleman]

The AAS file should be the same, regardless of platform/arch it's compiled on.

Note: I've only tested win32 using WINE as of writing.

[zturtleman]

AAS file created on linux x86_64 does not work. Game VM complains about items being unreachable for bots. AAS creating using win32 via WINE works.

[zturtleman]

[This issue was brought up in a discussion and I'm just writing some more I remember of it. I haven't worked on this recently.]

It's hard to trust/recommend Spearmint BSPC due to different AAS reachabilities on every platform/arch. I don't know how to find what is causing the differences and no idea what the correct AAS reachabilities are. One guess is float point (x87 FPU (x86) vs SSE (x86_64)) — which also affects some maps in-game (MAX_PATCH_PLANES error, ioquake/ioq3#186) — but it doesn't explain Windows vs Linux differences.

One thing I haven't done is test if BSPC included with GtkRadiant 1.6 (TTimo/bspc) has the same issue (different AAS reachabilities on every platform/arch). If it doesn't have the issue then it should be possible to fix Spearmint BSPC.

I don't remember the specifics about AAS file not working if produced by Linux x86_64 BSPC. I have q3ctf2 AAS files built using Spearmint BSPC for Windows (x86) and Linux (x86, x86_64) from April 9, 2014. All of them work in-game.