Binarise crashes after 1.58 update

[DarthRogue 25]

The terrain I'm working on has worked flawlessly up until today.  I did the 1.58 update, updated the config to the new version, did an Arma3P on all the new files so the most current stuff is on my P drive, and re-saved my project with the new version of TB and exported the WRP again, so all that stuff should be on the same version.  But when I go to pack it all up the binarise process crashes when using pboProject.  "Binarise crashed with error status -1073741819" is the only error it gives.  Anyone else seen this yet and have a fix?

[Guest]

Hi there,

I´ve also encountered this problem (already in the dev)
At that time the fix was to go back to stable, but that isn´t a solution any more ;)

 

Thanks for any help :)

 

ir0n

 

scanning for jobs to do....

Processing ir0n\Highway7\ir0n_highway7

scanning wrp for binarised p3d's

creating texheaders.bin

Creating texture headers file...

87 texture headers saved to file "ir0n\Highway7\ir0n_highway7\texHeaders.bin"

using binarise.exe

        copying/crunching to temp...

        <Bis Binarise...>

        Binarise crashed with error status -1073741819.

        Depending on the number of goats you sacrificed,

        this may, or may not matter.

        </Bis binarise>

        stripping the binlog

 

MakePbo x64UnicodeVersion 1.90, Dll 5.24 "ir0n_highway7"

 

No error(s)

 

signing C:\Program Files (x86)\Steam\steamapps\common\Arma 3\_ir0nMods\@ir0n_highway_debug\Addons\ir0n_highway7.pbo...

Done

Job(s) completed in 117secs on Thu Apr 21 19:33:09 2016

[ANixon 8]

Hi there,

I´ve also encountered this problem (already in the dev)

At that time the fix was to go back to stable, but that isn´t a solution any more ;)

 

Thanks for any help :)

 

ir0n

 

scanning for jobs to do....

Processing ir0n\Highway7\ir0n_highway7

scanning wrp for binarised p3d's

creating texheaders.bin

Creating texture headers file...

87 texture headers saved to file "ir0n\Highway7\ir0n_highway7\texHeaders.bin"

using binarise.exe

        copying/crunching to temp...

        <Bis Binarise...>

        Binarise crashed with error status -1073741819.

        Depending on the number of goats you sacrificed,

        this may, or may not matter.

        </Bis binarise>

        stripping the binlog

 

MakePbo x64UnicodeVersion 1.90, Dll 5.24 "ir0n_highway7"

 

No error(s)

 

signing C:\Program Files (x86)\Steam\steamapps\common\Arma 3\_ir0nMods\@ir0n_highway_debug\Addons\ir0n_highway7.pbo...

Done

Job(s) completed in 117secs on Thu Apr 21 19:33:09 2016

I got the same exact error on a terrain that was working before patch.

[Uro 220]

Could you guys running Arma3 Tools Stable Branch - go to your arma3tools\binarize\ directory and open binarize.rpt, go to the latest entry in the RPT (Bottom most one) and tell me the Build it's giving you?

 

The reason I ask is because I am on stable branch tools atm, yet when binarizing in the log it says:

 

Type: Internal
Build: Development
Version: 1.59.135016

 

And usually of late, Dev branch versions of tools are wholly incompatible with Stable branch of tools.

 

So to hazard a guess BI pushed internal dev branch tools to stable.

 

If you guys could verify, that'd be sweet.

[ANixon 8]

Could you guys running Arma3 Tools Stable Branch - go to your arma3tools\binarize\ directory and open binarize.rpt, go to the latest entry in the RPT (Bottom most one) and tell me the Build it's giving you?

 

The reason I ask is because I am on stable branch tools atm, yet when binarizing in the log it says:

 

Type: Internal

Build: Development

Version: 1.59.135016

 

And usually of late, Dev branch versions of tools are wholly incompatible with Stable branch of tools.

 

So to hazard a guess BI pushed internal dev branch tools to stable.

 

If you guys could verify, that'd be sweet.

Original output filename: binarize

Exe timestamp: 2016/03/18 00:00:09

Current time:  2016/04/21 09:55:27

 

Type: Internal

Build: Development

Version: 1.59.135016

 

P.S. I am on stable as well.

[Guest]

Yep I have the same as Anixon and I´m on stable too

[Uro 220]

Reported to Dwarden on discord, expect update on situation tomorrow.

[Guest]

Reported to Dwarden on discord, expect update on situation tomorrow.

 

Thanks man! 

[bludski 4421]

Same problem here. This really ruins my day!

 

How ever.... Buldozer draws water MUCH better now and it is easier to work on sub sea stuff from above the surface! At least I can keep productive there!

[Tom_48_97 523]

FYI, I have collected some data via Skype (sources and crash dumps), we will look into this issue very soon, thanks for the report and sorry for the inconvenience.

[hoverguy 177]

If I can add something to this issue (for devs), binarization process works in dev-branch.

[Auss 208]

Yep same issue here on Australia, Binarized last night went to bed, got up then removed a building off the island and tried to binarize and same issue, Using Mikero's tools sets plus BIS binarizing tool both screwed.

[Auss 208]

Oh I'm not using the Dev Build

[DarthRogue 25]

For what it's worth, here's another RPT and crash dump from this morning.  Hope it's helpful.    I can also confirm that the Binarize tool version is showing 1.59.

 

https://www.dropbox.com/s/te4l75yj5ptx7y9/Binarize.7z?dl=0

[Cype_Revenge 651]

same here, crash with stable tools after Update....

[Uro 220]

If I can add something to this issue (for devs), binarization process works in dev-branch.

 

I just switched to dev-branch and ran a build, same crashing issue.

sent more crash-dumps to Dwarden.

[Tom_48_97 523]

We are still investigating the issue but a few points to mention:

• The development and the main branches are 1 to 1, there is no difference between them.
• The current version of Binarize is 1.59 and this is normal.

[hoverguy 177]

We are still investigating the issue but a few points to mention:

• The development and the main branches are 1 to 1, there is no difference between them.
• The current version of Binarize is 1.59 and this is normal.

I can binarize using pboProject without any problems, when am on my PC I'll take a screenshot.

Guys be sure you verify cache after every A3Tools update you'll see that 1-2 files failed to validate and are being re-acquired, then you launch it to re-build registry and stuff (starter.exe).

Once again it definetely works.

[Auss 208]

I can binarize using pboProject without any problems, when am on my PC I'll take a screenshot.

Guys be sure you verify cache after every A3Tools update you'll see that 1-2 files failed to validate and are being re-acquired, then you launch it to re-build registry and stuff (starter.exe).

Once again it definetely works.

 

Tried that earlier still broken

[hoverguy 177]

Ok here's the proof with screenshot

 

[INFO]: Type: Public

[INFO]: Branch: Stable

[INFO]: Version: 0.99.4.5952

[INFO]: 

[INFO]: =====================================================================

[INFO]: == Application info ==

[INFO]: ProductName: Arma 3 Tools utility

[INFO]: AssemblyName: Arma3Tools

[INFO]: Version: 0.99.4.5952

 

[bludski 4421]

Tried that earlier still broken

Same here. Nothing to re download.

[DarthRogue 25]

Tried verifying tool cache.  11 files failed to validate and were replaced.  I fired up A3Tools to run starter and accepted the new license.  

 

Run pboProject and it crashes on binarize.  

 

Run DevP.bat again.

 

Run pboProject and it crashes on binarize.

 

Delete "P:\temp" folder 

 

Run pboProject and it still crashes on binarize.

 

I'm gonna completely remove the P drive and all files on it and redo it from scratch.  Will let you know how it goes.  In the meantime, here's another crash dump.

 

https://www.dropbox.com/s/ifzfp97zryefgjy/binarize.zip?dl=0

 

 

UPDATE - Ran it again with a clean set of fresh files and re-extracted PBOs with AtoP and it's still crashing.  No joy here.  :(  

[Uro 220]

No need to wipe your P:/ drives and start with fresh data people.

 

The only thing that has changed is the update to the tools, specifically binarize.exe

 

It's binarize thats crashing, any data that compiled pre-patch there shouldn't be any issues with.

 

So save yourselves some hassle and just wait for a fix from BI.

I know it's frustrating having to wait, but there is also no point slamming your head against the desk trying to create a work-around.

This is something that only BI can fix by patching the executable.

[Cype_Revenge 651]

update is coming ....

[Auss 208]

one step forward two steps back.......