Addon Builder checks every Folder in Drive P while binarizing

[MrF 10]

Hi

After the update, Addon Builder checks every folder with a config inside (while binarizing other folders) and reported errors (sure, some config's aren't finish...) about these configs !! This is sh****... anyone else have the same problem ?? :(

Regards, MrF

[da12thMonkey 1943]

Yea, I'm getting this too - Error messages about config.cpp files that are in other project folders on my P:\ drive, but are not part of the addon that I'm compiling into a .pbo.

It's kind of annoying. (BIS pls fix ;))

[roberthammer 582]

This is annoying as hell - why the it needs to check every folder is beyond my mind :p

[egilsandfeld 7]

You guys do know about ProProject, right?

http://dev.withsix.com/projects/mikero-pbodll/files

Haven't binarized anything after the newest update but PboProject by the almighty Mikero should work out of the box

[mikero 79]

stop wasting your time then

pboProject

https://dev.withsix.com/projects/mikero-pbodll/files

[MrF 10]

Ok, thought the problem was only be with me... so, BI have to fix it !! :P

@Mikero

Thanks, will give it a try...

[NZXSHADOWS 0]

For some reason i was under the impression that I needed to use the Addon Builder with the P:\ drive. But Ive found out that it doesn't work that way. Everything links to the actual steam/tools dir. Only path used from P drive was for the "Path to project folder".

Edited May 30, 2014 by NZXSHADOWS
t(O.o)y Missunderstanding.

[LODU 19]

@Mikero

I stop wasting my time...

Thank you.

[bwph4273 11]

same here worked fine before the update and now its crap. and when it does get done its leaving out some folder,textures and rvmats

[MrF 10]

Check...

Have open a ticket at Arma Tracker :

http://feedback.arma3.com/view.php?id=19027

Regards, MrF

[NZXSHADOWS 0]

What method are you guys using to setup your addon builder. Currently this is my setup.

Works fine for me.

[MrF 10]

This :

[NZXSHADOWS 0]

In your options tab try pointing the "Path to project folder" to you P:\Drive addon location path. an on the main menu point the Addon Source Directory to your real addon directory not the P:\ path. It should pack with out an issue. but again im still messing around with the settings. My issue is getting buldozer to convert my .tga's to .paa's.

[MrF 10]

If i choose my project folder, Addon Builder chrashed... :confused: :(

[NZXSHADOWS 0]

If i choose my project folder, Addon Builder chrashed... :confused: :(

An what did you use for your "Addon Source Directory" path?. If your "Addon Source Directory" is set to where your tools are installed for example "I:\Steam\steamapps\common\Arma 3 Tools\Addon Folder" You should be ok. An set your "Path to project folder" to P:\Addon Folder. I dont know if this is the offical way to point to directory's but it makes sense to me that this is the way the tool needs setup.

[MrF 10]

Trying multiple things, nothing works for me... it's very annoying !! Now, after the "hotfix" the beahviour is the same and i get the same error like before...

[NZXSHADOWS 0]

Its odd that starting some tools from different locations have a different effect. I have to start Object Builder from its P: drive installation path or buldozer wont find viewer when started. It just wont work when trying to start it from steam or the tools gui. Now the Addon Builder is the complete opposite. An once I got everything working. I did a reboot an I started the tools like normal an now they are not working properly after that last update. Oh well.

[MrF 10]

edit, still valid...