Bog9y

Ok, I think I have figured out what the problem is. It's not a bug (per se). So when I swtich to A-G master mode, it defaults to CCRP mode and the SOI defaults to the HUD. During my pop up attacks I must have moved the TD box by accidentally touching the slew button! Because we have no GM mode on the FCR you can not change the SOI by pressing DMS down. So, it's not a bug but not being able to change SOI with dumb bombs certainly doesn't help.

WOW! Did you make that or is it available online?

Just flew the Goldwater range bombing practice mission and did the same pop up attacks. The TD box stayed where it was supposed to so I can only assume the previous bug has something to do with the NTTR mission. Maybe too many static objects are causing the bug? Jeroen, I think I read something about the problem you have. Have a look at the bugs section at the top of the F-16 forum. I think ED are working on fixing it.

Interesting Shaun, glad it's not just me. I'll try to repeat another pop up attack sortie with a different bombing range scoring mission.

Hi, I just finished a little session on the NTTR bombing range with the 476th range objects. I practiced pop up attacks and encountered a very frustrating problem that I was unable to fix. I have encountered this before btw. So, here's what happens. I fly out to the range, 6 x BDU33s to practice pop up attacks. My steerpoint coordinates match the target coordinates and when i approach the target I can see the box pretty close to the target. However, after about 4 passes I noticed that the steerpoint/TD had crept away to a different location. - the steerpoint coordinates were still displaying the correct location on the DED but the steerpoint/TD box was not on the target - I had BDUs, no mavericks, LGBs or any other munition or targeting pod. - The SOI was never turned to the HUD as far as I can tell. I cycled between CCRP/CCIP/DTOSS/STRAFE with the MSL STEP button. - I tried entering different coordinates and back to the original target one but no matter what i did it would not set the STP/TD to the correct location Is this associated with the STP bug I've read about? And has anybody else had this same problem?

Same, I get an error.

+1 Should be easy to code and record audio for. A brake channel check option would be cool too.

Not that promising? I'm surprised you say that. What is it that is underwhelming? I'm quite excited about the Ampere's arrival. Of course I will wait for the benchmarks first before buying but surely even the 3070 should beat the 2080ti in performance?

They would have mentioned Cyprus if the maps covers a part of it so I wouldn't get your hopes up too much.

Bollocks? Ok dude, do you fly in real life? I've been flying for 17 years and I can guarantee you that seeing an airliner from over 10 miles away is not easy. I'm not talking about contrails, of course those are easy to see but seeing the actual aircraft is not. I'm not saying it's impossible. Anyhow, this thread is about the patch. PM me if you want to discuss this further.

Can they tell us which military airbases are included in the 32 airport list?

Damn, that sucks dude! I wonder why it would have dropped. Especially with your 2080ti. Which Nvidia drivers are you running? I rolled those back to an older one because the newer one gave me perf issues.

VR performance has significantly improved with the last couple of updates. I run SteamVR SS at 170 now, before it was 130-ish, every setting left the same as before. FPS is the same or even better. For the guys talking about seeing planes out at 18 nm...man, in real life it's hard to spot another airliner (like a 737 or A320) at 10+ miles! There is no way you can easily see a fighter jet that far out. Use your radar/datalink to get an idea of where you expect to see the other aircraft then use your eyes to scan that patch of sky to spot him.

Ah ok, so can I just copy the whole RANGE script and paste it at the bottom of the RAT script?

Funny that you mention that, I noticed my steerpoint coordinates changing randomly when I am doing CCRP/CCIP bombing practice. I wasn't sure if it's key binding or a bug.

Can someone please explain to me how I can get 2 scripts to work in 1 mission? For example, I want the RAT and the Range scripts to work.

Quick fix patch coming next week.

Thanks Frederf. I had another look and was not able to rollback. I'll be patient until a fix comes out. In the meantime...back to Falcon BMS

Just another flight to see if there was a way to fix any of the bugs. The only thing I managed to get is the tadpole in NAV mode...but ONLY if the steerpoint is manually created or an existing one amended. Grim reapers are the Viper beta testers? no frikkin way, I don't believe that.

I'll have a look at how to do a rollback with Steam until a fix becomes available.

So I should uninstall the whole open beta setup I have and go through the full stable download again to make the viper flyable again? Nonsense, not gonna do that. And what if I want to use the other features that have been added to other modules? And anyways, we should report these bugs so that they can get fixed.

And in Steam?

The jet is now completely unusable. As per the bugs posted in this thread and this one: https://forums.eagle.ru/showthread.php?t=276475 without the tadpole the NAV mode is useless and you can't really plan an Air to ground mission. With the dim HUD and blocked FCR you can't do air 2 air stuff.

Hi ED, can you please take a look at these F-16 bugs that appeared with this last update. They make the Viper completely unusable. Will there be a hot fix for it or do we need to uninstall this last patch? How do we uninstall the last patch with Steam? https://forums.eagle.ru/showthread.php?t=276475

Just had a little flight and yes, I also get all of the above issues. So annoying, got a flight planned tonight but won't be able to now. Is it possible to roll back to previous patch?