British_Dragon_14

Me too. Antenna elevation buttons needed re-mapping. Strange.

I can't find the 'Autoexec.cfg' file. What folder is it in? I can only see a 'autoupdate.cfg' file in the main game folder. Shall I just create one? Thanks.

I just switched back to 'System Managed' and it chose exactly 28672 MB. It currently says: Minimum allowed: 16 MB Recommended: 9066 Currently allocated: 28672 MB I wanted to reduce my Pagefile size as I now have 64GB's of RAM. My Pagefile was previously set to 40000 MB. I've also changed 'processor scheduling' to adjust for best performance of: 'Programs.' Instead of 'Background services.' I'm hoping it will reduce stutters. I also discovered that DCS doesn't like it when I overclock my RAM speed. Even if it's just by + 200 MT/s. I would keep crashing in multiplayer servers at 6800 MT/s and at 6600 MT/s, so I reduced it to stock XMP profile 1. Which is 6400 MT/s.

I have no .lua files in the views folder. I just have a bookmarks folder that contains other folders that are also empty. I even checked my older versions of my saved games folder (I have three) and they were the same. Do we create the .lua and what do we call it?

Thank you so much! Brilliant!

Hi! I've just tried to enable Resizable Bar with the latest Nvidia Driver 572.16 and the latest (stable) Nvidia Profile Inspector 2.4.0.8. And the options have changed. Does anyone know the correct settings to enable resizable Bar for rBAR - feature, rBAR - options and rBAR - Size Limit? I've provided an unlisted video here that shows the settings: I assume 'feature' should be switched to 'enabled' but their seems to be another two 'on' options just for 'rBAR - feature.' The other two 'feature' options apart from 'enabled' looks to be two different profiles for two groups of different games. The 'rBAR - options' option has two settings: 0x00000000 0x00000001 (Returnal, Red Dead Redemption 2). rBAR - Size Limit has four options: 0x000000000C800000 (Returnal, Diablo 4,) 0x0000000060000000 (Dragon Age: The Veilgard, Deathloop) 0x0000000040000000 (Red Dead Redemption 2) 0x0000000012C00000 (The Riftbreaker) I haven't a clue what most of these options do. Does anyone know what settings are best for DCS in general especially for VR? It doesn't look like it's just as simple as 'turning it on' anymore. Thanks!

The simulated F-35 Radar we are going to get isn't going to be simulated as it is in real life. Not even close. The DCS Simulated World we already fly around in knows exactly where everything is, the information is already stored in the CPU RAM. The F-35 MFD Touch Screen is just going to give you the information that you already have or what the Server already has that is stored on the CPU RAM. Such as unit type, position & heading, speed & attitude and possibly IFF. I imagine it will be similar to having a cheat menu open on the Cockpit MFD screen as this AESA Radar is so powerful. Giving us huge amounts of data in real time. But Eagle Dynamics needs to model and simulate the speed at which we obtain this information and the limits of the Radar such as angles, blind spots and Ground Radar and some other highly technical things.

My God! What's the range on this Radar? At least 80 miles I see! Crazy! It has over one thousand different Radar sensors that move individually on one plate, that can simultaneously track at least 23 airborne units. This is going to be the new Magic, beaming all of the real time data to other allied forces using technology more advanced than Link 16 etc. The High Definition Ground Radar looks amazing too! No need to visual ID ground units as the Radar and OS does it for you. Amazing technology! I hope we get long range missiles with this as well.

I don't know if it's a recent bug but it seems that the eye-tracking wasn't working with the side mounted extension for some reason. I would personally recommend that people just plug it in directly. Their has been quite a few Pimax Play updates recently and I haven't been in VR for over a month now. I've only just purchased the VR controllers so I'm hoping to try it again ASAP. Maybe with some other VR Contoller type games too. I just received an E-Mail from Pimax. This is just to say that my issue was resolved by doing the above, which was bypassing the extension. Thankyou!

This just happened to me. Thankyou for the quick fix! I clicked on the link and installed and then restarted the PC and then booted DCS and it worked. I had the '0xc0000142' code as well. I just scanned and 'repaired' my PC the other day and it must have deleted some important files. I used 'Advanced SystemCare Ultimate' to clean my PC, if anyone's wondering.

What a nice surprise! I'm personally really looking forward to trying the updated F-16C flight model stall behavior and turn speed and the HUD update, plus the new spotting dots. So many fixes for the F-16C FCR in the last few updates as well! It's just a shame I can't try it out now. Maybe later or tomorrow. Thanks ED!!! Merry Christmas!!!

That sounds amazing! Thanks for this information! I was wondering what 'Handoff Mode' was. I was just trying to imagine what that would be like and it sounds epic! It would serve to immerse us even more into our cockpit sounds. No listening to music in the F-16 anymore when they model that!

Same for me. Edit: It works. I was extracting the files wrong. Thanks

I unplugged the Display port that goes in to the head sets extended cable that is on the left side of the HMD and I then plugged it in directly into the HMD, bypassing the extender. The cable isn't in that picture. It is what the furthest left cable plugs in to, on the left side of the HMD.null

Yep.

Just to let you know and anyone else in the future. It is fixed and it was the Display port cable. Someone told me from Pimax that I should try and bypass the cable on the left side and plug it straight into the HMD directly. The IR lights came on straight away! I have just been testing it in quick missions on Syria and Nevada for a couple of hours just to make sure and it's now fine. I would never have guessed that it was the Display port cable that goes into my GPU. I guess I just need to zip tie the cable to the side now. I've also tucked the unused cable behind it's port to keep it from hanging down.

I have a picture of all my USB inputs that I have access to further up. They are all 3.2. My Crystal worked fine since I set it up months ago. Now all of a sudden the eye tracking has stopped. I tried unplugging absolutely every USB wire and trying every port with the Crystal wire multiple times and I did get the IR lights to come on once yesterday but they turned off as soon as I lifted the HMD up and put it to my face to do the eye calibration. I've been at this for the third day in a row now. I'm going to try to repair Windows 11. I would re-install Windows 11 but I haven't enough space to back up my C drive.

The IR lights and Eyechip just came on as I took every USB cable out. I then started to tactically put the rest of my cables in whilst leaving the Crystal USB cable in it's own HUB (blue left side) on the motherboard. The lights were still on until I went to calibrate my eyes and it turned off again. Thanks.

I have 3.2 ports. Red and blue. I think the red ones are faster but I read that the cable doesn't like the red inputs. My Crystal has been working fine since I've set it up, until yesterday. I tried switching to every port where it would fit on the Z690 Auros Master. It's always worked on the top left one. I've followed the instructions on the Pimax website as well: Crystal Eye-Tracking Troubleshooting Steps : Pimax Support I know the lenses are properly seated because they are auto detected as 35PPD Glass. I'm just about to send a ticket with an export log attached.null

Hi, I loaded up DCS yesterday and noticed that the rendered box wasn't following my eyes after I loaded up a quick start mission. I then uninstalled Pimax and reinstalled (the same version: V1.33.02.01.03 ) and the 'eye chip' in Device Manager was still greyed out and the IR lights were off in the HMD. I then updated Windows 11 and tried multiple USB cable combinations, even unplugging everything except both the Pimax cables, black into red, blue to blue. To see if it was an underpowered USB issue. I only have Blue plugged into Blue usually as I have a USB power box for prolonged Crystal battery life. So the black cable is just left hanging unplugged and I have a powered USB cable plugged into the right side of the HMD. I have tried re-seating the lenses and nothing I've tried from the internet seems to work. I did get it working briefly when I re-installed the Pimax software. I double checked with my camera phone and all the lights around the lenses were on, I re-calibrated my eye tracking with the Pimax software, loaded DCS up and the eye tracking seemed to work in the DCS menu until I loaded up the quick mission in the F-5 Tiger II 'Cold Start: Syria' and the eye tracking stopped working. I've been trying to figure this out all day today and last night.

You used WizTree to open the file? Is that from the Microsoft Store? Is their any word from ED on this? I also noticed the pilot has really low detail textures. Especially the helmet.

It is a file called 'Sounds.edce.' In the Main DCS F-5 folder. I think for new/modded sounds (for ED modules) the files need to go in the saved games folder but if their is no buffeting sound code to begin with, the volume can't be increased.

Oh wow! I just looked in the main DCS folder and it seems that all the ED aircraft modules don't even have a Sounds folder to change the volume in the SDEF files...

Are their any 'SDEF files' where you can change the gain number to increase the volume? Or is their literally no buffeting audio files to edit in the F-5? I change the gain for things like aircraft high-G stress, such as the Viggen and some F-14 'SDEF files.' As I used to rip off the wings in the Viggen without even hearing the aircraft groan.

Wearing thin trainers or slippers may help you when you are in the air off the toe brakes. It can be more comfortable to have your heels on the floor, rather than fighting your own leg weight when doing small movements. Force Feedback Rudders would be great some day!