What is the most likely cause of No Qualifying Equipment Error? Solved!

[WABAC]

This error is really puzzling me since it is occurring with my Soviet forces that I did after I modded the Americans. I am sure it is something simple that I am just not seeing. But what is confounding is that in many cases the equipment was already in the spreadsheet.

Is it likely to be in the formation page that is calling the equipment or on the units page?

>>> It turns out that the lack of a comma between items in the weapons list column on the unit sheet is quite sufficient to cause the problem I was experiencing.

Many thanks to Capn (Eagle Eyes) Darwin for helping out a would-be TOE modder. [&o]

[CapnDarwin]

The primary reason is that there is no platform(unit) of the type available for the given date. This is a valid situation (assuming the dates are correct). If the dates are right, then is could be an error in the CompID of the unit not matching the unit type callout in the formation composition. A third case could be using the wrong set of formations in the editor. Setting a date like 82 but using the 85+ series formations could cause a type mismatch or no valid equipment.

Hope that helps. If not hit me up with some screen shots. I am working on Mod guide 4, but right now I have some code issues and I have to get the 2.04 update doc done and also update the other 3 guides to 2.04 and try to shoehorn in the Quick/Start too. Just a case of more work then hour available I'm afraid.[:(]

[WABAC]

Thanks for the tips Cap'n. I'll try to post something a little later today. Oscar Taveras is debuting today for the Cardinals and I have some beer to drink. I'll drink one for you too.

The funny thing is that most of the new stuff I entered seems to be working. It's mostly the old stuff that's acting up. Sometimes when I call the specific item like the PT76 and other times when I call for a TANK or TRUCK.

[CapnDarwin]

Thanks. Enjoy the game and the beer. I'm diving back into the hell of updating documentation for the rest of the day/night. Then on to a whole other level of hell with scooting and standoff that has things ground to a halt[:@] with the update.

[WABAC]

I'm going to re-do the whole Soviet thing the way I did the Pentomic Americans. Then I'll see where I end up.

For anyone else reading along, you might enjoy this site to add to info available in the Aggressor Handbooks: http://www.armouredacorn.com/#!1961/cq1j

[WABAC]

Hi Capn'. I won't have any time to work on this stuff again till Thursday AM most likely. So if you could eyeball it between now and then that would be great.

What I did this afternoon, while the Giants firehosed the Birds, was to start breaking things out the way I did for the Pentomic Americans. What I have reworked so far should be visible. Out of the items called, the only things showing up are INF_HQ, RU164, RU114, and RU117.

In my next post I will upload the units page

[WABAC]

So in this post I have tried to pare the units down to the things that are called, and are showing up, and to the things that are called that are not showing up.

Part of what is confusing me is that I am having the problem whether I call the compid or sutag. So if I call TANKS, they don't show up. And if I call SU313 it doesn't show up.

[WABAC]

It turns out that the lack of a comma between items in the weapons list column on the unit sheet is quite sufficient to cause the problem I was experiencing.

Many thanks to Capn (Eagle Eyes) Darwin for helping out a would-be TOE modder and scenario designer. [&o]

[CapnDarwin]

Yep, a missing comma or invalid type, or unknown sensor or special will trip the editor and game up. The formation editing is the same way. It's not easy business and I have made those mistakes and other along the way myself. One item on our wish list is better data validation tools to help with finding these errors. It's just behind many other things that need to get done for the game. Bottom line, edit twice and run once or some such words of wisdom.[:D]