Alex Okean

part of 'Config\MonitorSetup\3Cameras.lua' --[[ also you can use "displays" table to perfectly match you configuration . it is generated by DCS automatically. displays table is contains information about all currently attached displays for example my setup is : displays = { [1] = { x = 0, -- note : x == 0 and y == 0 is always mark primary windows display y = 0, width = 1920, height = 1200 }, [2] = { x = -1440, -- mark that secondary display is on left side of primary display y = 0, width = 1440, height = 900 }, ... for all displays } screen table also contain x, y members which mark top left corner of DCS window note about fullscreen : directx doesn't allow fullscreen applications with resolutions more than primary display can handle, so multimonitor presets in DCS will fall back to windowed mode if fullscreen initialization failed ( this info also will be printed to dcs.log) for reconfigure viewports setup for each unit type independently you can declare here function function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "A-10C" then Viewports = ... define new Viewports table -- also you can define cockpit displays viewports here RIGHT_MFCD = ... define new RIGHT_MFCD viewport else Viewports = ... define default for others RIGHT_MFCD = nil -- remove for others end end --]]

DCS internal bug - fixed internally will be in next openbeta build

that was epic fail from my side . sorry , i will update binary visualizer.dll as soon as possible Attached Visualizer.dll in zip should help Visualizer_fix_reset_projection.zip

2.5.4.27314 in 2.5.4.27314 this tool window will appears for all users of Odyssey headsets , also added ability to save you setting in to the file to do not bother you next launch

Next investigation round I need volunteers for further investigation There is another version of Visualizer.dll attached for latest Openbeta with Debug tool window for Odyssey workaround . there is slider control for each projection component and three buttons RESET PROJECTION - revert all sliders positions to factory defaults MAKE SYMMETRIC USING LEFT - copy left eye setting to the right eye MAKE SYMMETRIC USING RIGHT - copy right eye setting to the left eye If "MAKE SYMMETRIC" buttons will help you , please post your feedback here 4 rows at the bottom - eye to head projection matrix for each eye. post your screens any feedback is usefull . VisualizerWithOpenVRDebug.zip

Post your options , please

As stop gap solution until new build arrives there is new version of Visualizer.dll inside zip available at link https://forums.eagle.ru/attachment.php?attachmentid=202447&d=1547806234 Unpack it into DCS/bin folder , it will fix viewport handling attachment originally from this post https://forums.eagle.ru/showpost.php?p=3763716&postcount=28

Diagnostic bins Guys who have problem with crosseye : there is attached Visualizer.dll with diagnostic print enabled , please download it , unpack and place into DCS/bin folder after that in DCS.log you will find blocks like this 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR Projection///////////////////////////////////////////////////////////// 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR Projection Bounds Eye 0: 1.24345,1.03872,1.41314,1.42582 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR GetProjectionMatrix(0,150000,0.02) result: 0.87636,0.00000,-0.08971,0.00000 0.5f,0.00000,0.70449,0.00447 0.5f,0.00000,0.00000,0.00000 0.5f,0.00000,0.02000,0.00000 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR Projection Converted to DCS: 0.87636,0.00000,0.00000,0.00000 0.5f,0.00000,0.70449,0.00000 0.5f,0.00000,0.08971,0.00447 0.5f,-0.00000,1.00000,0.00000 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR ed::makePerspectiveForHMDProjection result : 0.87636,0.00000,0.00000,0.00000 0.5f,0.00000,0.70449,0.00000 0.5f,0.00000,0.08971,0.00447 0.5f,-0.00000,1.00000,0.00000 2019-01-18 08:51:14.782 INFO VISUALIZER: ------------------------------------------------------------------------------------- 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR Projection Bounds Eye 1: 1.05205,1.22679,1.42065,1.42600 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR GetProjectionMatrix(1,150000,0.02) result: 0.87764,0.00000,0.07668,0.00000 0.5f,0.00000,0.70258,0.00188 0.5f,0.00000,0.00000,0.00000 0.5f,0.00000,0.02000,0.00000 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR Projection Converted to DCS: 0.87764,0.00000,0.00000,0.00000 0.5f,0.00000,0.70258,0.00000 0.5f,0.00000,-0.07668,0.00188 0.5f,-0.00000,1.00000,0.00000 2019-01-18 08:51:14.782 INFO VISUALIZER: OpenVR ed::makePerspectiveForHMDProjection result : 0.87764,0.00000,0.00000,0.00000 0.5f,0.00000,0.70258,0.00000 0.5f,0.00000,-0.07668,0.00188 0.5f,-0.00000,1.00000,0.00000 2019-01-18 08:51:14.782 INFO VISUALIZER: /////////////////////////////////////////////////////////////////////////////// i want to collect these logs to investigate issue deeper Visualizer.zip

Hello guys , I definitely cannot reproduce this issue with my headset Samsung Odyssey 800ZAA , Do you have any workaround ? Is it related to original Odyssey headset or reproduced only on Odyssey+ , can it be reproduced for other vendors ? any other info will be helpful

Hello guys , I definitely cannot reproduce this issue with my headset Samsung Odyssey 800ZAA , Do you have any workaround ? Is it related to original Odyssey headset or reproduced only on Odyssey+ , can it be reproduced for other vendors ? any other info will be helpful

ok ,thank you found issue and fixed internally

in 2.5.3.21444 this issue should be fixed , if it still reproduced for you please post your DCS.log, options , and describe your scaling settings in windows

It is definitely problem with your "2_monitors-FA18C.lua" file : dcs is execute this file to extract preset name ( this name then pushed into the selection listbox in options ) , problem is that this execution is not completely guarded - we will fix it. but now i recommend to remove this failed file or fix it manually ( update : fixed internally rev #141259 - monitor setup execution is now properly guarded )

it was internal ED problem , not RAZBAM. fixed today in internal build (for Larry : rev #141159 )

Touch controllers use builtin profile for VR. But any HOTAS is also used as input for aircraft : DCS input works as layered system - one of them is UI layer , other layers - are aircraft specific Most likely your HOTAS button assigned twice - one in UI layer , and the other one in aircraft layer , and aircraft layer is in priority . that is why do not see reaction on zoom assignment