• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Bug in AB3.0b - 40K (v1.8 data file) rosters - reproduceable

Wet_Jimmy

New member
Hiya,

I've been informed that the bug (""Roster References critical information that does not exist in the loaded data files." ) which I reported is actually a problem within AB3 itself.

Is there any ETA on a fix?

The bug report I posted at the 40K Maintainers site has been reproduced below (I've since been informed that this effects more rosters than UM's);

----------------------

Bug : When loading a roster that contains an Ultamarine Special Character with a Comman Squad attached, an error occurs and the roster is loaded as a "blank" roster.

Reproduceable.

----------------------

FYI - I performed a "fresh" install of the AB3 40K 1.8 file by deleting my old WH40K data directory and importing the 1.8 file in order to ensure that there were no funny bugs brought in from older versions.

To test the Command Squad bug, perform the following;

1) Start a new Ultramarines roster, any size.

2) Select one of the following "special" HQ's - Marneus Calgar in Power Armour (NOT Terminator), Chief Librarian Tigurius or Chaplain Cassius.

3) Give the HQ unit a Command Squad.

4) Save the roster.

5) Load the roster you just saved - you can quit AB or just load it straight away, the same error occurs.

6) When you attempt to load the roster containing a "special" HQ with an attached Command Squad, the following error occurs;

"Roster References critical information that does not exist in the loaded data files."

- and the roster will load as a blank roster, with no existing entries.

I can produce this error every time and I am using a recent install of AB3.0b. I have the data files set to re-compile on every load, but the error occurs whether this setting is turned on or not.
 
A preliminary release of AB V3.1 just entered Beta testing. One aspect of
this bug has already been fixed in the Beta, and the other aspect is
planned for correction in V3.1. There is no set date for V3.1 yet, but this
bug should definitely be fixed when V3.1 comes out.

-Rob

At 12:24 AM 7/5/2005 -0400, you wrote:

>Hiya,
>
>I've been informed that the bug (""Roster References critical information
>that does not exist in the loaded data files." ) which I reported is
>actually a problem within AB3 itself.
>
>Is there any ETA on a fix?
>
>The bug report I posted at the 40K Maintainers site has been reproduced
>below (I've since been informed that this effects more rosters than UM's);
>
>----------------------
>
>Bug : When loading a roster that contains an Ultamarine Special Character
>with a Comman Squad attached, an error occurs and the roster is loaded as
>a "blank" roster.
>
>Reproduceable.
>
>----------------------
>
>FYI - I performed a "fresh" install of the AB3 40K 1.8 file by deleting my
>old WH40K data directory and importing the 1.8 file in order to ensure
>that there were no funny bugs brought in from older versions.
>
>To test the Command Squad bug, perform the following;
>
>1) Start a new Ultramarines roster, any size.
>
>2) Select one of the following "special" HQ's - Marneus Calgar in Power
>Armour (NOT Terminator), Chief Librarian Tigurius or Chaplain Cassius.
>
>3) Give the HQ unit a Command Squad.
>
>4) Save the roster.
>
>5) Load the roster you just saved - you can quit AB or just load it
>straight away, the same error occurs.
>
>6) When you attempt to load the roster containing a "special" HQ with an
>attached Command Squad, the following error occurs;
>
>"Roster References critical information that does not exist in the loaded
>data files."
>
>- and the roster will load as a blank roster, with no existing entries.
>
>I can produce this error every time and I am using a recent install of
>AB3.0b. I have the data files set to re-compile on every load, but the
>error occurs whether this setting is turned on or not.


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (408) 927-9880
Lone Wolf Development www.wolflair.com
 
Back
Top