Jump to content

Pericles

Members
  • Posts

    165
  • Joined

  • Last visited

  • Days Won

    1

Pericles last won the day on October 26 2018

Pericles had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Pericles's Achievements

Senior Member

Senior Member (3/3)

22

Reputation

  1. Tim Stone - who was fired from RockPaperShotgun a couple months ago for taking a conservative stance on the trans issue - now has a new website. Enjoy his writing and support him at (https://tallyhocorner.com/).
  2. I want to play the game (CMSF2 and CMBS) on Steam by getting a Steam key for my Battlefront purchases of CMSF2 and CMBS (using these directions: (https://community.battlefront.com/topic/137434-how-to-get-your-cmsf2-game-on-steam/). However, when I fill in the information on the Slitherine sign-up page to create an account (https://www.slitherine.com/register) and click "REGISTER" I get: "Oops! An Error Occurred The server returned a "500 Internal Server Error". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused." I am unable to contact Slitherine support because you need to have an account with Slitherine to do so (that is what I was trying to do). Navigating through Slitherine's antiquated website has left quite the impression but I'll try to remain polite about this. Any ideas as to how to go about resolving this issue?
  3. No, I committed two platoons to move up the middle forest area and had one of those platoons decimated by the Germans hiding on the other side of the forest road next to the trucks (quick moved several squads across the road a few action spaces without scout precheck). I then swiftly uninstalled the game to stop myself from falling into a more serious CM spiral. I will be sure to try it again when I have time. It was tricky but I only skimmed the surface. I liked the plausibility of the scenario, with the Germans in retreat trying to rest for the night and the Indians with low morale knowing the end of the war is near.
  4. I have often overlooked mission briefing editing mistakes, including grammatical errors that interrupt the flow of reading and mistakes in listings of assets available. However, I recently read through a mission briefing that takes the cake in terms of editing errors (there are five of them in the short briefing). The mission is R2V One Final Effort, where you fight as the Indian army. Normally, I wouldn't take the time to make a comment about this, but the author of the scenario goes out of his way in the Designer's Notes to thank someone else for "assisting with briefing review and editing". This just doesn't seem right. In any case, I'm sure the mission is well designed, just needed to chime in on the on-going "mission briefings could use better editing" feedback. Like, seriously. Here are the five errors: "...streaming north is what can only be described as..." [should be "in", not "is"] "...have already been or likely to be liberated..." [should be "are likely" not "likely"] "Using whatever transport available elements of the..." [should be "available, elements" not "available elements"] "One Humber IV armoured car is also available to you command to assist" [should be something else (maybe "your command to assist")] "...estimated that perhaps there are two platoons of worth of infantry." [should be "worth of infantry" not "of worth of infantry"]
  5. Is there any information on which armies the player controls in the two campaigns? If not, why not?
  6. I currently have two games installed: CMRT and CMSF2 CMRT works no problem on my Asus 1920x1080 external monitor when "Display Size" is set to "Desktop" in Options. However, CMSF2 does not work for "Display Size" = "Desktop". After the Battlefront intro screen, the proper resolution is displayed for a split second, then the resolution becomes enlarged and wonky. Can this be fixed on my end? Seems to be something about the game itself given that CMRT displays fine.
  7. I would love to see an EU army - the softest army in the history of armies
  8. The team withdrew on its own. There were no orders for that team on that turn.
  9. In the particular case of the video below, I don't see how the unit is thinking only of itself based on the knowledge it has available to it when it runs back toward the enemy a second time instead of down the road or behind the wall. It simply doesn't make any sense given the in-game situation (e.g. the unit is aware of enemy contacts North). Would you agree, or am I missing something? Battlefront wrote: "However, we have been at a point now, for a while, where it's getting harder and harder to find reproducible, addressable corner cases. That's good." Agreed. And the discussions in this thread may have contributed to the identification of a reproducible corner case in the Wilcox scenario. If it's not sufficiently addressable, then that's not good, but only mildly not good. I realize that expecting a video game like this to be completely free of errors is not realistic. As a customer and proponent of the CM franchise I will continue to poke and prod with evidence, reason, and an open mind in an attempt to contribute to the improvement of the game experience.
  10. sburke - I didn't realize TacAI problem identification was so complicated. I thought that identifying TacAI problems in the most current engine version 4.0 was all that was relevant in improving the engine. The developers would take your ticket submission regarding an identified TacAI problem and make changes to the most current engine version 4.0. If you are correct, and it is actually relevant to know whether or not TacAI problems identified in the current engine version were also present in the previous engine versions, then my belief that your question is not relevant to the discussion is wrong. That being said, it would have been constructive if you would have given your opinion on the topic of the post, which is TacAI problems with the Shock Force 2 demo. You've had a chance to look at the videos and to experiment with the demo. What do you think?
  11. sburke, I don't believe your question is relevant to the discussion. The issue here is identifying problems with TacAI in engine 4.0. Clearly, the engines before 4.0 were imperfect (that's why we have continued engine development), and one would expect to see problems with TacAI behavior in those versions as well. I seem to recall TacAI problems before 4.0 came around. Shock Force 2 demo TacAI problems do not happen a lot. But the fact is they happen (I was able to provide three examples from one play-through of the Wilcox scenario) and many of us would like to contribute to their solution.
  12. If my writings in this thread are "aggressive", I would say the same about IanL and others. I am writing these things in the interest of furthering a reasonable conversation about known issues. And as an aside, I have great respect for IanL as a Combat Mission veteran and tester - his work has advanced the development of the CM engine through the years. I just disagree with him in terms of how he has approached reasoning about the issue of TacAI problems in this particular thread.
  13. ncc1701e - Great. So it seems you have replicated the problem that I identified in those three videos I posted. This is what I would call a "TacAI problem". I read you loud and clear the first time. I understand the fact that pixel soldiers do not make good choices all the time. It is a very obvious point to make. However, I don't believe the observed behavior - as documented in my three videos, as replicated by ncc1701e, and as confirmed in writing by others in this thread - can be explained in terms of bad decisions. And I don't believe that you can look at those videos and honestly say "The soldiers just made bad decisions. This is not a problem that could be solved (an aspect of the TacAI that could be improved)." The fact is, this game is about simulation, believability, and realism. It is simply not believable that soldiers would run towards an enemy when panicking rather than running away. That is why the TacAI is programmed as it is (run away from direction of enemy). This is what happens most of the time. But when soldiers panic and run towards the enemy stupidly, having known contacts in the area, there is a significant loss of believability and realism because no one would do this in real life without some sort of aneurysm or suicidal wish. The TacAI will not be perfect. There will be coding problems, like with any game. This is something you seem to be incapable of admitting.
×
×
  • Create New...