Compile after update/import unreliable

This is the short version, mind you.

I'd submitted some bug reports for the Tau files under 40k, and there were
patches released.

So I download/import the patch. Didn't work. Re-submit bug report for new
files. Have a response come back of 'already patched, get latest file'.

This goes back and forth a few times, then I download/import the patch
file on my other computer that has the second of my licenses for
armybuilder. This time the patch works.

I update the bug forum with these events and someone says that you can do
a manual forced recompile by hitting 'ctrl-c' inside the program. I try
this but nothing happens.

In the end I have to delete the data directory for the game system,
redownload the whole kit, apply the patch file, and then open the game
system for the first time and have it compile that way and it works.

---

I see the 'auto compile new data files' under development & debugging on
the settings menu - but it's apparently not catching everything. Is there
some setting where it will automaticly re-compile after any import? Also -
what is the method for forcing a compile by hand (other than deleting like
I had to do)

<EOL>
Tib

[deathlynx]

> I'd submitted some bug reports for the Tau files
> under 40k, and there were
> patches released.
>

Given that ou haven't actually identified what sort of
bug it was I'm guessing but was the bug you're
refferring to related in some way to which stats are
being displayed? If this is the case I ran into this
durring testing and found out you have to manually
reset the displays (for output, roster and displays)...






__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/

On Sun, 6 Mar 2005, Death Lynx wrote:

> > I'd submitted some bug reports for the Tau files under 40k, and there
> > were patches released.
>
> Given that ou haven't actually identified what sort of bug it was I'm
> guessing but was the bug you're refferring to related in some way to
> which stats are being displayed? If this is the case I ran into this
> durring testing and found out you have to manually reset the displays
> (for output, roster and displays)...

It was a points related issue where when assigning equipment to a model,
and hitting + to increase the count of that model (and it's gear) it would
not add the proper points for another model.

Specificly:
Broadside w/ twin linked plasma rifle and shield generator = 100pts
Hit + and rather than get 200pts it counts 190.

I'm curious, how does the display settings that you mention affect whether
a datafile shows the proper statistic values/point values?

The only thing I've ever changed has been setting the print output to be a
'roster' display setting. But that was on both my installations of ab3 and
still had the issue of one of them working with the patch, and the other
not.

<EOL>
Tib

[deathlynx]

> It was a points related issue where when assigning
> equipment to a model,
> and hitting + to increase the count of that model
> (and it's gear) it would
> not add the proper points for another model.

Not sure in this case...There were some option points
bugs in 3.0 (not 3b) but this doesn't sound like
them...

> I'm curious, how does the display settings that you
> mention affect whether
> a datafile shows the proper statistic values/point
> values?

It causes problems when you are adding/removing/moving
a stat around in the various views...for example I had
forgotten to include a stat in BFG and when I added it
I had to reset all views...AB doesn't automatically
check to make sure a new version has different
displays...Asode from that it doesn't actually change
the stat in any way...



__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Colen]

At 08:28 AM 3/5/2005 -0600, you wrote:


>This is the short version, mind you.
>
>I'd submitted some bug reports for the Tau files under 40k, and there were
>patches released.
>
>So I download/import the patch. Didn't work. Re-submit bug report for new
>files. Have a response come back of 'already patched, get latest file'.
>
>This goes back and forth a few times, then I download/import the patch
>file on my other computer that has the second of my licenses for
>armybuilder. This time the patch works.


I might have an idea what caused this... I'll investigate and get back to you.


>I update the bug forum with these events and someone says that you can do
>a manual forced recompile by hitting 'ctrl-c' inside the program. I try
>this but nothing happens.


Firstly, you don't seem to have data file debugging enabled (which should
be enabled by default when you install the authoring kit). If you're
writing data files, I strongly recommend that you enable it - Settings
menu, Development and Debugging, and check 'Enable data file debugging'.

Once you have this enabled, hitting Ctrl-C from the main form (you can use
it any time you could add a unit to your army - i.e. not when the 'new
roster' or 'switch game system' form is showing) should bring up a form
inviting you to recompile a set of data files. Using this you can recompile
data files and fix errors without having to restart Army Builder each time.


Hope this helps,



--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com

I found the 'enable debugging' option in the basic client and gave it a
run. Great - I can now compile on my own :] Thanks. I still think the
hit/miss compile thing after an import should be looked at - I don't think
I should have to remember to compile it on my own just to be doubly sure.

<EOL>

On Mon, 7 Mar 2005, Colen McAlister wrote:
> Firstly, you don't seem to have data file debugging enabled (which should
> be enabled by default when you install the authoring kit). If you're
> writing data files, I strongly recommend that you enable it - Settings
> menu, Development and Debugging, and check 'Enable data file debugging'.

That would likely be because I don't have the authoring kit :] I think I
remember seeing an option like that in the basic client (ab v3.0b) though?

> Once you have this enabled, hitting Ctrl-C from the main form (you can use
> it any time you could add a unit to your army - i.e. not when the 'new
> roster' or 'switch game system' form is showing) should bring up a form
> inviting you to recompile a set of data files. Using this you can recompile
> data files and fix errors without having to restart Army Builder each time.

I'll have to give this a shot. If the basic armybuilder program can do
this and not just the authoring kit one, then I can certainly spare myself
some headaches in the future. Thanks!

<EOL>
Tib

[Colen]

At 10:23 PM 3/7/2005 -0600, Tib wrote:

>On Mon, 7 Mar 2005, Colen McAlister wrote:
> > Firstly, you don't seem to have data file debugging enabled (which should
> > be enabled by default when you install the authoring kit). If you're
> > writing data files, I strongly recommend that you enable it - Settings
> > menu, Development and Debugging, and check 'Enable data file debugging'.
>
>That would likely be because I don't have the authoring kit :] I think I
>remember seeing an option like that in the basic client (ab v3.0b) though?


I see... is there any particular reason you don't have the authoring kit
installed?


> > Once you have this enabled, hitting Ctrl-C from the main form (you can use
> > it any time you could add a unit to your army - i.e. not when the 'new
> > roster' or 'switch game system' form is showing) should bring up a form
> > inviting you to recompile a set of data files. Using this you can recompile
> > data files and fix errors without having to restart Army Builder each time.
>
>I'll have to give this a shot. If the basic armybuilder program can do
>this and not just the authoring kit one, then I can certainly spare myself
>some headaches in the future. Thanks!
>
>I found the 'enable debugging' option in the basic client and gave it a
>run. Great - I can now compile on my own :] Thanks. I still think the
>hit/miss compile thing after an import should be looked at - I don't think
>I should have to remember to compile it on my own just to be doubly sure.


Yes, it's definitely a bug which we'll do our best to address in the next
release. Thanks for the report.




--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com

[Colen]

At 10:23 PM 3/7/2005 -0600, Tib wrote:

>On Mon, 7 Mar 2005, Colen McAlister wrote:
> > Firstly, you don't seem to have data file debugging enabled (which should
> > be enabled by default when you install the authoring kit). If you're
> > writing data files, I strongly recommend that you enable it - Settings
> > menu, Development and Debugging, and check 'Enable data file debugging'.
>
>That would likely be because I don't have the authoring kit :] I think I
>remember seeing an option like that in the basic client (ab v3.0b) though?


I see... is there any particular reason you don't have the authoring kit
installed?


> > Once you have this enabled, hitting Ctrl-C from the main form (you can use
> > it any time you could add a unit to your army - i.e. not when the 'new
> > roster' or 'switch game system' form is showing) should bring up a form
> > inviting you to recompile a set of data files. Using this you can recompile
> > data files and fix errors without having to restart Army Builder each time.
>
>I'll have to give this a shot. If the basic armybuilder program can do
>this and not just the authoring kit one, then I can certainly spare myself
>some headaches in the future. Thanks!
>
>I found the 'enable debugging' option in the basic client and gave it a
>run. Great - I can now compile on my own :] Thanks. I still think the
>hit/miss compile thing after an import should be looked at - I don't think
>I should have to remember to compile it on my own just to be doubly sure.


Yes, it's definitely a bug which we'll do our best to address in the next
release. Thanks for the report.




--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com

On Tue, 8 Mar 2005, Colen McAlister wrote:

> I see... is there any particular reason you don't have the authoring kit
> installed?

Because... it didn't come with the basic download of ab3? Plus I don't
actually author any data files :] I'm just fairly active in
poking/prodding the ones that get put up by the ab40k3.homelinux.net folk
and submitting bug reports.

> Yes, it's definitely a bug which we'll do our best to address in the next
> release. Thanks for the report.

Thanks for listening to those of us that find them :]

<EOL>
Tib