JimmyWA

Tonight I flew on the Sinai map, Falklands and Caucauses and George behaved perfectly. Tried the German map again, and George just wants to keep going up!

I have had the same problem, flying in Germany. Except George ascends up to about 2000 feet! Immediately makes me a target when I ask George to go from a hover at 20 feet to start flying. I have attached my track file - this happens all the time since the last update. ApacheUpAndUp.trk

After about the tenth DCS restart I went from seeing 250 servers to getting around 550 servers but still couldn't see Rotorheads. However, on trying a direct connect, this time it worked.

I've just done the latest update and now have this problem where no MP servers show. If I restart DCS I then get some servers, but not all - my squad mates who also did the update can see those servers I can't. While doing one restart of DCS I got this error (see attached file) when I went to start up the DCS launcher.

After watching WAGS latest video on the soon to be released air radar, I think the problem was that the ground radar was picking up some helicopters when it probably shouldn't have been. Based on the radar beam in ground target mode the choppers probably should not be showing up at all, unless they get really close. The ATM should solve the problem/process of the ground radar not picking them up.

I tried manual elevation very early on. It made no difference.

It is probably not a map thing. I'm guessing I just got lucky on the Caucuses and Syria maps when the FCR picked up the KA50s. Am I flying too low and the radar is scanning below the approaching choppers? If so, why did it pick them up on the Caucuses and Syria maps in my testing? Flying MP on Syria last night I had three separate occasions when MI-28s flew directly towards me. I just went through the replay to make sure I hadn't done anything silly, like having the FCR looking in the wrong direction. I didn't. I was hovering at around 60 to 80 feet, trees in front of me, and the MI28N visible, approaching from 12 o'clock. Only one time did the radar pick up one Mi28, showing it as at maximum range on the FCR, although I was sure it was a lot closer. It then disappeared of the FCR until I had to run away. Unlike in the video below, the enemy choppers get a lot closer - like 300 - 500 meters - before they kill me, without them appearing on the FCR. I've tried changing the radar to narrow band and back to wide but it makes no difference. The FCR didn't pick up a friendly Apache flying towards me on my 12 o'clock - until the Apache flew side on at a range of 3000 metres. I then had two more times when Mi28s flew directly towards me and the FCR didn't pick them up. The last time I didn't run away in time and was shot down. Each time the Mi28 was close enough to laser me, but I could not pick them up on radar. The track is too long to upload but I've created a short two minute video that shows the last encounter of what is continually happening.

I should have thought of that! That's how I fixed a similar problem with the Kiowa that just started happening out of nowhere. Thanks - problem fixed!

I can find no binding or control conflicts. When switching from CPG to Pilot without the George AI overlay on, there is no problem switching. If I have the George AI overlay on and I switch to Pilot, it goes into a nose dive. I did the CTRL ENTER to bring up the controls position screen, and that shows the joystick being in the total up or total down position. I also tried using George AI from the CPG, then switched off the George AI overlay, and switched back to the pilot - everything was OK. I have included my test flight. I've uploaded two files. The first shows this behaviour. The second shows me hitting the trim reset as soon as I jump into the pilot seat - but I still crash into the ground. I tried disabling the AI Handover in the Special menu but that just made the whole thing worse - aircraft becomes uncontrollable when switching to CPG. ApacheCrashWhenSwitchingBackToPilotV2.trk ApacheCrashWhenSwitchingBackToPilotV2ResetTrimPressed.trk

Further testing - FCR works as advertised on Caucuses and Syria map. Doesn't pick up choppers on South Atlantic and Sinai map (I haven't tested any others). Why would the map make a difference to the radar?

Thanks for the suggestions. Unfortunately I had made sure I had cleared all trim before I switched out of the pilot to CPG. BUT, as there has been no update and this problem has just started happening, it must be a controller issue on my PC. I will have a closer look at it today.

Was in multiplayer, flew in the pilot seat to the first location, switched to CPG, engaged targets. Got a laser warning, switched back to Pilot and aircraft nose dived into the ground. I tried again and I made sure George was flying fast and higher (the last time I was hovering). Switched back to pilot seat and aircraft nosedived. I tried in a single player Instant Mission - the Hercules one - and got the same result - track is attached. I went into the Special section for the Apache and unchecked the AI George Handover. This made it worse. When I switched from Pilot to CPG the aircraft crashed into the ground. ApacheCrashWhenSwitchingBackToPilot.trk

I've created a mission with an enemy ground convoy being followed by two KA50 IIIs. If I remove the KA50s I can easily find and take out the convoy with the FCR. It is the Falklands map with flat terrain, daylight with clear weather. Unfortunately, no matter if I use GTM or ATM or use a wide or narrow scan, change my Apache's altitude from 50 to 400 feet, I cannot pick up the KA50s. According to the map showing the scan of the FCR the KA50s are within my scan zone. The FCR does not pick up the KA50s at all. They get to withing gun range and shoot me down - every time. I have uploaded a track file. Can you please advise. FCRDoesntPickUpChoppers.trk

Same problem. I still cannot fly the Kiowa properly since the update. The controls don't react correctly after clearing and reassigning. I even went into the Special controls and tried adjusting the throttle setting there. No difference. I also had to reassign the axis controls for the P51 (I only checked a few of my modules). I will try the clear, restart and then reassign for the Kiowa tonight. What a mess!

I noticed that after the update the new launcher defaulted to ST. There is no way to change this besides manually updating the shortcut. I imagine that a lot of people are now flying in ST without realising it, and probably blaming the performance drop on the new update - my testing showed that DCS starts up on my PC in around 55 seconds in MT compared to 1:20 seconds in ST (after the update). Can we please have the option of selecting to run the MT or ST option from the new launcher? This will make it easy for non-technical minded flyers.

Hi, I set the ROE to free and have tried using both burst types. I set arm to on. I can fire rockets and guns, but the ai gunners won't activate either in SP or MP. I can jump to position 4 and fire the gun manually - I cannot get to position 5. Can you please advise? Here is a short track file. I've had other types of targets that fire back, but set this to fuel trucks to make it easier. Can you please advise? Mi8NoFire.trk

I’ve always turned on the batteries, requested startup, started up then requested takeoff - getting a positive response to both.

Well done on the entertaining missions. Once airborne I fly to the friendly task force overflying each waypoint. I change to channel 10 but get no traffic or option to communicate with anyone using the radio. I’ve circled the troops and landed next to them but don’t get a cue on when to attack the bandits. I attack and wipe out the bandits in the ravine but when I return to base and switch to channel 2 there is no option to request landing, just the option to abort takeoff. I land and end the mission and get draw, and a score of 50. Completed twice now and skipped so I can progress. should something have triggered?

In mission 3 the helicopter starts off overweight - beyond the flyable limit - and Im finding I have to reduce fuel and weapons before taking off.

And it turns out it was all my fault! Just got the Varjo Aero and hadn’t used light houses for many years - previous headset is a G2. When setting up SteamVR I put in 1000cm instead of 100! That’s why I was miles above.

Solved. I'm not sure why my joystick button didn't centre the screen as it normally does, but hitting Num 5 brings the menu back into the normal position in VR. I'm unsure why, with the VR headset powered off, it goes into the strange 3d screen (as shown above) instead of the normal 2d. Is this because of the latest update?

I have since deleted the options.lua file and this time run a full repair (while sleeping on the problem I realised I'd only done the quick repair). Running Non VR it comes up with the normal menu. With VR selected and the VR headset powered off, the menu screen appears - not an empty hanger, but in a strange VR type window with the right hand menus off screen. This means I have to click on the exit icon on the top of the screen which always makes DCS do a cyclic restart - it won't shut down - and ask me for my password. It has always done this over the many versions over the years. It is why I only exit using the right hand menu. When powering on the VR headset with VR selected, I still get the empty hangar. I've attached a screen shot of the menu produced with the VR headset powered off and VR selected. Previously, with the headset powered off, the normal 2d DCS intro screen would appear instead of this. Note the window is out of focus because I had to alt tab out of DCS to be able to take the screen shot.

Hi, After searching for a fix, which for others appears to be to delete the options.lua and run a repair, I did this twice and it has not fixed it. I flew after the update yesterday and made no changes when I shut down. Today, I am unable to fly in VR as the startup screen is a hanger. Previously when I powered off my VR headset, the game (with VR selected) would go to the normal 2d screen and display the initial menu page and I could fly in 2d. Now, with VR selected in the options.lua and the headset powered off, the startup screen on the 2d screen is the hanger and no menu. When I went into the options.lua and disabled VR, the game (with the VR headset powered off) then boots normally onto my 2d screen. After the repair I changed no other options except for enabling VR which then causes the hanger problem. I am unable to run DCS in VR. Can you please advise.

I’m pretty sure it is the general shadows setting. Turn it off and the darkness goes away. https://youtu.be/x3E-ygd4Vpo

Thank you for what must be an inordinate amount of time working on DML! It is a brilliant add on. In case someone else has this problem. I've just spent hours trying to work out what I was doing wrong. I had read the manual - yes, truly - and wanted to setup a FARP zone. I placed my DCS FARP heliport, FARP, then created a trigger zone extending a little way out from it. When I went to run the mission I kept getting the error [string "FARPZones = {}..."]:247; Parameter #3 (point) missed.... I ended up removing all the optional parameters, still got the error. I triple checked I was loading the correct modules, overwrote them again in case I'd accidently put a corruption in the DML modules while copying. I wondered if it was because I didn't have the trigger zone right on the zoomed in all the way FARP zone. I looked at the function in the FARP.lua. I tried to work out what was different from my mission to the example one. Finally I noticed that the example mission had a much larger trigger zone than I had in my mission. Mine was set to 800, the example was around 7000 from memory. I went back and changed the trigger zone to 7000 and with just the FARP declared - no optional arguments added - it fixed it. It makes my FARP zone a lot larger than I wanted, but hey, it works, and I will see how low a circumfrance I can go without getting the error again. I couldn't find anything about this in the large manual, so if I missed it apologies, otherwise can I suggest you add a warning about the minimum size of a FARP?