Falconeer

No, because the F-16 doesn't have such feature

what is is your range set at? 3000m?

This doesn't worl for AMD users? I have the same issue with RX7900XT in the menu's. Everything is very jittery/laggy to the point where it causes tremedous strain on the eyes. Once ingame everything is ok, however i noticed since last OB update, more screen tearing while flying and i haven't touched any settings since weeks

Agreed, it's utterly dog<profanity> the way it is now

Sadly it's not resptricted to that throttle only. There are numoures threads in the wishlist and controller/bugs section asking for a more controllable antenna setting. Either ED doesn't care or it's very low on the priority list (even how freakin' annoying this is)

It also might be related to: And: Seems there are more problems with MT not utilizing multicore properly

I also stepped over from Nvidia (3060) to AMD (RTX7900XT) and i had the problem my Windows kept installing it's own drivers, instead of using the AMD ones, causing al sort of issues First make sure your Windows updates are not pending (yes, sometimes this is an issue!) and up-to-date. Download the lastest "stable" AMD Adrenline drivers Try going to "device manager" and select display adapter, right click and remove device. Then reboot Windows in safe mode and run DDU and make sure to select the option for Windows NOT to install drivers. Seriously just click it, Windows will screw it up!!!! Then reboot and install AMD drivers, but only the recommended stable build. Don't install beta drivers and only install the recommended part and avoid optional stuff. For VR i would first recommend lower your expectations. VR needs a powerfull system to run decent graphic settings fluently. Setting 1 or 2 settings to high really hurts on average PC i would also recommend higher frequency of 90Hz (72Hz minimum) if your setup can handle it and lock FPS to 45fps and play with your ingame settings to keep a constant 45fps (gives much smoother experience) I personally run a Ryzen 7 58003XD and 64Gb RAM and have 90% of settings maxed out and till have occasional stutters

I'm having the same problem in VR. When i'm in the pilot seat, George menu is on top of compass in IHADSS. If he finds vehicles, the target list is in the middle of the IHADSS. When i'm in CPG seat, the George menu is on the bottom of the screen of the IHADSS. Like i said, i'm running VR on a Quest 2 at max resolution. My 2d screen is set at the lowest possible resolution and if i take my VR goggles off, i saw that the George menu is at the correct position. Since i build a new pc a couple of days ago, it's a fresh install of the latest bèta, MT version.

I don't have problems with the loading times. But i do have 64Gb RAM. For MP, i think 32 Gb was recommended a while ago, especially on the larger maps

Same here, i have a powerful system, but frames drops and starts to lag close to the ground and in forest areas. Flying over a forest at 7000ft or 1500ft is a huge difference in terms of smooth gameplay. Doesn't matter if i set it to low or ultra settings, it keeps lagging/stuttering in those areas. If i'm higher up in the air, i'll easily run at 60fps on ultra/high settings, down low at the forrest and urban areas, it drops till around ~35fps and lags/stutters. I tried every seting there is, in Meta, AMD and DCS and none of them seem to fix it completely AMD Ryzen7 58003XD @ 4,5Ghz AMD RX7900XT 20Gb Corsair Vengeance 64GB Ram DDR4 @ 3600Mhz DCS on Samsung M.2 SSD with 7000 read and 5000 write speed Meta Quest 2 with cable plugged and tested in USB 3.0 port

In the Warthog throttle, there is a detent in the idle setting. If i pull against the detent, the engines go to idle. If i pull them beyond the detent, the engines shut down (cut off setting) which is how it works. I can imagine that for joysticks without a detent, this would be an annoying issue, as pulling the throttle levers back to idle, results in shutting down the engine

I told that before, but got no response

See answer below

correct

I talk to F-16 pilots almost daily in my work and had a chat with one of them explaining this issue. He also says they don't need to be that precise on the bomb fall line. Hence the point of dropping LGB's is to drop close to the target so the seekerhead picks up the signal. And because i work with F-16's myself i have acces to all the T.O.'s

And this is exactly why it's not fixed. Because this kind of info won't be avaiable to the public. May i suggest contacting your SME (atleast a F16 pilot)

there are enough reports already made about this issue and more than 1 topic as well If the FPM is not perfectly centered on the bomb fall line, the bombs won't release, which is wrong. It used to work fine couple of patches ago and got broken/implemented wrong

Pre order.....

im not in a hurry as a "second" rate Steam costumer

I'll wait till it gets to 50% discount on Steam

Yes, i have the error right now and error 503. Also it says my modules authorization are expired and disabled! What is going on here??

How many GBU-12's can be loaded on the F4? Probably less than MK-82, due to the GBU being longer, i assume they can't be mounted on a MER?

Maybe in America yes, but not so much here

It's Razbam mess

Thats not on you or ED to decide where i decide to purchase. They made the step to go on Steam with DCS World years ago and now they are creating a divide with this nonsense! So you either release it on both mediums, or you don't, simple!! You give 1 side a 30% discount on preorder, than you give it to the other side aswell or don't do it at all!!