@Sandwichlizard (View Post)
I don't know, I haven't been bugging Simon to release it for a while because I've been busy myself. I recommend just using these snapshots (and maybe when official TPT comes out, still keep using them!)

@alexelcaza (View Post)
Because that would just be another TPT that I have to compile when 32 bit works for everyone on windows. Also 64 bit could potentially have bugs or differences that the 32 bit version doesn't (although I use Linux 64 bit and it seems fine usually)

@alexelcaza (View Post)
maybe slightly, but I doubt you would be able to notice a difference.

Finally created a new snapshot, using a new build server. The new build server uses vagrant to launch the VM. Haven't automated the part where it does the compiling without me even needing to manually go into the vm and do it (old build server didn't have this anyway), but it shouldn't be too difficult, vagrant is really nice. It is just a single command and it does all the needed setup, creating a fully functioning environment that can compile for LIN64, WIN32, and MACOSX (don't have LIN32 at the moment).

Changes in build 14:
Completely new build server
Fix a potential crash when messing with SOAP in the console

LIN64 specific:
Fix autorun.lua sometimes causing "infinite loop" errors and not running

WIN32 specific:
Now compiled with SSE2 (if you get a crash on startup, delete powder.pref and report it)

MACOSX specific:
Now uses SDL 1.2.15, so fullscreen will work


TODO: LIN64 build apparently needs static bz2 and zlib, need LIN32 build, need to save config.log for each platform

New snapshot #15

Fix flood fill delete on normal particles also deleting photons
Change shift+wind tool to not always act like alt was pressed
Remove "Unspecified Error"

LIN64: Bzip2 and zlib are static again

@alexelcaza (View Post)
Depends, what OS are you on? On windows there are probably 64 bit compilers somewhere. I've never used them though. On Linux I think there is a 64 bit mingw compiler you can use (never used that either)