Jump to content

Manfredo

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

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

Manfredo's Achievements

Junior Member

Junior Member (1/3)

0

Reputation

  1. I managed to get it working at a good framerate with dgVoodoo 2: http://dege.freeweb.hu/dgVoodoo2/dgVoodoo2.html Because I have a widescreen monitor the 3d graphics were stretched until I manually specified 1920x1440 resolution in dgVoodoo config settings. So at least there are workarounds to get it working. Win 10 Pro, Nvidia 2080 Ti, i7-9700k, 16GB RAM. Actually, that's very interesting that its working fine on your system. My older rig has a GTX 980, too, and I still got slow performance on 1.03 but good performance on 1.04. My laptop has integrated graphics and runs fine on 1.03 so I assumed it was an issue with new cards. My Windows 7 machine with a GTX 670 runs 1.03 at solid 60 fps.
  2. I was pleased to see that Combat Mission Afrika Korps and Barbarossa to Berlin are being sold on GoG - I bought them both for posterity's sake even though I already had them from when they were offered on the Battlefront store. However it looks like the versions uploaded to GoG are versions 1.03 instead of 1.04. This is important for me, because 1.03 runs with very low frame-rates regardless of what kinds of compatibility settings I use on my machine. Patch 1.04 runs fine. Are there plans to update the GoG version to patch 1.04? I guess I don't mind right now since I still have versions 1.04 from battlefront. But I would be very disappointed if the GoG release tarnishes the perception of this game due to preventable technical issues. I want to buy this game to some friends so we can PBEM but I want to make sure it'll run well on modern systems with patch 1.04.
  3. Troops behaving strangely under fire has been a known issue since Game Engine 4 was released. If I recall correctly, the intent was to make troops be more intelligent about avoiding fire. Sometimes this works well, with troops changing their "quick" or "move" commands to "fast" commands when a shell lands near them or if they're peppered with MG fire. But one of the consequences seems to be that troops are too willing to change positions when under fire. Even more concerning is that they'll frequently leave cover when fired upon, which makes little sense even if we do agree that our pixeltroops shouldn't behave like Rambo. This has been pointed out in numerous threads: http://community.battlefront.com/topic/124910-has-40-made-the-stock-campaigns-unplayable/ http://community.battlefront.com/topic/124976-how-can-i-prevent-infantry-running-away/ http://community.battlefront.com/topic/124998-infantry-breaking-to-easily-in-40/ http://community.battlefront.com/topic/124569-infantry-behavior-under-arty-bombardment-in-cmbs-40/ http://community.battlefront.com/topic/124173-40-infantry-ai/ <- somewhat related, more about infantry sneaking when under fire. It'd be good to have a tweak that makes it so that when fired upon infantry retreat to cover if they're in the open, but keep their heads down and stay put if they're already in cover. Some people say that if you give troops a "pause" order this will prevent them from running away, unless their morale goes as far down as "panic" or "broken".
×
×
  • Create New...