Snake122

There are 4 installs of both SSA and the Sound module in the folder for a total of 8.

Just one Simshaker Sound module in the drop down, can't select the beta. Hope that trick does work for you!

It does, my problem is that I have both the sound module beta and standard 2.14 installed. Once I ran 2.14 again it now starts 2.14 automatically! Per our 3rd Space Vest discussion, I think you could tie this to LoGetAccelerationUnits() Accel.x as I'm trying to do for the vest. The cat launch is 3G+ in that direction and I haven't found anything else yet that causes that much. AB is only .6G and that's only other thing I could think of that generally causes large acceleration that direction.

Do you have the actual sound shaker module installed and running too? Just getting back into using the sound module today with my bass shakers pucks. I have been manually starting both but not sure if that's required because I think I saw SimShaker for Aviators start the SimShaker Sound moudle once.

I too am getting this since 2.5.6 stable. Seems it's my left eye that doesn't render. Clouds, contrails, tracers as reported and for me it also has some town lighting effects. I'll try the LOD distance edit and report back.

Click on the Configuration icon (gear with wrench) and there is a donate button for PayPal.

Honestly, I've been flying with the Leap Motion off because the hand tracking causes too much FPS loss with the Pimax. Have you tried binding the hand on/off keystrokes? When I get back around to it I was just going to keep the right hand off unless I really needed it. Left hand maybe on or maybe just map both commands to the HOTAS so you don't get the VR move the stick at least. As I mentioned, I am on the PointCtrl wait list and you should check out the new 2.0 controllers that will be coming out soon. They are reduced in size. It really does sound the closest like what you want. One problem with your good mix wish is that it will still be very hard to line up the switches in the physical cockpit with where they are in VR. I have to remember this everytime I reach for my MFDs since they aren't where they are in VR for all the planes that have them. If the switches in your physical setup don't line up exactly for every switch is in VR, you could be flipping the next one over. Plus you will have dead spaces due to HOTAS bases ect. One of the ironic pluses of PointCtrl is there is no Z axis so you don't have to do the laser gun of the VR controllers if you can't put your hand deep enough to flip the switch by the VR push. There is an interesting video out there of a simple plywood panel without switches being used with PointCtrl. At first I didn't get why, but it stabilizes your hands to click things. You then get the visual confirmation on screen which switch you are activating and then the tactile feedback as you push the button. Not ideal for sure but probably the closest you are going to get to your dream. Om, I just received a Kensington trackball with scroll ring for my left hand that I'm going to try. Right hand can still reach my normal mouse. Again, Leap Motion and Pimax work but something has to give with performance. The Rift S controller support in DCS isn't bad persay, but having to put the controller down, use HOTAS and then pick it up, then flip switch isn't optimal either. But the mouse control definitely loses some of the immersion effect I wonder if like in Vaicom voice command stages, a sound telling you you are on a switch and then a louder switch flipping sound would help Leap Motion since we can't get the tactile feed back that the VR controllers give with vibration...

I get it, just saying it is available and waiting for the right Virpil stick to come in, then ship, and then get to wherever from Lithuania can be frustrating. It doesn't have the twist axis nor the analog paddle. But I will say when I was using my T-50CM stick on my Warthog base, the paddle became digital and it wasn't that bad for taxi, I would call the analog only a minor improvement.

The Thrustmaster grips work well on it too and are more obtainable. The F/A-18 grip is also "correct" for the F-15 and AV-8B if you care about that kind of stuff. It is the grip I probably use the most on the base.

A see a few posts back, f4l0 doesn't own P-47. Suggest you use the link in SimShaker when you got Effect Settings to donate. The DCS-BIOS users did this for that developer and they were able to add the support now. EDIT: sorry for the somewhat double post, rowdgordypiper beat me to it.

Agreed, GBU-12 same class but at least in real life can carry more of them and easier to employ. Some SEAD with HTS is more what I would want than Mavericks.

That's the spirit for those of you that want the P-47 support. There is a link at the top in SimShaker when you open the effect settings page.

I had an Alpha that I got with my T-50CM2 base. It did not feel good in the hand at all and sold it off.

Thank you! Now that makes sense. Is there a reason why the "Start when Windows Starts" box can't be checked?

Oh yeah, being left handed, I didn't think of that. One of the few times in my life I can say "right handed people problems" :megalol: The H640P needs the pen to detect writing so you can rest your arm on it as long as it is comfortable for you. Your arm shouldn't hit the forward located buttons though.

VRK is setup to you the longer side inline with your thigh, not across, like real life kneeboard/tablets in flight (like portrait layout). It can be setup to go longer across the thigh (landscape) but it honestly works better the traditional way. Using this way doesn't get in the way of my center mount. You can see the edge of my Virpil T-50CM2 base in the picture I attached, you can also see the "kneeboard" bracket I use to hold it in place so I added a picture of just that as well.

Trying to reduce the things I have to remember to run before DCS and since this doesn't have a traditional .exe that I can find, I can't add it to my .bat script. So my other option would be to run at start but I cannot actually check the "Start when Windows Starts" box. in SimShaker Starter. Is there something else I need to do to get this to run on Windows 10 boot?

Highly recommend the Huion H640P. It is affordable, not too big, not too little, mappable buttons to help out with VRK. You just need to make sure you follow the install instructions in the guide and use Rider's custom driver, you don't need to ever install the Huion ones for VRK use.

Thanks for reminding me about fpsVR! Oculus doesn't support it but I had heard of it and wanted it then but forgot about it after I switched to Pimax. I got the i7-9700kf because with DCS only utilizing 3 CPU cores and really only one well, it was the most single core performance I could afford. I use this website as my general CPU benchmarks and I think it does a decent job. Note that I linked specifically the single core graph. For most other games you can stick to the overall, but specifically DCS and most other flight sims, single core performance is still king. With those settings in DCS, I am getting an average of around 10 ms for my CPU time and 18 ms GPU time, so definitely GPU bound and about 45 fps. However my 80% SteamVR setting on Normal FOV is only 2756x2352, which is what I ran. If DCS could thread across your cores better, you would get better performance than me with stock CPU frequencies for sure. I don't know if you play a lot of other games or not, the Ryzen chips are great deals for sure when using modern gaming engines that multi-thread effectively. As my second link shows, I had to pay almost $130USD for my CPU than yours and in almost all other programs it out performs mine, except for DCS and other sims that have limited CPU threading. I think this would probably do more than Vulkan since it would allow for multi-thread processors to be better utilized for those of us CPU bound. But Vulkan would probably help the GPU bound like me. Of course the other factor is the overclock, which is just 100mhz higher than the turbo setting for my CPU (4.9ghz) and only 400mhz than your turbo. I'll try to get some time later to run it with the stock CPU timings to see if that puts me back to being CPU bound. So yes, a 2080Ti will give me better performance, but wonder if it is worth it. To afford it, I have to sell my Rift S (and 1080Ti), so I'd be giving up the VR headset that gives me great performance for what may only be moderate increase in the Pimax. The two general comparison websites I use for GPUs say an 24% to 32% increase but rarely do you actually get that full percent increase. If we are talking say only 10% effective performance increase for DCS, that's only about 49 fps, but the full 32% would be almost 60 fps with the setting you had me run. The one thing I can't factor in is the RTX support for FFR, which seems like it could be a big deal for the Pimax with all the extra FOV that doesn't need to be rendered as well. Support it no, it will still be a PCIe card. In theory your PCIe lane if not 16x or also higher version (6.0 is coming out next year), it could be motherboard bound, but that generally would take a huge leap in performance for that to happen. Nvidia knows that they will sell more cards if they work with in the confines of the typical motherboard bandwidth even if they could somehow blow the PCIe lanes out of the water at consumer prices. But to not be CPU bound then, who knows...

Got a chance to try it out today and really like the changes. Its cool that it makes them the Vive Index "Knuckles" instead of the old wands. I also didn't have to run VRK first nor the Leap Motion app, it just works with my Pimax. Great stuff, thanks! I did notice that it added them as a controller in DCS as well. Since I'm new to SteamVR and 2.5.6, is this the driver or the the latest update that made are mappable (the only physical VR controllers I have used are Oculus and they look to be hardcoded)? What's the best way to manipulate rotary knobs with your driver update? FWIW, I believe Ultraleap will still call the current unit the Leap Motion. I'm watching now for the Ultraleap+Pimax unit to be available. It is supposed to have better hardware and a better mounting solution. I'm running all of those apps as plus VRK and DCS hasn't crashed on me. It definitely starts to lose some tracking down to the sides. I feel like my really low mount on my Pimax (literally level with my mouth) is not helping as well.

I received my 5k+ the middle of last week to try something different that the Rift S after having lots of issues with Oculus Home and somewhat missing multiple monitors FOV (although I would pick VR over it anyway). First impressions was the massive performance hit and slightly less clarity, but the FOV being amazing. But I've been honestly on the fence about it until I went back to the Rift S and instantly knew how horses with blinders feel like! Also my constant connection problems with Oculus Home makes PiTool detecting my 5k+ seem the much better option. So it looks like the 5k+ is here to stay. Here's my question, how much performance boost would I get putting the money I got from selling my Rift S and 1080Ti towards a 2080Ti? Would the on paper about 30% increased horsepower of the 2080Ti plus the RTX's ability to use FFR be actually that noticable to get close to a true 30% increase in DCS with my system in my signature? If I'm not going to get that much of an increase, I'd probably wait for the 30XX cards and possibly put the Rift S sale funds towards Vive Index controllers and 2.0 Lighthouses for room scale. But I will say I have been impressed with the seated experience with just one 1.0 lighthouse for those of you thinking about getting a Pimax without the controllers.

Good to know!!! Thanks Rider!

Now I understand your offset, I thought you were saying an x/y/z offset because you can control that in VRK. Does the middle finger+thumb pinch work with standard SD Draw? Or is that the only way to flip switches and why it has been hard for me since I've been trying how you describe you changed it too all along:lol: I read the DCLeap guide but not anything for the standard driver. I thought that was just added by DCLeap for turning knobs. Did you also implement the DCS VR palm up/palm down altogether or is it easier now without the offset?

Okay, guys check me here now that I have a better understanding Current DCS Leap Motion Implementation: 1-Basic SteamVR Hand tracking provided by Drivers by CBuchner, SDraw, and the latest by Havok2. Emulates Vive Controllers in SyeamVR. Havok2 may or may not have optimized for DCS, but these would in theory work with any SteamVR app (and headset). 2- DCLeap- Adds mouse emulation and hand gestures for DCS with the previously mentioned drivers 3- VRK- adds basic hand tracking for Oculus users (these users also have the option to use 1 and 2 if they use the --force_steam_vr command line parameter) Pimax- I did get it to work with the SteamVR driver this morning. I had to run VRK kneeboard app and for some reason this activated the SteamVR Leap Motion driver that doesn't load if you enter DCS with just how PiTool activates SteamVR.

Sorry I've been laying low on the thread, been setting up the Pimax 5k+ this week then downloaded 2.5.6 Stable most of the day. I have the Leap Motion attached to the Pimax. For a little bit I was getting the Leap Motion driver to work in the Steam VR house. Then I exited to restart everything so I could run 2.5.6 for the first time and in the restart of SteamVR made me loose some of the controller icons and now I just have the Pimax and Lighthouse icons and no Leap Motion tracking. If I run DCLeap it will detect the gestures and I can occasionally see the hands for less than a second. Not surprised since Pimax isn't supposed to support it but I'll see if there is anything else I can do. The interesting thing is that inside the Pimax planet (think simple SteamVR room for Pimax) before SteamVR is running, I get hand tracking with the Leap Motion! I know they have agreed to work together to bring out a new version so maybe that is why, but it isn't usable as a controller as far as I can tell.