Ok, I'm not sure if this is a Data File Bug, or an AB Bug, which is why I'm posting it here. I've just noticed (with the newest release of the 40k files) that when I add any type of Tau Crisis suit (Shas'el, Shas'o, Crisis Battlesuit) instead of the Weapons Tab being highlighted in red, the Add Units tab is highlighted in red. The problem is this: A Tau Crisis Suit has 3 "hardpoints" that must be filled with either a weapon are a special device. The way I set up the files to work is including each weapon and device in an exclution group that has limits of 3-3. The Error is that all the weapon options are showing up in red (as they always have) but the tab that is being highlighted is the "Add Units" tab. I don't remember changing anything that would cause this to happens, but if someone could look at the current AB40k Files, and see if they can maybe spot what I did, or tell me if this is an AB problem, that would be great.
-
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
A Problem I've just noticed
- Thread starter Shi_Vral
- Start date
At 05:54 AM 2/16/2006 -0500, you wrote:
>Ok, I'm not sure if this is a Data File Bug, or an AB Bug, which is
>why I'm posting it here. I've just noticed (with the newest release
>of the 40k files) that when I add any type of Tau Crisis suit
>(Shas'el, Shas'o, Crisis Battlesuit) instead of the Weapons Tab
>being highlighted in red, the Add Units tab is highlighted in red.
>The problem is this: A Tau Crisis Suit has 3 "hardpoints" that must
>be filled with either a weapon are a special device. The way I set
>up the files to work is including each weapon and device in an
>exclution group that has limits of 3-3. The Error is that all the
>weapon options are showing up in red (as they always have) but the
>tab that is being highlighted is the "Add Units" tab. I don't
>remember changing anything that would cause this to happens, but if
>someone could look at the current AB40k Files, and see if they can
>maybe spot what I did, or tell me if this is an AB problem, that
>would be great.
Oops! This one is my fault. Unfortunately the only way to avoid it is
to have 32 or less option categories in your data files (the problem
was with a number not being converted to a 64-bit integer correctly,
which runs into problems when there are more than 32 option
categories). Can you cut down on the option categories you're using right now?
Hope this helps,
--
Colen McAlister (colen@wolflair.com)
Chief Engineer, Lone Wolf Development
http://www.wolflair.com/
>Ok, I'm not sure if this is a Data File Bug, or an AB Bug, which is
>why I'm posting it here. I've just noticed (with the newest release
>of the 40k files) that when I add any type of Tau Crisis suit
>(Shas'el, Shas'o, Crisis Battlesuit) instead of the Weapons Tab
>being highlighted in red, the Add Units tab is highlighted in red.
>The problem is this: A Tau Crisis Suit has 3 "hardpoints" that must
>be filled with either a weapon are a special device. The way I set
>up the files to work is including each weapon and device in an
>exclution group that has limits of 3-3. The Error is that all the
>weapon options are showing up in red (as they always have) but the
>tab that is being highlighted is the "Add Units" tab. I don't
>remember changing anything that would cause this to happens, but if
>someone could look at the current AB40k Files, and see if they can
>maybe spot what I did, or tell me if this is an AB problem, that
>would be great.
Oops! This one is my fault. Unfortunately the only way to avoid it is
to have 32 or less option categories in your data files (the problem
was with a number not being converted to a 64-bit integer correctly,
which runs into problems when there are more than 32 option
categories). Can you cut down on the option categories you're using right now?
Hope this helps,
--
Colen McAlister (colen@wolflair.com)
Chief Engineer, Lone Wolf Development
http://www.wolflair.com/
At 08:35 PM 2/27/2006 -0500, you wrote:
>Does this mean it will be fixed in a future release of AB? Just curious.
Yes, it'll definitely be fixed in a future release.
--
Colen McAlister (colen@wolflair.com)
Chief Engineer, Lone Wolf Development
http://www.wolflair.com/
>Does this mean it will be fixed in a future release of AB? Just curious.
Yes, it'll definitely be fixed in a future release.
--
Colen McAlister (colen@wolflair.com)
Chief Engineer, Lone Wolf Development
http://www.wolflair.com/