BinPBO; Clear temp folder

[Snake Man 401]

I have no problem with BinPBO but couldn't decide if this topic would suite o2 or v3 editing, so I decided to drop it to tools troubleshooting :)

BinPBO - Clear temp folder

If someone doesn't know how this works, its simply an option to leave the temporary directory intact when binarizing/packing your addon. This means when you first run BinPBO it fills the temp dir with your processed addon files and when you run it second time, if clear temp folder is NOT selected, your addon binarize/packing process is much much faster. This is very handy when testing some addon which has many files to be binarized/packed and only one or few of them have been edited.

My question is; what are the downsides of leaving the temp dir intact, can some edited files be skipped when running it unselected, are all textures/rvmat's really copied over properly if edited etc?

[Synide 0]

what are the downsides of leaving the temp dir intact,

Don't know of any of the top of my head.

can some edited files be skipped when running it unselected,

Haven't come across any problems.

are all textures/rvmat's really copied over properly if edited etc?

yes.

Turning off 'Clear Temp' folder (after your first initial large convert with it turned on) has no adverse effects as far as I'm aware. With it 'off' BinPBO and the tools called by it should only 'touch' the files that have a later timestamp. Although, you should always keep 'binarize' checked.

Edited September 22, 2009 by Synide

[[aps]gnat 28]

are all textures/rvmat's really copied over properly if edited etc?

No

Well .... mostly

One exception (a fairly obvious one once you do it once), is the Sat_lco or mask etc

Just editing these file will not pass the results through to the final product, you have to rerun the Import and Buldozer convert process.

BUT, the tool still shortens that process and binarization so that only tiles that actually got affected in your last edit are updated. The rest remain intact.

[.kju 3239]

Well we had it couple of times that old files were used if clear temp was not active.

[Snake Man 401]

I also recall some post in these forums from Opteryx/Nicholas Bell who said he actually had to manually delete the TEMP dir before his terrain compiled properly (sorry don't have link to the post).

Usually when I'm hammering some small issue which I'm familiar with and perhaps the addon is large, I run the clear temp dir OFF. But when time comes to make final pbo or if my addon is very small (compile time quick) I keep clean temp dir ON.

[t_d 47]

If BinPBO works the way I think it does then it puts all the binarized and needed data to temp folder and then it will pack this temp folder. If you for example remove a texture from the source folder and pack again, the removed texture is still present in temp folder and will be packed when you dont set "Clean Temp".

[mr burns 131]

My question is; what are the downsides of leaving the temp dir intact, can some edited files be skipped when running it unselected, are all textures/rvmat's really copied over properly if edited etc?

One downside i recently found is that .log files won´t show any errors that have already been progressed - i.e. for files in the temp folder.

This leads to confusion when packing a .pbo twice in a row (with "clear temp" unchecked) as it makes you think that no errors are present, while of course any eventual errors from the first run are still very much there.