Hierarchy Module Document

[nemo69]

Bob,
Will it be possible for non-members of the development team to take part in the Beta test?
Best,
Marc

[Curtis Lemay]

Bob,
Will it be possible for non-members of the development team to take part in the Beta test?
Best,
Marc

Of course. That's the whole point of a Beta Test.

[Curtis Lemay]

First, I want to point out that today is the sixth anniversary of the start of coding on the Hierarchy Module. Unfortunately, we are still not quite done - still one very tough bug to go.

However, I have made big progress on it. The bug screwed up the movment paths for units in formations with non-infinite command radii. I've fixed that today.

However, now that the paths are good, I can finally try moving units, and, guess what! Moving the units is broken. But I'm sure it's the same issue I found with the paths and I'm close to fixing it. (Hopefully that will be the end of it).

[rhinobones]

Bob,
Will it be possible for non-members of the development team to take part in the Beta test?
Best,

Of course. That's the whole point of a Beta Test.

Good to hear that the wheels of progress are still on the track, but . . .

I’m still concerned that you are not providing a list of functions which need to be verified. As is you’ll have no guarantee that features you find critical have been thoroughly investigated. After years in development, I would think you would want to maximize the beta test response; making a check list should be a snap for the one person who is intimate with the revisions/upgrades.

Maybe something as simple as an editing of the overview posted on December 1, 2024 would suffice.

Regards

[Curtis Lemay]

Good to hear that the wheels of progress are still on the track, but . . .

I’m still concerned that you are not providing a list of functions which need to be verified. As is you’ll have no guarantee that features you find critical have been thoroughly investigated. After years in development, I would think you would want to maximize the beta test response; making a check list should be a snap for the one person who is intimate with the revisions/upgrades.

Maybe something as simple as an editing of the overview posted on December 1, 2024 would suffice.

That sort of crude checkout has been done as features were developed (except where there are some who experience issues that I can't reproduce, of course).

What we need for the Beta Test is designers to design (or at least update) and players to play. And let's see what issues crop up.

[Curtis Lemay]

First, I want to point out that today is the sixth anniversary of the start of coding on the Hierarchy Module. Unfortunately, we are still not quite done - still one very tough bug to go.

However, I have made big progress on it. The bug screwed up the movment paths for units in formations with non-infinite command radii. I've fixed that today.

However, now that the paths are good, I can finally try moving units, and, guess what! Moving the units is broken. But I'm sure it's the same issue I found with the paths and I'm close to fixing it. (Hopefully that will be the end of it).

Well, getting closer. Now I can move units (ones that ARE within their command radius). But now the mechanism to move units that are "Under Orders" is broken. So...stay tuned.

[Curtis Lemay]

Here are the remaining Hierarchy Module bugs:

1. Movement path bug for units in formations that have finite command range.
2. Each time invoking the Commander Inventory Dialog erases one On-Map Panel.
3. Clicking on a subordinate formation that has no on-map units causes CTD.
4. Flag unit total elimination doesn’t cause commander casualty in some cases.
5. Manpower Estimate bug for side 2.
6. Spare Commander picture should be invoked if there is no picture for a commander’s name. (Necessary for spawned commanders).

Once these are fixed (first two are non-trivial), I may start the Beta Test.

OK, the first one is now fixed. And that completes the Hierarchy Module! It took six years and three days.

[Curtis Lemay]

Just to illustrate the fix, my Shiloh 1862 scenario has from 4 to 10 hexes for command radii for all formations, so it is the test of this issue.

Here, a correct movement path is displayed for a CSA unit.

[Curtis Lemay]

And, here it has moved as per that path:

[Curtis Lemay]

Here, a USA unit is Under Orders (light pink band). I can't show the movement path for some reason, but it ran from this unit to its flag unit.

Edit, while the "PrtScn" function doesn't work while the path is showing, I can just take a picture of it with my camera. That picture shows the movement path. (Note that the path remains showing for 10 seconds):

[Curtis Lemay]

And, after selecting "All at once", it has made the move:

[Curtis Lemay]

1. One feature remains to be finished. This was the Commander Vacancy Fill procedure. It is now finished.
2. Scenarios need to be modified/designed to incorporate the new features for testing and publication. Six scenarios now so modified: Shiloh 1862; Kaiserschlacht 1918; CFNA 1940-43; Soviet Union 1941; Germany 1945; Okinawa 1945.
3. Those scenarios need to be play-tested to ferret out any remaining bugs with the new features. There are already 3 or 4 bugs identified that remain in the new features.
4. There is a significant suite of legacy bugs that need to be fixed.
5. Language files need to be updated with the text of the new features. There were seven in TOAW-III:
_____a. English
_____b. Chinese
_____c. French
_____d. Spanish - finished by Josant.
_____e. German – not yet in TOAW-IV
_____f. Italian – not yet in TOAW-IV
_____g. Polish – not yet in TOAW-IV
_____h. Note to volunteers: Digital Translators make it unnecessary to speak the language to translate.
6. Documentation for the new features needs to be crafted.
7. Scenario Designers will be canvased for any new scenarios to add.
8. Matrix needs to make the installation build for the update.
9. That build needs to be tested.

My estimate/hope is that the release could come in the first quarter of 2025.

And here is how we stand on the remaining tasks.

[Curtis Lemay]

I will now get to work on the Beta Test stuff. That means getting the files all together, creating documentation, and checking with Erik. Soon.

[Curtis Lemay]

I actually despaired of fixing that last bug, it was so difficult. To see how deep it was nested, the attached spreadsheet shows the path, using the de-bugger, to get to the bust:

Each step required stepping into a function to get to the ultimate problem. The spreadsheet shows that it was nested 11 steps deep! This could never be found without the de-bugger. Plus it took forever to find where to start from.

(Note: when it gets to "getBestPath", it uses courier movement for that path - screwing up the path in this case. Fixed that (for this specific call) and the problem was solved. )

What a relief! I must have spent a month on this one bug.

[nemo69]

I actually despaired of fixing that last bug, it was so difficult. To see how deep it was nested, the attached spreadsheet shows the path, using the de-bugger, to get to the bust:

Each step required stepping into a function to get to the ultimate problem. The spreadsheet shows that it was nested 11 steps deep! This could never be found without the de-bugger. Plus it took forever to find where to start from.

(Note: when it gets to "getBestPath", it uses courier movement for that path - screwing up the path in this case. Fixed that (for this specific call) and the problem was solved. )

What a relief! I must have spent a month on this one bug.

Most excellent. Looking forward to the beta.

[joey]

I am impressed with your dedication to this fantastic program. I look forward to the beta version!

[Curtis Lemay]

I will now get to work on the Beta Test stuff. That means getting the files all together, creating documentation, and checking with Erik. Soon.

I have the installation zip ready. It's 157MB, so we will need a public FTP site.

[joey]

I will now get to work on the Beta Test stuff. That means getting the files all together, creating documentation, and checking with Erik. Soon.

I have the installation zip ready. It's 157MB, so we will need a public FTP site.

When you get the FTP site, will you be posting is here or in the above 'topics' section?

[Curtis Lemay]

I will now get to work on the Beta Test stuff. That means getting the files all together, creating documentation, and checking with Erik. Soon.

I have the installation zip ready. It's 157MB, so we will need a public FTP site.

When you get the FTP site, will you be posting is here or in the above 'topics' section?

I don't have any site yet, so no way to know for sure. But I expect there will be instuctions on this forum on how to access it.

[joey]

I have the installation zip ready. It's 157MB, so we will need a public FTP site.

When you get the FTP site, will you be posting is here or in the above 'topics' section?

I don't have any site yet, so no way to know for sure. But I expect there will be instuctions on this forum on how to access it.

Any update on the beta?