AAR Op. ''Haunted Georgia''

[mwd2]

Please post your comments about performen (FPS drop, etc. pp) und unit setup (different units, more or less units, etc. pp.) here.

 

If you have special wishes for a battle senario, let us know......

[Ike4fin]

I think MLRS should be removed because its known to cause FPS drop.

Balance wise the red SAM(tunguska) seems terrible compared to roland(looking at tacview). Switch to SA-8/15(for both sides)? Otherwise it seems good as long as player numbers are even.

[jj_pt]

Hello,

 

first of all, let me thank you for allow me to join this mission. I enjoy this kind of missions where we have "a lot" of human fighting together or against each other.

 

About the mission itself: It didn't go very well on my side. I crashed or got shot down at least 4 times, and had 2 mishaps when taxiing to the runway.

If this was not enough, I show down one of our Air-Defenses units by mistake.

On the first attack run, there were also some technical malfunctions, probably due to the technicians loading the wrong pod... So I was able to see the targets at night but unable to shoot the Kh-58U.

The base commander is not pleased...

[jj_pt]

I did have some very low FPS at times, with an average of around 22 in SUKHUMI - BABUSHARA (UGSS) airfield. I'm not sure if the rain and snow effects contributed to the problem.

 

What I think can be improved:

 

* Comms between the pilots. Some pilots just give unnecessary information on the radio. It get tiring on long missions. This is something that gets better with time.

* The briefing and debriefing should be much more extensive. I can not recommend this enough. If I go flying somewhere, I need all the details on the mission, including procedures used by all pilots in the flight, altitude profiles for NAV and attack runs, minimum or maximum engagement altitude, threats to be encountered and their limitations against our aircraft.

* Disable the outside views. It's to tempting to have a look.

* Pilots should take good attention to the ATC. Everyone was taking from from the opposite direction!

 

 

Best regards,

JJ

[mwd2]

I think MLRS should be removed because its known to cause FPS drop.

but they are a lot of fun, if you see all the red dots flying from the battery down to the enemy line - but yes we can remove them .... :hmm:

 

* Comms between the pilots. Some pilots just give unnecessary information on the radio. It get tiring on long missions. This is something that gets better with time.

each mission is 2hrs long....so not a real long mission! But yes it is possible to get boring if you still got shut down. About the communication, this part need training and communication, most of the guys are not realtime pilots!

 

* Disable the outside views. It's to tempting to have a look.

should be de-activated - need to test again!

 

* Pilots should take good attention to the ATC. Everyone was taking from the opposite direction!

again talk to each other, we have no real ATC, or someone need to take over the role...

[mwd2]

* The briefing and debriefing should be much more extensive. I can not recommend this enough. If I go flying somewhere, I need all the details on the mission, including procedures used by all pilots in the flight, altitude profiles for NAV and attack runs, minimum or maximum engagement altitude, threats to be encountered and their limitations against our aircraft.

The briefing is up during the week, if you have question, just ask.

For SOP, it is hard to setup a SOP about with new guys and old guys without comms during the week

 

flight, altitude profiles for NAV and attack runs, minimum or maximum engagement altitude, threats to be encountered and their limitations against our aircraft.

if you just come on TS 15min. before the mission starts and just fly - again communication is a key factor in each game.

[D4n]

I have no MLRS fps problems/drops at all (maybe due to my specs [i7 2600k, GTX 570, 8 GB RAM], I don't know what JJ has though), only thing was the bug that my instrument had error at some point "max. angle of attack" instrument. Serversetting "random system failure" was apparenty turned on... :/