Terry Dactil

So you want the rudder surface to move some time after you move the rudder pedals? Why? This does not happen in real aircraft. Having lag in a control system is the perfect setup for getting over controlling and pilot induced oscillation.

Yes. Is it actually on your computer? After you purchase, you should get a 'click to download' pop-up window. You should see this immediately after purchase or the next time you start DCS. You can check for a successful download with ... Module Manager > Installed > Campaigns To fly the campaign use the DCS Main menu ... where you should see ...

Have a look at this thread ... The Spitfire was designed as a short range interceptor with only about 200 miles range. (that is out and back, not a radius.) It is a bit over 100 miles from Tangmere to Le Havre. You can see why drop tanks were invented.

Rigid joystick.f3d You should be able to extract individual components from this assembly file. If not, let me know and I can did out the individual flies.

Voice Attack can be useful for this sort of thing. I have the HOTAS flap lever for incremental flap movements, but if I want to go directly to any particular setting I use a voice command. I had 'Betty' remind me of the limiting speeds when I was learning to operate the P-51, and this can be removed if no longer required. Here is the Voice attack command structure for anyone interested. ==================================== When I say: Flaps [UP; ZERO; 10; 20; 30; 40; 50; DOWN ] Variables used: Actual position, Selected Position ==================================== Start by checking if flap position value has been initialized Begin Integer Compare : [Actual Position] Has Not Been Set Start Loop : Repeat 5 Times Press Left Shift+F keys and hold for 0.1 seconds and release End Loop Flap lever must be at zero now Set integer [Actual Position] value to 0 Say, 'Actual Position value is initialized to zero' (and wait until it completes) End Condition ==================================== Now get the Selected (desired) position Begin Condition : [{CMDSEGMENT:1}] Equals 'UP' OR [{CMDSEGMENT:1}] Equals 'ZERO' Set integer [Selected Position] value to 0 End Condition Begin Text Compare : [{CMDSEGMENT:1}] Equals '10' Set integer [Selected Position] value to 1 Say, 'Limit 400' (and wait until it completes) End Condition Begin Text Compare : [{CMDSEGMENT:1}] Equals '20' Set integer [Selected Position] value to 2 Say, 'Limit 275' (and wait until it completes) End Condition Begin Text Compare : [{CMDSEGMENT:1}] Equals '30' Set integer [Selected Position] value to 3 Say, 'Limit 225' (and wait until it completes) End Condition Begin Text Compare : [{CMDSEGMENT:1}] Equals '40' Set integer [Selected Position] value to 4 Say, 'Limit 180' (and wait until it completes) End Condition Begin Condition : [{CMDSEGMENT:1}] Equals '50' OR [{CMDSEGMENT:1}] Equals 'DOWN' Set integer [Selected Position] value to 5 Say, 'Limit 165' (and wait until it completes) End Condition ==================================== Now calculate how many steps in what direction are required Set integer [Move] value to the value of [Selected Position] Set integer [Move] to [Move] minus [Actual Position] Now send the commands Begin Integer Compare : [Move] Is Greater Than 0 Start Loop While : [Move] Is Greater Than 0 Select down Press F key and hold for 0.1 seconds and release Set integer [Move] to [Move] minus 1 End Loop Else If Integer Compare : [Move] Is Less Than 0 Select up if negative Start Loop While : [Move] Is Less Than 0 Press Left Shift+F keys and hold for 0.1 seconds and release Set integer [Move] to [Move] plus 1 End Loop End Condition Set integer [Actual Position] value to the value of [Selected Position] Write [Blue] 'Selected {INT:Selected Position} Actual {INT:Actual Position}' to log Say, 'Flaps {CMDSEGMENT:1} selected' =========== END ========================

OK. Here they are .Rigid joystick STL files.zip (If you need to make modifications and use Fusion360 I can probably find those files too).

Yes. Seems that all the theme music files have been moved All of mine don't work anymore.

My not-so in-depth analysis ... The P-47 has rather complex engine management issues. The Spitfire is great airborne, but a bitch on the ground. The P-51 has good handling both air and ground. Plus you get bombs and rockets to blow things up.

More info that may be of interest. I stuck an oil rig platform in the sea to mark the position of a 10 mile final for RW 28 at Manston. Any time I called 'inbound' I receive an accurate heading and distance to that position However there was never any notification when I arrived there and I just overflew the position.. Next, I used visual sighting of the oil rig to turn onto the final approach heading Now everything worked! At 5 miles I was cleared for a visual approach and to call the tower. The tower cleared me to land when I requested landing. The tower also cleared me to find a parking spot at the end of the landing roll. The big problem is that WW2 aircraft with no radio aids have no way of knowing when they reach the approach fix. Real world ATC give an instruction to turn onto final with allowances for intercept angle, turn radius/speed etc. If ED could just tell me when I had one or two miles to run I could probably work most of that out myself.

Thanks for the replies. I set up a mission where I started on the runway center-line and 30 miles out. The vector I received was runway heading for 20 miles. It looks like the vectoring could be to a point 10 miles out on the runway center-line. I'll check from some other directions and see if that still applies. I guess there will be a few adjustments needed for magnetic variation and turn radius if not on a direct approach. It is starting to make more sense now.

I am in a P-51 with no radio navigation aids at all, so an initial approach fix for an instrument approach is useless to me. (even if it existed then - this is WW2) It can't be a visual reporting point if it is over the water. All I want to know is the direction to the airfied. So where do I find this 'any map' which will show me where I am being vectored?

Some more information: I made a small mission where I flew on a track of 270° inbound to Manston. Along the way I announced I was 'inbound for landing' and also requested vectors. The resulting ATC vectors were OK at long range but rapidly deteriorated as the range decreased.. In fact, near the coast the vector was to go somewhere behind me! Here is a plot of the bearings I was given and which wanted me to go some distance to the South East of Manston. I checked the map coordinates for Manston and they are correct. However, DCS obviously thinks Manston is somewhere out to sea.

I have been exploring the channel map in a P-51 and preset 4 of the airfield radio frequencies using the mission editor. Communication with a selected airfield (using Vaicom) works fine, but if I request a vector (navigational assistance) or announce 'inbound for landing' then ATC will give me a completely incorrect heading to fly. The error is generally around 60° but can be 180° sometimes, and is never anywhere near being correct. It is not a great problem as the kneeboard and waypoints woks fine for navigating, but it would be nice to have ATC vectors working too. Is anyone else seeing this error?

Over the internet? I am amazed. How do you do that?

It is already there ! There is a 9000' concrete runway at Manston. You could use that.

Apologies to those that had a problem with the 3d printed replacement gimbal. All I can suggest is that you modify the Fusion360 file and make a new STL file with the clearances required. I did not have any problems, but then I did not use it for very long before abandoning it for a new project. As the F-16 module was now available, it was obvious that I needed a rigid side stick to go with it. I have completely removes all all of the base and replaced it with a length of plastic tubing and two strain gauges. (not quite finished yet, as programming the USB descriptor makes my brain hurt!)

Go to the topic below. It is exactly what you need.

You can also use batch files so clicking one icon on your desktop restores things to normal. Here are mine ... @echo off :: Shut down all the programs started by DCS Updater :: Use quotes if there are spaces in program name taskkill /IM "DCS Updater Utility.exe" /F taskkill /IM VoiceAttack.exe /F taskkill /IM OVGME.exe /F :: taskkill /IM joy.cpl /F taskkill /IM OculusClient.exe /F :: :: Move audio back from headphones to the computer :: Requires nircmd utility program installed "D:\DCS WORLD\UTILITIES\Windows Audio.bat" :: replacing ::C:\nircmd\nircmdc.exe setdefaultsounddevice "Acer X34" 1 ::pause :: See how it all went :: then cls exit .. and the other batch file that resets the audio to the desktop. I have made that separate now, but it can be included in the first batch file (Check device manager to find the name of the audio system on your desktop). ::@echo off C:\nircmd\nircmdc.exe setdefaultsounddevice "Acer X34" 1 :: exit

Don't use curves? Some posters here seem to have no idea about what they are saying. Curves are often designed into control systems. There is even a name for the bit that does it: the 'differential control unit'. Have a look at this clip which applies to the FW-190 control system. FW-190 curve.avi

I have had a request for the stl files for the collective lever, and I have put them here in case anyone else is interested.. Collective lever.zip Be aware that this was designed around an old length of aluminium tube I had in a junk box. The outside diameter is 22.3 mm so it appears to be some 7/8" tube that was used before we went metric. In case you can't get tubing this size, I have included the Fusion 360 design files so you can make any changes required. Two 6mm bolts and some rubber tubing for the handgrip will also be required. Collective fittings v18.f3d

Suggest checking all your axis controls. The default values have things like the rudder also wanting to control pitch, roll and throttle. The default settings bind anything that can control an axis to everything it can find!

I have been testing things and shifting between various missions in both Open Beta and Stable. I am now getting instances where the main program is not using the Saved Games (modified) file and the view is now that strange one looking forward from the left wing root. Until we find the cause (it may be the large file size for a mod) all I can suggest is to just make the changes in the main file in CoreMods.

That would be normal for repeated key presses. I use Voice attack so that press and hold a hotas button gives me the rear view until the button is released and it goes back to normal view. When I press joystick2 button 17 the result is... Press Left Shift+F4 keys and hold for 0.3 seconds and release Start Loop While : Joystick 2 Button 17 Is Pressed Loop Continue End Loop Press F1 key and hold for 0.3 seconds and release

Sorry, there was a backslash typo error in the path. Try using CoreMods\WWII Units\P-51D.lua

Not additional entries, just alter the existing ones and and it should work. The hard part is finding the location of the chase view code and then setting a good position to look from. Lots of stuff in the cockpit wanted to get in the way. So far the only other one I have done is the TF-51. I'm hoping others will have a fiddle with the code for other aircraft and publish their results here.