Snake122

Olaf, I forgot to mention the new beta did fix the launch bar effects unless you click the switch within a few seconds of entering the cockpit. If you wait a more realistic amount it seems to work fine. Also for those of you interested in the 3rd Space Vest mentioned in this thread a couple times, see the link in my signature. I think SSA/Sound Module/JetSeat are what you should go for first because they provide more overall feedback, but the vest does provide G info in a different way. That's great to hear!

That will probably suit you well. The BST-1 would still probably give you the effects you want. Honestly I've never played with a ButtKicker because over the years there has been cheaper DIY options, the Dayton stuff being one of them. Note see the BST-1 for only $39USD at Parts Express. Two of them would give you more shake and SimShaker Sound Module would give you stereo effects. Currently I use the Dayton Bass Pucks with a cheap Lepai LP2020 amp. I just got two more pucks to mount close to the sides of my center mount T-50CM2 base. I do it this way because I can position the pucks for specific zones. When I was specifically flying just the Viper on the other sim, I had one puck where my heels would rest on floor for the the rudder and one an armrest for the stick hand. Now I've moved that extra puck to the floor board for left and right channels (helps in the SimShaker Sound Module for G effect sides and other details). My heels now rest on these pucks. The other two pucks I'm hopefully mounting today will maybe be felt through the stick a little and definitely my legs. I also used to use an Aura Interactor bass shaker for larger effects but don't anymore due to the JetSeat. I like the zone/stereo effects the Dayton Pucks give me and are pretty quiet especially when you use Andre's "Limiting Compressor" in SimShaker Sound Module. The previous Aura bass shaker I used was loud and higher sounds bleed through (but may have been before that setting option). The two pucks mounted under the seat came close to the overall effect with L/R channels but I shortly transitioned then to the JetSeat for seat effects. If you are interested in zone effects you could also pick up a couple pucks and will probably have room to drive them with that amp you have picked out.

Update: I have a very basic software version (no GUI, just console) and more clunky than I would like on some of the cell inflations, but it works! It right now is working more like a basic G Seat than a G Suit. Again, I think you get more bang for your buck from the JetSeat and Simshaker bass effects, but this will improve your G cueing for sure. List of effects: -Positive G Stage 1 ~4Gs: lower back cells inflate to simulate being pushed into seat -Positive G Stage 2 ~7Gs: upper back cells also inflate to simulate being pushed further into seat -Negative G Stage 1 ~ -1G: upper front cells inflate to simulate feeling the straps go into your shoulders -Negative G Stage 2 ~ -2G: lower front cells inflate to simulate further feeling the shoulder straps straps dig in -Catapult Acceleration (~3Gs backwards): all back cells inflate together to simulate being pushed back into the seat -Wire catch (~3Gs forward): all front cells inflate together to simulate being thrown against the seat belts Software Roadmap: -Code improvements!!! This is my first ever C++ project and very limited coding experience before this. -GUI or would love for f4l0 to incorporate into SimShaker for Aviators -Slider for G level activation for effects -G Suit mode: unfolding the Vest makes it like a G Suit (see attached pictures). Right now looking at the code I haven't really been able to create a intensity effect on the cells so I may have to make suit mode inflate up the legs to the "cummerbund" as Gs increase instead of the cells inflating more and more over time. -I don't think this is possible looking at the code but I would really like for this to happen: two 3rd Space Vests supports at the same time for both G Seat and G Suit simulation.

I found .725 right if you are using parallel projection mode, but you shouldn't need to use parallel projection mode anymore. It used to required for VR zoom to work right, but it causes a large FPS and clarity hit. Without parallel projection on try what was quoted here earlier of .590 for normal FOV. Without parallel projection Pimax 5k+ large FOV mask size is somewhere between .625 and .650, trying to fine tune it now but takes awhile since the shaders have to be redone each time.

I turned this off today, and wow!!! The performance and clarity is much better! Earlier in the thread it was mentioned that maybe 2.5.6 fixed the zoom issue, which I wasn't running when I first got the Pimax since I run the stable. With parallel projection on, HUDs weren't that readable at large FOV due to aliasing, now I don't have that problem and much better performance than I was getting with normal FOV with it on.

To further derail the thread towards MOAR VR:cry::lol: As a former triple monitor user in the other sim, I switched to DCS pretty much full time due to VR with a Rift S. But I missed the FOV of triple monitors. I can definitely say that the Pimax 5k+ FOV to me seems the best of both worlds of you have a good system to run it. I think I get a larger FOV with the Pimax than my previous triple monitor setups (19"x3, then a PLP setup w/ 32"x1 + 19"x2). Sorry to not be helpful with your current issue but something to think about for the future.

Well, yes that did fix it, but...:music_whistling: So testing from aircraft ready to go missions with just the launch bar effect enabled (haven't cold started mission test yet), In the F/A-18 I won't get a launch bar effect on the first extend, similar to as I said yesterday when I wasn't getting a launch effect, I have to cycle the launch bar. So after the first extend I will get an effect on retract then an effect will happen on extend. F-14 is similar but a little different, probably since the launch bar/switch operates differently. There are times I have to completely kneel it the bring the nose back up to feel the launch bar effects, other times I don't. Also sometimes I will feel the launch bar effect as soon I hit FLY when I'm in the cockpit, but even then I won't always get the effect on the first kneel. It seems like most of the time I have to extend before the launch bar effect effects on kneel will be will enabled, but there are times the F-14 launch bar effects works right away on the first kneel. Something with DCS and SSA detecting the switch state for both planes?

New effects are great Olaf! All I had to do specifically trying to break it with what overalien is reporting by import old settings is to select a different model in the drop down and then go back to the F/A18 or F14 for the new effects to show up. So for me a database reset was not necessary. However, I'm not seeing (nor feeling) a launch bar effect in the F/A-18 menu when I do it that way nor when using the "reset Settings Dataabase" button in the Service tab. The effects work great in both F/A-18 and F-14, but I do need to cycle the launch bar up/down in the default DCS F/A-18 carrier takeoff mission to get the Cat effect (launch bar entering cockpit defaults to down and lined on the cat).

Dang, I'm out of town for a few days and won't be able to test it for awhile! Did you bind the launch/trap to Accel.x? If so, what G level?

For the ground that can be pretty normal since DCS always has a FPS hit on the ground/low altitude. Start a free flight in the air to see what it is. Even then I doubt you'll be able to hold 80 fps at altitude though. Smart smoothing is required for Pimax right now. Remember your are basically running 8,000,000 pixels in stereo, which makes it more demanding than standard 4k gaming at about 8,000,000 pixels as well but the extra issue of having to do a left and right eye view. Standard 1440p monitor/Rift S is pushing around half that amount with the monitor in 2d, Rift S in stereo. Now that I have a good amount of time in the 5k+, I plan to fly some more hours in the Rift S next week to do a comparison of FPS of Rift S vs FOV of 5k+.

Yep, switching to 1.3.12.2 allowed both of the sound modules to show up. I'll try to stay up on the betas for both of you. Thanks guys! Also the new website looks good Andre!

Just so you know, Rift S doesn't have those crosses either which is too bad. I knew my number from the Rift CV1 and then confirmed it using a ruler in the mirror. There is a dial under the right rear of the 5k+, I would assume it's there with the XR. When you adjust it with the headset on it tells you the number. I leave parallel projections on because without it the zoom is screwed up and I need that a lot in VR. The setting that had the most effect on double vision in PiTool is turning off the Hidden Mask Area. Also this post earlier in the thread seemed to have the biggest effect overall for me: https://forums.eagle.ru/showpost.php?p=3997329&postcount=1347

My system most of the time is not CPU limited. My bet is the next generation of video cards will come out (September) before Vulkan does for DCS. Yes, Vulkan is on the DCS roadmap but they have had a lot of issues lately slowing them down. As we talked about with my fpsVR test, my CPU frametime can get a little lower than 10ms with average being around 11-12ms with the settings you wanted me to run. Sometimes it will get higher than the video card frametime if I get down low or there is something complicated going on in newer aircraft, but there is far more orange on the video card side. I'd be happy to run more tests and save them with fpsVR for you but my time maybe limited on it until next week. However, with the testing I did today with lower resolutions, it doesn't seem that the VRAM is my bottleneck, but I'm still always close to filling up the 11Gb with newer aircraft like the F-16.

Correct, sorry for the more than that installs, I searched for the .exe and I found the temp folder for unpacking when installing. Yes only one in the drop down in the "Service" tab:

The shimmering and jaggies are pretty big immersion killers for me, but those are the first thing to turn off if I need the performance. But most of the time since I can't run at full refresh rate with both of those off and them being on still allows for the half refresh rate of smart smoothing, if I'm running smart smoothing it's a wash. VRAM usage hovers at least 95% and actually the time I ran with MSAA and AF off to confirm what I was saying for this post it was 100%.

Now that you mention it, I do have Pimax support experience. My shipping label was created within 24 hours after my order but it didn't actually leave the warehouse. I created a support ticket and they got it moving. Most of the the replied were within 24 hours (mostly seemingly due to the 12 hour time difference) with another follow up about a week after it arrived. The key to Pimax support really does seem to be to create a help ticket. My concern about the 8k+ (or even 5k+) and the 30xx is VRAM. Even at only 80% resolution of the 5k+ with 2x MSAA and 4x AF, I'm filling up my 11GB of VRAM and I think this is why even with my ok CPU frame times, I'm only getting 60-70% GPU utilization while non VR 1440p sometimes I hit 100% GPU with only 8gb VRAM usage. The rumored new 3080 Ti (possibly renamed to 3090) is supposedly only going to up to 12GB VRAM, it's the new Titan that will have 24GB and the regular 3080 will have 11GB. I really think for DCS, VRAM is a bottleneck with Pimax headsets with how many pixels it needs to push in stereo.

I don't think you will get 6DOF headset tracking with Oculus sensor, they work in a different way. You might be able to use the touch controllers in SteamVR but I'm not sure if it allows it of a non-Oculus headset is being used. This for sure. With my Pimax 5k+, I had to slightly turn down from my Rift S visual settings that were often times at full refresh, and I'm happy when Smart Smoothing (ASW) holds 45 fps with the 5k+. But the FOV is amazing!

For the record you don't need the base stations for 3DOF tracking. Seated in DCS a single lighthouse 1.0 or 2.0 will work for 6DOF. While I agree the company has a lot of issues, they don't make the Vive stuff so they have to drop ship it from other suppliers and getting those Vive items in general right now without having to go through Pimax is hard. Getting the headset from China only took a couple of weeks.

As requested:

It seems like looking through this thread that it maybe doesn't work with the F/A-18, esepcially if the anti-skid is on. But even then it may not support it:

Again, recommend looking at Accel.x Like the cat, a wire trap is well over 3 G in that axis in the opposite direction. Will do when I get back to my computer. EDIT: Screenshot added

Yep, that! Your project is different application for sure, just throwing it out there for kneeboard usage like Andrew discussed :thumbup:

It's been done, developer moved away from display tablets to drawing tablets (no screen) to get better writing support since you don't see the tablet screen in VR and if you don't have a tablet to dedicate to it already you can get one of these drawing pads for $40USD. https://forums.eagle.ru/showthread.php?t=246970

We agree with basically the solution is what his asking for in a different wording :lol: We all agree that this would be more realistic than the what I'm doing now with holding down a random throttle button that doesn't exist on the F-16 throttle. I considered a macro but A. trying to move to a pure DX button in DCS mapping and B. concerned that I it would make my gun and/or laser intermittent.

That's not what happens when I try it. L never flashes with first detent unbound and second detent held to impact which misses using CCRP with TGP. First detent then bound to another button and L flashes the whole time it is held and results in a hit. It would be great for us that don't have a 2 stage could do this. I plan to use my X65F for F-16 for a long time still (I have spares) since it's force sensitive. My really only complaint about it is the lack of 2 stage trigger.