manashttu

I tried 310.3.0 tonight. Using DLAA, ghosting is almost non-existent now. Tried using preset J and K---to my eye, K looks very crisp with only the slightest occasional ghosting looking down in F3 view with a plane flying over water. K looks sharper than J. DLSS/DLAA has come a long way with DCS.

Attached is the server.lua that works on my end. It is in the saved games folder under users--the following is the directory tree. \users\[your user]\Saved Games\DCS\Config\View Server.lua

It does work on my end. But, I already had a server.lua in my saved games\dcs\config\views folder. When I'm back at my flight pc, I'll upload my server.lua file. Maybe you could put try using my file and see if it works.

If you had to create a server.lua file, I suspect the one created doesn't have all the info DCS needs and it's reverting back to the server.lua in the install folder of DCS. Since you didn't already have a server.lua in the saved games/DCS/config/View folder, you might try copying the server.lua from the install folder of DCS\config\view folder to the saved games\dcs\config\view folder. Then edit that one and copy the string I posted above.

Through some experimentation, I found that putting the following entries in the Server.lua in \Users\ . . .\Saved Games\DCS\Config\View\ folder allows an increase of the maximum FoV for the Corsair to 140. ViewSettings["F4U-1D"] = { Cockpit = { [1] = {-- player slot 1 CockpitLocalPoint = {0.00,0.00,0.00}, --{-2.00,0.62,0.00}, CameraViewAngleLimits = {20.00,140.00},--/N/ best non-distorted image at 30..70 CameraAngleRestriction = {false,90.00,0.50}, CameraAngleLimits = {180.00,-80.00,90.00}, EyePoint = {0.00,0.00,0.00}, ShoulderSize = 0.15, Allow360rotation = false, limits_6DOF = {x = {-0.05,0.35},y ={-0.20,0.10},z = {-0.22,0.22},roll = 90.00}, --limits_6DOF = {x = {-0.50,0.65},y ={-0.40,0.40},z = {-0.52,0.52},roll = 90.00}, -- just for testing }, }, -- Cockpit Chase = { LocalPoint = {-13.0, 2.0, 0.0},--{-3.0, 2.5, 0.0}, AnglesDefault = {180.0, 0.0}, }, -- Chase Arcade = { LocalPoint = {-21.5, 5.6, 0.0}, AnglesDefault = {0.0, -8.0}, }, -- Arcade } ViewSettings["F4U-1D_CW"] = { Cockpit = { [1] = {-- player slot 1 CockpitLocalPoint = {0.00,0.00,0.00}, --{-2.00,0.62,0.00}, CameraViewAngleLimits = {20.00,140.00},--/N/ best non-distorted image at 30..70 CameraAngleRestriction = {false,90.00,0.50}, CameraAngleLimits = {180.00,-80.00,90.00}, EyePoint = {0.00,0.00,0.00}, ShoulderSize = 0.15, Allow360rotation = false, limits_6DOF = {x = {-0.05,0.35},y ={-0.20,0.10},z = {-0.22,0.22},roll = 90.00}, --limits_6DOF = {x = {-0.50,0.65},y ={-0.40,0.40},z = {-0.52,0.52},roll = 90.00}, -- just for testing }, }, -- Cockpit Chase = { LocalPoint = {-13.0, 2.0, 0.0},--{-3.0, 2.5, 0.0}, AnglesDefault = {180.0, 0.0}, }, -- Chase Arcade = { LocalPoint = {-21.5, 5.6, 0.0}, AnglesDefault = {0.0, -8.0}, }, -- Arcade } This is a transfer of the base settings (with max fov of 110 increased to 140) from the Corsair settings in the main DCS folder. Since this is a change in the Saved Games folder instead of the game folder, it works with multiplayer. I suspect fiddling with the eyepoint and other settings can work to tune the seating position, too . . . though I have yet to try tuning that.

Through some experimentation, I found that putting the following entries in the Server.lua in \Users\ . . .\Saved Games\DCS\Config\View\ folder allows an increase of the maximum FoV for the Corsair to 140. ViewSettings["F4U-1D"] = { Cockpit = { [1] = {-- player slot 1 CockpitLocalPoint = {0.00,0.00,0.00}, --{-2.00,0.62,0.00}, CameraViewAngleLimits = {20.00,140.00},--/N/ best non-distorted image at 30..70 CameraAngleRestriction = {false,90.00,0.50}, CameraAngleLimits = {180.00,-80.00,90.00}, EyePoint = {0.00,0.00,0.00}, ShoulderSize = 0.15, Allow360rotation = false, limits_6DOF = {x = {-0.05,0.35},y ={-0.20,0.10},z = {-0.22,0.22},roll = 90.00}, --limits_6DOF = {x = {-0.50,0.65},y ={-0.40,0.40},z = {-0.52,0.52},roll = 90.00}, -- just for testing }, }, -- Cockpit Chase = { LocalPoint = {-13.0, 2.0, 0.0},--{-3.0, 2.5, 0.0}, AnglesDefault = {180.0, 0.0}, }, -- Chase Arcade = { LocalPoint = {-21.5, 5.6, 0.0}, AnglesDefault = {0.0, -8.0}, }, -- Arcade } ViewSettings["F4U-1D_CW"] = { Cockpit = { [1] = {-- player slot 1 CockpitLocalPoint = {0.00,0.00,0.00}, --{-2.00,0.62,0.00}, CameraViewAngleLimits = {20.00,140.00},--/N/ best non-distorted image at 30..70 CameraAngleRestriction = {false,90.00,0.50}, CameraAngleLimits = {180.00,-80.00,90.00}, EyePoint = {0.00,0.00,0.00}, ShoulderSize = 0.15, Allow360rotation = false, limits_6DOF = {x = {-0.05,0.35},y ={-0.20,0.10},z = {-0.22,0.22},roll = 90.00}, --limits_6DOF = {x = {-0.50,0.65},y ={-0.40,0.40},z = {-0.52,0.52},roll = 90.00}, -- just for testing }, }, -- Cockpit Chase = { LocalPoint = {-13.0, 2.0, 0.0},--{-3.0, 2.5, 0.0}, AnglesDefault = {180.0, 0.0}, }, -- Chase Arcade = { LocalPoint = {-21.5, 5.6, 0.0}, AnglesDefault = {0.0, -8.0}, }, -- Arcade } This is a transfer of the base settings (with max fov of 110 increased to 140) from the Corsair settings in the main folder. Since this is a change in the Saved Games folder instead of the game folder, it works with multiplayer. I suspect fiddling with the eyepoint and other settings can work to tune the seating position, too . . . though I have yet to try tuning that.

The link I provided has a "How to Use" section if you scroll down the page. It's a little involved, but pretty logical.

Check out a tool called Devreorder. It's here at Github: https://github.com/briankendall/devreorder I've used it for years for games like IL2 1946 and others to dictate the order the game sees controllers. It's a little involved, but straightforward to set up for individual games.

I am running triple 1440p on a 4090. Installed new drivers last week and used nvidia Profile Inspector to force DLSS4 usage by DCS. The tangible improvement I’ve seen is the ability to use DLAA instead of MSAA 4x with no or barely perceptible ghosting. Previously, the ghosting was pretty bad, offsetting the better antialiasing and fps offered by DLAA. DLAA looks amazing to me, even better than MSAA, and runs very smooth in comparison. DLSS upscaling is improved a lot…much reduced ghosting, but it is still noticeable. The boost in fps from DLAA (which is already a big jump in fps from MSAA) isn’t worth the ghosting.

That looks great. Where did you source the 0.5mm silicone sheet?

With the tracking started, open this tab in Opentrack and tweak the Threshold under Point Extraction until all three lights consistently have a tracking circle around them. It's a bit trial and error, but it ensures the Puck lights are tracked and any stray flashes of light are not.

The camera mount has some adjustability to allow for tilt, so it will work on top of a monitor fine. It just needs to be positioned such that all three LED's on the head tracker are detected simultaneously.

Amen to that. salival007's F-4E profile is really cool.

Ok. When I fiddled with multiple viewports using the 3 monitor setting, I had some luck with the attached lua. You might compare it to your 3cameras.lua, or back yours up and replace it with this one and see if it helps. Months ago when I experimented, I found using Surround and a single monitor setting to be preferable, as it had better performance, was easy to set up, and maintained usable view at varied FoV's. I run my FoV in Surround at 120, zooming out to max 140 from time to time. 120 is pretty zoomed in, but to me it presents a near 1:1 size presentation of the cockpit sitting about 24-30 inches from the screen. Also, any fisheye/warping is eliminated at 120 FoV. I'm not sure what FoV number works best on the 3cameras setting, as the number ranges differently in Surround. 3Cameras.lua 1Camera.lua

I find the F16EX, particularly with the shaker addon with the additional hat and axis, is an ideal universal stick for modern, cold war, and even warbirds. I am using it the the F-4 and it translates easily, with switches to spare, of course.

They can be used to tighten-up the on-center feel of the stick.

Couple of questions---hopefully I can help. What resolution are your 32" monitors? Are you running nvidia GPU? I'm running triple 32 1440p monitors on nvidia Surround at 7770x1440 using the bezel correction tool in nvidia Control Panel. If your monitors are 1440p and you set up surround, maybe I can share a couple of my ini files to get you fixed up.

The StreamDeck is totally worth it. Extremely versatile. There are some excellent profiles on the DCS user uploads, as well. By the way, I've been using StreamDeck for quite some time and have yet to have an update mess up the ExportScripts profiles.

The key for me to virtually eliminate the step in transition from displacement to force was to set the displacement value at 7 %. The 2 % dead zones I used were to simply help with re-centering. Not sure it's even necessary, as it seems DCS has a hard-coded deadzone on the Viper even when set to zero in game.

I recently procured an Orion2 MFSSB base and grip, having read through this and other threads about the potential to tweak the physical gimbal and software. I must say it was somewhat out of curiosity to compare to my previous indulgences which were second-hand purchases of an RS R3 Lighting (Meant be be lightning?) with a Warthog grip w/ custom angle-mount and an R3 Ultra with an RS Viper grip. In the end, with the following physical and software tweaks, the WW MFSSB compares nicely to the R3 Lighting, which I already prefer slightly over the R3 Ultra. First the physical adjustments: I 3-d printed Beezer's excellent insert for each axis to place around the bearing which makes contact with the force sensors. To do this, I loosened (but did not remove) the MFSSB pcb's, inserted Beezer's spacer, then re-tightened the pcb. This set the spacer evenly within the force sensor and still allowed for very slight movement in the center. Then, I installed all six spring plates on each axis, and used the set screws to center the axis while connected to the software. This took a bit of fiddling and adjusting, but it wasn't difficult or too time consuming. Beezer's spacers and the spring plates gave a nice feel with very slight movement around center and a nice, virtually undetectable (by feel) transition from center spring to force application. To the software tweaks: Even with Beezer's insert, there remained a deadzone if the MFSSB Config settings were left on "Force Only". Physically, I found this deadzone desirable, as it allowed what I perceive to be pretty realistic initial movement of the stick. To eliminate the dead zone and the oft-criticized software transition from displacement to force sensing, I came down to the following MFSSB Config and Dead Zone settings: null nullWith these tweaks, there is virtually no software flat spot or deadzone at either the center or in the transition from displacement to force sensing. As far as comparison of the three bases and grips now: I really like the WinWing F-16 grip. It has excellent build quality, and, much like my WW throttles, I love the switches (especially the trigger). I'm torn now between the R3 Lighting base and the WW base---they perform quite similarly. The RS software is outstanding, I have to say. The Ultra base---despite the rave reviews online, I find it a bit sponge-y, for lack of a better term. I prefer the firm feel of the Lighting and WW bases. I rather like the very slight, free movement in the center of the WW base now that the physical tweaks were done. Without Beezer's insert, the free movement on center was way too big. Can't thank Beezer enough for sharing the stl file of his spacer design. It is brilliant. The sum of the matter is this: If I were confronted with the choice of dishing out $1,100 to $1,200 for an R3 and grip shipped to the U.S. vs the $500 or so shipped for an MFSSB (with these physical adjustments) and the wonderful WW F-16 grip, I'd strongly consider the latter. Hope this is helpful.null

Haha. Yeah---the naming conventions are pretty obscure. I just found it a while back by opening one after the other.

On Winwing's downloads page, they have pdf manuals available. Look for this one for the MFSSB kit: EX2_J2_2-User Manual EN V1.1

Looks really nice. I would be interested. I'm in Texas.

Running 5800x3d. Upgrade from 3090 to 4090 took fps up 75 to 200 percent on my triple 1440p setup, depending on map and situation; and DCS frametime counter still reports GPU as limiting factor in multithreaded DCS. You're in for a treat.

Love this tool, SkateZilla. THANK YOU.