4.0.1.23 Public Beta Update
RE: 4.0.1.15 Public Beta Update
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.
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.
RE: 4.0.1.15 Public Beta Update
thank you - thats great newsORIGINAL: 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.
any comments on the bit about old/wrong values being in old scenarios and whether they will be fixed on import?
RE: 4.0.1.15 Public Beta Update
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.
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.
RE: 4.0.1.15 Public Beta Update
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?
RE: 4.0.1.15 Public Beta Update
Ok, now I'll copy my reply from another thread !
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:
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.
[/quote]
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.So every scenario should have a value of say "100"?
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:
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.
[/quote]
RE: 4.0.1.15 Public Beta Update
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..
But then post this about fixing a scenario that was not updated..
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??
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..
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??
RE: 4.0.1.15 Public Beta Update
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?
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?
RE: 4.0.1.15 Public Beta Update
Of course not, there are different scales, which is why there is a Divider.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
- ralphtricky
- Posts: 6675
- Joined: Sun Jul 27, 2003 4:05 am
- Location: Colorado Springs
- Contact:
RE: 4.0.1.15 Public Beta Update
Thanks! I'm glad to hear it worked.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?
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.
Ralph Trickey
TOAW IV Programmer
Blog: http://operationalwarfare.com
---
My comments are my own, and do not represent the views of any other person or entity. Nothing that I say should be construed in any way as a promise of anything.
TOAW IV Programmer
Blog: http://operationalwarfare.com
---
My comments are my own, and do not represent the views of any other person or entity. Nothing that I say should be construed in any way as a promise of anything.
-
- Posts: 2949
- Joined: Tue Sep 28, 2010 12:26 pm
RE: 4.0.1.15 Public Beta Update
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.
RE: 4.0.1.15 Public Beta Update
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?
Which buttons did you use for this? Thanks.
Jim Cobb
RE: 4.0.1.15 Public Beta Update
Really nice that the F1 key opens the manual.
RE: 4.0.1.15 Public Beta Update
The only files you need to copy are the OPART4 and the OPART4-slow files, correct?
Tony
-
- Posts: 4915
- Joined: Sun Feb 10, 2008 7:37 pm
- Location: Germany
- Contact:
RE: 4.0.1.15 Public Beta Update
ORIGINAL: Oberst_Klink
the .MAP, too.ORIGINAL: Toby42
The only files you need to copy are the OPART4 and the OPART4-slow files, correct?
Klink, Oberst
Ralph Trickey said that the .map files were de-bugging files and not needed? I can copy them too?
Tony
-
- Posts: 4915
- Joined: Sun Feb 10, 2008 7:37 pm
- Location: Germany
- Contact:
RE: 4.0.1.15 Public Beta Update
ORIGINAL: Oberst_Klink
I always dumped them into the directory. Didn't do any harm.
OT: How did a Manx end up in Gatorland?
Klink, Oberst
I had to look this up. The Isle of Mann flag is very much like the Sicilian flag (triskelion ). So I'm not a Manx but an American of Sicilian ancestry! I moved to Gator land to get away from Winters in Ohio!
Tony
-
- Posts: 4915
- Joined: Sun Feb 10, 2008 7:37 pm
- Location: Germany
- Contact:
RE: 4.0.1.15 Public Beta Update
A Buckeye Don Corleone who moved to GatorlandORIGINAL: Toby42
ORIGINAL: Oberst_Klink
I always dumped them into the directory. Didn't do any harm.
OT: How did a Manx end up in Gatorland?
Klink, Oberst
I had to look this up. The Isle of Mann flag is very much like the Sicilian flag (triskelion ). So I'm not a Manx but an American of Sicilian ancestry! I moved to Gator land to get away from Winters in Ohio!


Klink, Oberst
RE: 4.0.1.15 Public Beta Update
ORIGINAL: Oberst_Klink
A Buckeye Don Corleone who moved to GatorlandORIGINAL: Toby42
ORIGINAL: Oberst_Klink
I always dumped them into the directory. Didn't do any harm.
OT: How did a Manx end up in Gatorland?
Klink, Oberst
I had to look this up. The Isle of Mann flag is very much like the Sicilian flag (triskelion ). So I'm not a Manx but an American of Sicilian ancestry! I moved to Gator land to get away from Winters in Ohio!Oh well... Too hot for me (and I've been to NC and SC)... even in WV during Jul/Aug it is too hot... alas, there I was only 'threatened' by snappy turtles, potential copperheads, timber rattlers... BUT no cottonmouth or gators
Klink, Oberst
We live in North Central Florida. It does get hot in August, but Winters are great! 55 in the morning and 80 in the afternoon. Low humidity also...
And you are doing an excellent job with the tutorials! [&o]
Tony
RE: 4.0.1.15 Public Beta Update
ORIGINAL: Toby42
ORIGINAL: Oberst_Klink
I always dumped them into the directory. Didn't do any harm.
OT: How did a Manx end up in Gatorland?
Klink, Oberst
I had to look this up. The Isle of Mann flag is very much like the Sicilian flag (triskelion ). So I'm not a Manx but an American of Sicilian ancestry! I moved to Gator land to get away from Winters in Ohio!
Hi Tony, baciamo le mani! [;)]