Jump to content
Sign in to follow this  
icebreakr

Never run buldozer from beta! Corrupts \bin folder on P:

Recommended Posts

Spend half hour figuring this one out:

I tried running regular arma2.exe instead of P:\buldozer.exe as I tried setting resolution up to 1920x1080.

Of course I didn't want to search for CD and run beta\arma2.exe - big mistake.

Even when reverted to old settings, Buldozer kept crashing with "Shaders not valid (mismatch of exe and data?)". I've searched for cd and tried regular game and everything works. Tried beta, works. Buldozer? Nopers!

It seems that running beta arma2.exe destroys p:\bin\ shader files. Luckly I had a backup and by replacing \bin everything is working again *pheew*.

Share this post


Link to post
Share on other sites

I have not installed the ArmA 2 tools yet so I don't know, but isn't the buldozer defined as arma2.exe anyways as it is with earlier o2:

"d:\arma\ArmA.exe" -window -buldozer -noland -profiles=d:\armatools\armawork\

Share this post


Link to post
Share on other sites

In the default visitor install (well, mine anyway), its...

"p:\buldozer.exe" -window -buldozer -addons=p:\V3addons.txt

B

Share this post


Link to post
Share on other sites

There is alredy a thread about that problem and i though my example should be clear enough ;) and Planck explained it in detail.

http://forums.bistudio.com/showthread.php?t=91197 (there is a reason of using the buldozer.exe, added the info to the wiki)

Edited by Atsche

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×