Random Battle and Campaign Generator Mod

[dazoline II]

Hi Junk,

My apologies for not seeing this earlier, I claim all the usual excuses such as my browser didn't register the change in the thread, too many things to do besides Ostfront and too many senior's moments.

Did you happen to get this fixed?

I installed the v0.2 on my system and ran it just now. It works for me with no errors on the 7th Russian RCG.
The first 2 errors mention comms.vbs which is still an OOTB file. I imagine the follow on errors in the PzCRCg.hta are results of the first two errors. Take a look at comms file as I include mine (2nd beta applied) here.

At this point I'm not sure what it could be.

[junk2drive]

I haven't tried it since I posted these shots. I'll try again and see what happens. I did have a different version of the beta update than the public so maybe that is it.

[junk2drive]

I first made IE8 my default browser in case that was it. Still have the same errors.

The first 2 errors mention comms.vbs which is still an OOTB file. I imagine the follow on errors in the PzCRCg.hta are results of the first two errors. Take a look at comms file as I include mine (2nd beta applied) here.

I'm not a programmer and don't know where to look for this to compare. As long as the program still works and no one else is complaining we should let it go and wait for you to finish the next version.

[dazoline II]

The file is in Panzer Command Ostfront/Editor/comms.vbs.

Take a look at the modified date on your original file and see if its been altered. Mine has a date of 03/01/2009.
If it has a more recent date its been touched possibly corrupted. If that's true rename your file to something like comms.vbs.orig and put the file I included in my last post in the same directory and rename it comms.vbs.

Test by running the same RCG and then post results.

[junk2drive]

Same date and same text.

[dazoline II]

Did you ever run the OOTB generators from this install?

After reading a bit about vbs files seems they have to be saved as ANSI. Can you reopen your comms.vbs.orig file in notepad and ensure its saved as ANSI.
If its not save it as ANSI and re test.

[junk2drive]

That seems to have fixed it. I think unicode is default but I don't remember where I saw that. Maybe a browser setting?

Also I turned off security checking on this program. Not sure if that did it instead of saving as ANSI.

[dazoline II]

Its a strange issue for sure.
Funny, XML files can have the same issue appear in them when saved as different text types from their declaration.

Good to see its fixed.

[junk2drive]

What is OOTB?

Looking forward to testing your other projects.

[dazoline II]

Out of the box. Refers to default installed files.

[junk2drive]

Thanks

Yes I did run the stock RCG without errors. Good to know for the future what this was.

[ComradeP]

Seems the error is also there in the latest patch. I tried opening the comms.vbs file with notepad, saving it as ANSI, but the error persists.

Edit: using Dazoline's file fixed the comms.vbs issue.

[ComradeP]

I did run into another problem, though. I wanted to play with Stugs in my starting core, but the battle file couldn't process the request for some reason. I used Stug IIIC as the unit ID, the way it's noted in the armoured units folder. After removing the Stugs, the random campaign with a different core was generated normally.

[junk2drive]

This is what is in the xml

<armouredunit type="StuG IIIC" side="German" mass="22000" size="-1"
stun="0" speed="120/240" turretrotation="" month="7" year="41"
points="32" movetype="4" horsepower="300" endservice="9/43" medservice="10/41"
medprev="5"

Did you use upper case G in the name?
Start date 7/41 end date 9/43 Did your campaign fall before or after these dates?

[ComradeP]

Hmm, maybe it was the availability date. I thought the availability date would be roughly the same date as the start of production.

I don't think the upper case matters, as many units are upper case in the armoured units folder but not in the core units .xml.

[dazoline II]

Upper case matters especially with unit type as its an identifier between XML files and the name of the file itself.

And looking in the ArmouredUnits/StuG IIIC.xml file its "StuG IIIC", at least mine is.

[junk2drive]

I made a mistake in my post with the end date, it should say 9/43, sorry

I posted the contents of the xml for a reason. The xml name may not be the name of the unit. We call these outer names and inner names. I get bit by this all the time.

For example, the outer name of the xml is Pz Kpfw VI Tiger I Late but the inner name is Pz Kpfw VI Tiger IE. If you use the outer name it will crash.

[ComradeP]

And where do I find those correct names?

Can't say I like the fact that some of the names in the armoured units folder are wrong in that case.

Why is, for example, the Panzer IIIH called PZ KPWFW IIIH on the folder, Pz KpfW IIIH in the compendium.png in that folder, but PZ_IIIH on the models? Why not use a single standardized name so everything would be clear instead of confusing?

[dazoline II]

I doubt the original producers of the game had that as a requirement and getting the XML up to spec as in simplifing it would be a major effort for no gain in playability.