Jump to content

Chops

Members
  • Content Count

    619
  • Joined

  • Last visited

About Chops

  • Rank
    Senior Member

Converted

  • Location
    California
  • Occupation
    Pilot

Recent Profile Visitors

665 profile views
  1. Here is the link to the original thread about this bug; read down a few posts in the thread (December 2016) - I actually sent a saved game to you sburke at the time.
  2. Why do you need a saved game? This behavior was introduced after the Engine 4.0 upgrade was released. I remember there was a lot of discussion about it at the time, and I even remember uploading a saved game back then. I think the Engine 4.0 upgrade was released around December 2016. I thought that this would be one of the bugs fixed in the Engine 4.0 patch.
  3. Thanks guys - 1. Is there any supporting documentation that describes exactly what was changed in the Engine 4.0 patch for CMSF2? When a patch is released it is common practice to include documentation describing what was included in the patch. So I would simply like to know specifically what was changed, as it took over a year for this patch to be released. My understanding is that in the original Engine 4.0 update, the behavior of troops under High Explosive (HE) fire was changed, in order to make their behavior more realistic. However, it actually caused them to leave good cover, and run into the open. So, was their behavior changed back to what it was originally in the Engine 4.0 update, or were additional changes made in the new Engine 4.0 patch? 2. Additionally, where is the documentation for the CMSF2 v2.01 patch? As I mentioned previously, no file was included with the CMSF2 installation.
  4. I recently purchased and installed CMSF2 v2.01, and have not found any documents in the installation directory that refer to the Engine 4.0 long-awaited patch, or for that matter any information about what is included in the v2.01 patch. The installation directory does contain the Engine 4.0 manual, however it is not dated, and it looks to be the original Engine 4.0 manual. I scanned the Forums but did not find much information on a 4.0 patch. One thread in the General Forum states that the Engine 4.0 patch will be released after CMSF2. Was the Engine 4.0 patch included in CMSF2? If so, is there any documentation describing what was changed?
  5. Thanks for listening to customer feedback, and making changes to the Patches > Download link for CMSF2. I hope it helps future customers. In order to show my appreciation I just purchased the game.
  6. Exactly, and it doesn't seem like a good idea for a company to send a customer on a surprise-filled adventure when trying to purchase products or download patches for products. When I recently saw the new thread "CMSF2 v2.01 Released!" I went to the Battlefront > Patches download page to see if it was posted. This page only showed a CMSF2 v2.0 patch link, so I obviously assumed that it was the 2.0 patch. Initially after looking at the forum and website, it seemed that two patches had been released , v2.0 and v2.01. As a result, I started this thread in order to locate the 2.01 patch. The first person to respond to this thread, stated that the patch was named incorrectly on the website, and it was actually the 2.01 patch. Since then, I have seen other posts from customers in different threads, also stating that the patch was named incorrectly. A simple solution to this unnecessary confusion, would be to name the patch download link the same as the actual patch name. For example - patch v2.01 is released, and the download link is also named patch v2.01. This seems like a normal, logical, and rational approach. Putting the dates next to the patches will really help reduce confusion as well. I noticed that the patch download link was just renamed to "for v2.0" I have no idea what this means. Why can't the patch download link just be called v2.01, or better yet v1.01 since it is the first patch for CMSF2? This whole thing may seem like no big deal to people that frequent the forums and website on a daily basis, but for someone that does not, this is the end result...confusion and frustration.
  7. I have not purchased CMSF2 yet, as I was waiting until the game was patched. So in my case, there was no reason for me to click on the patch link. I went to the patch page several times hoping that the patch had been released, only to find that 2.01 was not posted based on what I saw on the website.
  8. The 2.01 Patch was released 9 days ago, however, it still is not named correctly on the Battlefront > Patches website. How is it that Battlefront releases a patch and does not give it the correct name on their own website? Could we please have some attention to detail and professionalism on this issue? This is has caused unnecessary aggravation and frustration for this customer, and I am sure others as well. Additionally, it would be helpful to have the date that the patch was posted listed next to the patch download link.
  9. I am unable to locate the new 2.01 CMSF2 patch. As you can see from the screenshot below, only a 2.0 patch is listed on the Battlefront > Patches website. Is this another one of those "soft releases" where BFC keeps the patch link buried in another thread? This is really quite annoying and frustrating.
  10. I totally agree with the OP's messages. While CMx2 is a technological marvel and BFC has done an incredible job, it is definitely time to progress and move on. CMx3 is well overdue and I certainly hope BFC is in an advanced phase of development behind the scenes on CMx3. The flaws/limitations of CMx2 are readily apparent to me, and I would think anyone, that has been playing the games for an extended period of time. -spotting, whether a tank spotting hidden infantry instantaneously, or troops not spotting a tank an action spot away, etc.... -pathfinding issues, TacAI troops and vehicles doing ridiculous things -the lack of mouseover pop-ups and basic information for the player in a large section of the GUI -ongoing weird or ugly graphical issues, shadows, water, fog, foxholes, trenches, etc..... While playing CMx2 scenarios, I have multiple WTF moments every game now, where it just blows immersion and creates frustration.
  11. If you read further up in this thread, my idea of "Rout Zones" may help. However, in Pericles' second Bug 2 video there are also other issues with the TacAI for troops negotiating areas with walls, doors/gates, buildings. In the second video, real troops would have obviously gone around the side of the building, while staying covered by the compounds walls, and through the side gate toward the south.
  12. There was nothing passive aggressive about what Pericles said. So stop abusing Battlefront's customers, and stop your troll-like behavior. You are not a representative of BFC, and you are not a forum administrator. You are just a guy with to much time on your hands, based on your number of forum posts. So cut this sh*t out! The behavior that Pericles describes is nothing new. I have been seeing this type of thing for a long time, across all of the CMx2 engine 4.0 games.
  13. Thank you for your post and I agree that these improvements are long overdue. It is definitely way past time for CMx3 as well.
  14. Maybe "rout zones" could be set by the scenario designer, similar to the way setup zones are painted on the map during the scenario design process. So, when units are shaken or panicked they will retreat toward the nearest rout zone. I have seen the path finding behavior that you describe across all of the CM games. It is not exclusive to the CMSF 2 demo. This brings up another point, which is the original CMSF 1 had routing instead of surrender. Troops would rout, and an icon would be shown, and then they would disappear from the map. I think that routing should be brought back to the game, without the disappearing act until they get to a rout zone (which could be a map edge). The game should have both surrender and routing.
×
×
  • Create New...