=475FG= Dawger

It helps if you understand what Q codes are. They originated with the need for shorthand methods to ask and answer questions using Morse code. So each three letter group is, originally a specific question and response. QNH is the question "What should I set on the subscale of my altimeter so that the instrument would indicate its elevation if my aircraft were on the ground at your station?" and the response "If you set the subscale of your altimeter to read ____ millibars, the instrument would indicate its elevation if your aircraft were on the ground at my station at ____ hours." In real world use, you hear something like " Descend to five thousand, QNH 1011". You could ask "QNH?" and the response would be "QNH 1011" The time is implied as currently. QFE is similar except the datum used is field elevation instead of Mean Sea Level. QNE is a different sort of question and answer. If you were to say "QNE?" , you are asking " If I set my altimeter to standard pressure (1013 or 29.92) what would my altimeter read at your station?". This question has no practical use in aviation. No will ask for QNE. You will occasionally hear "set QNE" and "QNE set" (More often the crew will use the actual numbers) as part of a challenge and response between flight crew members. In communication with ATC, if you are assigned a flight level, you are expected to set standard pressure on the altitude upon crossing the transition altitude in the US and immediately elsewhere.

QNH, QNE and QFE in common aviation use are altimeter settings. When you set each one they indicate your distance vertically from a particular reference datum. QNE is standard atmospheric pressure , 29.92 in hg or 1013 mb and results in your distance above the standard atmosphere datum, referred to as your "flight level". QNH is the local atmospheric pressure reduced to altitude above Mean Sea Level at the measuring station. This is what is meant when someone says "altitude" QFE is local atmospheric pressure corrected for temperature. The altimeter will read zero at the measuring station elevation and this is referred to as "height"

Actively standing by...

Turn off VOR-ILS control unit and the noise will go away.

Did you edit missionscripting.lua after updating?

A few hours in the F1CE have convinced me you have a good team working on flight model. It feels like a swept wing jet. Also, the wings remain attached during BFM And of great importance to me, you have granted access to the auto start lua. That alone earns it a hearty “buy” recommendation to my group. I hope other third party developers follow your lead

There is a simplified gear lever checkbox in the special tab for the F1. It bypasses the need to move the guard separately.

On Caucasus, some work and some don't. It isn't a bug with the F-5. Its the map.

TACAN in DCS is very hit or miss. Which map are you using? I recommend NTTR for TACAN Also, TACAN in real life is line of sight and in DCS. More details would help diagnose the issue.

I agree with you. Many real world fighter pilots agree with you. Aerospace engineering, physiology and materials science agrees with you. However, if you persist, you will discover that you must "git gud" and that this "feature" is entirely realistic. I have given up any hope of this being reversed. I have also given up paying money to ED until it is fixed or every other module is treated in the same manner. Maybe Aerges will entice me to spend money again once I know for sure their new module does not suffer from the same "feature" but even then how do I know it won't receive the same treatment at a later date?

I sent you the possible fix. I missed a syntax error in your botsay.lua. Its almost always a simple syntax error.

You can build your own setup for less money and attach it to your flying chair/cockpit. You don't necessarily need a sound card. You can split off signals using Voicemeeter, which is what I do. It was absolutely worth the money and effort.

It should outperform the F-5 at the same weight and, hopefully, the wings will remain attached.

Interphone is how you talk to the ground crew if they plug in to the aircraft at an exterior jack. It is not a radio.

I don't have the A-10 but with easy comms OFF, if the radio you are transmitting on is not tuned to the correct frequency, no one will answer. The same thing should apply to the interphone. This is an approximation of how it works in real life. The visibility of the receiving station in the menu doesn't mean you are correctly tuned. As far as the ability to talk to the "ground crew", I personally don't think there should be any limitations. 98% of the time the crew knows what is to be loaded before the crew gets to the aircraft and the aircraft is already loaded per the mission. For a rearm/refuel, again, the ground crew would already know what you want/need and/or hand signals can easily convey the required information.

There are two errors repeating. Both in scheduler functions. One is probably in MOOSE from the line number, the other script is unknown (line 35 is producing the error). If you send the mission, I will look at. Barring that, it is just guesswork.

Please, no. As another implementation clearly demonstrates, modeling “fatigue” is not a good idea. Fatigue disappears when adrenaline is pumping.

Rapid oscillations from negative to positive G greatly reduces the positive G required to g-LOC, IRL. If this were modelled, the stick pumping would disappear. That is the missing piece here.

Are you running MOOSE in the mission? I would suggest you structure a simple message sent from the mission to make sure everything works if you are already running MOOSE and getting an error. If you arent running MOOSE, then your problem lies there. The unedited botsay requires MOOSE for the event handlers

Your reading comprehension is lacking. Or you just didn’t bother to read. The mission editor is, essentially, already standalone. You can do exactly what you want to do by running a second instance of DCS.

I still have to switch from ME to Multiplayer and join my server to actually fly the mission running on the server as a client. A third machine would save that step but one would need to a third DCS account and pay for the maps used on the server for ME. The ability to join an MP server directly from the ME with a password to bypass exterior view restrictions so I could fly around in F11 and use F2 and F6 would be handy in my particular case. I don't know if ED has any motivation to do such a thing. I normally don't need to "fly" to debug. I create AI for the player slots and and debug in the mission editor using time acceleration and only load it on the server when it appears mostly bug free.

You describe essentially what I do with separate server machine with the mission on a drive accessible by both machines. When I need to edit the mission, I stop the mission on the server, edit the mission on my client machine, and restart the mission on the server. I don't know how much demand there is to run two instances of DCS on the same machine, one as the server and the second as a ME only. I would think you could probably make that happen without a special ME version by running a server only DCS instance and a regular client instance on the same machine. You could symbolic link the map location so you only need one install of the maps for both instances to save storage space since the server version grabs ALL the maps every update.

I don't see how a standalone ME would resolve the need to upload and start an edited mission on a remote server. Basically, it seems you are looking for a Gamemaster functionality with the ability to save what you Zeus into the mission. The script for that already exists although I haven't used it.

The closest you can get is a server on a separate machine with the missions on a shared drive. But you still have to stop the mission on the server to save your ME edits. I have this setup and it works pretty well. However, if your edits are all in separate lua scripts, they can be edited and reloaded while flying without ever stopping the mission. The key is to avoid the need to edit using the ME.

You will need to post your script that calls the DSW.exe