Battle of Moscow Single Player Career Glitch

[spreckair]

While flying as a Russian pilot in Career Mode on the Battle of Moscow map and timeframe, from April 8 onwards the mission maps indicate that the target locations are off of the far Western end of the map.  I started one mission and the main leg of travel was 256 km, and off of the end of the map, so I aborted.  This seems to be happening regardless of the mission type.

 

Has anyone else seen this?  Thank you.

[AzureDragoon04]

Its happening on both sides of the Moscow career I was doing a Ju-88 career and its also happening,

 also mine is also happening on Oct 16 onward, and is yours also going off the southwest corner of the map.

Edited March 17, 2022 by AzureDragoon04
update

[Wilhelm_Heidkamp]

Same here. Carrer deleted. 

[Dutchvdm]

Issue has been reported and will be fixed.

 

 

[Casus_Bellum]

Just wanted to chime in and say I'm experiencing the same bug. Battle of Moscow. Happened in early December of 1941, Axis side, flying the BF109. Completed the first mission of escort bombers, 1 hr and 15 mins. Shot down 2 planes. Checked the AAR in the planning room and it said Mission failed, and didn't give me credit for the kills. When I viewed details on the map, friendlies were attacking each other on the ground, OPEL Blitzes and Ford transports were killing each other... or something. It was hard to read, being that the objective was in the far South West, deep in friendly territory, almost off map. 

 

I proceeded to the next mission, and it was exactly the same as the last one. Deep in friendly territory, South west, almost off map. I changed squadrons. Same problem. Ended up deleting the career after almost 30 sorties. Such a disappointment. Was on expert mode. Using VR. 

 

I had recently downloaded Pat Wilson's campaign generator, but it was not running at the time. Not sure if that makes a difference, but I'm trying to give you guys as much information as possible. 

 

Hopefully you guys can pinpoint this and fix it soon. Great game!

 

[MadMav24]

I am having the same problem.

[spreckair]

This was fixed super quickly--thank you very much Devs!