4.0.1.23 Public Beta Update (Full Version)

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



Message

Tamas -> 4.0.1.23 Public Beta Update (11/24/2017 11:02:13 AM)

Hi Everyone,

EDIT: The public beta has been updated to version 4.0.1.23. Download link below has been replaced, and changelog updated.

The TOAWIV team has been working hard to address the few issues that have come up during the week since release, and also to incorporate the feedback that you have provided.

All of these fixes and changes are now available in this public beta update. While we have found this version to be stable, with such a complex game we need more testing to confirm everything works as intended, before we can make it official.

If you want to have an early look, and help us test the patch, you can grab it from the link just below. If you have any technical issues to report with this patch, please make sure to use the "[4.0.1.22]" prefix on any thread title you open in the Tech Support sub-forum. If you wish to leave any general feedback on the beta update, please use this thread.


DOWNLOAD TOAWIV 4.0.1.22 Public Beta


INSTALLLATION
The update comes in a zip package. It needs to be unzipped into the game's main folder, overwriting the existing files.
This folder, by default, is "Program Files(x86)\Matrix Games\The Operational Art of War IV"

If you are unable to unzip the package into this location (this is possible with certain system settings), then please unzip it into a separate folder, and then copy the files into the game's main folder referenced above.

-------------------------------------------------------------------------------------------------------------------------

LIST OF CHANGES:

4.0.1.23
Fixed saving JPGs.

4.0.1.22:
Made a change that may help with the black boxes.
Fixed loading a unit into the editor.
Tooltips should now remain onscreen.
The editor will no longer crash with a bad OOB, instead it will try to clean it up and give warnings.
Did some more rewriting to make the scenario loading code even more bulletproof.
Hints no longer happen when a popup menu is open.
Supply over railroads when there is a RoadCost other than the default now work correctly.
Modified the AirBorne cost when there is a RoadCost other than the default but haven't had a chance to test it.
Made a change that might help with the issue of the combat report dialog crashing.
The close dialog on the New Scenario Dialog now returns to the start screen.

4.0.1.15:
- Fixed crash in Bitter Victory Sicily. I believe this was caused by a land unit being knocked out of ship transport mode while moving as a fleet when it was the last remaining unit.
- Fixed issue with the AI not moving Ships. It may have prevented some land units from moving as well. I made a change to make the ship AI faster but didn't fully test it.
- Found and fixed the bug that causes the formation lines to show up. Since it's intermittent, I can't verify 100% that it's fixed, but I believe it is.
- Added a Graphics entry under the [Scaling] section fo the Opart 4 Fonts.ini file
This upscales many of the graphics. Values greater than one make things bigger, values less than one make things smaller. This should be used with larger or smaller fonts.
- Added in some updates to the expanded time and distance rules. Bob had made these a couple of weeks ago but since none of the current scenarios use them I didn't want to put this out as part of the release. No UI changes, just some cleanup of the existing new levels.
- Chinese characters should now show up in the diplomatic pouch.
- Classic view map resizing no longer leaves classic view.
- Fixed issue with Chinese in diplomacy pouch
- Fixed issue with zoom in classic view leaving classic view.
- Fixed issue with loading/saving non-game object like units.
- Fixed Net Awards calculation
- Fixed F1 now opens the manual
- Made scrolling easier.
Increased the scrolling area around the main map to 32 pixels.
Modified the dialog boxes so that the mouse capture no longer extends beyond the visible area
Modified the dialog boxes so that the drag area is 15 pixels around the visible area
- Hid the warfare panel on screens equal to or smaller than 1024x768.
- Clicking in the combat planner should no longer cause a double-click.
- To help isolate and/or fix the problems some people are having with Chinese logins, if you add a file called DefaultFolder.txt file and put the path to the folder inside, it will use that instead of trying to find the my documents folder. To use this, you might create a folder called C:/TOAW and put contents of Documents/My Games/The Operational Art of War IV and all it's subfolders into it. Then launch TOAW as an administrator and it should work.
- To help diagnose an issue some people are having with pauses, if you open the Opart 4.ini file in Documents/My Games/The Operational Art of War IV and add a line labeled smallram=Y it may help.
- Game Select dialog now has labels for the buttons. This should help new players.
- PBEM Errors should no longer leave you on a blank screen.
- Shifted Units slightly left in the smaller views to make them look better.
- Start up code show now give better error messages.
- Tweaked the position of the counter on the map.
- Fixed the issue with right scroll not working after changing from large to small map view
- Fixed occasional crashes with playback in PBEM++



nnason -> RE: 4.0.1.15 Public Beta Update (11/24/2017 1:19:36 PM)

I have yet to start playing OAW IV. If I install the beta will that put me on a different server like it does in Strat Cmd? If so is there a way to be on both servers?



Tamas -> RE: 4.0.1.15 Public Beta Update (11/24/2017 1:25:40 PM)


quote:

ORIGINAL: nnason

I have yet to start playing OAW IV. If I install the beta will that put me on a different server like it does in Strat Cmd? If so is there a way to be on both servers?


No, this one will keep you on the main PBEM server as this update should be 100% compatible with the official version in terms of PBEM.



RJL5188 -> RE: 4.0.1.15 Public Beta Update (11/24/2017 1:35:48 PM)

where does the Opart 4 map files go?



goodwoodrw -> RE: 4.0.1.15 Public Beta Update (11/24/2017 1:40:17 PM)

Not sure if game updated, where do i find the game version no.



Tamas -> RE: 4.0.1.15 Public Beta Update (11/24/2017 1:45:21 PM)


quote:

ORIGINAL: rjl518

where does the Opart 4 map files go?


main folder like the exe files.



Tamas -> RE: 4.0.1.15 Public Beta Update (11/24/2017 1:46:13 PM)


quote:

ORIGINAL: goodwoodrw

Not sure if game updated, where do i find the game version no.


In the main menu, go to the Help section in the top bar and click about. The version number will flash up before the credits (admittedly, it flashes up too briefly)



goodwoodrw -> RE: 4.0.1.15 Public Beta Update (11/24/2017 1:53:13 PM)

Yes I thought so your right gotta be quick[:)]



ralphtricky -> RE: 4.0.1.15 Public Beta Update (11/24/2017 3:42:59 PM)

If you mouse over the executable in Explorer, you will also see the version number, of you can go into properties and it lists is there.



Shadrach -> RE: 4.0.1.15 Public Beta Update (11/24/2017 3:57:54 PM)

What are the .map files? Look like some kind of debug log, probably from a debugger? Do we even need them, I deleted them and it worked fine... :)



ralphtricky -> RE: 4.0.1.15 Public Beta Update (11/24/2017 4:06:02 PM)

Sorry, I forgot to remove them. I keep them so that I can debug any crashes. They aren't needed.



Ginetto -> RE: 4.0.1.15 Public Beta Update (11/24/2017 4:19:56 PM)

The 4.0.1.15 file I downloaded wouldn't unzip in the main TotH folder. I had to open it and drag each file of 4.0.1.15 into the main TotH folder and install them there. Each time before dragging it asked me if I had administrator privileges. Not user-friendly at all.



Tamas -> RE: 4.0.1.15 Public Beta Update (11/24/2017 4:22:29 PM)

quote:

ORIGINAL: Ginetto

The 4.0.1.15 file I downloaded wouldn't unzip in the main TotH folder. I had to open it and drag each file of 4.0.1.15 into the main TotH folder and install them there. Each time before dragging it asked me if I had administrator privileges. Not user-friendly at all.


As I mentioned in the original post above this is possible depending on your system settings.

Yes, this is not ideal, of course the official patch will self-extract. But we wanted to get this beta update out before the weekend and uploading it as a zip file was the only option for that.



Splatsch -> RE: 4.0.1.15 Public Beta Update (11/24/2017 7:20:32 PM)

quote:

ORIGINAL: Tamas
[...] But we wanted to get this beta update out before the weekend and uploading it as a zip file was the only option for that.

Thanks for that, I'll try it right now :)



jzardos -> RE: 4.0.1.15 Public Beta Update (11/24/2017 8:09:36 PM)

Thanks for a fast patch. I know you tried to address the scrolling issues, don't see much help here. Still a pain if using the mouse. Can we please get a full window mode? That would solve the problem completely.

thanks



Meyer1 -> RE: 4.0.1.15 Public Beta Update (11/24/2017 8:55:54 PM)

Thanks a lot. Scaling works great. Scrolling south is better.



Meyer1 -> RE: 4.0.1.15 Public Beta Update (11/24/2017 8:57:36 PM)


quote:

ORIGINAL: jzardos

Thanks for a fast patch. I know you tried to address the scrolling issues, don't see much help here. Still a pain if using the mouse. Can we please get a full window mode? That would solve the problem completely.

thanks

You can use this tool to put TOAW in full screen mode. Works perfectly:
https://github.com/Codeusa/Borderless-Gaming/releases



Meyer1 -> RE: 4.0.1.15 Public Beta Update (11/24/2017 9:56:08 PM)


quote:

ORIGINAL: Meyer1

Thanks a lot. Scaling works great.

It does, but at 2560x1440 and 27" screen, I think I would only want to make bigger the unit panel. Maybe the status panel too, would be great if there were separate settings for the different panels [:'(]



RFalvo69 -> RE: 4.0.1.15 Public Beta Update (11/25/2017 5:36:01 AM)

Will the official patch include the upgraded/fixed scenarios?



sanderz -> RE: 4.0.1.15 Public Beta Update (11/25/2017 6:48:42 AM)


quote:

ORIGINAL: RFalvo69

Will the official patch include the upgraded/fixed scenarios?


Following on from this there have been a lot of posts with updated scenarios (thanks all for that) but i went off on a bit of a rant (apologies) about this in the Operation Torch thread which i repeat below:-


quote:

ORIGINAL: sPzAbt653
OPERATION TORCH SCENARIO
By accident, the release version of this scenario was not updated to handle the changed naval circumstances better, resulting in too high casualties to coastal fortress gun fire.

This version fixes that.
In the Editor > Deployment > Edit, at the bottom of the list is a Naval Attrition Divider. It is set to the default of ten. It needs to be reset to 100 [or more] to keep the Coast Batteries from getting too many shots at targets. It affects other naval stuff too, just like the Attrition Divider.


quote:

ORIGINAL: Sanderz
So every scenario should have a value of say "100"? What about any old scenario that we import and "save as" does that change the value to 100? If not do you know if the game be patched to do so?

Are you aware of any other values not updated by "save as" that have serious consequences to game play.

I'm assuming patches won't include scenario updates, do you know if so will matrix be setting up a scenario bank (like VR designs) so that scenarios can easily be found and updated - because if the only way is digging through lots of forum posts then that really is not good.



Tamas -> RE: 4.0.1.15 Public Beta Update (11/25/2017 7:21:24 AM)

I'll copy my reply from there here as well, then. [:)]

The plan is that we will include scenario updates (hopefully new scenarios as well) in patches, yes.

We are also looking into how best to facilitate the uploading and downloading of scenarios, to make it as user friendly as possible. But please do use this forum for that in the meantime, we will give everyone a heads-up well in advance once we start implementing a new solution.



sanderz -> RE: 4.0.1.15 Public Beta Update (11/25/2017 7:29:00 AM)


quote:

ORIGINAL: Tamas

I'll copy my reply from there here as well, then. [:)]

The plan is that we will include scenario updates (hopefully new scenarios as well) in patches, yes.

We are also looking into how best to facilitate the uploading and downloading of scenarios, to make it as user friendly as possible. But please do use this forum for that in the meantime, we will give everyone a heads-up well in advance once we start implementing a new solution.

thank you - thats great news

any comments on the bit about old/wrong values being in old scenarios and whether they will be fixed on import?



Tamas -> RE: 4.0.1.15 Public Beta Update (11/25/2017 7:32:40 AM)

The only generally problematic old value we have found is the naval attrition divider you quoted above, and that is only problematic in the context of previous designers setting up scenarios unaware of the updated naval rules in TOAW4. We have manually changed this in what we believed to be all scenarios affected by it, but clearly Torch was left out.

I think it would be a bad idea to force a naval attrition value on saving a scenario, as that would remove one of the new tools that's available for designers.



sanderz -> RE: 4.0.1.15 Public Beta Update (11/25/2017 5:23:23 PM)


quote:

ORIGINAL: Tamas

I think it would be a bad idea to force a naval attrition value on saving a scenario, as that would remove one of the new tools that's available for designers.


I was thinking more of "converting" the variable rather than forcing a value - after all it is an editable field. The way it seems at the moment is that any scenario not converted by you is very likely broken in respect to any ship combat.

If we edit the scenario ourselves would it be fair to say a value of 100 would "always be reasonable" or is it so variable that this just wouldn't work?



sPzAbt653 -> RE: 4.0.1.15 Public Beta Update (11/25/2017 5:27:47 PM)

Ok, now I'll copy my reply from another thread !


quote:

So every scenario should have a value of say "100"?

The Naval Attrition Divider is used just as the Attrition Divider. Players need not be concerned with either, they are parameters for the scenario designers. Importing pre-TOAW IV scenarios to TOAW IV and 'saving as' never changes scenario parameters, it updates to the IV game engine.

If you really want to know more about Attrition Dividers [and again, as a player you do not need to know], go here first, then see the paragraph below taken from the What's New:
http://www.matrixgames.com/forums/tm.asp?m=3045873

Naval Attrition Divider: This is the same as the normal Attrition Divider, but applies to naval combat only. The normal Attrition Divider does not affect naval combat. A setting of 10 is neutral. A setting of 5 doubles shots. A setting of 20 halves shots, etc. Note that it also scales naval combat supply costs. See Appendix I.




sanderz -> RE: 4.0.1.15 Public Beta Update (11/25/2017 6:20:59 PM)

I'm confused why you post this (see bit in bold) - pretty sure i don't even know enough to ask the right questions but here goes..

quote:

ORIGINAL: sPzAbt653
The Naval Attrition Divider is used just as the Attrition Divider. Players need not be concerned with either, they are parameters for the scenario designers. Importing pre-TOAW IV scenarios to TOAW IV and 'saving as' never changes scenario parameters, it updates to the IV game engine.


But then post this about fixing a scenario that was not updated..

quote:

ORIGINAL: sPzAbt653
By accident, the release version of this scenario was not updated to handle the changed naval circumstances better, resulting in too high casualties to coastal fortress gun fire.


All i'm asking about is old scenarios NOT included with the game that we import ourselves i.e. won't they all need the Naval Attrition Divider changed or you end up getting the same problems as you had with Operation Torch??




Te55 -> RE: 4.0.1.15 Public Beta Update (11/25/2017 7:05:17 PM)

I've just installed the public beta and then spent a while playing around with the graphics scaling and font sizes. Between the two I've now got the game set-up so that I don't have to change resolution or desktop scaling using the Windows display settings - excellent result! Out of interest I'm playing on a Surface Pro with desktop resolution set to 2736 x 1824.

However, may I be awkward by saying that the same scaling fix needs to be added to the scenario editor. At the moment all the buttons in the editor are very small and difficult to use. Is there any chance of applying the same fix to the editor please?



sPzAbt653 -> RE: 4.0.1.15 Public Beta Update (11/25/2017 11:07:17 PM)

quote:

All i'm asking about is old scenarios NOT included with the game that we import ourselves i.e. won't they all need the Naval Attrition Divider changed

Of course not, there are different scales, which is why there is a Divider.



ralphtricky -> RE: 4.0.1.15 Public Beta Update (11/26/2017 1:12:36 AM)


quote:

ORIGINAL: Te55

I've just installed the public beta and then spent a while playing around with the graphics scaling and font sizes. Between the two I've now got the game set-up so that I don't have to change resolution or desktop scaling using the Windows display settings - excellent result! Out of interest I'm playing on a Surface Pro with desktop resolution set to 2736 x 1824.

However, may I be awkward by saying that the same scaling fix needs to be added to the scenario editor. At the moment all the buttons in the editor are very small and difficult to use. Is there any chance of applying the same fix to the editor please?

Thanks! I'm glad to hear it worked.

I can take a look, but the editor is all 'Old Code' so answer will almost certainly be 'not soon.' You'll have to use the other method of setting the overall screen resolution.

The new stuff is completely object based and when objects resize those dialog rearranges them around the new dimensions. I only had to add a flag and some behaviors and mark the components that should scale in the new code. The old code individually places each pixel and checks for mouse clicks by absolute screen locations. I might try and see if I can just change the whole screen resolution (like Y does) and mouse clicks, but it will make things fuzzy and it's going to be a while before I can try that.

Since you've got a Surface Pro, did you know the game is touch enabled. Set MenuDelay to 1 and you have to hold the finger down instead to get the right click menu to pop up. Dragging and even pinching should work fine. I play that way sometimes.



Phoenix100 -> RE: 4.0.1.15 Public Beta Update (11/26/2017 8:20:29 AM)

This beta works wonders with scrolling. I never had any probs with small to medium scenarios but big ones like the entire war scenarios in the WW2 misc folder just wouldn't work at all. Now they function. Good job.



Page: [1] 2 3   next >   >>

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
2.21875