Ziptie

Should add, that many do not have this file in their folder - as this to my knowledge is something that is user created. The developer of our dynamic mission created this for me, and works a treat. I can PM you the file if anyone is unsure of how to do this, or simply copy the contents of mine in plain text and you can simply "create" the autoexe.cfg file. Takes less than 30 seconds. Works a treat and no longer have the issue of rendering, but still suffer from the draw distance issue that has presented itself in 2.5.6 Cheers, Don

Work around for fellow A10C pilots until they fix the issue: Turn APU on Turn on APU Gen Shut down engines (so INS alignment stays and other systems are retained) Request rearm/refuel Perform engine start cycles Turn off APU Gen and APU Off to the sortie you go Cheers, Don

Work around for fellow A10C pilots until they fix the issue: Turn APU on Turn on APU Gen Shut down engines (so INS alignment stays and other systems are retained) Request rearm/refuel Perform engine start cycles Turn off APU Gen and APU Off to the sortie you go Cheers, Don

Do you have the JHMCS (HMD) on? If so, the AIM-9 seeker head will follow that if you have master arm on and AA mode selected.... If you do, try turning off the JHMCS (not just using the RECCE switch as it simply removes the display while leaving the system active). When I have it turned off completely, the seeker head stays bore sight locked until I uncage the seeker head. Cheers, Don

I have noticed that a slight adjustment of the DDI brightness will change from yellow to green (slight adjustment of it). Not sure if this is intended behavior of the color on displays, or an adjustment that needs to be addressed internally from ED. Haven't flown the F/A-18C lot 20 in real life, so can't have a RL reference. Cheers, Don

What warning are you getting? Assuming you are getting a master caution light? Anything displayed on the left DDI? Home fuel, engine overspeed, inlet icing? I am not experiencing any "constant engine warning" after 2.5.6 and the aircraft seems to be performing as expected. PS: I have of course noticed the "dirty" exhaust from the Hornet, as others have stated as well - also noticed it on the A10C (although it seems to only be noticed from the port/left engine on the 10C). Cheers, Don

Yeah, and I clear those after each update as well, along with the download/torrent folders as it is wasted space. When it moves them to backup, it is the same thing as me having them as a "copied file" - so nothing of benefit there. Works just fine. Cheers, Don

There is currently an issue where the FLIR "can at times bounce" after using WPDSG via the HSI or SA page. What I have found to get around that issue is: (assuming you have aligned the JDAM, if not do so) MASTER ARM on AG MODE selected OSB pushbutton to select JDAM OSB pushbutton TOO OSB pushbutton JDAM DISPLAY OSB pushbutton MSN WPDSG to slave FLIR NWS to undesignate waypoint target (should leave FLIR at location) FLIR SOI SCS in direction of FLIR display for PTRK mode TDC slew to target TDC depress (to designate target) Verify coordinate entry HSI will now display bearing and launch zone Weapon release Cheers, Don

Indeed you can, have been doing it for quite some time now. Good advice, Notepad++ is the way to go when changing .lua files (or others). No, anytime there is a repair or update performed, it will overwrite changes to this file (or others). I have copied the parameters for the F/A-18C and the A10C, so I can quickly replace the originals when a repair/update has been performed. Cheers, Don

The TCTS pod, A/A mode, OSB pushbutton SIM, select gun. It actually does simulate the "hits" on the HUD, although I haven't found a way to dissect / process that information after the flight. From what I have found, you just have to rely on the pilot who employed the gun to be truthful in calling his "hits." We have loaded the training 9x (catm I believe they call it), but don't seem to get any further information from that ordinance. Would certainly like to hear from someone if they have had better success with trying that. Cheers, Don

Yes, this is the same for aircraft as well. Also, even static units (like a red bull air pylon) is impacted by this issue. Hopefully something that they can/will address - especially brutal in VR. Cheers, Don

Crazy, how big is the Oculus update? My DCS 2.5.6 update was 31 gigs..... Cheers, Don

Although the logic is backwards (from what it was prior to 2.5.6) - I can confirm that this fixes the issue of things not rendering in the left eye: options.graphics.stereo_mode_use_shared_parser = true This line goes in the autoexe.cfg file in your saved games folder. However, the draw distance is still compromised after the 2.5.6 update..... But one step at a time right? Cheers, Don

On our server (and on connecting clients) - we are experiencing MASSIVE data usage spikes and consistent high data transfers. Sending 10-30 Mbps and Receiving 10-30 Mbps. This is absolutely not normal from what has been experienced over the last year or more with DCS. This might be worth investigating as well, along with the other current issues. "OpenBeta" 2.5.6 Cheers, Don

Yeah, I have also had to turn the terrain textures to low. Unfortunate. Cheers, Don

I haven't used it personally, but someone I was flying with yesterday (in MP) said they used it - and that it lofted, but didn't seem to be as substantial as the sparrow in loft mode. Can't confirm or deny first hand. Cheers, Don

Yes, I have also noticed a hit to performance while using VR. Shame, as they had just gotten it dialed in not that long ago. Cheers, Don

I was just referencing when you didn't actually even have to boot the Oculus software, as any program running takes CPU/GPU/RAM resources away from your system. It's a negligible amount currently, but with things ramping up on DCS' side for resource requirement - any little bit helps so of us. Cheers, Don

My VR is functioning, CV1 user here. That being said, DCS is no longer rendering all images in the L lens. This used to work: options.graphics.stereo_mode_use_shared_parser = false but now no longer has the effect it should. I use OTT, with settings to disable Oculus mirror and some other settings, but certainly have to have Oculus Home open. Too bad, as it used to function without it being open. A change that happened along time ago now. Bummer. Have you tried running a repair for DCS, to see if that sorts out the issue of VR not functioning? Cheers, Don

options.graphics.stereo_mode_use_shared_parser = false This no longer serves it's purpose, so something has been done "internally" to counteract this solution, which was working prior to 2.5.6 .... Hope there is a simple and speedy solution. Cheers, Don

+1 Also experienced this, and in daytime operations as well Cheers, Don

+1 They have enabled that setting you were talking about where it only renders something in one eye. just tested it. Visual cons at 30 miles, closed left eye, still visible, closed right eye, no longer visible. It is a render problem with the left eye, which is why shadows do funny things, air and ground targets are inconsistent with their visibility distance..... Very frustrating. Cheers, Don

Don't recall them as able to select prior.... But could be wrong. The program name has certainly changed though. Cheers, Don

Not my experience, certainly on a “busier” server like one of the ones I have flown with you, in terms of players and/or environment. Single player, marginal. At the end of the day, the more programs running, taking CPU, GPU and RAM - the more resources are being utilized from a system. Cheers, Don

I use Oculus Rift CV1. Originally used Steam, which then launches SteamVR, on top of having to have Oculus software open, then DCS software. Using standalone, only requires Oculus and DCS software. Instantly frees up resources of your PC. I don’t recall the exact FPS increase, but it was between 5-10 FPS. Take into account that FPS increase, along with reduction of CPU and RAM usage of the additional software running while using Steam, equals more performance. Then you can use Oculus Tray Tool to further extract performance gains. I use OTT for super sampling (1.2), disable selective USB suspend, disable oculus mirror, disable Rift power management and probably forgot something else in there..... Cheers, Don