-
Posts
622 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Events
Everything posted by 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
-
[REPORTED]Problem in triple screen since the update
Alex Okean replied to FMAX's topic in Multi-Display Bugs
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
-
[FIXED INTERNALLY] 2.5.3.21444 Mouse cursor graphical glitch
Alex Okean replied to backspace340's topic in VR Bugs
ok ,thank you found issue and fixed internally -
[FIXED INTERNALLY] 2.5.3.21444 Mouse cursor graphical glitch
Alex Okean replied to backspace340's topic in VR Bugs
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
-
i just leave it here : Palm grip axis is used for selection of interaction hand (with green ray) Index trigger used as left mouse button mouse Thumbstick as mouse wheel, X as escape button, Y as centering, A as zoom Specially for Oculus in Steam VR: new command line option -force_steam_VR added, it allows to use Steam API for Oculus Known issues: - GUI renders on front - no controls mapping for VIVE
-
LoGetWindAtPoint return wind vector at desired point local vx,vy,vz,absolute_height = LoGetWindAtPoint(x,y,z,is_radio_alt) to get direction of wind: local direction_in_radians = math.atan2(vz,vx); (or math.atan2(-vz,vx) depends of what sign you prefer )
-
already here dcs.exe --force_enable_VR dcs.exe --force_disable_VR
-
"over the shoulder" fix for track IR is not included to this update , but fixed already in internal version ( together with combined arms TIR and VR sight camera ) . Overall using of Track IR is fixed - slanted view bug , mouse interraction etc.
-
[REPORTED]Oculus View Reset No Longer Works (Hotfix 3)
Alex Okean replied to Deano87's topic in General Bugs
NUMPAD 5 actually mandatory used for Rift and Vive reset because of i was in need to get it working in main menu , previously reset was not available there. (and actually yes , numlock affected to it's state , sorry this is bug:) ) I will look to alternatives how to make it reassignable again and keep working everywhere same time. -
local value = env.getValueDictByKey(key)
-
probably DCS lost focus , Alt + TAB should help
-
Howto make specific KNEEBOARD pages for special aircraft?
Alex Okean replied to uboats's topic in DCS World 1.x (read only)
Kneeboard already have functionality for per unit separation see part of Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD\indicator\init.lua local terrain_path = get_terrain_related_data("KNEEBOARD") local common_path = LockOn_Options.common_script_path.."KNEEBOARD/indicator/CUSTOM" local user_path = lfs.writedir().."KNEEBOARD" local unit_name = get_aircraft_type() if unit_name ~= nil then scan_path(terrain_path..'/'..unit_name) scan_path(common_path ..'/'..unit_name) scan_path(user_path ..'/'..unit_name) end it means that itry to find images for unit in three folders : inside active terrain folder Bazar\Terrain\Kneeboard for example for P-51D it will try to scan Bazar\Terrain\Kneeboard\P-51D folder inside self kneeboard folder Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD\indicator\CUSTOM\P-51D and inside user dir C:\Users\<USER>\Saved Games\DCS\KNEEBOARD\P-51D also it try to find pages inside mission with same pattern <MIZ_FILE_ROOT>/KNEEBOARD/<UNIT_NAME>/IMAGES/ -
guys i am under NDA , but we use a slightly newer SDK than you can find , where core things are changed
-
recomended scale factor has nothing with black borders cause borders is conected with recomended FOV , installed lenses and nose-to-screen distance . scale factor is intended for optimal pixel density in the screen center