Terry Dactil

It is even worse as the lower part gets cut off if the text size has been enlarged. It has become completely unreadable for me now. (Text generated by auto start)

You might also find some suitable files on Thingiverse https://www.thingiverse.com/thing:4658260

Same thing with the other covered button ( the Fire Extinguishers and IFF Detonators). Probably someone thinks it is a helpful feature to save a click, but it is not realistic, and I'd like to see it back the way it was.

My setup has the controllers mounted on a large sheet of MDF particleboard bolted under the seat of an office chair. Just about everything has been screwed onto that in some way or other. The Authentikit .stl file is easily modified (in Fusion360) to have an appropriate extension with a couple of screw holes. (The black 'L' shaped thing in the photo). I didn't have any of the small crushable ferrules for non-soldered connections, so I just soldered them in the standard fashion. I did have a problem with the cheap Chinese rotary encoders I used. The connector tabs would break off if bent more than once. The white gunk is to make sure they can't move now. Fusion360 file here to modify as required Rotec backplate mount v2.f3d

The best Authentikit feature is that the replica controls mount on an adjustable framework so that they match exactly with what you see in VR. The improvement in immersion must be enormous! (Unfortunately, I am still using my old Warthog system so I can't do this (yet!). However, all the Authentikot files are free to use so I have taken their elevator and rudder trim files to make add-ons to my setup. Now I am not cheating by using the hat switch trim for WW2 aircraft. Thank you Authentikit )

Thanks funkster. That fixes a problem that has annoyed me for years!

Sorry, this probably was not explained well in the original thread. Mine has been working fine for years. The mod is a direct edit of the textures zip file. It will not work in the usual manner of installing in the saved games folder. I use OVGME to put my edited file directly into DCS World OpenBeta The path is <drive>://DCS World OpenBeta/Mods/aircraft/Spitfire/Cockpit/Textures/Cockpit_Spitfire_LFMkIX_Textures.zip

Try this one .. it's perfect.

It's a bug. I I have the same problem and cannot feather either engine. The feather button does not stick in as it should when pressed. The prop starts to feather while the button is held pressed in, but immediate starts unfeathering if the button is released. (I guess the appropriate authority will have to ground all Mosquitos until this problem is fixes, as they are no longer airworthy).

Brake lever thread is here ...

Congratulations, and welcome to the DH98 appreciation club. You do know that you are doomed now? If you are anything like me you will soon realize that you desperately need a brake lever, RPM levers and a manual elevator trim wheel. null True happiness is having a 3D printer and a BU0836 circuit board /smug mode off (PM me if you want details.)

I have a Thrustmaster Warthog setup and have no problems with the Mosquito. However, I don't use TARGET at all; any fancy button configurations get done with Voice Attack. Can I suggest you try a basic profile without using TARGET. The standard troubleshooting methods I have seen all recommend disabling all mods and add-ons to get a minimized system working, and then adding stuff one at a time to find out what causes the problem. Good luck- you must get your Mosquito working!

Maybe this will help. If you only have text and no musical background during the intro (following the jeep bit) then you need to check the audio settings here as it affects a lot of other things. Once in the cockpit start the engine and when you start to taxi forward you should get instructions to turn left to the runway and you are cleared for takeoff. Further criticism of your piloting abilities will then occur.

It is here ... Options -> Gameplay

Yes. There appears to be something wrong with the ground dynamics of the Mosquito. It gives me the impression that the CG distance is too far back from the main wheel axis and it is like trying to control a wheelbarrow at 100 knots. The slightest deviation rapidly diverges out of control. However, I have no problems with the Mosquito, as there is a simple way to set your control sensitivity. Get into close (very close) formation with another aircraft and adjust your control sensitivity until you can hold a steady position without any oscillating. You will be unstable and oscillate if the control is too sluggish and also if it is too sensitive. Adjust either the curve or the limits until you are stable. I have a huge adjustment set for the Mosquito on my Thrustmaster pedals - Curve =30, Deadzone = 10, but that is what works for me.

OK. I couldn't resist seeing if Voice Attack could handle this problem. It can! I programmed VA to look at a 4 position switch on the stick. Left sets the throttle mode, Right sets the RPM mode. Up and down move the selected levers fore and aft. Short presses move the levers in small increments, while a long press gives continuous movement. It's almost like an analog axis control. It works well on my setup, but some adjusting of the key down times may be needed on othe computers. I noticed that the RPM levers stopped responding if the time was too short. Here is the VA profile for anyone who wants to use it.Moz throttle & RPM-Profile.vap

That is easily fixed. Normally Voice Attack would be set to listen for a command only while a particular (e.g. radio tx) button is pressed. In this case it does not have to listen at all; just respond to some button presses to move the throttles. However, that would be wasting the capabilities of Voice Attack. In my case I use it to get Nigel (my navigator) to set up the bomb arming panel, select fuel tanks, feather an engine, read me a checklist and lots of other useful useful stuff.

Sorry to see you have that problem. It must be hard to fly with throttles like that. I checked using keystroke for the throttles on my Mosquito and Spitfire,. Like you I found it terrible with only 3 or 4 button presses for full travel no matter how short the press. However there is an easy solution using Voice Attack. This is a great program, as apart from reacting to voice commands, it can also recognize keystrokes or hotas button presses and output a different keystroke or button press(or a series of) them. I mapped some hotas buttons to the throttles (num+ & num-) and changed the default key down time from 0.1 second to 0.01 seconds' Success! I It now takes about 25 button presses to get full travel on the throttles. Voice Attack to the rescue once again! I haven't checked this in a mission yet, and it is possible the sensitivity may change a bit when the CPU is working hard. However, it is possible to use a voice command to vary the sensitivity or other parameters if required. PM me if you need help with Voice attack. This could be an interesting project. I'm thinking that if you steal the use of the 8 position hat switch, you could control the Mosquito throttles individually or both together, and also switch to controlling the rpm levers too. Also having a long button press giving increased travel would be handy when large power changes are needed.

I have just flown mission 2 again. Set course much improved. The gaggle circling over the airfield got itself organized fairly smoothly. Flying in formation still pretty hopeless at times. When at altitude and near the bombers my IAS varies from 120 to 180 kts requiring slamming the throttle from full power to idle and back to remain anywhere near. There were also periods when the other aircraft had a 10° nose down attitude in level flight. Agreed. It's a great campaign. (Even with some bugs that will hopefully be all gone one day.)

The version of the Mosquito that we have has the rocket firing button on the starboard throttle. Still, in typical British engineering standards of the time, where fuel system controls are behind the pilot's seat let's improve other versions.. Put all 4 weapon firing buttons on top of the stick; have 3 of them thumb operated; and 2 of them identical and adjacent. What could possibly go wrong? See ED's manual that is hidden at <...> :\DCS World OpenBeta\Mods\aircraft\MosquitoFBMkVI\Doc\DCS DH Mosquito FB.VI Flight Manual EN.pdf (page 119)

Yes. I agree with you. I was quoting from a video that was first on the scene explaining how to set the fusing. I thought 11 seconds delay was a bit excessive for what we needed with the Mosquito at low level, but I thought it may have had something to do with the options available for the arming revolutions. I thought we would need about a 3 seconds delay, but since you can survive with only a 1 second delay I'm all for that now! (Although 270mph for 1 second gets you only 396 feet away from the explosion. Seems a bit too too bloody close for me )

Delayed action bombs are now available. You can set them in old missions using the Mission Editor before starting, or in-game with the ground crew rearm and refuel commands. (Recommended is to use 500 lb MC short tail bombs, Tail Pistol 30 mk3 fuses with 11 second delay. A forum search will give more details).

My navigator's name is Nigel. If I ask him politely using VoiceAttack he will select fuel tanks, feather/fire extinguish an engine, or make selections on the bomb arming pane. He will even turn on the radios if asked, but I need to move over into his seat to do the fine tuning. He will, however, turn the radio volume up or down if asked. Also he will read checklists on request. I can highly recommend VoiceAttack for this and lots of other things, particularly in VR where you can completely eliminate using a keyboard.

Here is a great video that shows just how complicated the DI is. It shows that there are lots of built in errors due to the physical properties of a gyro that need to be corrected. One that may be significant is the correction for the latitude error due to the earth's rotation. This is a small weight on the gyro axis that causes a correcting precession. However this depends on the gyro rigidity, which depends on the gyro rpm, which depends on the system suction, and that depends on engine rpm. I doubt ED would code all of this to any precise accuracy, and it is the one area where the DI can be affected by engine rpm. I suspect that if it is done at all, it is just gyro rpm (rigidity) is proportional to engine rpm, and this is slightly incorrect at low rpm. I don't see this as much of a problem anyway. We don't fly around wildly varying engine rpm. Also the DI is expected to drift over time, and good airmanship requires periodic checking and resetting against the magnetic compass.

More info is on Suntstag's video about the latest update..