transporter

I found that if I go to level 1 to track movement I have to pause repeatedly to, I guess, let the video catch up. I don't use 1 very much anymore using it mainly to look around. My system, on occasion, will still freeze on level 2 but I found that if I just wait for a few seconds, sometimes up to 15-20 seconds which can seem like a long time when you are waiting, that the video will catch up and continue as normal. Don't know if that makes any sense or why it works but it does for me. I still have the best video settings but find that the more scenery intensive the more processing the video card has to do and the greater chance of a freeze. Perhaps the new engine they are working on will solve the problems. My computer has the save specs as yours except it is a 2017 Imac Pro with a 10 core Xeon W, and the Radeon Pro Vega 64. I just upgraded to Ventura so we shall see. Good lick!

Upgraded and all work fine. I did have to restart the computer twice to get CMFI and CMRT. But once I did that all was well.

Never had that but I had a tripod mounted 50 cal with a box magazine that held 50 small plastic bullets that would fire when you turned a crank.

I have found a company named "Matrix Games Pro Software" which sells a game amazingly similar to CM Shock Force 2. Is it a related company?

One of the scenarios I played I had 3 jumbos knocked out by panthers at ranges of 500m+ In each instance the round penetrated the mantlet. I thought the mantlet on the jumbos was thick enough to withstand that.

This shows how the black computer cursor aligns itself on top of the green game cursor. The black curson stays on top no matter how you move the game cursor. Hope this comes through and is understandable/

Usually happens in CMBN but has happened in others. it does not happen all the time but next time it does I will get a screen shot and try to explain better.

Because this is a wish list I would like to see all the weapon systems in CM1 used in CM2. For example, Pershing tanks, Puppchin AT, on map 105's (not just priests)et al. And the ability to use them in any of the scenarios. Not exactly historically accurate but makes for more fun.

If memory serves CM1 had a line of sight (LOS) feature. CM2 's line of sight is for targeting. In CM 1 you could have a line of sight but not be able to target. LOS would be a nice feature to return.

A little over half the time I play the game the black cursor overlays the green cursor. It does not effect game play other than it can make some movements i.e. troops embarking into a vehicle difficult to see. The black cursor is larger than the green one and can cover the vehicle. I have tried cursor size adjustment in my computer settings but to no avail. Like I said it doesn't effect play it is just a small pain to work around. Just curious if anyone else has this and if it could be corrected.

Someone who has more info than I do can check the width of the Tigers track vs the M-10. A wider track helps spread out the weight making a lower "footprint" weight per square inch. This is one of the reasons the T-34's did so well in soft ground conditions.

Have you run the native CM on your Mac laptop or do you use only the windows version via parallels?

CM1 had a good "shoot and scoot" command but I think it was for armor only.

Tried this. Extended game by an hour then deliberately slowed down my attack. Still got end of game without all objectives met and OPFOR having undeployed reserves.

Perhaps a solution would be to go to scenario editor and increasing the length of the game before you start it.

When the "Victory" page is displayed instead of merely having the choice to view the map or end the game, how about another choice of "10 more minutes" You could play to the last man if wanted or perhaps figure out a way to pull victory from the jaws of defeat. Granted you could continue to press 10 more minutes many times but eventually you would end the game. PS. to be fair don't view the map before extending the game.

I remember in CM1 that virtually every weapon used was available, from the puppchin (s) to the super pershing. Not exactly historically accurate but a lot of fun to add to a scenario.

Right now it is in UK "The Full Monte" but I have noticed it in other British scenarios.

Apparently the command folks with the 51mm mortars cannot call in other indirect fire support. Also, after they use the 51 mm HE rounds and all that is left is smoke I get "out of range" when I try to use even ranges as close as 150 meters. The mortar info says it is good to 800 meters. Even if I try to target with the AR's it still says 'out of range" Is this a glitch or am I doing something wrong. Thanks.

Interesting. I agree with the challenges mentioned above. Others would be: 1. If you have both smoke and WP rounds, be able to pick which ones you want to use. Smoke is just smoke while WP especially fired into a building can cause much damage. 2. Noticed that a smoke round fired from a 51 mm mortar does not seem to have the same range as a HE round. 3. It would be nice to separate squads while on board a vehicle. There by you could drop a few off, drive farther, drop some off etc. 4. And this is just for the sake of fun. In CM1 you could add any vehicle or weapon system to a scenario. 5. In CM1 (if I remember correctly) you could display all gun target lines at once. Kinda like displaying all vehicle movement routes now. If you are in a large game it is not easy to remember who you have firing at whom unless you go to each unit individually. I have had units run out of ammo because i forgot they were firing. But, despite everything, I enjoy playing the games even if I get my butt kicked now and them. (Of course I can always replay the scenario with one I have modified lol)

Running into the same challenge. Started fire mission with multiple 155's when spotter got killed a few seconds before fire for effect was called. However, on target was not on target with most of the rounds covering a wide area. There has to be someone in the chain of command that can order cease fire.

Just upgraded to the recent version and ironically the program has not frozen - yet. Hopefully others with the freeze dilemma will have the same positive results.

I have an 2013 Macbook Pro and the game plays perfectly on it. I agree that it has to be the Radeon Vega card. One thing I have found is if you move the camera via the keyboard while simultaneously moving the mouse it tends to lock up more frequently. At least the game is playable which is a good thing.

It will freeze when either moving the camera or following troop/vehicle movement. I have tried virtually all the different combinations of video settings to no avail. BTW, I have the problem on all of the CM games. Having said that, all my games are on turn based and basic training as I play for fun and like to take my time figuring things out. I have not tried any other setting. If you do let me know how it comes out.

Some times I think there are an abnormal number of gun hits but then the next game there is hardly a gun hit. But if I do have a tank with its main gun out of action, that tank now becomes an armored recon vehicle.