Jump to content
Sign in to follow this  
memphisbelle

ArmA3 Addon Builder RPT File, location?

Recommended Posts

Hello busy Addon creators,

Has anyone already found the rpt logfile location?

The Biki page is as virginal as my little daughter, so no relevant information to be found there yet.

Same for the readme, which refers to respective empty biki page ^^

Share this post


Link to post
Share on other sites

Usually when I PBO an addon the log file is created in the same location. Naturally, you must ask for a log file (I think it's in the advanced tab).

Unless you mean another type of logging.

Abs

Share this post


Link to post
Share on other sites

yes, you are right. But as soon as I run the config I get a message that there´s an config error...I mean, I have a working config, so thats not the deal. But I wanted to use the latest one, so I wanted to search for the reason why the error message appears at all...the only message that there´s an error in the config is not very helpful :).

So, do I have to live with the fact, that there´s no way to figure the reason for the error?

If yes...developers life sometimes must be a hard one :)

Share this post


Link to post
Share on other sites

Yea it'll say that when binarizing but if you open the rpt file it should go into more detail there

Share this post


Link to post
Share on other sites

As usual the rpt of the exe you use gets stored in the respective appdata folder

You have 3 Ways to aproach and minimize errors:

First, check Bulldozer rpt (appdata\local as usual)

Second, check binarize logfile (where you point it in addon builder)

Third, check the ArmA rpt (appdata\local as usual)

But as soon as I run the config I get a message that there´s an config error...I mean, I have a working config

If you have an error when binarizing then it must show it in the binarize log.

Binarize checks also other configs in your project directory keep that in mind.

Happend to me several times, that i couldent find any errors in my configs and found out that it was caused by other configs in my project dir.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×