Zeus67

Initial development build. Later we got a real USMC pilot who explained to us that everything is green except for the moving map. The point of using green is to control cockpit brightness when using NVG.

NAVFLIR camera is fixed.

Folks, When you report a bug, we try to reproduce the circumstances that made that bug appear. Sometimes we can do that and sometimes we cannot. And squashing a bug that refuses to appear is quite difficult and some people think that we are calling the liars, when we believe that they are experiencing the difficulties that they claim. Please when reporting a bug, we will ask that you do the following: 1. Write a short explanation. 2. Save a track file, if possible. 3. State what were your actions at the time the bug appeared (i.e. "I was firing rockets."). 4. State what mission were you flying. If the mission is custom made, please attach a copy (this can be omitted if the track file was included). Thanks for your help

This is a known issue. For the time being click on the "Left MPCD view Export toggle on/off" and "Right MPCD view Export toggle on/off"to enable them in cockpit.

Which one? The top one is for the RWR. The middle one is for the Chaff/Flare system. The bottom one is for the jammer when loaded.

The MPCDs are in color but they only use green for their compatibility with NVG

It is a development holdover.

Just to be clear, you are using keyboard buttons to handle the NWS, right? We will check the issue.

That shouldn't happen. We'll check.

when in the cockpit use the [Left MPCD view export on/off] and [Right MPCD view export on/off]

TGP/TPOD is WiP.

Because still WiP

TDC axis slew control are not enabled yet.

When you are finished getting all the abstractions you need, I will include them in the default.lua

Okay. I did not know that. I guess I'll have to purchase a warthog HOTAS as well.

The TPOD is still WiP. Having said that, in this version the aircraft does not take steering cues from the TPOD. It uses its own onboard sensors to do that: INS, ARBS or IRMAVs.

hmm. There is a flaps switch up and a flaps switch down key bind. Check VSTOL Controls * Flaps Mode Up (STOL - AUTO - CRUISE) * Flaps Mode Down (CRUISE - AUTO - STOL) * Flaps Power Left (OFF - ON - RESET) * Flaps Power Right (RESET - ON - OFF) * Water Mode Up (LDG - OFF - TO)' * Water Mode Down (TO - OFF - LDG)

The way this feature works is as follows: 1. When you start DCS it will call home and verify the activation status of your mods. 2. It will save a copy of this activation status in your PC. 3. If you cannot connect, it will just check the list and go from there. 4. The list expires in 3 days. 5. On the fourth day it will try to connect again to renew the activation status list. So if you are not flying multiplayer, you only need to connect to ED once every 4 days.

Press the "undesignate target" HOTAS button. That should clear the seeker.

What do you need? Blueprints? I'm afraid those are neither open source nor publicly available. A set of cockpit drawings are in the publicly available NATOPS and in the Pocket Guide. But no dimensions detailed, you will have to extrapolate/make educated guesses.

Please tell me which mission and airbase it is so we can change it.

View distance is the main FPS hitter. Experiment until you get a setting that works for you.

These are my setting for my GeForce GTX970 with 4GB VRAM. I have a rift but it is disconnected because it is not ideal for development purposes.

I will advise to reduce the viewing distance to 50% and test for the mean time. We will check the problem.

That looks like server overload.