MackTheKnight

yea, tried reinstalling varjo base. I was not running the dfr mod, but I am running openxr toolkit. Going to try removing it and see what that does. EDIT: Looks like that was it. So for some reason this new version of DCS doesn't like OpenXR Toolkit. Thank you all!

Previous version worked fantastic in VR MT, with my Varjo Aero. After today's update, I can no longer launch the multithread version of DCS in VR on the Aero. All I get is a blank black screen. Have done a full clean/repair of DCS with no improvement. ST opens, but I hate the sacrifice in performance, now that I'm spoiled by MT. Checked the Varjo forums, and it seems like I'm not the only one with this issue.

Running DCS latest version open beta, MT mode, with DFR in the Varjo Aero. In night missions I have a repeatable crash to desktop in the harrier. To replicate, all I do is start the jet up, turn on the TPOD, and then turn on the FLIR HUD mode. As soon as the FLIR HUD mode is toggled on, the sim crashes to desktop. Not sure if this is specific to running DFR yet or not. If someone NOT running DFR could test above, I'd appreciate it!

This is happening to the entire VMA-513 squad on a daily basis. We fly the harrier exclusively, and every single one of us has this issue since the 2.8 update. The work-around that seems consistent, is to open DCS and load into a single player mission before joining a multiplayer server. Once you do that, no more crash for that session. But as soon as you close & reopen DCS and attempt to go directly to a multiplayer server and spawn in the harrier, it immediately crashes to desktop.

I'm curious - have you experimented with simply disabling reprojection outright? I too was struggling with reprojection, including some strange screen tearing and flickering on my Valve Index. (Have an HPG2 on pre-order) Disabling reprojection via the steam control panel solved this issue for me. (It's called motion smoothing in steams lingo) -Mack

Thanks Guys and especially to Voyager for pointing out the 30 minute bug. I think that's what I'm seeing! -Mack

Hi All, Really enjoying the P47, but for the life of me I can't figure out what I'm missing. Is there a fuse or switch hidden somewhere for the Oxygen system? I can't seem to get it to turn on from a cold-start, and suffer from hypoxia at high altitudes of course. I'm probably missing something simple, but would appreciate it if someone could enlighten me. :helpsmilie: Thanks! -Mack

Thanks All - I've just started flying the Spitfire and have noticed this happening in multiple missions I fly. I thought I was doing something wrong that was causing it to burn-out the bulb for the reticle...

wish we could get this tomorrow!

Sounds like I should give this process lasso thing a try just out of curiosity. I honestly don't care what the cpu/gpu usage stats show as long as I'm getting good FPS with no hitching. And my FPS is solid now since getting rid of that Intel utility that was screwing my system over. I ran a mission last night and the FPS never dropped below 60 and was generally hovering around 100. That is a far cry from the annoying hitching and low 20 some FPS I was getting before, so I'm a very happy simmer now! I haven't tried the F18 in the Oculus yet, as I wanted to get more familiar with all the systems before jumping into VR. But I'm hopeful that my VR performance has improved dramatically as well, thanks to figuring this out!

here's a screen-cap, while sitting on the carrier deck...

Hi Lefty, Yes, I have MSAA set to 4X. In the Gulf map, I'm now getting FPS in the 60s at the air-field and 100+ up in the air. Prior to figuring out the cpu affinity issue I was getting low 20's no matter what settings I tried along with constant micro-stutters every few seconds. So happy to have it fixed now! For reference I've a 1080Ti GPU OC'd to 2050/6005. (Under a custom water loop - don't try that on air) -Mack

Do you ship these to Canada?

I'm running great at 2560 X 1080. No issues running ultrawide monitors with DCS.

Thanks - corrected a mistake in my write-up. It's actually broadwell-e, not sandy. I can never keep-up with the code-names. :music_whistling:

If you're running on the Intel x99 platform, make sure all cores of your CPU are being used. I discovered that my system was defaulting to using a single core, due to a bug in an Intel CPU driver: See thread here: https://forums.eagle.ru/showthread.php?t=211549&highlight=cpu+affinity -Mack

So I found the cause of this behaviour. I'm running an older Broadwell-E CPU, (i7-6850K), with an MSI Tomahawk X99 motherboard. One of the drivers it installs by default is called "intel Turbo Boost Max Technology 3.0". The utility included with it that's enabled by default, supposedly optimizes CPU affinity based on application demand. Turning that thing off has solved the problem. DCS now defaults to use all 6 cores/12 threads. Anybody running X99 should check/verify this thing is turned off as it's not running as designed or is bugged with DCS. (Yes I have the latest motherboard drivers, etc. And this is the latest driver/util that Intel has available for the X99 chipset). Details on how to get rid of the utility entirely can be found here: https://www.pugetsystems.com/labs/support-software/How-To-Prevent-The-Intel-Turbo-Boost-Max-3-0-Software-From-Launching-On-Startup-1078/ Make sure you read the comments section as there are some additional details there you need to follow, that weren't covered in the initial article. Hope this helps someone else out there! -Mack

All, So I was having some seriously frustrating issues in the latest 2.5 beta with F-18 and the Persian Gulf map. I'd load a simple MP mission up and the ground textures wouldn't load. Cockpit textures would be all solid black. Sometimes textures would load but if I went to the F10 map, and then back to the cockpit, the ground textures would disappear... Long story short - after alot of messing about with settings (None of which made a difference), I discovered that DCS.exe was defaulting to use only one core of my 6 core/12 thread CPU. Manually going into taskman and setting it to all cores, fixes all my issues. I can now run DCS with high settings and zero stutter or strange texture behaviour. But... I have to do this every single time I launch DCS. I can't figure out why it continues to default to CPU0, but at least this work-around is easy. Anybody else notice or experience similar behaviour? Cheers, Mack

You can still get the rift+touch bundle on sale, from amazon.ca: https://www.amazon.ca/Oculus-Rift-Touch-Bundle/dp/B01LYCUM3L/ref=sr_1_1?ie=UTF8&qid=1501692261&sr=8-1&keywords=rift I already had the rift but got the touch controllers. As for saying you'll never use them, don't knock it till you try it. I didn't think I'd care for it, but it's really very fun and quite amazing. There's an X series (X Rebirth I think) space simulator converted to use the touch controllers and it's really amazing how easy and intuitive it is to control a space-craft with the touch controllers. (I'd never use them for a real-world aircraft, but I play all genres of games & sims) Ultrawide works very well with DCS as well. Cheers, Mack

If you have the budget I highly recommend checking out the BenQ XR3501. http://www.benq.us/product/monitor/xr3501/ Best monitor I've used to date for gaming, especially flight sims.

Can't go wrong with the MFG Crosswinds. They are far superior to anything else I've used.

So far I've only tested the P51, but... I am impressed, Sir! You've brought my butt kicker back to life. I'd kinda given up on it in the past, as I could never get a satisfactory result with it in DCS. Thank you! Looking forward to testing more of my favorite airframes with this. :) Edit: One thing I feel is missing and maybe mentioned before - is there a way to implement impact effect? For example if you're flying P-51 and it gets hit by rounds from another aircraft we should feel some sort of effect on airframe. That is just a small nit-pick - overall it is very impressive.

Donated via your page - is there a way to get in on the testing? I've a buttkicker gamer 2 and a few spare audio interfaces... Cheers, Mack

Just started reading about this today, so missed the indiegogo campaign. Donated via your web-page. Excited to see this in action! Best of luck to you and your team, Andre.

Got mine yesterday. I'm so glad I bought these. Best flight-sim related purchase I've made since the HOTAS Warthog. I can actually keep the Huey stable in flight now. A feat I was never able to accomplish with the old CH Pro pedals. Also, the toe brakes are amazing compared to my old set. The mustang is much easier to tame on the tarmac, and on takeoff/landing. Well worth the wait and investment. Anybody who has doubts - rest assured, these are the best flight sim pedals you will probably ever purchase, and the build quality is top notch. Props to Milan - Thank you for a fantastic product! Keep up the great work! -Mack