rtimmons

after launching go to full screen mode with Left Alt-Enter. Then you will have full screen on your monitor and you will be able to click on stuff with the mouse like normal. slyfly

Right Alt-J to exit the aircraft you are in or enter the aircraft that is selected in the F2 view. I think it is called the "Jump In/Out" command in the control setup. slyfly

I believe it is a bug......not sure if it has been reported but it is pretty obvious so I assumed it was. Anyone know? slyfly

use left-alt + ' and you can get the screen up slyfly

yes...create the folder, put the file in it and restart DCS World. Yes ... delete it and restart DCS World to revert back. That's how I do it anyway,.... slyfly

I do not use any curves or tweaks with the extension and it works fine for me without them. Actually works better without them... slyfly

do a forums search on user name Sahaj and you will see several option including Sahaj's extension that I bought. slyfly

I use a 5 1/2" extension and the Spit fly's really nicely for me. Also the helicopters and other aircraft are much easier to control. The Warthog stick is very stiff and was making my arm hurt so I tried the extension and would never go back. Plus the stick in the Spit has a very long throw as well. I just hate the braking system :) slyfly

VampireNZ, Thanks for clarifying that.....Joytokey is not needed if you use Voice Attack. slyfly

I had this problem and finally found a good solution. I have always had problems using the voice command sleep mode because I would need to make a command quickly and forget I had the voice commands disabled. If I left the voice commands active I would have false commands triggered and often eject myself. I used the qualifier phrase "Voice Comm" before every command (Voice Comm Radio On, Voice Comm F10, etc,) to prevent misinterpretation and that worked well for background noise but not when I talk in Teamspeak. Apparently my voice triggers false commands very easily when I talk in the mic. So the solution was to enable Teamspeak Push to talk while simultaneously disabling voice commands via push to talk. The problem is the VAC software does not accept joystick input for the push to disable. It only allows key strokes. I use L-Alt +F5 to disable the VAC. I can use my joystick button 4 to enable Teamspeak so I needed the joystick button 4 to simultaneously send L-Alt +F5. I tried using the Target Gui for this but as soon as I made a new configuration DCS-World saw it a a new joystick and I would need to re-map all my controlls in all my aircraft plus it no longer sent button 4 to Teamspeak so I needed a better solution. I tried Joytokey and it worked perfectly. It allows you to set the joystick to send pretty much anything while also sending it's original mapping to it's original location. So nothing changed in DCS-World or Teamspeak/Discord but now VAC gets a "Push to disable" while Teamspeak or Discord gets a "Push to talk". I played online while talking on Discord for hours last night without a single false command being triggered. Hope this helps anyone else having this problem...I use VAC but when I checked into Voice Attack it seemed to have the same issue of no joystick input. I did not try it though so I am not sure.... slyfly

The good thing about having DCS 1.5 and 2.0 is that you can copy the config files from one to the other or use one to back up the other. I never completely lost a file before but if I did I would prefer it was the keyboard. I only have one mod since my keyboard does not have a right windows key but I try to avoid changing keyboard inputs because they are so common between different aircraft. slyfly

Sounds like your input file got corrupted or overwritten so the default file is being loaded. The files or at user/Saved Games/DCS/Config/aircraft type/controller type/. Look to see if the file is still there or if there are more than one, if you are selecting the right one. The files have dates that help identify when they were created/modified. If your old file is not there anymore then you will probably need to re-create the profile unless you can find one in a backup or something. slyfly

Go to the DCS start up screen and select settings. In the "Special" screen go to the Spitfire section and oyu will have a setting for Auto-Rudder and also Takeoff Assist. It will be much harder to keep it on the runway with 0% Takeoff assist and no Auto-rudder but that is the way most of us do it. slyfly

I wouldn't get close enough to shoot a shilka or a geppard with guns or rockets in any aircraft. They use radar to aim their guns and they will kill you. slyfly

When you get used to the way it flies it does really well in close in combat. You can get the gun lined up easily because it spins so easily and you can fire missiles close in by putting the circle on the target and firing. The thing is it is so effective at long range you really don't want to get close in very often. slyfly

I always approach them while doing maneuvers because if you fly striaght at them they will shoot you. You can avoid their fire a number of different ways but you do have to maneuver. Only line up for a shot for a short period of time. Turn away from the target after firing and continue to maneuver. Make them have to move their guns and they won't be able to hit you very easily. I often approach them in a circular pattern. Changing dive pitch also works. Some of both is even better. Circle in on them from a distance until they start firing and when you see the tracers you can see how to avoid them as they are moving their guns trying to follow you. When you get close in if you are taking heavy fire don't line up for a shot. Instead try to scrape them while maneuvering and live to make another pass. slyfly

That's what I use but I have a 5 1/2 inch extension.. slyfly

I use VAC voice commands and my mouse left handed. I have a horrible time communicating in multiplayer though. I can't type blind and if I use Teamspeak I always have problems triggering false commands if VAC is enabled. I am down to a very minimum list of available commands and I have to say "Voice Comm" as a prefix to every command and it still seems to find ways to screw me in flight. I need a way to use a joystick button that enables Teamspeak and disables VAC at the same time. But VAC doesn't take joystick commands so for now I just have to vocally disable VAC when I use Teamspeak. I will say that mouse clicking cockpit controls in VR is much easier/better than using Track-IR as is almost every other aspect of the flight except communication. slyfly

["Part of my issue is that the nose seems to float all over the place, even with perfect trimming. This makes getting a straight sight on a target pretty difficult."] This does not sound normal from my experience. Do you have a good joystick? I do have floating nose when firing in level flight but when diving for a ground target it is pretty stable. slyfly

It was new to me....I liked it very much..thanks There is also a series on Netflix called Plane Resurrection that is really good if you haven't seen it. It has an episode on the the P51 and also one on the Hurricane among other vintage aircraft. slyfly

I convert missions to WWII versions all the time. Just change all the aircraft to warbirds and SAMs to AAA. Convert any modern helos to hueys and MI-8's to shoot at for fun. You can kill the the APC's and AAA's with your Spit cannon but you will need the P-51 rockets for the tanks. slyfly

When i have had this kind of problem in the past it has been because controllers were preset to control my rudders etc. that I was not aware of. I always get a set of warthog preset settings that I have to undo before things work right. Check that two different things are not assigned to the rudders in both the AXIS controls screen and the regular rudders control screen. slyfly

Pull back the throttle and the RPM.... I always interpreted that 2700 RPM thing to be just for the approach but not touch down. slyfly

Having just gone through all this myself I think you are just coming in too fast and touching down too fast. The P51 takes longer to slow down in the air than a 109. Try slowing down to 110 to 120 mph before you cross the runway threshold. Then don't let your wheels touch down so fast. Don't "fly into the runway". As you slow down you will have to keep pulling the nose up to keep from gliding down onto the runway and stay a couple feet up until you can not keep it up any longer and it just falls onto the runway. Your stick will probably be way back at that point. if you bounce you will probably lose control because you are too fast. I always try to remember that takeoffs and landings take much longer in a P51 than a 109 or a Spit so you need extra patience waiting for it to get up to speed on take off or to slow down enough for touch down. slyfly

I have good success with the huey door gunners.....you can stay up high to avoid ground fire and they will eventually kill all the ground targets. The MI-8 gunners never hit anything so I have stopped using them. slyfly