Werewolf_fs

OK. Thanks for the info!

AMD only supports foveated rendering under DX12, DCS is DX11.. That's why under OXRTK you don't have support, sorry.

@IronMike What are the chances of the AGM-45 B Shrike and AGM-78A/B Standard ARM being included in the future DMAS variant?. Thanks!

I answer myself.. reinstalling solved partial the problems, One server (instance 4), not running, same error....., all the others are working perfectly

Same problem, we have 4 instances and all 4 start but they can't be seen or managed after the update of August 9th "2024-08-10 15:24:24.351 ALERT Dispatcher (Main): Error starting dedicated server: [string "./MissionEditor/modules/Options\TabViewGraphics.lua"]:11: module 'MeSettings' not found: no field package.preload['MeSettings'] no file '.\MeSettings.lua' no file 'D:\DCS World OpenBeta Server\bin\lua\MeSettings.lua' no file 'D:\DCS World OpenBeta Server\bin\lua\MeSettings\init.lua' no file 'D:\DCS World OpenBeta Server\bin\MeSettings.lua' no file 'D:\DCS World OpenBeta Server\bin\MeSettings\init.lua' no file './Scripts/MeSettings.lua' no file './Scripts/Common/MeSettings.lua' no file './Scripts/UI/MeSettings.lua' no file './Scripts/UI/F10View/MeSettings.lua' no file './Scripts/UI/InputDeviceVisualizer/MeSettings.lua' no file './Scripts/UI/MultiplayerSelectRoleMap/MeSettings.lua' no file './Scripts/UI/RouteTool/MeSettings.lua' no file './Scripts/UI/View/MeSettings.lua' no file './Scripts/DemoScenes/MeSettings.lua' no file './dxgui/bind/MeSettings.lua' no file './dxgui/loader/MeSettings.lua' no file './dxgui/skins/skinME/MeSettings.lua' no file './dxgui/skins/common/MeSettings.lua' no file './MissionEditor/modules/MeSettings.lua' no file './dxgui/skins/skinME/MeSettings.lua' no file './dxgui/skins/common/MeSettings.lua'MeSettings no file '.\lua-MeSettings.dll' no file '.\MeSettings.dll' no file 'D:\DCS World OpenBeta Server\bin\lua-MeSettings.dll' no file 'D:\DCS World OpenBeta Server\bin\MeSettings.dll' 2024-08-10 15:24:24.351 INFO EDCORE (Main): (dDispatcher)enterToState_:2" dcs.log

Meta has released an update on the PTC channel today ,(Public Test Channel), for v68 and they have fixed the whole layer issue in OpenXR, so QVF and OpenXR toolkit are working again.

Great!!!, Thank you for everything, you are wonderful!!!!

No, but at least until meta change the version it detects it as V68 and I won't update it. If it happens, overwrite again

https://drive.google.com/file/d/15MKjcySAdbD6xE8Bq-fWVlYmrZvlmIpZ/view Folders, oculus-client, oculus-diagnostics, oculus-runtime v67. Stop ALL oculus services, unzip, copy and overwrite v68 to C:\Program Files\Oculus\Support, reopen meta app, and.... QVF and OpenXR toolkit work again.

V68 official launch... *EDIT nothing works but A particular solution, intall folders v67, oculus_vclient, oculus_diagnostics and oculus-runtime, about installing v68. I will be able to link to the files as soon as the drive allows me to.

I will modify my words... We need to do better, because it is proven that the ideal or better range of resolution is very very small or minimum.

As I indicate in this post: The problem with the different perception of the dot system between different users is working at different resolutions, as it works now, there is an ideal resolution at which it will work relatively well. If you increase this resolution it will become increasingly difficult to see it or if you reduce this resolution further and further down the black megadot will stand out. The system needs to scale according to the resolution or it will never be a complete solution for everyone.

@BIGNEWY. The problem with the current dot system in VR is scalability, the higher the resolution implies less visibility. With the version of 2.9.5 with QVF at approximately 4200x4300 (App oculus x1.0, oculus tray tools P.D. x1.8 + SS by default of QVF 1.1) the detection was super realistic, you detected it slightly at 16 miles, you saw it at 12-10 and at 4-5 you identified it and it eliminated the distant giant black pixel, without the QVF it could be seen clearly. Now with 2.9.6, at this resolution it is IMPOSSIBLE to see it until you are less than 3 miles away and even then at that distance it is difficult to maintain the tally, I should go down to 3200x3300 to have something similar again. You need to scales the spotting dot system with the resolution or this detection problem will never be solved. I don't know if that is even possible in DCS.

@mbucchia. You are absolutely right, and I just see the reason for this situation. With QVF the configuration (.ini) makes a slight supersmaplin, and for me it operates at 4259x4382, but when using VRS foveated in OpenXR Toolkit I operate at 3872x3984, so the performance is similar, although still slightly lower with VSR Foveated. But with QVF what I do notice is a slight suttering that does not happen to me with foveated VRS. CPU limitations?. Also the eye tracking of Foveated VRS is apparently faster, it is practically not noticeable if you look from one side to the other quickly, while the QVF is seen a few ms. My configuration is, Intel i9 13900KF, 64gb, RTX4090.

Aquí igual dcs.log-20240716-073004.zip