The multiplayer server list load is something we are working on. I have tested some fixes recently and hopefully they will be in a future patch.
Its important at the moment to allow time for the server list to load, wait until the refresh icon turns yellow before looking for the server.
Strangely enough, since my venture into OB and online then back to stable, both my sim and mission start times have decreased noticeably.
Unsurprisingly the previous noise on my Index screens has also been vastly reduced since my recent spring clean of the headset.
So now, despite having a clearer view in Pico 4, Iām back to flying DCS in the Index. Much simpler and easily good enough with the 4080 driving it.
Thing is, Iām sure I could up the settings, but Iām not sure which ones would have the biggest impact on my experience (i.e. make it look better), as the obvious ones are already maxed. MY GPU has lots of headroom - the CPU not as much.
Can anyone tell me, if I learn the DCS Viper and itās systems, will I be okay using that info on the BMS aircraft?
I know there are some things in DCS that arenāt in BMS - such as Link16 - and maybe vice-versa, but Iām talking of the stuff thatās in both. I think DCS tute missions are far better for learning aircraft systems (at least the ED ones are - the Mirage F1 tutes can be a bit of a nightmare, for example) and though Iād like to fly a BMS campaign, I donāt want the headache of learning the systems in VR in that sim (due mainly to the poor cursor control).
If needs must, Iāll do it all pancake with TrackIR, but Iād rather not.
I havenāt touched BMS in many, many years.
While I enjoyed the campaign in F4 the graphics just finally got too outdated for me. The terrain was never even as good as Strike Fighters and thatās saying something.
Iāve had the Viper since release and while it wasnāt worth it the first year it is now. Itās second only to the Hornet in versatility now and the HTS makes SEAD better in the Viper. I spent a long time flying the Hornet almost exclusively, went to the Viper, went back to the Hornet for the carrier/Harpoon/SLAM stuff, and now Iām ready to go back to the Viper.
While I can understand the feeling of not wanting to duplicate, I think the Viper was worth it. YMMV
Yes for the most part. I havenāt flown BMS in a long time but when the DCS F16 came out the controls where still second nature from my time in Falcon 4.0 and BMS.
There are a couple of tiny bothers, but to summarise a post I made ages ago (I doubt it would have turned up in search), youāll be fine. The bothers are:
the startup is different: if you start the BMS Viper like you do the DCS Viper youāll probably hot start it and definitely forget to set the air source and cook the electronics, and have a FLCS fault that you canāt clear (or at least I couldnāt without shutting the jet off again). And if you try to use the BMS checklist in DCS youāll get stuck when you canāt complete the prestart checks (again, at least I did).
the low speed handling in DCS and the handling when you abuse the limiters āfeelsā more as if thereās a real jet under the FCS (to me, this is subjective and you wonāt be flying in these regimes often).
The actual combat operation of the jet is so similar that you can bring muscle memory from one to the other.
Aside from a few of the missing HOTAS commands the only complaint I really have in the DCS Viper is that baked-in deadzone/breakout force/whatever in the controls. The BMS Viper responds perfectly to controls, but the DCS Viper seems to have this weird delay and then it overreacts to your input. I canāt pull specific G to save my life and AAR is as busy as doing it in a Tomcat.
I have the same issue. Ended up putting a significant negative curve on, but it still doesnāt fly as precisely as it should (compared to the Hornet, say). ED should put some work into this, perhaps give players the option to use a conventional joystick setup.
Also in landing gains, it requires considerable back stick for the FPM to not creep down. AFAIK in landing gains no backstick should be required for the FPM to hold the flight path angle. In this mode, the FLCS should hold pitch angle, aka it should trim itself for zero pitch rate. In DCS, this just isnāt the case.
Thatās great info thanks - I actually use the separate start-up procedures for each one as per the relevant sim manuals as if they were different aircraft so that wonāt be an issue.
*unfortunately, so far itās the only procedure Iāve learned properly for each one! Though I do know how to use the ICP & DED
Thatās an interesting observation - Iāve always used a TM Warthog stick with a short extension mounted in the sidestick position for the DCS Viper, and a centre mounted G940 (again, with extension and lots of mods) for everything else.
I do know what youāre talking about, but I think I assumed it was because of yhe Warthog stick not the DCS Viper flight model!
The reason I deleted that post is because it was an assumption of mine that, at second though, canāt be true. If you fly the AoA bracket, the AoA is always the same regardless of loadout.
I can say something like:
An F-15E should be able to land on a carrier because itās built to withstand a higher landing stress/weight blah blah blah (even though Iām just b/sāing).