Page MenuHomeFeedback Tracker

Bis Binarize has poor/no error reporting when binarising.
New, WishlistPublic

Description

Occasionally while building/populating a terrain and then compiling a test version binarize fails with un-known reasons.

It outputs errors such as "binarise returns error status -1073741819", which sometimes (50/50) results in an "Arma 3 has stopped working" binarize crash in Windows, and mini-dumps - which are of literally no use to anyone but BI.

Having some sort of reference of what these codes mean (-1073741819) would allow us to better locate the culprit causing binarize to crash. {F27104} {F27105} {F27106} {F27107}

Details

Legacy ID
1689906580
Severity
None
Resolution
Open
Reproducibility
N/A
Category
Tools
Steps To Reproduce

If we knew what the error code related to then we would be able to setup a repro, alas without knowing what causes the crash we cannot.

Additional Information

Using Arma 3 Tools - Dev Branch

When these error appear while compiling a terrain your project is pretty much fubar/corrupt/broken - (unless you have backups from your previous build)

I have TB's of HD space containing backups of WIP Arma stuff, just incase of unforseen things like this ;)

Event Timeline

Uro edited Steps To Reproduce. (Show Details)Sep 24 2015, 7:35 PM
Uro edited Additional Information. (Show Details)
Uro set Category to Tools.
Uro set Reproducibility to N/A.
Uro set Severity to None.
Uro set Resolution to Open.
Uro set Legacy ID to 1689906580.May 8 2016, 12:47 PM
Uro added a subscriber: Uro.May 8 2016, 12:47 PM
Uro added a comment.Sep 24 2015, 7:55 PM

Attached screenshots, binarize.RPT, bidmp & mdmp from binarize.exe

Hi, I see you're using pretty old version of binarize. Could you please try it with current version to see if the issue is still there?

Uro added a comment.Oct 31 2015, 4:52 PM

We backtracked via our git and found the issue manually and fixed it, so unfortunately we cannot repro this using the latest binarize as we fixed it manually via reverting commits.

But better binarize error logging would have saved us a weeks worth of sifting through data and a possible terrain revert to last working full build. Which would mean 1 months of collaborative work could have been wiped, and we would have had to manually check/re-check everything added from that point to ensure the error wasnt replicated elsewhere.

If it happens again I will report any updates to this issue, along with relevant data and create a clone of our repo at that point for testing binarize.

:)

Uro added a comment.Nov 21 2015, 10:32 AM

New Info:

Assets/Objects with class=House in GeoLOD and incorrect config.cpp entry I.E. not defined as a land_ class can cause Binarize to crash which results in Terrain PBO created without WRP inside.

Grabbed from PboPro window, using latest mikero pro tools(09/11/2015) and binarize(dev branch, 1.53.133.12):

"
<Bis Binarise...>
Binarise crashed with error status -1073741819.
Depending on the number of goats you sacrificed,
this may, or may not matter.
</Bis binarise>
"

Any building that has animation - ladders / doors / ruins+destruction class / hitpoints / etc, requires class=House in GeoLOD and class Land_ config.cpp entry, else Binarize crashes out-putting the error above ^.

Hope this aids you in adding error reporting to Binarize &/or some sort of included document that references these errors + how-to fix would be useful instead of searching for the illustious needle in haystack ;)