RE: TOAW XML Editor (Full Version)

All Forums >> [New Releases from Matrix Games] >> The Operational Art of War IV >> Mods and Scenarios



Message

Curtis Lemay -> RE: TOAW XML Editor (11/2/2018 3:09:32 PM)

Kudos to you for creating this. However, be aware that the .gam file format is not set in stone. Its format changes each time the game gets any expansion of any kind, and this editor will have to adjust accordingly. I don't think the 4.0.1.23 format is even the same as the 4.1.0.6 format, for example, since there were a couple of game options and a game parameter added between them.

Furthermore, there is very little, if any, TOAW4 backwards compatibility for the xml files (including the .gam file). So, designers using this should regularly convert their .gam files back into .sce files via the TOAW4 editor ASAP.



Lobster -> RE: TOAW XML Editor (11/2/2018 3:58:24 PM)

I just keep all of the old TOAW builds. That way you can work on it via the old build and when it's all done load it into the old build to save. Then open it in the new build and save it there. All that the tool designer has to do is provide the build number the program was made under so people will know to use his tool with that build. Not really rocket science.

Considering the huge amount of time this tool saves it is well worth that small effort.



Oberst_Klink -> RE: TOAW XML Editor (11/2/2018 6:40:05 PM)


quote:

ORIGINAL: Lobster

I just keep all of the old TOAW builds. That way you can work on it via the old build and when it's all done load it into the old build to save. Then open it in the new build and save it there. All that the tool designer has to do is provide the build number the program was made under so people will know to use his tool with that build. Not really rocket science.

Considering the huge amount of time this tool saves it is well worth that small effort.

I also do the retrofit scenario design appraoch... use TOAWIII, Andy's tools, load it into TOAWIV, adjust to the new features and Bob is your uncle. Btw, how's Nigel doing? Haven't seen him on the radar for quite some time.

Klink, Oberst



76mm -> RE: TOAW XML Editor (11/2/2018 7:11:25 PM)

quote:

ORIGINAL: Curtis Lemay
Kudos to you for creating this. However, be aware that the .gam file format is not set in stone. Its format changes each time the game gets any expansion of any kind, and this editor will have to adjust accordingly. I don't think the 4.0.1.23 format is even the same as the 4.1.0.6 format...

I was wondering about this...how do old scenarios continue to work if the xml format changes all the time?

Also, it is very possible that I'm completely missing something, but I'm not sure if additions to the format would really be an issue--it seems like the main thing that would screw up my code is if the XML tags changed? It seems like additions to the XML would only mean that the program would need to be updated for those additions to be accessible in the program? But I'm a rookie to all this, so pls correct me if I'm wrong.

Finally, once I get this further along, I will probably upload it to GitHub, so that even if I am hit by the proverbial bus or decide to focus on My Little Ponies games instead of TOAW, the code could be updated.



76mm -> RE: TOAW XML Editor (11/2/2018 7:14:34 PM)

By the way, here is what I'm working on now:

[image]local://upfiles/11887/51AD53A2C67348DC8DB9E1501ECC2CC5.jpg[/image]



76mm -> RE: TOAW XML Editor (11/2/2018 7:15:09 PM)

And this:

[image]local://upfiles/11887/F789CEA7D4FE4C3AA651A7EEB35121EE.jpg[/image]



Lobster -> RE: TOAW XML Editor (11/2/2018 7:42:34 PM)

Good stuff :)



Curtis Lemay -> RE: TOAW XML Editor (11/2/2018 7:54:18 PM)


quote:

ORIGINAL: 76mm

I was wondering about this...how do old scenarios continue to work if the xml format changes all the time?


The game supports backward compatibility for the binary files (.sce, .sal, .pbl, etc.) via lots of convoluted code in the file reading process. You can load an ACOW .sce file into TOAW IV. Not so for the xml files.



Lobster -> RE: TOAW XML Editor (11/2/2018 9:58:55 PM)


quote:

ORIGINAL: Oberst_Klink


Btw, how's Nigel doing? Haven't seen him on the radar for quite some time.

Klink, Oberst


Banging away at his books. Going to put them in different formats now. He has at least one volume out in hard cover.



sPzAbt653 -> RE: TOAW XML Editor (11/3/2018 3:30:22 AM)

Those features in posts 35 & 36 are already in the Editor, I think.

[image]local://upfiles/24850/4D93CB36FFAD4C58A660E886E94CE9BA.jpg[/image]



Lobster -> RE: TOAW XML Editor (11/3/2018 11:48:11 AM)

Looks to me like TOAWxml does it all at once instead of having to play around with one item at a time. Kind of like one stop shopping and with the units displayed in a nice hierarchy format.



biddrafter2 -> RE: TOAW XML Editor (11/3/2018 5:36:01 PM)


quote:

ORIGINAL: Curtis Lemay

Kudos to you for creating this. However, be aware that the .gam file format is not set in stone. Its format changes each time the game gets any expansion of any kind, and this editor will have to adjust accordingly. I don't think the 4.0.1.23 format is even the same as the 4.1.0.6 format, for example, since there were a couple of game options and a game parameter added between them.

Furthermore, there is very little, if any, TOAW4 backwards compatibility for the xml files (including the .gam file). So, designers using this should regularly convert their .gam files back into .sce files via the TOAW4 editor ASAP.


The Header tag in the .gam XML has a version attribute that has not changed since TOAW III (according to my tests). Perhaps this could be changed to reflect the version of TOAW that produced the XML save? This would allow 76mm to prevent corruption upfront and not require an XML load test to detect changes.



biddrafter2 -> RE: TOAW XML Editor (11/3/2018 5:37:50 PM)


quote:

ORIGINAL: 76mm

quote:

ORIGINAL: jakobscalpel
BTW, I've been a programmer for a long time and since you are using .NET I could help out with your project down the road if you'd like. Hopefully C#???

Yes, C#, generally using Linq to XML. It would be great if you're interested in helping out, if nothing else with tips on stuff I'm having trouble with (ahem, deployment...).

One stand-alone piece is the event editor, let me know if you have any ideas about how to set that up.


I'd be happy to take a look. Send me a PM if you'd like to get in touch via e-mail or Slack.



76mm -> RE: TOAW XML Editor (11/3/2018 6:36:42 PM)

quote:

ORIGINAL: jakobscalpel
The Header tag in the .gam XML has a version attribute that has not changed since TOAW III (according to my tests). Perhaps this could be changed to reflect the version of TOAW that produced the XML save? This would allow 76mm to prevent corruption upfront and not require an XML load test to detect changes.

That would probably be an easy enough change, as long as it wouldn't break the *.gam files so that they couldn't work in the game... Do you want to give it a try?!



76mm -> RE: TOAW XML Editor (11/3/2018 7:22:38 PM)

I thought I'd upload the latest version (attached). Here are the current features:

Current Features:

--Revise Force, Formation, and Unit Settings: Change any of the enabled settings. Be careful, because I have not yet added any data validation, so if you enter data in the incorrect format, etc., it will probably break your *.gam file. IF YOU CHANGE ANY SETTINGS, BE SURE TO PRESS THE “SAVE CHANGES” BUTTON OR THE CHANGES WILL BE LOST WHEN YOU LEAVE THAT SCREEN!!!

--Transfer (Drag-and-Drop) Unit: Select unit in treeview, left click on unit and drag to formation to which it should be transferred, release mouse button. It will become the last unit in the selected formation.

--Transfer (Drag-and-Drop) Equipment: Select equipment in treeview, left click on equipment and drag to unit to which it should be transferred, release mouse button. It will become the last equipment line in the selected unit.

--Change Position of Formation, Unit or Equipment: Right-click to select Move Up or Move Down, or use the indicated key shortcuts (Ctrl-Up and Ctrl-Down, respectively). Note that in the in-game editor, units are ranked by index number and so will not be in the same order as in TOAW XML.

--Delete Unit: Right-click, select Delete, or use the key shortcut (Ctrl-Del). Confirmation is required for deletion, but there is no “un-do”, so be careful with deletions!

--Propagate Settings: Right-click, select Formation Propagation or Unit Propagation, as appropriate. On the form which appears, uncheck any settings which you do not want to propagate.

If you haven't figured this out already, you guys are the beta testers, so please let me know if you encounter any problems. I encountered one strange problem when I moved from the Debug version to the Release version: units were showing blank deployment and location settings, even though these settings worked fine in the Debug version--let me know if you encounter this problem, or any others...

Next up:
I need to clean up some things with existing units, such as Reinforcements, Air Unit missions, also copying of existing units, and fixing any bugs that come up. After that I'll move on to creating new units, formations, etc.

[EDIT] See first post for latest version.



Lobster -> RE: TOAW XML Editor (11/3/2018 8:37:33 PM)

Thanks for what you've done. [;)]



76mm -> RE: TOAW XML Editor (11/3/2018 8:41:35 PM)

@Lobster, is everything working for you?



76mm -> RE: TOAW XML Editor (11/4/2018 11:56:26 PM)

Guys, I came across a problem with transferring equipment between units, so pls don't transfer equipment until the next version. Transferring units between formations seems to work OK...



Lobster -> RE: TOAW XML Editor (11/5/2018 1:11:56 AM)


quote:

ORIGINAL: 76mm

@Lobster, is everything working for you?


Going to change a bunch of settings in 2k units tomorrow. Let you know how it goes. [;)]

Probably not going to do anything with equipment or moving units around.



Lobster -> RE: TOAW XML Editor (11/5/2018 1:19:54 PM)

Not sure if this is possible but...When editing the highlight goes from the current item being worked on (formation/unit/etc.) to the field being edited, in this example loss tolerance. Could the current item be highlighted in some way, say a grey background or something similar? It's just a very small thing but makes it easier to relocate where you are in a long list of items. Also, when going to a different item is it possible to have a button to choose between auto saving edits or manually saving an edit?



[image]local://upfiles/45799/EAE54DCECB2A499F9A7173F1D92CC39E.jpg[/image]



76mm -> RE: TOAW XML Editor (11/5/2018 1:32:51 PM)

It should work now so that when you save changes made in the right panel, it goes back to highlight the unit you just changed in the unit tree. Does that work?

Autosaves are certainly possible, but I'll probably add a bit more functionality first.



Lobster -> RE: TOAW XML Editor (11/5/2018 1:40:09 PM)

Bah...working with the wrong TOAW executable. I have to download the right one. I must have overwritten it. [8|]



76mm -> RE: TOAW XML Editor (11/5/2018 1:52:04 PM)

I'll try to add version numbers to the next one, couldn't figure out how to do it last time.

Also, jakobscalpel has signed up to help with the event editor. He's a real programmer, so that's great news, although he's a busy guy so don't expect anything really quickly...



Lobster -> RE: TOAW XML Editor (11/5/2018 3:42:09 PM)

When working with a .gam file in TOAWxml tool that has a deployment field that is completely empty (just a white field) this exception happens. The TOAWxml tool has to be able to handle completely empty fields since when editing this will be fairly common.

Edit: In many cases TOAW adds a default value. I guess in the deployment and Location fields this isn't true. Even if you fill the fields after opening the .gam file in TOAWxml tool you still get the exception. I got this when testing the tool with FitE2.



[image]local://upfiles/45799/8A751A57EEF244CD93532EA305BBB2CF.jpg[/image]



76mm -> RE: TOAW XML Editor (11/5/2018 3:54:40 PM)

Thanks for the report (and sorry about that!), but a couple of questions:
1) Was the deployment box empty because the unit was a reinforcement, or because it had just never been set? I've already made a change to show when a unit is reinforcement.
2) Generally I don't think that data fields should be empty--they should be filled with default values upon unit creation, and can then be changed as necessary.
3) But of course the program should not crash if a data field is empty. This is a bigger pain than it sounds like but I should be able to figure it out.

Keep the comments coming! I want to straighten out all of these issues before adding any more features.



rbeeler81 -> RE: TOAW XML Editor (11/5/2018 5:01:49 PM)

First of all, thank you for creating this program. I spend hours with the built-in editor, however this tool should save time and allow for more gameplay.

I too receive the same error as Lobster. I am using the latest updated version of TOAWIV as well as your editor.



76mm -> RE: TOAW XML Editor (11/5/2018 5:33:33 PM)

OK, but it would be helpful to understand if the deployment box is supposed to be full, but is empty, or is actually still empty at this point in scenario development?




rbeeler81 -> RE: TOAW XML Editor (11/5/2018 7:16:42 PM)

The deployment box should be full. I have found that some .gam files work, while others do not. The scenario where the .gam file is empty is the TWW_Third_World_War series. However, other .gam files show the units as normal.



Lobster -> RE: TOAW XML Editor (11/5/2018 9:14:10 PM)


quote:

ORIGINAL: 76mm

OK, but it would be helpful to understand if the deployment box is supposed to be full, but is empty, or is actually still empty at this point in scenario development?




Using FitE2:

The German 270th Inf Div is set as a reinforcement:



[image]local://upfiles/45799/DF34AA3620644AE6B27E51C38DCBD8C5.jpg[/image]



Lobster -> RE: TOAW XML Editor (11/5/2018 9:15:16 PM)

And here it is in TOAWxml. Deployment is a turn (88) and not a mode.



[image]local://upfiles/45799/0C471F5A538B4A6EAEEBA5F0E304D876.jpg[/image]



Page: <<   < prev  1 [2] 3 4 5   next >   >>

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.765625