Jump to content

Pfalz XII

Members
  • Posts

    69
  • Joined

  • Last visited

    Never

Converted

  • Location
    St. Louis, MO

Pfalz XII's Achievements

Member

Member (2/3)

0

Reputation

  1. I don't think gridlines are gamey or unrealistic. What IS unrealistic is trying to look at 3D terrain through a 2D computer monitor. Gridlines are simply a visual aid to assist the player in determining the lay of the land. Golf sims frequently use gridlines for this very purpose.
  2. Many people in the War Department did not think Pearl could be attacked by carrier based torpedo bombers because they thought the bay was too shallow. American torpedo bombers at the time required a minimum depth of 100 feet in order to operate without plowing into the bottom. Unfortunately, the Japanese had developed torpedoes that required less than 75 feet. They also practiced a lot. The main threat was thought to be sabotage from Japanese nationals who lived on the island. That's why most planes on the ground were lined up wingtip to wingtip. [This message has been edited by Pfalz XII (edited 07-21-2000).]
  3. For an excellent and thourough analysis of the events leading up to the surprise sneak attack on Pearl harbor, read the book, At Dawn We Slept. Sorry, can't recall the author at the moment. In short, while there were numerous signs of an impending Japanese declaration of war and even a possible move against Pearl Harbor, these threats were never taken seriously. Many people in Army and Navy intelligence, as well as the War Department, missed these warning signs. However, there is NO convincing evidence that FDR himself knew ahead of time the Japanese were about to attack Pearl Harbor.
  4. Ignorant, arrogant, hypocritical, and dishonest to boot! Is your other hobby drowning newborn kittens? Hilmer, I believe you have just rocketed to the top of this forum's honorary Hall of Shame. Quite an accomplishment, I might add. Oh, and please DO tell all of your "friends" not to buy CM. You and your ilk will not be missed. Good day, sir. [This message has been edited by Pfalz XII (edited 07-21-2000).]
  5. For more information about this problem, see the thread I started titled Decisions, decisions--targeting that is! at http://www.battlefront.com/discuss/Forum1/HTML/007084.html [This message has been edited by Pfalz XII (edited 07-12-2000).]
  6. Thank you, Charles. Um, you wouldn't mind emailing me to let me know what changes have been made to increase the TacAI "smarts," now would you? Seriously, the step-by-step approach that you are taking to this problem is probably the wisest course at this point. Also, Villars-Bocage is probably an extreme case, so fixing targeting so it works in this scenario might futz up something somewhere else. Still, I have to say that I think a new targeting command is still the best solution. Any guesses as to the first scenario I will fire up after downloading the 1.03 patch?
  7. Ha ha! If you are looking for the definitive answer, you have come to the wrong place! From what I can gather there is not much of a difference between the SPW 250/7 and the SPW 251/2. They are both 81mm mortar carriers, have no transport capacity, and do not carry mg's. The 251/2 is heavier and has slightly better protection/armor sloping.
  8. Hmmm, while I disagree about the need for an LOS tool at each waypoint, I sorta like the idea of a camera lock or view which would track along your chosen path. This would give you a good troops eye view of the terrain you propose to travel and eliminate a lot of the guesswork with the control-click method. I also like the idea in alternative #2 of allowing your troops to use independent judgment to find the best terrain within 2 or 3 meters (less than 10 feet) of your chosen movement path. Unfortunately, my guess is that even state of the art pathfinding AI is not yet up to this task. Something for CM3 or 4 maybe?
  9. CrapGame, I apologize for not answering your question. Actually, my post was not directed at you. I was simply pointing out to a certain newbie 1) to use the search function, and 2) to not post everything in caps. Didn't mean to slight you in any way. [This message has been edited by Pfalz XII (edited 07-11-2000).]
  10. Mortar crews must not be hiding and should be unsuppressed before they will fire. This, and the answer to many of your questions about CM, can be answered by USING THE SEARCH FUNCTION!
  11. I saw from a post by Fionn on uselessnet that BTS has tweaked this in version 1.03 so that AFV's are less likely to target crews. However, he gave no details as to what may have been done to fix this. Since Steve and Charles have been on vacation and haven't responded to this thread, I was wondering what changes may have been made to help alleviate this problem. Since increasing target stickiness and adjusting the point values of vehicle crews have proven to be less than optimal solutions, I was hoping that maybe a new approach might have been used.
  12. Hi Fang! Why yes, yes I do, play Red Baron 3D. However, due to a number of factors (P200, 3-button joystick, 33.6 Winmodem, plus I suck) I rarely play MMP. I do have most of the FM, DM, and graphics add ons, which add tremendously to the game. IMO, anyone who plays RB3D without any of these enhancements is really missing out. Do you lurk over at Delphi's Flight Sim forum? Actually, I haven't had a lot of time for RB3D lately (too much CM) However, once I get a Duron and a new Asus A7V in a few months, I plan to revisit RB just to look at the pretty scenery with everything maxed out. I'm also looking forward to B17-II. Hmmm, I haven't updated my V3 drivers to 1.05 yet. You might try setting Z-Buffer Optimization to disabled and see how that works. I have no idea what Level of Detail Bias means. S!
  13. Your Eminence, Mr. Fang, I have a Voodoo3 2000 PCI card. Here are some things you can try. Go into Control Panel, select Display, and go to 3dfx tweaks. Make sure your Direct3D image quality settings for both alpha-blending and video display are set to "automatic." Also while in Display, click on Settings, advanced properties, and check out what refresh rate your card is set for. Try lowering the refresh rate and see what effect that has on CM. Good luck.
  14. <BLOCKQUOTE>quote:</font><HR>#1 ignores the problem of manpack AT weapons like Schrecks and Fausts, and even ordinary squads are a threat if allowed to get close enough. Of course, a skilled commander will try to have escorting infantry to deal with that threat, but you don't always have them around. You can't just ignore those threats.<HR></BLOCKQUOTE>I'm not ignoring this threat, believe me. First, as you say, a good commander will not usually let his armored units get close enough to these teams without adequate infantry support in the first place. Second, one reason why individual AT teams were so effective in WWII was because TC's sometimes became fixated on engaging enemy armor units, allowing these teams to sneak up on the otherwise engaged armor unit. This was particularly likely when buttoned. Third, under my approach, once these teams are identified as AT, they are treated by the TacAI as high priority threats and dealt with appropriately. Finally, since the "Target AFV/ATG Only" command is selectable by the player and is not the default command, you don't have to use it if you are concerned about getting clocked by an AT team. IMO, my approach (if it can be coded) is more realistic than having your turret needlessly rotate to engage fleeing vehicle crews which are no threat to you. <BLOCKQUOTE>quote:</font><HR>#2 forgets that if a tank is permitted to use its MGs, it will use its coax (denying it that would be unrealistic), which gets us back into the turret rotation problem.<HR></BLOCKQUOTE>Again, using your coax mg is a tactical decision that has to be made by the TC. In my view, if you are engaging enemy armor (even if temporarily out of LOS), you will NOT rotate your turret 90 degrees to engage low priority infantry targets. Most AFV's have 1 or even 2 other mg's to use against such targets, which they can use to great effect (suppress now, kill later). In this situation, the TC has bigger fish to fry. Although I agree in principle with what you said about #3, for the reasons stated in my above post, I don't see tweaking the point values of crews as being the most desirable solution. As Kump pointed out, the main problem is the TacAI gets overwhelmed by the sheer number of crews running around the battlefield. A target filter would help to reduce this confusion, IMO and lead to more realistic results.
  15. Okay. First, I think Combat Mission is an awesome game which has set the standard for virtually all wargames to come. It is even more impressive as a first time effort and is quite a testament to both Steve and Charles’ vision, skill, and commitment to historical accuracy, all while making a game that is not only impressive to look at and see, but also to play. Furthermore, I don’t think any of us can truly appreciate how enormously difficult it must have been for Steve and Charles to pull this off—making a product with such a “WOW” factor with so few problems. In addition to this level of commitment, they have been extremely responsive to the requests and comments of us, their adoring fans. However, there is one problem (of course)which has continued to bug me, from the original demo up to the current version (1.01): the nasty and annoying habit that armor units have of rotating away from enemy armor threats to engage low priority vehicle crews. As I see it, there are three or four possible solutions to this problem. Here they are, roughly in order of priority: 1) A separate targeting command for AFV's/AT units called, "Target AFV/ATG Only." This command would apply only to the main gun of an armored unit or to AT guns, forcing them to ignore crews and infantry units with their main gun, allowing the tactical AI to concentrate on any armored threats or AT guns that are out there but which are temporarily out of LOS. While this will not eliminate the problem of rotating the turret more than 90 degrees away from an armored threat that has popped smoke, it will limit the number of targets of opportunity (to enemy armor and AT guns) so that your armored unit has a better chance of engaging the enemy AFV when it comes back into LOS. It also seems to be more in line with the main purpose of armor units--to engage and destroy other armored units. Of course, this command would be selectable by the player, to be used in those situations when you are stalking (or are being stalked) by enemy armor and aren't as interested in killing troops. When not selected, your unit would behave normally, targeting any target of opportunity. While BTS's solution of increasing target stickiness has helped, I don't think it addresses the main problem: armored units get easily overwhelmed by having too many juicy targets to choose from. This problem becomes much more apparent in the mid to late stages of scenarios involving lots of armor, e.g. Villars-Bocage, where after a few turns, there are lots of 4 or 5 man crews running around. Furthermore, these crews are often out in the open, where they are easily spotted. Finally, when an enemy unit goes out of LOS for more than a few seconds, its threat value is reduced to zero (out of sight, out of mind). In this situation, the tactical AI gets too easily distracted by the units it can see. With my idea, even though your tank can see the crew, it ignores it with its main gun so it can concentrate on the more important armored unit or ATG's. I like this idea because it gives you some control, but not too much control. In essence, you are emphasizing to your TC that his main job is to engage enemy armor, when the situation calls for it. Sure, there will be times when your AFV will not find any enemy armor to shoot at and will sit there for a turn not shooting anything with its main gun. However, it will still be able to use its machine guns. And, if that enemy armored unit appears, you will have a better chance of taking it out because you are not being distracted by that pesky, but low threat, bailed out crew. To re-emphasize, I don't think the main problem is one of target "stickiness." Instead, it's that AFV's have too many targets to choose from—more specifically, crews. In contrast to other units which have more limited roles, and because of their unique combination of protection, mobility, and firepower, AFV's are asked to do a lot of things. Usually, this is a good thing. However, there are also times when you only want them to do just one thing--kill that Tiger, Sherman, etc. The problem with crews are that they are sort of like viruses—they quickly spread and are difficult to get rid of. In large scenarios, as enemy armor units are destroyed, they quickly overwhelm the ability of AFV’s to select the most important target. The target "filter" simply increases the chances that your AFV will perform its historical role of killing other armored units. 2) Instead of a "Target AFV/ATG Only” or a “Disregard Infantry” order, another option (assuming the game engine would support it) would be to prevent AFV’s from using their main gun against crews. Of course, they would still be allowed to use their MG’s against vehicle crews. An even more drastic alternative would be to prevent AFV’s from targeting crews at all, but this is probably not a very desirable option for most. 3) Another option (which BTS has already tinkered with, I believe), would be to reduce the “point” or “threat” value of vehicle crews to make them less attractive targets to AFV’s. The problem with this method is that it assumes the AFV has a selection of armored and infantry targets to choose from, and that it will choose the highest priority target. However, this frequently does not work because the enemy armor unit has popped smoke or has otherwise temporarily moved out of LOS. In this case, the AFV has a selection between a target with a value of “0” (because it is out of LOS) and a target with a value of “0 + X” In this case, the AFV will always rotate to engage the target with the value of “0 + X.” By the time the higher priority enemy armor unit comes back into view, your AFV has already rotated to engage the low priority crew. This problem is even more aggravating because it gives an unfair advantage to lower quality armor units which can’t slug it out “toe to toe” with enemy armor and which have to instead rely on stealth to survive (and so are frequently moving into and out of LOS). IMO, this also gives an unfair advantage to Allied tanks, because they tend to rely on speed and stealth, while Axis tanks, while powerful and well protected, are slow and have slow turret speeds. Phew! Glad I got that off my chest! Hopefully, this post didn’t come across as a bitch-fest, but simply as some constructive criticism and some suggestions for dealing with a problem that has bothered me and several other fans of CM. Again, I don’t consider this problem to be a game-breaker, but if fixed, would add a lot to both my own, and others, enjoyment of the game. Comments and criticisms are welcome. We now return to your regularly scheduled program....
×
×
  • Create New...