ParaBellum

In a current PBEM 2 of my 7 mortar strikes on TRPs so far have fallen way off target. The rest hit with very high accuracy. These were on-map mortars BTW, ordered by veteran FOs.

I usually use ~40m as minimum distance for anything up to 81mm and 75-100m for 105 and 120mm. Anything larger I'd keep my forces as far away as possible. This with veteran FOs and LOS to target or TRPs.

Any update on this problem? Because, honestly, this is a very annoying bug for me. In a dozen PBEMs so far about 1/5 of my savegames are not actually saved. I've even had it happen twice in a row. If you just wasted 20 minutes giving detailed orders to a force the size of a reinforced company plus support this is highly frustrating.

I'm currently playing a PBEM as axis attacker vs an allied defense. Since the terrain is bocage country with difficult LOS I've bought a couple of TRPs to help my mortars. To my understanding TRPs are pre-registered target points for the artillery. They have been carefully plotted, all data is ready, so when the fire order comes in I'd expect accurate fire on those spots. Now, in the 1st turn I plotted 4 mortar strikes on TRPs. 1 of them actually landed on target, the other three were all over the map. The FOs didn't have LOS to the TRPs, but I was always under the impression that the one reason to buy TRPs was to get accurate fire without LOS. Why gather all the data when the rounds would miss their targets by hundreds of meters? :confused: Another thing: I've encountered a concrete MG bunker. One of my Tigers started engaging the bunker from about 200m. That's not even point-blank range for the Tiger's 8,8, but after a dozen+ of direct hits the bunker and crew still seems rather happy about their situation, the war, and life in general. Shouldn't the 8,8 be able to put a round through the firing slit at that range? PS: game is patched to latest version.

I've run into the same problem, posted a thread about it yesterday (didn't see this one). I'm currently playing a QB scenario and had it already happen twice in a dozens turns. Running Win7 64 bit.

I've noticed that every now and then a PBEM file doesn't get saved. Seems to happen roughly 20% of the time, and it's quite a bit annoying having to re-do a whole turn, especially in larger scenarios. To clarify: after giving orders the savegame window pops up, click on OK, game exits to main screen. Savegame is nowhere to be found. Game is patched (happened in previous versions, too), system is Win7 64 bit. Known bug?

The what? Do you mean there's supposed to be another book in the box besides the 'Basic Field Manual/Soldier's Handbook'? :confused:

Meine Steelbox ist gestern endlich gekommen, habe sie eben von der Post abgeholt. 10,68€ Zollgebühren.

Falscher Alarm... war ein anderes Paket...

Komme gerade nach Hause und ich habe heute anscheinend ein Päckchen in Abwesenheit bekommen. Ab zur Post! Die Spannung steigt...

Anyone got his copy yet? Still waiting here...

Weee! Thanks Steve. Did I mention that you are awesome?

Every now and then it happens that I save a PBEM turn, the game switches back to the main screen, but the turn hasn't actually been saved. Also a couple of times the game crashed while trying to save a turn. I'm using Win7 64 bit. Known problem?

Tried it, didn't work. That Tiger continues to rotate in place after every move order. The other Tiger works just fine, but that one is just totally FUBARed.

Im Südwesten nichts Neues...

BTW that Tiger is giving me a real headache in that game... After I somehow managed to un-entangle him from various trees and houses I just wanted him to move towards the enemy. Preferably with his gun and frontal armour pointing towards suspected bad guys. Issued a hunt command to both the Tiger and the StuG: Both move out as intended But then, as the Tiger reaches his new position suddenly a blue 'face to' line appears, pointing straight ahead. And the Tiger AGAIN starts to turn in place until his flank is pointing towards the enemy. Both tank and crew are OK, the Tiger has NO visual contacts to any enemy, this is starting to become really frustrating. After this battle, if that commander somehow survives, he'll be reassigned to drive a Goliath, I swear...

Not every tank in WW2 actually could turn on the spot using neutral steering.

Hehe...

Still waiting for my box to arrive.

I've uploaded the two turns from the PBEM: http://dl.dropbox.com/u/31419968/buggy%20Tiger.7z Password is puschel. I hope my opponent doesn't read this. The game was a QB, map is QB-022.

I think the tree might indeed be the problem. Still doesn't fully explain that screw-up IMO. EDIT: Our viewpoint is NW. The Tiger saw the enemy tank when he arrived at its intented position, then lost LOS when he started reversing/rotating. He didn't open fire.

Just checked the map in the editor, that's not the problem. Friendly edge is NE, enemy SW.

...no, he continues his circling around... ...until he has his back turned towards the enemy: Anyone got an idea to what happened here? Are drunk tank commanders modeled?

First let me say that I'm thoroughly enjoying CM:N, both against the AI and PBEMs. But every now and then I seem to run into problems with the vehicle AI that cause serious frustration. In a current PBEM I had ordered a veteran Tiger to quick move to a new position to engage an enemy tank: No face command was given. The Tiger moved out but as he reached its intended position suddenly a 'face to' line appeared and he started to rotate. He continued to rotate in place until he presented his flank towards the enemy tank. In the command phase I give the Tiger a reverse command in order to get his front pointing at the enemy again and to get him clear of that tree. He starts a backwards turn but doesn't simply drive back a couple of meters...

Some of the artillery seems a bit slow. I just had to wait 8 minutes for a 4.2" mortar barrage called in by a veteran FO.