Knock-Knock

It would indeed. Some clever naming to a trigger zone for example: StartCamera_300_+2_45 300 being heading to look and +2 is orientation, 2 degrees up, and 45 is FOV.

Actual fixes and updates to the Harrier. There has been nothing since July, except the training missions - which were available on the forum for testing.

For single player its the unit with lowest ID that is active, in the order of air, land, sea, and the camera is always looking north. But in MP, clients will see something entirely different. Havent figured out how it picks the unit. So an air unit can have a higher ID than a land and/or sea unit, and it will be the unit seen.

Nah, I have a hard enough time with my brains random failures :)

Posting this again. 29% of earths surface is land, of which 33% is desert. Land surface area is 148 940 000 km2. 49 150 200 km2 is then desert, or a 7000 by 7000 km square. But no, I dont think I have come by any. Checking google maps, the only green areas are on the coast of the Caspian Sea. Some near the Iraqi border too.

Isnt only at longer ranges. All the way to 0, I wouldnt get any contact on the radar in the above described jamming scenario.

Goddammit I love clean Vipers!

And just for the hell of it, I get the same result against MiG-29S. Lock it with F-15, when jamming, jump into Hornet. Scope is clean.

Seems its jamming. Just did a test with Su-27 and J-11's in pairs. One with jammer, one without, headon at 100nm separation, spawning in with 2 min interval. First forced ECM always. No result. I would pick them up at 78nm in the Hornet. Control with F-15, and I saw no jamming on radar. Funny thing, it didnt detect them until around 50nm. Then put AI back to just standard CAP, and started with F-15. As soon as I lock one with ECM pod, it would start jamming. I then jumped into the Hornet (air starting all btw), and scope was clean. Was face to face with them, scope clean. But when I do it with just Hornet, lock them up so they would be jamming, I dont loose track. I can still track them when breaking lock again. And I can repeat this as often as I like. Start in F-15, wait for them to appear, STT lock the contact on the right (has the ECM pod), and it'll start jamming. Jump in Hornet.. and nothing, even within 78nm, and all the way in to my nose. So maybe its a late start Hornet into a jamming environment or something? Attached the test I used. Hornet vs Flanker ECM.miz

Depends on the definition. If its totally custom design, then I mind. If it is a Danish F-16A Block 10 livery on a F-16CM Block 50, or a some classic Navy designs from 60's and 70's slapped on a Hornet, also fine with me, or 'soon' to come US Navy and Marines F-4S on our F-4E, also very very welcome :)

In the VR section? :) They usually add the module once it reaches the stable branch.

I think its all the canopy and HUD (glass) reflections (the baked and the cockpit global illumination one), it makes them very milky, especially at X angle to the sun, and this is washing the image out, reducing contrast. Try to pause and switch to ALT+F1 and see the difference with and without canopy/HUD. And its something you really notice if you have to run the game without shadows due to performance. It gets a lot worse without shadows. So imo, to help this, ED and 3rd party devs have to reduce canopy/HUD opacity and reflections a great deal.

Oh that is indeed good stuff too, the Spyglass zoom. Thank you for that too :) 3 quick ones. Normal, regular zoom, spyglass zoom.

Oooh, nope havent. Thx for the headsup :thumbup:

Same, and on the Mirage too. So seems a more general DCS MP sync problem.

What a difference that little change makes. Perfect, thank you :thumbup:.

Well it does, but wont have on initial release.

Im skipping the pre-order of this one. Not for some cause or anything, but because I see this one as a very good bottle of wine, and I dont want to taste it before its actually matured and as intended. This is because the F-16 is my favorite jet, and my most anticipated module of all, and I wont have that spoiled.

A desks speed output isnt high enough to fulfill the 'need for speed' requirements.

You have to assign / use the 'UHF Radio Microphone Button', under 'UHF Radio ARC-164 Control Panel, Throttle Quadrant'. 'Communication Menu' button is only functional on the ground or with 'Easy Comms'.

You basically beat me to it. I was just coming back from reading the report (well some of it), to post: What is this, a witch hunt? This is insulting the developers on a very high level. Not cool. Dont care what has or hasnt happened. If I was at the receiving end of this, I would be fuming.