noxyd

Guys, With this week's update, a lot has been fixed, but I have an issue with the CMN Neutral (PCA Select) binding. When I push this button (knowing that 530 was preselected on the PCA), I go back to nav. The only way to have the 530 displayed on the HUD is to select another PCA item and reselect 530. If i switch to Magic and then back to CMN Neutral, I lose the 530 mode. Do I do something wrong ?

Well, to me FBW does not have a specific « should feel », as there are thousands of ways to program FBW computers, from very little to very much “intrusive”. Airbus vs Boeing “philosophies” are quite different on that matter for instance. Totally agree that the Mirage feels more synthetic, but the result is way better nose authority at low speed for instance, as well as being able to recover from a stall within seconds. I put the F16 in a flat spin at 0kts at 20,000ft, couldn’t do that with my Mirage ! It’s a different wing of course but I’m sure you see my point.

Pretty much all radar issues where fixed with yesterday’s update. I didn’t have the time to test it all, but it seemed way better. On a side note, I tried the F16C which is great, but it felt nowhere near our Mirage in terms of flying quality and maneuverability!

The SVI mode doesn’t work well for me either despite showing 20nm range on the radar...

God it's hard with the new radar... Feel like I'm blind! Need a lot of relearning everything... I can confirm the bug, the target's vector is taking random directions. I also have kind of a target at the base of the radar from time to time, like if it was right in front of me at 0 nm. Looks like a bug as there is no one. Question : New SVI now scans until 20nm, is this a bug ? We also have the radar elevation line directly on the HUD, but sometimes it's not correlated to the elevation indicated on the radar display : which one shows the right information ? It's hard to spot the elevation on the radar display, because on the left side we now see the 4 bars from 1 to 4, but not the elevation itself so it's kind of a guess. Just my preliminary thoughts after a 3 hours session online... !

Hi folks, With the last update I saw great improvements in image quality. I use to have artifacts while taxiing on the wing edges as well as missile heads, it's all gone now! I'm flying the M2K. Not sure if it's thanks to DCS update or Oculus... Are you seeing the same thing ? Cheers

Get to know your strengths and above all you enemies’ weaknesses and you’re good to go my friend !

It works, thanks :) So one should not forget to select 530 on PCA before entering a fight ! I liked my previous setting with only two buttons and possibility to cycle between magic and AA gun, it was faster ! (I think the cycle also worked with the 530...) But I guess I'll get used to 3 buttons! Thanks and safe flying!

Thanks Jojo; I do not use keyboard shortcuts neither, but did replace the lua file anyway. Maybe I shouldn't have... So : - PCA store 2 to select 530 : OK - For Magic / AA Canon what function do you use ? - If I understand what you said I also need a third button (binded to PCA store select) to exit from Magic ? Thanks again

Hi guys, Previously I had one button that cycled between Magic and AA Canon, and another to select 530. I understand that this is gone because of the bug. Now when I bind magic to a button and 530 to another, only the last one works (unable to select the other one). Can you please share your settings ? Are you using STORE SELECT of MAGIC SELECT for instance ? Thank you

Great to hear for us Mirage pilots ! Knowing that a new hire is dedicated to the aircraft and that the AdA is providing feedback this quickly is encouraging and will for sure help us put F18s down even more easily! Cheers to the team; keep up the good work!

You can adjust the brightness of buttons with a knob next to cabin lighting knobs.

Thanks BitMaster, I’ll check out IBT-v2. Because it was stable once in game, I did not think that OC could be the issue. I guess we learn every day! I have to say that I’m still wondering what make the server selection stage that greedy on resources though!

Agree with most comments, great improvements on image clarity and cockpit readability and sharpness. I can read the M2000 fuel gauge and bandit altitude on radar from default position at PD 1.2. Performances are excellent without changing previous settings in use with my CV1. The downsides to me are comfort and FOV : CV1 was just plug and play, did not have to adjust anything each time. I find the sweet spot harder to find and narrower. I also feel that FOV is significantly reduced with more blurry edges. I cannot tell if this is because of IPD or not, but I feel I'm going to need to adapt to the headset (was more natural on CV1 for me).

Guys, the problem for me came from my cpu overclocking. It’s now solved. More details here : https://forums.eagle.ru/showthread.php?t=241245

I have yet to see my RAM utilization at 100% even in MP. However, I finally found where my issue was coming from. How I got there : after having tried pretty much everything I could think of I loaded default settings in BIOS and crashes just vanished. So it turns out my CPU overclocking was causing the issue, despite being stable in Prime95 and Aida64 ! I just raised cpu VCore by 0.02V and i’m good to go know. So hint for Overclockers out there : best stability test for your OC so far is the DCS server selection page in VR!

Good afternoon, I'm getting random (but persistent) crashes at server selection stage. If I can make it into a server, I can then play for hours. However if for any reason I go back to the role selection page, I will most probably encounter a crash. I tried lots of things, including : - uninstall/reinstall nvidia driver - uninstall/reinstall DCS world (open Beta) - setting pagefile as suggested in other topics - uninstall/reinstall Oculus software - disable XMP profile in BIOS - uninstalled Asus GPU tweak and any other GPU monitoring software - No crash in non-VR mode I'm starting to loose hope... Here is a log of last crash that happened at server selection. Any help would be much appreciated. Thanks dcs.log-20190518-224836.zip

Some updates on my side on a potential solution and cause : I reinstalled my nVidia driver (complete install, no a basic reinstall) which seemed to have resolved the crashes. Shortly after (excess of confidence I guess!) I reinstalled Asus GPU Tweak 2 tool (my GPU tool for monitoring and overclocking) which I had deleted while searching for a potential cause. Crashes reappeared right after that (had like 10 crashes while trying to join MP servers yesterday). Had to reinstall nVidia driver again and delete GPU Tweak 2 (using the tool removal provided on Asus website, not the standard windows uninstall) and no more crash after that. Will do some more testing to confirm. I attached two logs from the last crashes prior last driver reinstall dcs.log-20190512-203540.zip dcs.log-20190512-203717.zip

Tried with limiting framerate at 90 fps. Still got crashes at server selection stage.

Did some testing : no crash in non-VR mode. I’m still getting a lot of crashes at the server selection stage or during loading phase after selecting a server. I tried reinstalling Oculus soft, I tried various nvidia drivers and did not put any GPU overclock. I also tried the pagefile trick. I have Oculus tray tool to disable ASW by default. One thing I noticed is that I have very high framerate in DCS menus (200-300 fps), and I can hear cool whine from the GPU. If I manage to join a server and then go back to the menus (though all that without crashing is pretty rare) the framerate is now at a more reasonable level (similar to in-game 45-90 fps). I’m wondering if the very high framerate/coil whine causes those crashes. I’ll try to see if there’s a way to limit framerate at say 90 at all times. Anybody facing the same issues ? Thanks for your help

Guys, I’m having the same issue. Crashes happen at server selection stage, or during the loading phase after server selection. It’s very random for me, and when I manage to join a server I don’t have crashes while in game. I also have the « track IR device unplugged » from time to time but it has no impact. I noticed recently some noise that seems to be coming from the GPU while in DCS menus, but this stops in game... I’lol try without VR to see if I have the same problems.

1.37 and last nvidia driver did not show noticeable improvements for me. I’m waiting for the new terrain engine I guess :)

Oldmanflan, what cpu and gpu do you have ? Having a good experience with the rift myself but I wouldn't say now to better sharpness so that I can read fuel gauge in the M2000 from defaut position. I'm concern that my 1080ti and 7600K aren't going to be enough for an O+... Thank you