⚠️ What the error means
If a material data file or allowance file becomes corrupt then the computations inside the software can't process the data provided and the calculation becomes meaningless, you might get these characters in the estimated waste area of your cutting list. -1.#J % Usually due to zero divided by zero and it looks like this is in the dialog box:
🧩 Common cause: CORRUPT LABOUR_V6.BIN
This is usually caused by the file Labour_V6.bin becoming corrupted by a network error.
We also got this result with a corrupted labour file. This file is where the default metal panel allowances are stored. The likelihood for a corruption is when you have several users on the same network and two users attempt to edit the file at the same time.
🛠️ Fix: replace or rebuild the corrupted file
The only fix is to find a backup up version of the file, delete and replace the corrupted file, or delete it and check the allowances again under [Estimate > Allowances] to set them up as you require them to be.
This only effects the Default panel allowances. If you save an allowance file for a particular profile, then a separate file, panel-name.SA2 is created. These *.SA2 files will not be effected.
🧱 Another example: panels on the wrong plane material
In a similar way, if you try to put metal panels on a roof model where you have designated the material to be tile you get a similar result. This issue is in trying to calculate the waste and dividing zero roof area by zero panel area.
✅ The Fix
Use [Tools > Change Plane Material] and change the roof planes to Metal, then run Gen Panels or Blocking again.
🧱 Similar problem on a tile job: TLabour5.csv
Another instance of this on a tile job where the TLabour5.csv became corrupt and we had -nan(ind) % in all the labour costing cells of Supply and Install.
✅ The Fix
Go to Setup > Pay Rates > Tilers' Pay - Variable and check all the numbers, hit [Update] and then rerun the job. It came back, but...
…then we found that the [Rafter Spacing] in the Construct Roof Defaults was set to 0, so we gave it a number and we seemed to be OK.
In another situation, we had to restore the CSV files from a backup copy from the previous day, as one of the CSV files was corrupt.