RE: The most frustrating feature of TOAW engine

RE: The most frustrating feature of TOAW engine (Full Version)

All Forums >> [Current Games From Matrix.] >> [World War II] >> Norm Koger's The Operational Art Of War III

Message

Fidel_Helms -> RE: The most frustrating feature of TOAW engine (10/26/2005 7:35:54 AM)
quote: ORIGINAL: JAMiAM Of course, if you're concerned about high-proficiency units causing turn burn due to staying in the battle too long, you could do the smart thing and break them down into thirds, to get the 20% drop in proficiency. Use the unit in a minimize loss tolerance attack, so that it doesn't stay in too long. Then recombine it for your own defense, or for consolidating the unit for exploitation RBC's. I have my doubts about this. First, you end up with a unit that is either half or a third as large as the parent unit. If the base unit for each side is a division, you're now sending brigades or regiments against enemy divisions. These are going to make better progress? Additionally, the manual says that formations with lots of subdivided units are more likely to go into reorg- so you may actually adversely affect the performance of the entire formation(if that's true).

JAMiAM -> RE: The most frustrating feature of TOAW engine (10/26/2005 7:49:02 AM)
Play more, talk less, try things in ways that you haven't done before, and see for yourself what works. You can believe me, or not. It's your choice. My play record, tells me what works, and what doesn't.

Fidel_Helms -> RE: The most frustrating feature of TOAW engine (10/26/2005 8:40:05 AM)
quote: ORIGINAL: JAMiAM Play more, talk less, try things in ways that you haven't done before, and see for yourself what works. I play plenty- but the sort of play I do is different from ladder play. Generally I don't subdivide units because it's typically not a good idea. It's been tried in Fall Grau, the scenario I'm mentally referencing most often in this discussion, and it didn't work so well. At any rate, even if there are kludges that allow imperfect means of bypassing the effects, it's still a flaw in the game. What general ever reorganized his units to make them less effective?

JAMiAM -> RE: The most frustrating feature of TOAW engine (10/26/2005 9:11:42 AM)
My apologies for my tone tonight. I should know not to post when I'm tired and in a rotten mood. As to your final question, what I am suggesting is to reorganize your units (and methods) to make them more effective, not less. You, and others in this thread, are portraying high proficiency units as turn burners. I merely showed you how to avoid that result. If you want to bring up some other possible by-product of the technique, then IMO, you are simply arguing for the sake of argument, since neither of your objections in post #181 are directly relevent to the method I described. To think that I was advocating only attacking with the broken down units is silly. I was referring to only those units which you seem to have a problem employing otherwise. Likewise, to bring up the manual case of formational reorg is beside the point. My example suggests to recombine the forces whenever possible, before your turn end. Formational reorg is checked during the ABP, and in my experience has been more a function of total losses throughout the formation, than the number of sub-divided units in it. TOAW has room for improvement, to be sure. However, in this particular issue - the use of high proficiency units - the problem lies with players not understanding how to optimize the usage of their forces, and not with the game engine.

ColinWright -> RE: The most frustrating feature of TOAW engine (10/26/2005 10:29:11 AM)
quote: ORIGINAL: Lava quote: ORIGINAL: ColinWright Let me try this one more time. It's my turn. At one end of the front, I have my hugely important attack to take whatever. Half my army is going to break through, and then if I get a second round, I can advance to capture the game-winning hex. At the other end of the front, I have an opportunity to make a low-odds attack that I think will consume many rounds even at 'minimize losses' to take a point of minor value. What should I do? Your kidding me right? From an operational level, planning and execution would focus almost exclusively on the main attack. This is the really world, and how staffs function. Have you ever served on a high level staff? quote: ORIGINAL: ColinWright In TOAW, I don't make the low odds attack -- of course not. I'm not stupid. In real life? Those guys can go knock themselves out -- it won't affect the big attack. Really? So you are trying to say that a "minor" level operation would get the green light when the fate of the war (the example you made) is at stake? Hardly. I'm actually a little baffled here. Are you making a large attack with your forces ordered to "ignore losses" and you think that the logistical, planning and execution of such an attack would not effect operations in other sectors or even theaters? What may I ask do you base your "real life" judgements on? Ray (alias Lava) This isn't worth responding to.

ColinWright -> RE: The most frustrating feature of TOAW engine (10/26/2005 10:31:28 AM)
quote: ORIGINAL: Oleg Mastruko Oh don't even get me started on proficiency values given by various scenario designers!!! [:@] Couple pages ago in this thread Golden Delicious (is his real name Ben Turner?) rhetorically aksed why I stopped playing TOAW - then continued to make a point that most players stopped playing the game because of various "flaws" in the system, and if those flaws would be corrected, those disappointed players will be returning to the game. Some wishful thinking Im afraid... Anyway, perhaps the biggest reason why I stopped playing the game, were not "flaws" in the engine. I can't remember a single flaw or bug that really put me off TOAW. Some PBEM security related issues got on my nerves but that's beyond the scope of this discussion. I stopped playing because in growing number of scenarios there were less and less good, realistic and playable ones. Scenarios like McBride's Tobruk and El Alamein (and Wintergewitter, which was mysteriously pulled down from the web) raised the bar considerably. Laugahble scenarios, based around ridicolously faulty OOBs, bad maps, bad scales, etc etc. flooded the scenario depots, and after I played every of 20 or so really excellent ones, I simply pulled the plug on the game. Perhaps I managed to miss couple great scenarios, but having to sift thru tons of garbage to find good scenario, simply got too time consuming. No deadly flaws for me sorry to disappoint you... [;)] From TOAW ME I want more good scenarios, firmly anchored within confines of operational art if possible. Hire McBride, make him do dozen or so scenarios, include the latest patch, tutorials for new players, cuple smaller improvements (realistically achievable in relatively short development time), better PBEM security if possible, and you have a winner... O. Your criterion of what is 'good' speaks for itself.

ColinWright -> RE: The most frustrating feature of TOAW engine (10/26/2005 10:33:31 AM)
quote: ORIGINAL: Oleg Mastruko quote: ORIGINAL: Fidel_Helms Try some of the TDG scenarios. The current featured scenario, Campaign for South Vietnam, is particularly good. Jarek's Lodz is good too. Jarek has some other stuff in the pipeline, and he pretty much exclusively designs small scenarios on more "obscure" subjects. I find them a refreshing alternative to Daniel McBride's scenarios, which I do not enjoy. I do wish we had a few more scenarios up- but to a large extent, doing that while still retaining quality would be at cross purposes. Must... keep.... mouth... shut... [:D] Anyway why don't you like McBride's scenarios? I think I loved one scenario from you, or was it Colin? Small, short and fun, obscure topic - Ecuador vs. Peru. It's either Colin's scenario which I played vs you, or your scenario and I played it vs Colin. O. It couldn't be either one. I've never played you, and I've never designed such a scenario. That rules out both possibilities. At least it does for me. I wouldn't be excessively surprised if you continue to insist one of the two must have been the case.

ColinWright -> RE: The most frustrating feature of TOAW engine (10/26/2005 10:41:59 AM)
quote: ORIGINAL: JAMiAM My apologies for my tone tonight. I should know not to post when I'm tired and in a rotten mood. As to your final question, what I am suggesting is to reorganize your units (and methods) to make them more effective, not less. You, and others in this thread, are portraying high proficiency units as turn burners. I merely showed you how to avoid that result. If you want to bring up some other possible by-product of the technique, then IMO, you are simply arguing for the sake of argument, since neither of your objections in post #181 are directly relevent to the method I described. To think that I was advocating only attacking with the broken down units is silly. I was referring to only those units which you seem to have a problem employing otherwise. Likewise, to bring up the manual case of formational reorg is beside the point. My example suggests to recombine the forces whenever possible, before your turn end. Formational reorg is checked during the ABP, and in my experience has been more a function of total losses throughout the formation, than the number of sub-divided units in it. TOAW has room for improvement, to be sure. However, in this particular issue - the use of high proficiency units - the problem lies with players not understanding how to optimize the usage of their forces, and not with the game engine. Still. One wants SS Leibstandarte to be better man for man that Infantrie 326, right? Now, if the 326th has 75% proficiency and SSLAH has 90% proficiency, you'll find that you're begging for early turn ending if you use SSLAH in any attacks that aren't gimmes. So you break it down. Now it's only 72% proficiency; in other words worse than the 326th. The solution is just to scale down all the proficiencies. Go into the editor and drop all unit proficiencies for both forces by 10%. Now SSLAH is 80% and the 326th is 65%. No problem. The proficiency thing is a red herring. It only came up because Oleg tried to argue that this wasn't the reason early turn ending was a problem in DitN.

ColinWright -> RE: The most frustrating feature of TOAW engine (10/26/2005 10:52:21 AM)
Can't delete this, apparently, and it contains additions. quote: ORIGINAL: JAMiAM My apologies for my tone tonight. I should know not to post when I'm tired and in a rotten mood. As to your final question, what I am suggesting is to reorganize your units (and methods) to make them more effective, not less. You, and others in this thread, are portraying high proficiency units as turn burners. I merely showed you how to avoid that result. If you want to bring up some other possible by-product of the technique, then IMO, you are simply arguing for the sake of argument, since neither of your objections in post #181 are directly relevent to the method I described. To think that I was advocating only attacking with the broken down units is silly. I was referring to only those units which you seem to have a problem employing otherwise. Likewise, to bring up the manual case of formational reorg is beside the point. My example suggests to recombine the forces whenever possible, before your turn end. Formational reorg is checked during the ABP, and in my experience has been more a function of total losses throughout the formation, than the number of sub-divided units in it. TOAW has room for improvement, to be sure. However, in this particular issue - the use of high proficiency units - the problem lies with players not understanding how to optimize the usage of their forces, and not with the game engine. Still. One wants SS Leibstandarte to be better man for man that Infantrie 326, right? Now, if the 326th has 75% proficiency and SSLAH has 90% proficiency, you'll find that you're begging for early turn ending if you use SSLAH in any attacks that aren't gimmes. So you break it down. Now it's only 72% proficiency; in other words worse than the 326th. The solution is just to scale down all the proficiencies. Go into the editor and drop all unit proficiencies for both forces by 10%. Now SSLAH is 80% and the 326th is 65%. No problem. I think people get hung up on those 'suggested' values Norm gave. 'If the average German division is supposed to be 75% percent proficiency, then I want the panzers to be 85% -- and so SSLAH has to be 95%.' Just drop everybody until the top unit is 80-85%. If your beloved German infantry are now an unimpressive 65%, learn to live with it. Take consolation in what you lowered their opponents to. Anyway, the proficiency thing is a red herring. It only came up because Oleg tried to argue that this wasn't the reason early turn ending was a problem in DitN.

JMS2 -> RE: The most frustrating feature of TOAW engine (10/26/2005 11:21:42 AM)
quote: ORIGINAL: Lava quote: ORIGINAL: JMS2 Simplicity is not going to wash with the core gamers that are likely to be the bulk of TOAW buyers, so in the end, yes, profits are a problem for Matrix, because if the product is not up to scratch, nobody's going to fall for it. Hi! No, I think you guys are all missing my point. I am not arguing for simplicity, what I am basically trying to say is to try to broaden the appeal of the game by including more scenarios and using some imagination. But my basic complaint is, when you look at the TOAW section of the forums and you see the biggest thread on it having a conversation about how the game is "broken", it doesn't lend itself too favorably to people who have never played the game. So, unlike you, I do believe that it not only depends on the product, but what the players have to say about it. And if the impression you are giving people is that it is broken, then you are doing Matrix and TOAW a disservice. Just take a look at some of the subject lines in this section of the forum... you'd think the game was a complete disaster needing a total overhaul. [:-] Ray (alias Lava) But Ray you are looking at just one forum, and one only recently dedicated to TOAW at that, opened because Matrix is going to update TOAW. What did you expect? a forum with only the good parts? a forum on how to design scenarios or how to play the game? those already exists, check http://www.strategyzoneonline.com/forums/forumdisplay.php?f=10 or http://www.tdg.nu/cgi-bin/yabb2/YaBB.pl where for years TOAW has been discussed, many times quite vehemently. On Matrix I expect subjects relating to improvements to TOAW.

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 12:15:33 PM)
quote: ORIGINAL: Oleg Mastruko As for including Finnish front in Northern Barbarossa - that may work. But obviously, you need to do something to balance things somewhat. Say, McBride in his DNO used Regiments as basic German unit, and "amalgamated" Finns into divisions. Thus you get balanced units. .... no. Daniel has regiments of Finns also. This scenario suffers a lot from the problem we're discussing, actually. Anyway, if you like Daniel's design so much, how do you feel about his infantry battalions in West Africa in his Great War Scenario? Should he make them divisions? Would that be better design. I don't think so. quote: and divided up his beloved Finns into smallest possible units ever, so the northern part of the map is full of "1-1" "ants" milling around Arctic doing funny things. In the arctic, a ski battalion is a significant unit.

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 12:40:23 PM)
quote: ORIGINAL: Oleg Mastruko it was stopped because of game mechanics. As it should be. One could use this argument to justify a lot of things. Remember how with Volume I the AT algorithyms made it possible for Jeeps to knock out Tiger IIs? Well, the Tiger II wasn't knocked out by the Jeep. It was knocked out because of game mechanics, "As it should be". A major change made to the original design, btw, because the players wanted it. Obviously, Norm's vision can be improved upon.

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 12:47:50 PM)
quote: ORIGINAL: Lava From an operational level, planning and execution would focus almost exclusively on the main attack. This is the really world, and how staffs function. The other attack would still go ahead. Are you saying that it wouldn't? quote: Have you ever served on a high level staff? Are you going to tell me that you have? If we're going to talk about staff planning, that big offensive needed to be planned out in some detail a couple of weeks in advance. Of course in TOAW you can just muddle through. quote: Really? So you are trying to say that a "minor" level operation would get the green light when the fate of the war (the example you made) is at stake? Hardly. Mm. Actually, it's common practice to keep up low level operations on secondary parts of the front to keep the enemy guessing as to your intentions. So your argument is nonsense. Three real world examples; a) Patton kept on fighting throughout 'Market Garden'. This wouldn't happen in TOAW. b) In 1942-3 The Russians kept hammering away at the German line opposite Moscow even after they had switched their emphasis to the South. This wouldn't happen in TOAW. c) In Poland, the Germans started up probing attacks against Warszawa whilst they were still exploiting their breakthroughs to the east and south. This wouldn't happen in TOAW. There are dozens more. You're really seriously wrong.

*Lava* -> RE: The most frustrating feature of TOAW engine (10/26/2005 12:49:28 PM)
quote: ORIGINAL: ColinWright quote: ORIGINAL: Lava quote: ORIGINAL: ColinWright Let me try this one more time. It's my turn. At one end of the front, I have my hugely important attack to take whatever. Half my army is going to break through, and then if I get a second round, I can advance to capture the game-winning hex. At the other end of the front, I have an opportunity to make a low-odds attack that I think will consume many rounds even at 'minimize losses' to take a point of minor value. What should I do? Your kidding me right? From an operational level, planning and execution would focus almost exclusively on the main attack. This is the really world, and how staffs function. Have you ever served on a high level staff? quote: ORIGINAL: ColinWright In TOAW, I don't make the low odds attack -- of course not. I'm not stupid. In real life? Those guys can go knock themselves out -- it won't affect the big attack. Really? So you are trying to say that a "minor" level operation would get the green light when the fate of the war (the example you made) is at stake? Hardly. I'm actually a little baffled here. Are you making a large attack with your forces ordered to "ignore losses" and you think that the logistical, planning and execution of such an attack would not effect operations in other sectors or even theaters? What may I ask do you base your "real life" judgements on? Ray (alias Lava) This isn't worth responding to. The TOAW "God" has spoken. [&o] Wow man, you really do have an attitude. Just what TOAW needs, and just what I have been saying over and over again. You guys walze in here, thinking now were going to have the game made the way "WE" want it, and if "we" don't get what "we" want, "we" will tell the world how crap the game is. I don't call that being a "grog", I call that being destructive. And that kind of destructive, almost suicidal, attitude has become synonomous with "grogs" and wargames. Good wargames are few and far apart, and thanks to "destructive grogs" they are becoming an endangered species. Ray (alias Lava)

Oleg Mastruko -> RE: The most frustrating feature of TOAW engine (10/26/2005 12:54:59 PM)
quote: ORIGINAL: ColinWright It couldn't be either one. I've never played you, and I've never designed such a scenario. That rules out both possibilities. At least it does for me. I wouldn't be excessively surprised if you continue to insist one of the two must have been the case. What is wrong with you? Take a chill pill dude...

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 12:58:31 PM)
quote: ORIGINAL: Oleg Mastruko Some PBEM security related issues got on my nerves but that's beyond the scope of this discussion. You should start a thread. Actually, these issues only matter if you don't trust your opponent. quote: Scenarios like McBride's Tobruk and El Alamein (and Wintergewitter, which was mysteriously pulled down from the web) raised the bar considerably. Interestingly, McBride's scenarios are some of the ones which suffer most from early turn ending, which you attribute to bad design, because they are so large. quote: From TOAW ME I want more good scenarios, Then let Matrix make a better TOAW.

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 1:03:44 PM)
quote: ORIGINAL: JAMiAM Of course, if you're concerned about high-proficiency units causing turn burn due to staying in the battle too long, you could do the smart thing and break them down into thirds, to get the 20% drop in proficiency. Use the unit in a minimize loss tolerance attack, so that it doesn't stay in too long. Then recombine it for your own defense, or for consolidating the unit for exploitation RBC's. Right. But we're not talking about how to play well here, are we? Let's look at this. Your 100% proficiency unit is going to be some monster SS division or something- and you're going to split it up into three bits to use seperately? This isn't realistic- not in the least. The fact that it's good play is neither here nor there. I'm not interested in discussing how to win at TOAW. I'm interested in discussing how to make a good simulation. quote: (through ignorance, or some mistaken ideal of what constitutes "realism" in an operational simulation) This bothers me. You're at the top of the WHQ ladder- so obviously the game must be a realistic simulation. Actually, I disagree. You'd probably be a top-rated player regardless of what the game mechanics are- but the fact that you've figured out how to work the game does not mean the simulation is perfect.

Oleg Mastruko -> RE: The most frustrating feature of TOAW engine (10/26/2005 1:03:58 PM)
quote: ORIGINAL: golden delicious quote: ORIGINAL: Oleg Mastruko Some PBEM security related issues got on my nerves but that's beyond the scope of this discussion. You should start a thread. Actually, these issues only matter if you don't trust your opponent. Yeah, like guys in this thread? [:D] I see this thread is bursting at the seams from all this mutual trust and goodwill [8\|] quote: Interestingly, McBride's scenarios are some of the ones which suffer most from early turn ending, which you attribute to bad design, because they are so large. They work fine for me. Wait... can it be because THE WHOLE GAME WORKS FINE FOR ME??? LOL [:D] Oleg

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 1:05:45 PM)
quote: ORIGINAL: Fidel_Helms I have my doubts about this. First, you end up with a unit that is either half or a third as large as the parent unit. If the base unit for each side is a division, you're now sending brigades or regiments against enemy divisions. These are going to make better progress? Additionally, the manual says that formations with lots of subdivided units are more likely to go into reorg- so you may actually adversely affect the performance of the entire formation(if that's true). Mm. When JAMiAM says something will work in the game, I believe him. He's thought a lot about this. However, the point here is to figure out how to change the system so he'll have to relearn it [:D]

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 1:24:32 PM)
quote: ORIGINAL: Lava You guys walze in here, thinking now were going to have the game made the way "WE" want it, and if "we" don't get what "we" want, "we" will tell the world how crap the game is. Well, we already have TOAW. We're guaranteed a release of TOAW volume 1.07. You seem to be content to accept what we've already been promised. That's not good enough. I want MORE. You're the one who's being destructive- destructive of the possibility of improving TOAW. quote: Good wargames are few and far apart, Right. We've got one in TOAW. You're telling us that a) it is not to be improved b) it's actually to be made less of a wargame so that more people will want to play it. Can't you go onto the Battlegrounds forum or something and ruin their game? I quite like this one.

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 1:37:04 PM)
quote: ORIGINAL: Oleg Mastruko Yeah, like guys in this thread? [:D] I see this thread is bursting at the seams from all this mutual trust and goodwill [8\|] I might disagree with you but I don't think you'd cheat at TOAW. Hardly anyone does. I suppose I could be wrong. quote: They work fine for me. Wait... can it be because THE WHOLE GAME WORKS FINE FOR ME??? Now who needs to chill? Anyway, you just said that you don't like the way DitN works, because of a problem which you attribute to bad design, which is even more acute in games like Drang Nach Osten. In my view, you can either see DitN and DNO as both good designs, or both bad designs, in the light of the above. In my view, they're both pretty good compared to the average, though could do with some improvement.

*Lava* -> RE: The most frustrating feature of TOAW engine (10/26/2005 1:40:50 PM)
quote: ORIGINAL: golden delicious quote: ORIGINAL: Lava From an operational level, planning and execution would focus almost exclusively on the main attack. This is the really world, and how staffs function. The other attack would still go ahead. Are you saying that it wouldn't? Operationally, I'm saying the other attack is insignificant and should be treated that way. If, however, you are willing to risk supporting other operations which detract from your main operational goal, then don't be surprised if you fail to achieve it. I personal believe TOAW does a fairly good simulation of operational level warfare. quote: ORIGINAL: golden delicious quote: ORIGINAL: Lava Have you ever served on a high level staff? Are you going to tell me that you have? If we're going to talk about staff planning, that big offensive needed to be planned out in some detail a couple of weeks in advance. Of course in TOAW you can just muddle through. Yes, I am going to tell you I have served on operational staff and have participated in military "wargames" up to the strategic level. Muddling through doesn't sound very "grog-like" to me. If you put together a major offensive in TOAW the computer will treat it that way and you will see the results of that offensive with multiple attacks. If the turn ends "early", possibly your muddling wasn't up to operational level thinking. quote: ORIGINAL: golden delicious quote: ORIGINAL: Lava Really? So you are trying to say that a "minor" level operation would get the green light when the fate of the war (the example you made) is at stake? Hardly. Mm. Actually, it's common practice to keep up low level operations on secondary parts of the front to keep the enemy guessing as to your intentions. So your argument is nonsense. Nice statement. I'm not making an argument, I'm basing my statements on real world experience, and I do so in a curtious manner. Before the operation begins, yes. Once the operational plan enters the execution phase, however, all activities that do not support the effort become insignificant. Believe it or not, in the real world, you don't get to move all your counters at once. [;)] Sounds to me like you guys want to "game" the system. The conversation has already brought up other "gamey" aspects which people "appear" to believe are "real." The 100% proficiency aspect, for example. Here's the real world. I was once in a attack squadron which won the "The Battle E" (efficiency) Award" and "The McClusky Award" for the best attack squadron in the Navy (24 at that time). I can assure you we were never close to 100% proficiency. Ray (alias Lava)

*Lava* -> RE: The most frustrating feature of TOAW engine (10/26/2005 1:51:44 PM)
quote: ORIGINAL: golden delicious Well, we already have TOAW. We're guaranteed a release of TOAW volume 1.07. You seem to be content to accept what we've already been promised. That's not good enough. I want MORE. You're the one who's being destructive- destructive of the possibility of improving TOAW. Please... Unlike Colin I'm not the one starting threads with subjects like "A nightmere scenario." I've seen this kind of stuff over and over again. The old grogs start spewing their, "this is unrealistic" crap, pressuring the developer to cater to them and resulting in a patch that totally quarks the game. Talk about a nightmere scenario.... Ray (alias Lava)

sstevens06 -> RE: The most frustrating feature of TOAW engine (10/26/2005 3:15:39 PM)
quote: ORIGINAL: Fidel_Helms quote: ORIGINAL: sstevens06 I think this is a key point Oleg is making - a number of scenarios, including some on the original CD, seem to ignore this. In the example of the 1973 Arab-Israeli war, it simply doesn't make sense to simulate both the Golan Heights and Suez Canal fronts on the same map in the same scenario... Ironically, Norm designed two scenarios which did exactly that. Do you think they're any good?

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 3:16:54 PM)
quote: ORIGINAL: Lava Operationally, I'm saying the other attack is insignificant and should be treated that way. It will happen though. If it's not happening in the model then the model is wrong. quote: I personal believe TOAW does a fairly good simulation of operational level warfare. Absolutely. The best one which is commercially available. That's why I think we (you, me, everyone) should strive to make it even better. quote: Muddling through doesn't sound very "grog-like" to me. If you put together a major offensive in TOAW the computer will treat it that way and you will see the results of that offensive with multiple attacks. If the turn ends "early", possibly your muddling wasn't up to operational level thinking. .... the thing is, the player doesn't represent your operational-level staff. It represents some non-existant entity which has control over every regiment on the Eastern Front, or whatever. I discussed this sort of thing in my BA dissertation. If we were to get really serious about wargaming, the player's view and powers would be restricted to that of his historical counterpart, and the AI would take control of the various corps and divisions. However, that would make it no longer much of a game and more of an exercise in military history. I don't want to do that. FWIW, I do plan my offensives. And I don't launch that marginal attack. That's not realistic though. Given that, in game terms, I am both the high level and the intermediate level staffs (including the corps' which is doing nothing else except launching this marginal attack), it doesn't make any sense for the attack not to go in. quote: Before the operation begins, yes. Once the operational plan enters the execution phase, however, all activities that do not support the effort become insignificant. Believe it or not, in the real world, you don't get to move all your counters at once. [;)] Look at it in terms of the examples I was giving you. Take Poland. 14th Army is making this drive on Lvov. XIX Panzerkorps is driving on Brest. These operations are the main focus of their respective army groups (Nord and Sud) and of OKH, because the intention of OKH is to cut off any Polish forces remaining in Eastern Poland. However, they are not the concern of 10th Army's headquarters. 10th Army's headquarters is interested in probing the defenses of Warszawa, and they will do that. Are you seriously suggesting that 10th Army's operations would come to a halt because their parent organisation had their focus elsewhere? Thing is, you're only looking at this from OKH's perspective. That doesn't help, though, because the player isn't OKH. He's some wierd amalgamation of OKH and all the subordinate HQs.

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 3:33:25 PM)
quote: ORIGINAL: Lava Unlike Colin I'm not the one starting threads with subjects like "A nightmere scenario." Colin had a specific and very serious concern, which was addressed by a Matrix employee. The thread has since not seen any activity. I don't see how this is destructive. quote: The old grogs start spewing their, "this is unrealistic" crap, pressuring the developer to cater to them and resulting in a patch that totally quarks the game. Since you like TOAW as it is already, and TOAW as it is already will still exist, I don't see what the problem is. Your stated desire is to see more scenarios. I suspect you have this idea that Matrix could pay designers for their work and then publish the scenarios. That won't work. Given the small size of the market, a scenario designer can never make a significant amount of money from such a deal. The way to encourage designers to make scenarios (speaking as a designer) is to give them tools which they want to use. TOAW scenario designers only do so because they enjoy it.

*Lava* -> RE: The most frustrating feature of TOAW engine (10/26/2005 3:33:34 PM)
quote: ORIGINAL: golden delicious Thing is, you're only looking at this from OKH's perspective. True enough, but then again, that's how I "perceive" the game was designed. At the army level, you can only do so much. You are constrained by things like time, logistics and intelligence. I understand what you guys want and believe, but I perfer the "operational" constraints placed on me by the game rather than try to simulate "some wierd amalgamation of OKH and all the subordinate HQs." When I play, I AM OKH. And the subordinate HQ's follow my orders. That is what I believe the game was intended to do. Ray (alias Lava)

Fidel_Helms -> RE: The most frustrating feature of TOAW engine (10/26/2005 3:42:12 PM)
quote: ORIGINAL: JAMiAM My example suggests to recombine the forces whenever possible, before your turn end. Formational reorg is checked during the ABP, and in my experience has been more a function of total losses throughout the formation, than the number of sub-divided units in it. Alright, I've misunderstood you then. This would work. Going back to my original point, it is still counterintuitive that a lower proficiency unit would be more useful in game terms than a higher proficiency unit. quote: TOAW has room for improvement, to be sure. However, in this particular issue - the use of high proficiency units - the problem lies with players not understanding how to optimize the usage of their forces, and not with the game engine. I would hold it up as an engine flaw because the optimization technique you mention has little to do with reality. I would like to see as much symmetry as possible between TOAW and the real world. A player should be able to make decisions based on real world criteria. Whenever your thinking strays from that and into what makes sense in terms of the game engine, you've probably hit on an area which could be improved.

golden delicious -> RE: The most frustrating feature of TOAW engine (10/26/2005 3:43:19 PM)
quote: ORIGINAL: Lava True enough, but then again, that's how I "perceive" the game was designed. At the army level, you can only do so much. You are constrained by things like time, logistics and intelligence. Right, and this would be a fine approach- if the game had the AI handling each of the subordinate parts of the army where OKH's focus isn't. Since the game doesn't do that, it's a worse distortion to prevent the player controlling everything than to allow him to do so. quote: When I play, I AM OKH. And the subordinate HQ's follow my orders. ... OKH gave 10th Army an operational order at the start of the campaign which incorporated the possibility of probing Warszawa. Come 15th September, OKH isn't interested in 10th Army and is focusing on 14th Army and on XIX Panzerkorps. 10th Army isn't crippled- it has it's own staffs at several levels. It probes Warszawa. Bang, bang, bang. 80% Proficient panzer regiment fights for nine rounds against fortified infantry. Guderian remains on his start line for three days. Your approach is certainly interesting, it shows you've thought about this more than some, and it does raise some more questions. However, I don't think it explains early turn ending.

*Lava* -> RE: The most frustrating feature of TOAW engine (10/26/2005 3:51:37 PM)
quote: ORIGINAL: golden delicious Your stated desire is to see more scenarios. I suspect you have this idea that Matrix could pay designers for their work and then publish the scenarios. Not at all. My experience has been that people who REALLY support a game design are quite happy to freely assist. Significant contributions such as scenarios are worthy of credit, and I believe they would receive that. quote: ORIGINAL: golden delicious TOAW scenario designers only do so because they enjoy it. Of course, that goes without saying. However, successful scenario designers or game modders (of whatever game), often find themselves gainfully employed by companies which seek their talent. So there can be benefit. Hopefully, with all the material out there, I should think that there are individuals who would willing provide their scenarios to Matrix for publication and credit. Ray (alias Lava)

Page: << < prev 5 6 [7] 8 9 next > >>

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.875