112th_Rossi

Freestyle. I just tried to keep disciplined by staying along the runway centreline

Pct4c-NFAzQ I'm doing a series showcasing all the DCS modules in a mini aerobatics series. I'm rubbish at aerobatics but I gave it my best shot!

F16C would be great.

Recently did a bad weather IFR landing in the L39 yFulK4G959M

TRsOS9LvEbo Thanks Polychop! Amazing work!

For some reason when I play back a track (only tried L39) I get a large square box in the bottom left with graphs. It looks like some kind of debug tool? How do I remove this?

4.2 flight hours between failures? That's a bit low?

The F5E carries an IFF transponder. Will this be working? So at least other aircraft can identify?

It's a great reference material. I've been looking around seeing whats what ready for the F5

Thanks chaps!

So at briefing I can say: Head 175 for 20 miles, Head 270 for 10 miles etc?

So when there are two dials on the HSI, what are they for? Course is an overall direction?

The F5E only has TACAN and HSI navigation. How is this going work with waypoints in the ME?

I see on the HSI there is a heading knob and a course knob? ELI5?

Doesn't make sense to me. The A10 was designed from the ground up for long loiter times and to be put up against armoured targets.

What was the point of an A-16 when the F-16 was a capable mud mover anyway?

g3B18x2hTWU

I bet you never get invited to parties!

That's awesome. Great reference too. Everything is well laid out and looks simple to use.

A bit of everything. I like these simple straight forward aircraft. I find no satisfaction flying a super-computer with wings. And if I can down an F15 then thats cool.

Yes. The only processes that can be threaded are processes that will work asynchronously. That is non-essential tasks that other processes do not rely on (ie block). I would imagine Air Traffic Control processing could be async and also loading textures async could reduce slow down of the overall sim.

Developer here. One thread can raise an event which is read by the main executing thread. These events are subscribed to by executing code (it doesn't matter what thread they are on). When it hears the event being fired it picks up any parameters that are passed over by that event and acts on it. The event handler is known as a delegate. EDIT: Also, CPU cores have NOTHING to do with threads. I wish people would stop thinking this.

Events.

Apparently it's a bug that ED need to sort.

yFulK4G959M Hope you enjoy! :)