lemoen

The A10C makes it a bit easier because the HOTAS is integrated with the TPOD and everything. You can also make mark points and stuff directly from HOTAS, for later automatic slewing and destruction. With the Harrier (and I guess the Hornet) there's a lot of MFD buttons pressing going on, no markpoints and the whole system is rather clunky in comparison.

I'm sure IFF AND Flight model AND weapons AND some other stuff can be done in parallel. Its not like they all code on one thing and then move onto the next thing. Personally I'm not sure what I'd like next. I'f I had to choose between, say, RWR or IFF I'd choose the RWR first.

Most airfields on these maps are civilian IRL and some of them don't exist at all (e.g. Novorossiysk)

Multiple threads.

The carrier is bugged at speeds over 20knots causing the planes to skid around like crazy. Slwo the carrier down a bit and add some wind to make up for it. ED: Please have a look

yep, too far

Short stick like that, start with curves of 20 for pitch and roll and see if you like it. Throttle should be linear, rudder to taste.

Don't have it yet, haven't tried but I was under the impression the virpil software could do stuff like this? Sent from my iPhone using Tapatalk

In short, all else being equal: smaller pixels -> Less AA needed -> less GPU more pixels -> More GPU and RAM foveated rendering (eyetracking) -> more CPU, less GPU, ram Next Gen is going to have more pixels and smaller pixels. If the resolution doubles (4x pixels), we'll need 4x the processing power if everything else stays the same, however, with eye tracking and foveated rendering you'll gain a factor of x2-x3 back ito performance under ideal situations, you will pay for this by using more CPU (to run the eye tracking and the foveated rendering stuff). That said, I strongly doubt that even a doubling of resolution up from our current Rift/Vive standard will allow us to get flat panel fidelity in VR. You will still need AA to get rid of jaggies at 2k per eye. However, it will be immensely better than what we have today. Now, DCS. DCS in general is heavily bottlenecked by CPU as it stands. Most of us today cannot get VR to run at 90 fps (except under special circumstances), even with a 1080ti which is the fastest GPU available. Basically, unless ED does something about the CPU load (Vulcan?), next gen VR will only give us better resolution but poorer performance.

Currently working on a LSO grader script. Stand by.

You have to zoom in quite a bit to get anywhere near realistic acuity. Remember, our eyes have a wide FOV and a 1 minute of arc "resolution".

You could program it to start slow and go faster the longer you hold it. Sent from my iPhone using Tapatalk

Multiple threads about this already

I think it stops aligning if you disable the parking brake (squadmate said this happens)

I think those have not opened yet, the Mk82AIR is selectable (ballute), Mk82SE always opens the fins I think.

I'm guessing, change the "f-18c" part with "spitfire" and see what happens :D

There's no mini-stick version right now, unsure when / if they'll produce one. The current model is currently in limited production and they announced today that most pre-orders will ship after July 9

I thought the finger lifts are for getting it from Stop to Idle?

Someone once told me: "The quality item remains long after the price paid is forgotten." I ordered the T-50 stick/base/throttle a week ago, so I guess I'll just wait a bit more. Nothing else to be done on my side. Hopefully the stick and mounts come sooner but I'm not holding my breath.

It is not only double racks. Happens when you load a single mk82 / 83 onto a pylon. QTY and MULT set to 1. Each pickle releases 2 or 3 bombs, depending on which pylon was selected (looks like) Track here: https://www.dropbox.com/s/zxayurzkspmlv7h/Pickle%20Bug.trk?dl=0 [url=https://www.dropbox.com/s/zxayurzkspmlv7h/Pickle%20Bug.trk?dl=0][/url]

The back left elevator doesn't have a collision model - The changelog.

What does AI stand for in this context?

Real life.

If you have 2 cores running at 100% then you have your answer. Your CPU is running as fast as it can already. Reduce things that causes CPU load -> view distance, shadows, mirrors.

Do you set it in the waypoint editor (Set tacan or whatever). In our squad mission we have it as 74X, so it is possible.