compass heading messed up in mission 1

[Esac_mirmidon]

Perfectly playable for me. If you mean perfomance.

 

The missions also are finished without problems for me. I have edited the first to February, no problems after that in the rest of the missions. Rename the first campaign mission to .rar, then open the mission file with notepad, search for Date and change to month 2. Thats all.

 

60 FPS all the time, no stutters.

 

 

 

Edited August 16, 2017 by Esac_mirmidon

[Joni]

Perfectly playable for me. If you mean perfomance.

 

The missions also are finished without problems for me. I have edited the first to February, no problems after that in the rest of the missions.

 

60 FPS all the time, no stutters.

 

 

 

 

1.5.7?

 

You should post that in the 1.5.7 stutters thread as you are the first one to report good performance. Kuddos!

 

https://forums.eagle.ru/showthread.php?t=190539

[Esac_mirmidon]

Yes 1.5.7

 

My settings.

 

[Joni]

It may be the no grass setting and no civ traffic. But still, you should post it in the thread I put above, you must be the only one saying this so maybe it will help ED determine the bug root cause by looking at your experience.

[Esac_mirmidon]

I dont think i'm the only one who can fly the campaign with no problems.

[Joni]

??? We're talking about the DCS version, not the Mirage campaign. 1.5.7 in general is unplayable, thats what we said before, not the campaign :)

[Esac_mirmidon]

This is a Mirage campaign threat.

 

Anyway i dont have any problem with other missions. Only the ones with certain SAMs or tons of units.

Edited August 16, 2017 by Esac_mirmidon

[sze5003]

I posted here about the one mission because I am running 1.5.6 where the January bug was still there. I can't remember why I rolled back, probably thinking the January bug was not an issue if I rolled back but seems it was.

Edited August 16, 2017 by sze5003