Frusheen

I think the only viable solution to the motion sim problem is a second imu on the platform and a custom oculus runtime which subtracts platform movement from the head tracker output in real time. There was a guy working on it a while back with dk1. I'm not sure where the project is now. You can see the imu on the back of the chair in this video:

Thanks Insonia but that didn't fix it.

Hansangb is your CPU overclocked?

I can manage shadows on but only barely. I still get the odd drop below 45 fps over Vegas with shadows.

Small problem but would be nice if it could be addressed as my cockpit is away from my PC and fixing this would allow me to remove my second mouse. DCS 2.0 - From the main screen once a mission is launched the switch assigned to mouse click looses focus during the load screen and the mouse must be clicked in the game window in order to allow use of the switch again.

Thanks. I compared to the other helicopters due to you stating it was not possible to model in dcs. The type of governor employed is not the issue. When a helicopters rotor is presented at high angle to the oncoming air flow with low pitch on the rotor blades they rotate more quickly (this is because the rotor head is free to rotate from the gearbox and is what allows autorotation). It has nothing to do with the other dcs helicopters. It is basic helicopter aerodynamics and it does not appear to be modeled. The engine governor is working to control the rotor rpm it can't overcome this phenomenon as the rotor head is free to rotate. Unless the Gazelle has some kind of active rotor brake in flight other than the rotor brake in the cockpit then performing the maneuver should cause a rapid increase in headspeed and a drop in engine rpm as the governor tries to compensate. At the moment the rpm needles don't even flinch. Thanks for passing it up the line so it can be addressed along with some of the other flight model issues.

I don't follow you Roie. The rotor rpm needle can over speed on both the Huey and mi8 by performing the same maneuver from fast forward flight. There is also an audio change associated with it. The gazelle rotor rpm can over speed when in autorotation but not in powered flight. This is not correct behavior.

BUG TEMPLATE: Description: From a stable hover performing pedal turns in either direction have no impact on the airframes attitude. DCS Version: 2.0 Steam: No Map: NTTR SP/MP: SP Reproducible: Yes Step to Reproduce: Turn off SAS. Perform a pedal turn from an established hover. The helicopter attitude remains completely neutral with no requirement for any cyclic correction. No apparent interaction between changing heading by pedal input and aircraft attitude. Screenshot/Video available: can be provided on request Track Available: No Mission File: No Controllers: In signature OS: Windows 10 CPU etc: in signature Mods: No Any Additional Information:

BUG TEMPLATE: Description: Helicopter rotor head does not change rpm when decelerating from fast forward flight with fully lowered collective and aft cyclic. DCS Version: 2.0 Steam: No Map: NTTR SP/MP: SP Reproducible: Yes Step to Reproduce: perform a rapid deceleration while maintaining altitude by lowering collective and applying a large amount of aft cyclic. Screenshot/Video available: can be provided on request Track Available: No Mission File: No Controllers: In signature OS: Windows 10 CPU etc: in signature Mods: No Any Additional Information: This does seem to be implemented when the rotor head is not being driven i.e in autorotation.

Hi guys. I've been flying the mi-8 a lot more recently using rift and really enjoying it. One annoyance I have is the cockpit glass. It has a blue sheen on the lower panels and around the window frames. In my opinion this looks terrible in VR. Is there anyone out there who could make a mod to remove this effect and make the chin glass appear more like the front windows. I did find one cockpit glass mod already but it does not address the blue colour.

I'm using a full length cyclic from Komodo Simulations. All linear the mi-8 has perfect response.

You have to manually enable it.

I'd much prefer to see active testing from the Polychop team on this and other flight model issues rather than videos of fitting hellfires etc... The priority in a full fidelity flight simulator has to be the flight model first.

Good stuff. The big issue in VR is maintaining the fps. You need to be able to stay at 45fps ASW all the time. Any dips no matter how brief can be very sickening. That's why I test over Vegas and preferably with a few other aircraft around. If the sim maintains 45 there then out over the desert will be no problem.

Defeats the purpose of you ask me. VR is to increase immersion and realism a virtual keyboard seems counter productive.

For a comparison I just tried my sim without VR and did not change any settings. I can maintain 45fps in VR using ASW over Vegas. My fps outside VR is showing about 170fps at 1920x1080. If you can get in that range currently then it is some indication that you will be able to run in VR.

There is no easy answer to this. It depends on the platform and how tolerant you are of spurious headtracking movements. Seat movers doing fast shallow angle movements such as those used in car racing seem to be ok for some people from what I've read. Platforms which move to extreme angles show obvious tracking issues. In the extreme case where the platform rotates 360degrees then it won't be easily usable. The rift imu detects platform movement and translates that to head movement even tho the users head hasn't actually moved relative to the game view. This can result in nausea. Edit: The easiest solution is to build a g-seat ;-)

There's no need for two files. Did you add (merge) the lines to your registry? Take your time and re read the instructions. Editing your registry wrong can cause serious issues with your PC. You can see if it's enabled in the oculus log files. You will also know by using the ctrl numpad shortcuts in game and turning on the frame rate monitor. With it on you should be locked at 45fps and off you should be st 90fps.

Oh please god no. The only way I enjoy DCS is in the rift. The other sim I want to use has no VR support precisely because it is cross platform (x-plane). My reason for making the move to Windows 10 was for VR improvements. I'm glad I did it and am now over the initial problems and have a much better looking sim with higher settings and smooth VR performance.

https://amp.reddit.com/r/oculus/comments/56af3t/detailed_stepbystep_guide_to_enabling_asw_through/d8hodir It really does give a massive boost in performance. Once you don't get greedy with your settings afterwards and ensure you stay over the 45fps threshold (use RCtrl Pause to check) it really looks just as good as full 90fps to me. Drop below 45fps and things get very ugly and sickening very quickly. I'm now running shadows which I could never do before.

To see if it's working bring up your frame rate monitor (RCtrl and Pause/Break). When it's active you should be locked at 45fps. After updating from Windows 7 I just had a few flights and find that over downtown Vegas I'm dipping below the 45fps threshold a bit which is very uncomfortable. I need to find the sweet spot with settings. I have flat shadows at medium which were off before. Looks like they may have to go off again. I also need to OC my GPU back to where it was before upgrading to windows10 and also stress test my CPU OC as I just had my first PC crash (Kernel error) while using my old overclock! While locked at 45fps the experience was very comfortable. Not hugely different to what it was like at 90fps before except my graphics settings are now higher of course.

May have spoken too soon. Just had my first PC crash. I had just reset my previous overclock in bios (I had it back to default for the update) and was flying over Nevada when I got a kernel power error.

Well I've just tested and Windows 10 with ASW for the rift in DCS is reason enough to put up with the auto updates. I'm glad I made the switch. Everything is much smoother now.

Sorry been busy with work and have also just formatted my PC to upgrade to Windows 10. I'll post once I have something to show but it will take me some time to get everything reinstalled. In the mean time you could fool the plugin by editing the export.lua file with the code from mrsparks.

Thanks all who replied. I installed from scratch and created a clean system. Managed to get around all the Microsoft spying settings thanks to a link to a video provided in another thread. Linking here for reference. All good so far.