JimmyWA

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?

Happened to me last night on MP - I have the latest OpenBeta.

I thought I had the same problem. I'd bought a new modem, and was blaming that. I didn't get the update message when I started DCS. I checked for an update, did the update, and problem solved. It would appear that in the hour between unplugging the old modem and putting the new modem in place, the update had occurred - Murphy's Law.

Great job, The only addition would be to change the throttle detente from off to idle before trying to start the engines.

I've been searching to see if this topic has already been discussed, but could not find it anywhere - the search words return at least 40 pages, and I stop after around the 5th page - but I wanted to share this. I have a top of the wazza PC with an older RTX2080ti video card, which I overclock. However, even by setting all the DCS video settings to low and no shadows, my FPS could be as low as 8. I then stumbled across a couple of articles, and in SteamVR went to settings, and changed the Render Resolution from Auto to 48%. This sets it much closer to what the actual resolution of my HP G2 is. This means in the Per App setting, I leave DCS at 100%. The results are startling. I am now getting around 60fps on both single and MP. I then added shadows, and even MSAA, and I was still getting nearly 60 fps. I can fly in DCS using VR again!

I’ve found my performance has gone downhill since the beginning of the year. From my testing DCS only uses around 12GB and the Windows system will always access the pagefile no matter how much RAM you have. That is why I have an NVME as my C: drive and DCS sitting on an SSD. Last year I resolved all my DCS performance issues by buying an RTX 2080ti, but after some DCS updates this year it feels like the CPU has a lot more to deal with, and that might be the bottleneck? I use process lasso but even that doesnt help these days. As a result, I’ve stopped flying DCS for now.