Shahdoh

"Take off assistance" is just an aid to help keep the aircraft straight while on the ground. Once in the air, it does nothing. You need to use Rudder to keep the ball centered unless at the prescribed power and speed mentioned, then it neutralizes itself. OR you could use "Auto Rudder" if you do not have rudder peddles (or equivalent control). If you want to change the speed/power settings where the aircraft naturally stabilizes, you can mess around with the on ground rudder trim setting, but this is ill advised unless you really know what you are doing and why. Good luck

You want to use "Switched" with "Part of Coalition in zone". Will only trigger once when the 1st of the coalition enters the zone, then will wait till the zone is clear, before it will allow it to trigger again.

The reason they are not fixing it is they are supposedly working on a whole NEW weather system that will address this and many other weather issues. Though, this has been in the works for quite a while now....

Around 2-3 years back, a tv channel advertising for the actual Blue Angels at a local event used a small clip of the DCS Virtual Blue Angels in their montage. You couldn't hardly tell the difference. Wish I could find it

Though, by trying to simplify it and using inaccurate description of what is REALLY going on with the controls, only confused him even more. Stick to the facts and there will be less confusion.

To back that up, from Page 35 of the P-51 Flight Manual: The propeller RPM is controlled by the Propeller Control lever on the throttle quadrant in the cockpit. The propeller governor automatically controls propeller pitch to maintain a constant speed between 1800 and 3000 RPM, depending on the Propeller Control setting. The propeller cannot be feathered.

Except that is wrong Campbell, you do NOT control the propeller pitch in the Mustang. The Prop lever controls the RPM. Prop pitch is automatically adjusted to maintain the manifold pressure set by the throttle and the RPM set by the prop lever. You can have a set MP and RPM, go to F2 view and watch the pitch of the prop change (on the data tape) depending on the aircraft's speed and load on the engine

I too have experienced this bug.

Deadzone is best used to get rid of twitchiness at the center caused by an inconsistent signal from the hardware. Use as little deadzone as possible, otherwise you are just reducing your effective control range.

I don't know WHAT value its at, but I do not that it is AT its max attainable pitch that maintains the RPM and MP. DCS will show you that pitch value in F2 view data tape, there, you can see the pitch increase slowly until the aircraft hits is top speed. Never does it decrease to a more efficient pitch angle, only increase.

You are automatically assuming that more pitch will cause RPM to drop, and it will, eventually, once it meets the balance of drag vs thrust. Then the pitch will stabilize. Its at this point the max speed is at. Not at a lessor pitch value, but the max pitch that can be maintained at max MP and RPM.

Yes, but the concept is the same, More pitch at max MP and RPM will result in more speed. DCS is limiting the pitch for an unknown reason at max RPM. Thus the lower than expected top speed at sea level.

Have you seen the pitch angles of the prop of a racing Mustang? They are near if not at MAX angle at that RPM (3000-3250). If the aircraft is capable of more speed, which according to the charts it should be, then the prop pitch should increase resulting in more speed. Increased drag will eventually limit speed increase.

Or programming inaccuracies? In the real mustang, pitch is automatically controlled by mechanics of the system(exactly how, I do not know). Under power, pitch is suppose to increase as long as the engine can maintain the manifold pressure set by the throttle and the RPM set by the propellor control lever, at least until it hits the max pitch allowed. This is not happening at sea level in DCS. The pitch is being restricted for an unknown reason at 3000 rpm. At lower RPM, higher pitch is allowed and pulls the aircraft to a faster speed.

Still looking for why trying to access the WebGui dashboard is not showing the server running on that very machine either by its default port 8088 or one set by the autoexec.cfg file. Operating System is Win 10. Works as advertised on my WIN 7 machine.

In DCS, at sea level, you can get the extra speed from WEP by backing down the RPM to about 2700-2750 RPM. Also, if you manually control your coolant radiator, you can reduce some drag by closing it down a bit. You will need to watch the coolant temp closely to keep it from getting to hot. With these setting, I can get the P51D to maintain 382 mph (332 knots), level flight at sea level.

You are about 8-10 knots slow with the TF-51 top speed, P51 clean can do about 332 configured properly at sea level, level flight, no dive in at your weather settings. (WEP for 67.4 MP, 2700-2750 RPM and manually control the coolant radiator to minimize drag and still keep it cool enough to run for a while.)

I can confirm this has happened to me as well. No dead battery as I fire up the mustang in under 10 seconds each time. Does not happen all the time, in fact only recall it happening a couple times, but yes, you hear the same sound you normally hear for the lockup. Then when you go to start, it doesn't budge.

Thanks, my friend tried the autoexec.cfg but still has the same problem. Server is up and can be joined, but can not connect the WEBGui to the server via the local index file. Says "Server not responding"

What would keep the local machine the Dedicated server is running on from seeing the server when using that machines local index file (..\DCS World OpenBeta\WebGUI\index.html)? Default port of 8088 was entered, we even tried to configure it to a custom port, but no change so took that back out. It works fine on my own machine, but a friend's server is having this problem.

A classic:

I use Winrar and do not even bother to unpack or change the extension, Just assign *.trk and *miz files to be opened with winrar. It will open up just like a folder, from there I can edit the compressed files (without extracting them), when you save, you get a message to if you want to update the compressed files. Yes, and all done. No hassles and less steps.

Yes, and I am saying that we are at those high settings for that whole period. I am agreeing with you that yes, it CAN break in very short order, but that I have also seen it last longer than 30 minutes.

Engine breaking from using WEP is very random. In the racing community we have done half hour races running the engine at full power (67/2700 note: 3000rpm at sea level is actually slower). Yes, about 50% of the time, the engine will fail, but it is not an immediate or sure thing either.

What has worked best for me is when you add the BIG FORMATION task for the non-lead is to set the "GROUP" to the lead first, and then set its position in the formation. A way to verify it linked properly is that you should be able to move the lead, and the other aircraft linked to it (group leads only) will move with it. If they don't, the link didn't establish for some reason.