13WELT_JankeS

Unfortunately, I don't have large production capabilities. The production process of my project took place by abusing friendly relations and harassing a few people ;) The only thing I can share is my idea ;P

Of course there is no problem - I send more detailed plans in PDF ;) https://1drv.ms/u/s!Al5ZBRu6iKgyoFlZiSWWn3qIPHF2?e=PdXExz

By default the base is straight, I leaned 13 degrees forward to have the handle skewed exactly the same as in a real F-16. The FSSB has centered itself.

I made a dedicated stick design. The whole construction is welded from stainless steel, so it is very stiff. I used the upper holes in the Playseat chair, only gave 8mm screws. At the bottom I made holes in the same places.

I finally attached my FSSB R3L to the chair (Playseat Airforce) - this is how it works: It's great - I'm waiting for Viper to get used to the new aircraft with the new control ;) My serial number 139 :)

Thanks, Mate! I will not hesitate to ask if necessary ;)

Thank you for the information - I will definitely check it out. I just bought the FSSB R3L and haven't even connected it yet. I'm just building the base of the joystick and I'm waiting for the F-16CJ :pilotfly: ;)

Thank You very much for information! I'm just building a VR F-16 cockpit with FSSB and I was wondering if the stick is twisted ;)

Does anyone know if the stick on the F-16C Block 50 is tilted from the longitudinal axis of the plane towards the pilot at an angle of 12 degrees? As the picture shows.

I know exactly what you write about. I know that pain. You can set FOV to small and the effect when rotating is the same. Maybe after the update DCS will squeeze over 64fps and then it will be possible to set the goggles to 64Hz and bypass smartsmoothing. I think that eventually Pimax programmers will deal with it, but it is not known whether and how long it will take.

Have you checked this improvement also on Pimax 5K + on a large FOV?

Of course I wrote about it on the Pimax forum. The guys are working on it, I hope that soon the operation of smart smoothing will be improved.

The operation of smart smoothing in this version is a disaster. They made a terrible ghosting. Frame generation times of 12-13 ms for GPU and CPU (i8700k 4.8GHz and 2080Ti), but unfortunately there is a double vision. I hope that after the optimizing update for VR we will be able to reduce the refresh rate and enjoy a smooth game without smart smoothing. At the moment in DCS it works very badly.

Yes it was fun :) But at first I thought that my RTX card was dying because of GDDR6 failure... :P

Now it works well - thanks Alex! If someone wanted to change something after pressing SAVE, he must exit DCS delete the file "Samsung Mixed Reality 800ZBA.lua" in SAVED GAMES \ DCS folder and restart.

Thanks Alex, i saved the setting for the menu - I pressed save and close, but in the cockpit the picture was crossed again. How do I call the settings window to set the image for the cockpit?

I checked it by setting it like SPARKAM user, that is L_TOP data goet to R_TOP, and R_TOP goes to L_TOP. Same for L_BTM R_BTM and actually is better than using only the symmetry button. I wonder how other applications start up that does not have this problem. As you can see, each Samsung goggle has different factory values. Many users do not even know that in DCS it can have an image shift if this offset is small. I launched fpsVR today - it is perfectly visible in goggles. DCS starts with a very double image, a symmetry button, then a slight correction of the settings and it seems that it is ok. But fpsVR immediately sets everything up and works on every goggles just as - I wonder where this small malicious difference lies. Fortunately, the work on the problem is already so advanced. Thank You very much for your work!

Oh Holy Mother! I just checked the symmetry setting and it works! I'm not sure if it is perfectly aligned but it is 1000 times better. I tried for the left and right eyes and it's okay anyway. Although it seems to me that it looks more comfortable with the symmetry of the left eye. You have to set the symmetry after each uploading the mission - but this does not seem to be a problem at the moment :) Whooohoooo finally, the promils have gone down from the bloodstream and I do not have a double picture like after a booze: D Here are my screenshots before setting the symmetry with the left eye and after: https://1drv.ms/f/s!Al5ZBRu6iKgygxurfdpHtDw4D3tR

I also try to follow topics related to this but no new official news for now. Unfortunately, today's update did not even mention the problem: / In addition, I noticed that from two updates after the launch of DCS by Revive Night Vision works only in the left eye. By running normally through SteamVR with crossed eyes, night vision works in both.

Unfortunately, also update number 2.5.4.26552 did not change the problem of the image's misalignment.

Yes exactly. only with Revive you can use DCS for now.

And then the image is perfectly aligned;)

I tried, but there is no data in the log at that time.

On my goggles, the effect of crossed eyes is very visible. Here is the record from my DCS.log: Projection///////////////////////////////////////////////////////////// 2019-01-18 13:41:47.316 INFO VISUALIZER: OpenVR Projection Bounds Eye 0: 1.24654,1.04049,1.43916,1.41800 2019-01-18 13:41:47.316 INFO VISUALIZER: OpenVR GetProjectionMatrix(0,150000,0.02) result: 0.87450,0.00000,-0.09010,0.00000 0.5f,0.00000,0.70000,-0.00740 0.5f,0.00000,0.00000,0.00000 0.5f,0.00000,0.02000,0.00000 2019-01-18 13:41:47.316 INFO VISUALIZER: OpenVR Projection Converted to DCS: 0.87450,0.00000,0.00000,0.00000 0.5f,0.00000,0.70000,0.00000 0.5f,0.00000,0.09010,-0.00740 0.5f,-0.00000,1.00000,0.00000 2019-01-18 13:41:47.316 INFO VISUALIZER: OpenVR ed::makePerspectiveForHMDProjection result : 0.87450,0.00000,0.00000,0.00000 0.5f,0.00000,0.70000,0.00000 0.5f,0.00000,0.09010,-0.00740 0.5f,-0.00000,1.00000,0.00000 2019-01-18 13:41:47.316 INFO VISUALIZER: ------------------------------------------------------------------------------------- 2019-01-18 13:41:47.316 INFO VISUALIZER: OpenVR Projection Bounds Eye 1: 1.04728,1.23286,1.41837,1.42546 2019-01-18 13:41:47.316 INFO VISUALIZER: OpenVR GetProjectionMatrix(1,150000,0.02) result: 0.87714,0.00000,0.08139,0.00000 0.5f,0.00000,0.70328,0.00249 0.5f,0.00000,0.00000,0.00000 0.5f,0.00000,0.02000,0.00000 2019-01-18 13:41:47.316 INFO VISUALIZER: OpenVR Projection Converted to DCS: 0.87714,0.00000,0.00000,0.00000 0.5f,0.00000,0.70328,0.00000 0.5f,0.00000,-0.08139,0.00249 0.5f,-0.00000,1.00000,0.00000 2019-01-18 13:41:47.316 INFO VISUALIZER: OpenVR ed::makePerspectiveForHMDProjection result : 0.87714,0.00000,0.00000,0.00000 0.5f,0.00000,0.70328,0.00000 0.5f,0.00000,-0.08139,0.00249 0.5f,-0.00000,1.00000,0.00000 2019-01-18 13:41:47.316 INFO VISUALIZER: ///////////////////////////////////////////////////////////////////////////////

The problem concerns only WMR sets from Samsung: Odyssey and Odyssey Plus. For me, after the last update, nothing has changed. But I received information about further work on solving the problem: TomMicrosoft writes: "Hey all we are working with DCS to confirm that we have a DCS update - it is not a WinMR update, but we should have a better idea soon. a full grasp on the fix we'll be reaching out to additional devs (iRacing, Euro Truck Sim) " I think that they will be able to fix it soon.