Public Beta patch 1.07h (2 versions)

[Pdubya64]

In my game, I have the following problems...

First, National Morale and Victory Points are not shown.

Second, element names seem to just take the first in the list, ignoring any state affiliation (i.e., my New York Brigades have California Regiments as they appear first on the list).

Here's a screenshot, this brigade doesn't even have any state names, but goes directly into random numbers for the regiments. (the two problems have been circled in yellow).

I'm wondering if you did a uninstall/reinstall before applying 1.07h McNaughton. IIRC, just a day or two ago there was someone else with weird problems and they disappeared with a clean install.

Yeah, it's a big pain in the keister, but after the 1.07 alphabet soup patches, it may be best.

[rasnell]

h standard link above says "link does not exist." couldn't download.

[arsan]

Now the patch its official
Try the link in this thread
http://www.ageod-forum.com/showthread.php?t=6557

[Eugene Carr]

I had to do a reinstall to combat the strange numbered units.

However even after that Union unit selection seems to remain erratic, CSA seems to maintain territorial association (as it should) Tenn bdes have Tenn regts (prior to reinstall everyone was getting Alabama regts).

For the Union in the April 61 campaign new inf units seem to start in California and work on to Colorado etc.

In the July 61 Campaign I seem to be able to recruit kentucky in Kentucky, Ohio in Ohio, Illinois in Illinois but I have New Mexico in Penn. California in NY.
Cavalry and Artillery seem to be ok so the Penn bde had 2 NM. regt and a Penn. cav regt and a Penn. Art battery.

So not clear to me whether it is a random feature or if some states have a problem and recruiting is defaulting to the top of the list. Also may be differences between April and July campaigns.

[McNaughton]

Here's what I did, and what I still notice.

I had done a compelte re-install. Installed the new patch. Copied the game for a version that I do my modding. (the screenshot was based on a fresh install, but copied to a new directory, then on edit-mode to compile my scenarios).

Now, it seems like the disappearing National Morale and Victory Points only happens in the 'copied' game, meaning that either the copying of the game, or the compiling of a new scenario caused it to disappear (something that should not happen either way). NM and VP still appear in the original, unmodded version of the game on my computer.

However, in regards to element names in a unit, there are still errors. All of my New York brigades are equipped with elements of California designation (the first on the element list). This happens in both the modded/copied and fresh install and patched versions.

So, there appears to be some instability in these new features, and the latest patch, as compiling a scenario, and making copies never resulted in disappearing features, and a fresh install and new patch results in some errors in the new designation of names to elements in a unit.

[McNaughton]

Here's what I notice when looking at the model files in an installed version...

$Connecticut|4th Connecticut|5th Connecticut|6th Connecticut|7th Connecticut|8th Connecticut|9th Connecticut|10th Connecticut|11th Connecticut|12th Connecticut|13th Connecticut|14th Connecticut|15th Connecticut|16th CT 'Plymouth Pilgrims'|17th Connecticut|18th Connecticut|19th Connecticut|20th Connecticut|21st Connecticut|22nd Connecticut|23rd Connecticut|24th Connecticut|25th Connecticut|26th Connecticut|27th Connecticut|28th Connecticut§

Here's after a models file has been compiled...

$Connecticut|4th Connecticut|5th Connecticut|6th Connecticut|7th Connecticut|8th Connecticut|9th Connecticut|10th Connecticut|11th Connecticut|12th Connecticut|13th Connecticut|14th Connecticut|15th Connecticut|16th CT 'Plymouth Pilgrims'|17th Connecticut|18th Connecticut|19th Connecticut|20th Connecticut|21st Connecticut|22nd Connecticut|23rd Connecticut|24th Connecticut|25th Connecticut|26th Connecticut|27th Connecticut|28th Connecticut?

The only difference is that § is replaced by ? in the compiled version. This could be why I am getting all of those weird errors resulting in some elements changing into numbers (instead of names). However, how do I stop this conversion from happening? Am I forced to edit ALL of the elements to switch from ? to § manually by copy and paste?

However, that still does not solve the problem of the disappearing National Morale, or why some states use elements that are incorrect designations.

[McNaughton]

Also, in my mod I had to eliminate all of the nicknames, as this is pretty much the only designation a leader gets from now on (other than when they are unattached to any command sitting in a stack). I want 'Joseph B. Hooker' not 'Fighting Joe' for my commander names.

[Gray_Lensman]

deleted

[McNaughton]

These type of problems/observances which seem to be associated with the .scn files and the common usage of the "official" database files used to generate the .scn files by everyone generating new .scn files only increases my apprehension of errors/conflicts being introduced into these new ".scn" files.

Not that I want to rain on anyone's parade, but I am highly suspicious that the database is getting "corrupted" for lack of a better word, and some sort of control needs to be exerted over it's use.

Here's an example: (but just one example, I am sure there are other examples, also)

Let's say I add to the database files regarding changing TransportLvl settings for my ongoing RR Accuracy fixes. I then submit them to Pocus, and he accepts them along with the database change in whatever particular scenarios I have adjusted. Meanwhile using McNaughton's work as an example, he is working on some scenario changes simultaneously.

Now, one of two things will happen, either McNaughton's work gets accepted into the official database files, if he happens to submit it to Pocus, or the most likely case, is that once, I have sent my database files to Pocus to "officialize", McNaughton's scenarios are no longer compatible with the new RR changes.

I hope my point is clear, and currently I have no solution of my own to this perceived conflict. I don't wish to invalidate other person's hard work if I can avoid it, but I also see this as possibly the cause of other things that are "mysteriously" showing up like the examples sited above.

Suggestions anyone?

Regards

I don't think that these are the issues at hand. The aspects of the game that are going awry (national morale/vp display, plus naming elements) are issues of the game that have not been addressed by modders, let alone AGEOD since its inception. Modding terrain deald with completely different files in the databases than modding scenario files or models and such. They are all in self-contained XLS files. Modding the stats of a unit, using the provided up-to-date XLS file should not affect if national morale appears on your screen, there is no logical connection between the two.

Also, as I found, the reason for numbers appearing in my mod for the elements is due to conversion errors (see my post above), meaning that it sees a charactor it does not recognize, and stops looking. However, for whatever reason my computer converts recognizable charactors into un-recognizable ones. That is causing this particular error.

However, there is another error as to why the game does recognize elements for Tennessee and Ohio, but not for New York and Pennsylvania. Probably some typo in the original files that causes these elements not to be recognized (since New York, Pennsylvania and I bet that the same errors are experienced for West Virginia, are all at the end of the lists).

[McNaughton]

Error in the models file. Somewhere there is an error in the models file that causes the game to ignore Pennsylvania and New York element designations. I also bet that the same error will happen for West Virginia units as well.

Back in HoI editing we had a similar problem, where some unit names were not appearing after a certain point. The problem was a SINGLE incorrect : instead of an ;

I bet, that somewhere before New York there is a typo in the Union Infantry Model Names file causing everything after it to be unrecognized.

This is what is happening in my modded files due to a conversion error exchanging § for ?. There probably is a tiny error, or an incorrect symbol used.

The way to find out what works, and where the problem is, is to find out where it starts.

[Gray_Lensman]

deleted

[McNaughton]

Just did a test, and all that I see, for any brigade built, anywhere for the union, are errors and incorrect designations.

I built a Maryland, Pennsylvania, New Jersey, New York and Ohio brigade. Each primarily used...

Infantry
California, then Colorado

Artillery
Minnesota

Cavalry
Colorado

This is unmodded, unedited, fresh install and fresh patch. So, this system (at least for the union) is very buggy.

[McNaughton]

McNaughton:



Incorrect.

The TransportLvl settings are imbedded in the individual Scenario database files and these have to be adjusted to coordinate the changes with the RR graphics and TransLinks fixes. These setting are within the "UID" definitions contained at the end of each scenario file. If the TransportLvl setting for a region is left at anything but =3 then the rails do not work regardless of the .rgn TransLinks changes.

As stated above, that is one example...

Not having worked with the other contents of the scenario files I can't be so sure of other conflicts, but it seems to me the scenario files are the link point for a lot of other files that are being modded also.

As I said earlier, if we are being supplied with the latest XLS files and told where major changes have been implemented, then this will not be a problem. Also, there are three parts to a scenario in the XLS file. One part deals with cities and connections (as you are talking about above), one part deals with scenario specific events, and the other part deals with units on the map (forts, units, depots, etc.). Modding a scenario does not mean that you will actually modify the things you are talking about, as you can easily tell your scenario to link to pre-existing files.

Why would linkages between cities cause a problem with model names and displaying National Morale and Victory Points? All and all, I believe that what is in a scenario affects that scenario. You didn't mod a 'rule' into the game, just different terrain linkages. If these linkages do not exist in my scenarios, then it will just use the old linkages, and should cause no problems with other aspects (just because scenario A uses linkages 1 does not mean that scenario B using linkages 2 will get errors).

However, this also is contingent to the point that we are given updated XLS files.

Lastly, the problems experienced are most likely problems that have existed since day one (in the models files), but since they have been dormant until now, the problems in them were never noticed. Also, there have been some major differences I have noticed as to how the game loads, and compiles scenarios in the later versions.

It worked fine before, even with changes resulting from player modifications. So, I don't think that this is the cause.

Also, the only thing that I ever submitted to get placed into the official AGEOD files are historic named Brigades.

[Gray_Lensman]

deleted

[McNaughton]

I am not discounting the fact that there are problems with other files .mdl files for example, that are not in the scenario files themselves.

Even though there are separate sections for the Scenario files, once regenerated into the actual .scn files that the game uses, a lot of the information from these separate .xls files seems to get imbedded into the single actual final .scn file. Therein lies the conflict.

The conflict only happens if you create a new cities file, and if this new cities file is not based on the latest release. You can create a scenario that uses the original cities file very easily. Even here I think that the link between the cities file and the new terrain files are limited, at best.

Every time there is a new patch, I check for changes, apply my changes to new XLS files, then completley recompile the scenarios. So, if AGEOD is dilligent at releasing the updated XLS files, and that enough information as to what has been changed has been provided, then there will be no problem.

Also, I really don't believe that the Cities file in the 'scenario' XLS really impacts the regions files at all. The regions file makes notice toward the city name, and this is the connection. If these links are not meddled with then there will be no problem at all. As long as the 'names' or 'linking names' remain the same, there will be no problem (regions look for a specific county name, then applies it).

The cities XLS file affects things like Control, City/Port levels, has a railroad (this is possibly the only conflict I can see, but should not cause the problems we are discussing).

I think you are looking for the problems in the wrong areas. There are some present issues that we are dealing with, and the discussion being promoted now seems to be 'what if's for the possible future' rather than 'I think that this causes the current problem'. I personally do not see that this connection is a viable one. What AGEOD does when they implement information is to take the actual changes and copies these changes into their XLS files. They take bits, then copy it to their own information, they don't use the entire XLS file I sent them for the brigade names (for example).

[Gray_Lensman]

deleted

[McNaughton]

McNaughton:

I'm sorry to derail your previous discussion, so by all means continue with it as it interests me also. I just wanted to possibly point out an area of possible conflict. Also, if you are taking the time to reevaluate your scenario after each update, then you are most likely addressing most of the points I have made above by incorporating the changes. A good thing.

Regards

I think that this would be good for a new thread, as making sure that we (as testers and modders) have all of the information, as well are giving AGEOD the correct information. While it could lead to future problems, (I totally agree, one of the reasons why I think that modding the txt files will lead to problems, while the XLS files are the best way to go).

[Guru80]

Just did a test, and all that I see, for any brigade built, anywhere for the union, are errors and incorrect designations.

I built a Maryland, Pennsylvania, New Jersey, New York and Ohio brigade. Each primarily used...

Infantry
California, then Colorado

Artillery
Minnesota

Cavalry
Colorado

This is unmodded, unedited, fresh install and fresh patch. So, this system (at least for the union) is very buggy.

That's odd McNaughton since I don't have the incorrect designations showing up at all for the Union and I have set up separate folders for mods and I have none of the disappearing NM, VP, and so on.

I wonder why we are having such different results?

[McNaughton]

That's odd McNaughton since I don't have the incorrect designations showing up at all for the Union and I have set up separate folders for mods and I have none of the disappearing NM, VP, and so on.

I wonder why we are having such different results?

My results are for a completely unmodded version of the game (those regarding the completely mixed up model names, for whatever reason the NM and VP appear and are only missing when I compile a scenario).

Others have also mentioned that (even with fresh and unmodded installs) that the naming system appears wonky, and some designations are not properly applying.

[Eugene Carr]

I raised 1 of each brigade in 2 sessions 2 turns apart ( raised all the money I could and the most conscripts!) 1st turn was from Kansas to W.Virginia.2nd to end.

California,New Mexico and Minnestota account for most of the odd infantry units but I did have 2 with no designation in Boston and a Mass. in New york.
However this time I did get New York and Penn. units.
Delaware, Kentucky,Michagan and Maryland were entirely correct.

Some of these units I have never seen before Infantry from DC, cav from Oregon and Colorado and Berdans Sharpshooters(raised in Penn.)

This was on clean install.

[Pocus]

Can you give me precisely an element name which has been given to the wrong unit (and the state of the unit) please? There are perhaps semi colons or erroneous states designations in the models files.

[Eugene Carr]

ok I've just recruited following 6 brigades in the July campaign have listed in order on the new units notice:

LOCATION - STATE REQUESTED - Bde NAME - UNITS
Boston-Ma.-Ferrero-1stCa."Mountaineers" 3rdCa. 6thCa.1stMn LArt 1st Co. cav.
Indianapolis -Indiana - McDowell - 7thCa. 8thCa. 2ndCo. cav.
Chicago - Ill. - Wallace - 1stCo."Pikes Peakers" 3rdCo.3rdCo"Bloodless Third" cav.
New York - NY - French - 1stDC 2ndDC 1stMn 22Mn LArt 1stOregon cav.
Louisville-Ky-Lauman- 1st Ky 2nd Ky 1st DC cav.
Philedelphia-Pa-Birney-2ndMn 3rdMn 3rdMn LArt 1st Me"the Puritans" cav
I ran replacements the following turn and they were Mn. Inf and Pa. LArt.

What I recieved tallies some what with my previous run ,its the same regiments but in different places suggesting they are being recruited in order. On my previous try I did eventually get Penn and NY units as I recruited enough I didnt note order though.

Going to recruit some more and see if I get Ill. NMex and Ind infantry! Also Kentucky Cav.

[Pocus]

I would need a modder to help me here, the problem stems for the lists which are with some errors.

[Le Ricain]

I just finished my first game using 1.07h Standard Edition (with mods). Playing as the Union in 1861 April GC. Basically, it was a most enjoyable game. Hats off the modder and to Pocus for making some real improvements to this fine game.

One bug that I noticed. I never received Alan Pinkerton. The South did get Belle Boyd however.

I played further on in the game and discovered that Pinkerton arrived in May, 1863. It would appear that the year has been altered and should be an easy fix.

[Paul Roberts]

I would need a modder to help me here, the problem stems for the lists which are with some errors.

Because I'm impatient, I'll go ahead and ask if work is proceeding here. Do we have a new patch on the way?

Please say yes, as I am putting off starting a new campaign until the update.

[Pocus]

I got no helping hands on that. At worse I will remove the new feature until the lists are cleared of issues.

[Paul Roberts]

I got no helping hands on that. At worse I will remove the new feature until the lists are cleared of issues.

I've no experience with modding AACW, but if it's mainly a matter of checking the appropriate text files for errors I would be happy to help!

[Pocus]

That would be most welcome. First trip for you is to go there

http://www.ageod-forum.com/showthread.php?t=3974

and grab the database.

Then post a thread in the AACW modding forum, I will explain you what is at hand. There is nothing difficult, if you know how to open an XLS file and search what are in some cells. Modding is an intimidating word for something which is mostly using Excel, word and text files.

[Paul Roberts]

That would be most welcome. First trip for you is to go there

http://www.ageod-forum.com/showthread.php?t=3974

and grab the database.

Then post a thread in the AACW modding forum, I will explain you what is at hand. There is nothing difficult, if you know how to open an XLS file and search what are in some cells. Modding is an intimidating word for something which is mostly using Excel, word and text files.

I'm willing to try! I just started a thread in the modding forum called "Pocus: helping with unit names files." See you there.

[McNaughton]

I did a lot of scans, but I cannot understand why the issues are happening.

Could it be due to the naming system? Is it better to use "New York" or "NY" to determine which state the element name is coming from?