Cougar29

LOL, as long as your pilot is doin' the "pilot shidd" perfectly fine and you have exactly NOTHING to do back there, everything is fine. KOLA is highestly appreciated to become available very soon. Better today than tomorrow!

Erm ... how does your question relate to my question, but anyway: yes, I did "TMS down" with maverick SOI ... yes, very often.

OB 2.7.17.29140 Single Player Nevada As can be seen in the track file, the WPN page (or better to say the Maverick missile?) got caught in PRE mode, and I wasn't able to get out of it to reach for VIS or BORE mode. Is this normal behavior or a bug? I used the ground radar in GM, then switching weapons from left to right by using the NWS button, then I couldn't get out of PRE mode anymore. 2022-08-27_F-16C_WPN-page_caught_at_PRE.trk

Guys, is any additional information needed to get this bug fixed? With NVIDIA drivers 516.94 this problem still exists.

Damn, I have no computer today. Anyway, good hunting gents!!

Unfortunately the F-14s where not available when entering the mission, thus Baron squad left the event early. Hoping for another event in the holy Cat. Best regards!

Cool! Count me in this time. Thank you!!

Unfortunately, Mariana Islands doesn't run on my rig so I think I will look forward for other maps (Syria again someday?).

Yes, me too, happened on 4th of June on Buddyspike Syria Modern. I have ACMI File where it is clearly visible that HARMS are going somewhere, but not on target. 4 weapons just fly right over the target, and are going into ground far behind the target. I was using HAS mode, locked the SAM, wait for the rectangle to flash, fire (as always). I never had problems with that in former versions of OB. I am still investigating, since I can't say for sure if the SAM units kept their radars on during my engagement. Are you sure about seeing the SAM's radar active until impact? Edit: Just did a test sortie against SA-11, had no problems. HARM flies to target at higher altitude, then dives steep, boom. Seems all OK so far...

Today I cleard the FXO cache. I then flew with the Hornet on the SC in MP (as single client only). Then I stopped the session for lunch. I then restarted the MP session, and this time I selected the Tomcat A. After a click on the FLY button DCS didn't respond anymore, I had to kill DCS.exe via the task manager after a minute. I have no track file, since I disabled writing of it with autoexec.cfg. Attached, find logfile and the mission file. dcs.log C-SUPERCARRIER-HORNET-8-TOMCAT-4-POPULATION TEMPLATE TOViper v4.miz

Is there anything planned within the next days/weeks? Looking forward for a new engagement ...

Hey, its a "limited edition". He might misunderstood something here ...

Hi Captain, hello Alpenwolf! Thanks for providing the statistics, very interesting information to me. Thanks very much for hosting this interesting mission. I read all posts above, so my feedback (apart from the fact that I had a super-situational-aware RIO on my seat at that day), is the overload of the frequency 251. I know people like to share everything, but getting out the important things was an exhausting task (despite some things indeed were pretty funny, not to forget about this!!) Technically the mission worked fine for me, good fps during most times, and very little amount of MP related stuttering (which I consider not-related to my computer config). I am looking forward to have fun again, whichever config/coalition/setup I will choose.