Frusheen

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.

Hi today I started the upgrade process to Windows 10. Im performing a clean install and want to get the best possible OS performance without too much background crap running that I'll never use. Anyone been through the process have any advice? I disabled my modules before I started. After the upgrade from w7 I created a boot disc and have now selected a custom install. I've disabled cortana and all the windows reporting features.

Well I bit the bullet and just upgraded to Windows 10 from Windows 7. I've created a Windows disc and I am now performing a clean install. My drives were due a clean up anyway. It's going to be a long day installing software but I hated the idea of moving to a new OS and not having it clean. Anyone got any tips or things I should address which may boost performance of the new OS? Please pm me if you wish to avoid derailing this thread.

Thanks johnco. I'll look into it.

I avoided the free move to Windows 10. Like Derek I'd prefer to keep Windows 7 but this feature has me tempted.

I hadn't seen that graph for the 341 but it illustrates my figure of 30 degree descent angle being the boundary of the danger zone of VRS. That figure is quoted for many typical single rotor helicopters and has been established from extensive wind tunnel testing. It is quoted in a lot of helicopter flight dynamics reference material I have studied as part of the hobby. EDIT: increasing collective pitch beyond OGE hover position in VRS should actually make the rate of descent increase rather than the current situation where the descent can be arrested.

This is the issue. Helijumpers video shows it and I've spent another few hours testing and got the same results. The helicopter WILL enter VRS but once established its possible to get out of it with collective which is not realistic. I also must question the parameters for the onset of VRS. Any kind of forward momentum no matter descent rate is enough to prevent its onset. I understood from manuals that it should be possible to enter VRS once the descent angle is over 30 degrees. At the moment that angle seems more like over 80 degrees. I'll put a video together later of a track I saved which clearly shows the issue.

You are correct there is VRS but it's so subtle and easy to recover from that it seems unrealistic. EDIT: Removed off topic content relating to other oddities of the flight model so as not to derail the thread.

Your video proves it well enough for me. You recovered from VRS with just collective.

It is possible to get into VRS. It requires zero forward or lateral movement in the descent and I've only managed it in testing and then when close to the ground. I just spent an hour test flying the gazelle in 1.5 and in that time managed to get into VRS only once! The slightest forward or lateral movement and the Heli recovers on its own. The implementation is very unrealistic. I identified it by seeing judder in the airframe and an increase in descent rate. Just touching the cyclic results in a recovery.

Sorry guys. I've been busy on other projects and had no way to test my second plugin. I did send it out to a guy who had a suitable platform to test but I never heard back on how it worked so it ended up on the back boiler. The first plugin I published has issues. Using the rate of change of bank and yaw as an alternative proves to be very difficult especially at the crossover points. I can remove all that code and integrate mrsparks solution into a plugin and publish it over there if that would help. That would mean no need to mess around with lua code for those who prefer not too and it would keep the export lua tidier for those who just need the roll fix for 2dof platforms.

I produced a plugin which does exactly this and sent it out to a guy with a seat mover for testing but never got any feedback from him on the results. I didn't want to publish it without first hearing how it worked. Sorry you had to reinvent the wheel so to speak. EDIT: With your permission I can integrate your code into a plugin if it would benefit others with 2dof platforms. Seeing as your code has been tested and it works it would make sense to release it over mine. I will remove the other rate of change code and just provide your alternative roll on extra 1.

Curious which 3rd party applications do you run with dcs that you'd want to import into VR?

If you're in doubt then don't buy it. There will always be some screen door given the state of the current technology. Even at 2.0 you will not have a crystal clear image. For any of us using VR though it is not just about the visuals. It is the fov, 3D and immersion that make it better than a monitor. If what you want is similar visual fidelity to your monitor then wait another 10years for the technology to be available.

I think the next iteration of VR headsets could well feature vestibular stimulation in which case there will be no need for a motion platform at all. The gseat alone will be enough when coupled with manipulation of the balance system in the inner ear. Samsung (partners of oculus) have already shown the Entrim 4d headphones which feature GVS. For now the bigger issue for all motion systems is getting the right data out of dcs as neither the X-sim or SimTools plugins are good enough yet and designing/implementing a proper plugin is proving to be very challenging. There are a few of us working on it so hopefully it will improve.

It depends on the simulator and software being used for motion.

That is most likely a USB issue with your tracking camera and not related to dcs.

Just save your flight as a track and replay it in VR. The headtracking will work and the person can be a spectator in the plane for the replay.

My concern is with the inertial measurement unit in the headset not the camera sensor. The imu in the headset is doing the orientation tracking with the camera being used for error correction, canceling drift on the gyros and aid positional tracking. It updates at a much lower rate than the internal imu. The result of platform movement on the imu is clearly visible in some videos. Even with the camera on the platform the pilot view is seen to tilt and wobble when the users view isn't moving. Here's an example.

That is great news Wags. Turning cockpit shadows back on will greatly aid immersion. If possible could we have the option to turn on the players aircraft shadow as well? It's really nice to have it on the ground for low level helicopter flight.

Looking forward to hear how those who purchased platforms for DCS in VR find the experience. I was too concerned about the IMU sensor causing unwanted tracking movements due to the seat motion to proceed with my 6dof build and went the gseat route instead. Motion seems to be fine in a limited motion rig with fast movements like the racing examples but any videos I've seen with large slow movements involved have looked very concerning. Of course it may be different with the headset on but having watched many videos where the view obviously changes when the user hasn't moved their head was very disconcerting.

They are very possible. I've never experienced this issue. You don't centre the stick in a turn to hold a given bank angle. It's not a plane! This is not what this thread was originally referring too though.

I managed to enter VRS. It requires close to zero forward or lateral momentum and is so easy to recover from its almost a non event.

A certain amount of perceived FM issues will be subjective. Real world pilots being placed in front of a 2d monitor with a hotas joystick that has springs and completely different travel to the real thing coupled with no feedback other than what they see on the screen will have a hard time expressing how good or bad the flight model feels. Similarly us sim guys can only offer feedback based on implementations of helicopter flight dynamics from this or other sims. The key is to identify known helicopter behaviors and see are they implemented. That is not subjective. They either happen as expected or they don't. The Gazelle has several areas where improvements need to be made in this regard. The background of the person raising the issue be that real world or sim flying has no bearing on that. I hope Polychop will revisit the FM issues raised that are repeatable and clearly incorrect.