Jump to content

Search the Community

Showing results for tags 'wmr'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • Official Updates
    • Community News
  • DCS World Tutorial & Training Range
    • New User Briefing Room
    • Guides & Tutorials
  • English
    • Digital Combat Simulator
    • DCS World War II
    • DCS World Topics
    • Licensed Third Party Projects
    • Reality
    • Legacy Versions
  • International support
  • Русский
  • DCS Finland's DCS Finland
  • 3Sqn's 3Sqn
  • 49th Black Diamonds's 49th Black Diamonds
  • -=Пилотажники=-'s -=Пилотажники=-
  • Polacy's Polacy
  • = Flammeus Vulpes = fighting squadron's = Flammeus Vulpes = fighting squadron
  • Banda-DV's Banda-DV
  • Comedy Central's Comedy Central
  • =UVAF='s =UVAF=
  • 100 KIAP's 100 KIAP
  • VVS 504th Red Hammers's VVS 504th Red Hammers
  • Lock-On Mod Makers's Lock-On Mod Makers
  • Sweden's Sweden
  • Leftside Limited Tech section's Leftside Limited Tech section
  • Ground Troops Aviation Training Center's Ground Troops Aviation Training Center
  • German DCS Community's German DCS Community
  • Spanish DCS Community's Spanish DCS Community
  • °United Fight Spirits° - Germany's °United Fight Spirits° - Germany
  • Чат's Чат
  • RedRodgers's RedRodgers
  • Совместные вылеты онлайн's Совместные вылеты онлайн
  • -=Air piretS=-'s -=Air piretS=-
  • Клуб Веселых Пилотов/Smile Pilots Club's Клуб Веселых Пилотов/Smile Pilots Club
  • 161 Squadron's 161 (Recce) Squadron
  • German DCS Serveradmins's German DCS Serveradmins
  • Escuadrón 701, Colombia's Escuadrón 701, Colombia
  • LowLand Tiger Meet's LowLand Tiger Meet
  • 279KIAP Regiment's 279KIAP Regiment
  • Australian DCS Community's Australian DCS Community
  • Scandinavia's Scandinavia
  • Crazy Canuks's Crazy Canuks
  • The Silver Falcons's The Silver Falcons
  • 127Th Sibйrian Tiger's 127Th Sibйrian Tiger
  • 129th A-10 Squad: The Guard Sharks's 129th A-10 Squad: The Guard Sharks
  • Virtual Red Arrows's Virtual Red Arrows
  • Hellenic Pilots's Hellenic Pilots
  • =2IAE='s =2IAE=
  • 16th ACCW Tigers DEN's 16th ACCW Tigers DEN
  • USMC Veterans's USMC Veterans
  • United States Air Force's United States Air Force
  • =BAF='s =BAF=
  • Fighter Combat Simulations's Fighter Combat Simulations
  • =Воздушные Войны= aka =BB='s =Воздушные Войны= aka =BB=
  • CADelta's CADelta
  • DCS: Combined Arms's DCS: Combined Arms
  • Oceanic Wing and Friends's Oceanic Wing and Friends
  • The Virtual Horsemen's The Virtual Horsemen
  • Hellas's Hellas
  • NoPryl Warthog Squadron's NoPryl Warthog Squadron
  • Aeronautica Militare Virtuale Italiana's Aeronautica Militare Virtuale Italiana
  • Carrier Air Wing Seventeen — CVW-17 —'s Carrier Air Wing Seventeen — CVW-17 —
  • 蜂鸟特技飞行表演队 HummingBird Aerobatics Team's 蜂鸟特技飞行表演队 HummingBird Aerobatics Team
  • 1st Cav Div (Air Assault)'s 1st Cav Div (Air Assault)
  • CrimsonFlag - 102° GVv's CrimsonFlag - 102° GVv
  • AIEclan's AIEclan
  • Virtual Black Sheep's Virtual Black Sheep
  • 929th's 929th
  • French DCS Community's French DCS Community
  • 373rd Online Tactical Campaigns's 373rd Online Tactical Campaigns
  • Just For Laughs Simulation DCS's Just For Laughs Simulation DCS
  • "Russian Air Force" =RAF='s "Russian Air Force" =RAF=
  • ECV56 Cóndor's ECV56 Cóndor
  • Master Arms's Master Arms
  • 141 Wolfs's 141 Wolfs
  • 314. ШАП Моздок (Су-25)'s 314. ШАП Моздок (Су-25)
  • Escuadrón 117's Escuadrón 117
  • Austian/Germany Pilots's Austian/Germany Pilots
  • Итория авиации's Итория авиации
  • Clan Vikingos's Clan Vikingos
  • Virtual Royal Danish Airforce's Virtual Royal Danish Airforce
  • United Operations Air Forces's United Operations Air Forces
  • United States Navy's United States Navy
  • Europe clan's Europe clan
  • No.66 Squadron's No.66 Squadron
  • De Belgae's De Belgae
  • v47th Fighter Squadron's v47th Fighter Squadron
  • 105 Wirtualny Pułk Śmigłowców Bojowych (105th Virtual Combat Helicopters Regiment).'s 105 Wirtualny Pułk Śmigłowców Bojowych (105th Virtual Combat Helicopters Regiment).
  • 7 Wirtualna Eskadra Działań Specjalnych's 7 Wirtualna Eskadra Działań Specjalnych
  • 223rd CAS "Wolfpack"'s 223rd CAS "Wolfpack"
  • www.TAW.net - DCS Division's www.TAW.net - DCS Division
  • Jagdfliegergeschwader 1 “Fritz Schmenkel” (JG-1)'s Recruitment
  • 64th Aggressor Squadron - Public's Images and Videos
  • =BK= Братские крылья's Связь
  • =BK= Братские крылья's Сервера =BK=
  • =BK= Братские крылья's Вопросы
  • Virtual Carrier Air Wing 1's Topics - Bugs
  • Virtual Carrier Air Wing 1's COOP Flights - Request
  • Virtual Carrier Air Wing 1's Video and Live Feed
  • Virtual Carrier Air Wing 1's Recruitment questions
  • Air Combat Wings's Video
  • DTA - Comunidad Hispana de DCS's Muro
  • Virtual Skyblazers's Information
  • Virtual Skyblazers's Conversation
  • The Flying Kiwis's The Flying Kiwis Zorb ball of death dedicated server
  • The Flying Kiwis's ANZAC Mission
  • LINCI's Discussioni
  • [OFS] Open Flight School's Informationen
  • The Pirates Cove's Mods
  • The Pirates Cove's C-130 MOD
  • VF-211's Contact us
  • Comunidad Española de DCS - Interescuadrones's Discusiones
  • Sabre Squadron's Campaign & Mission Updates
  • Neko PMC's Topics
  • 74th Flying Tigers's Questions and Answers
  • 300th Fighter Regiment's Currently Accepting Pilots
  • Cerberus Fighter Wing's Screenshot Posting
  • Digital Coalition Air Force's Posts/Forum
  • Strike Fighter Squadron's VMFA-35 Skin by Stellou
  • 1st VFW's General Discussion
  • VFA-41 Black Aces's VFA-41 Black Aces Squadron Info
  • 154th Air Wing's New Server
  • Task Force Uniform Charlie Sierra's Links
  • delete's The discord link
  • 1(F) Squadron RAF Air UK's Operations
  • TFB 8's Dedicated Public Servers
  • Nemesis HAW's Topics
  • 枝江虚拟航空队's 涂装展览
  • 511th Fighter Squadron- Virtual Vultures's Public Affairs
  • 「301sq」Virtual Squadron's MemberShip


  • Community Calendar
  • Jagdfliegergeschwader 1 “Fritz Schmenkel” (JG-1)'s Events
  • ASOR 234 squadron's Operations
  • 11TSG's Events
  • 51st Virtual Fighter Wing's Events
  • DCS Español || D3W's Calendario
  • DTA - Comunidad Hispana de DCS's Eventos
  • Carrier Air Wing 66's Events
  • DCS - Allied Forces - Open Missions and Beyond's Events
  • The Flying Kiwis's TFK Flying schedule
  • VF-211's Training nights
  • VF-211's Calendar
  • Comunidad Española de DCS - Interescuadrones's Eventos
  • Neko PMC's Events
  • VFA-86 Sidewinders's Winder schedule
  • 74th Flying Tigers's Trainings and Missions
  • 300th Fighter Regiment's Events
  • Cerberus Fighter Wing's Events
  • Digital Coalition Air Force's Events
  • uosef's عقابهای ایران
  • v81st Fighter Squadron's Training and Operations
  • Darkwater Aerial Security Ltd. (Task Force "Caucasus Dragons")'s Contracts and Operations
  • Darkwater Aerial Security Ltd. (Task Force "Caucasus Dragons")'s Events
  • Delta Force Squadron's Events
  • Virtual Fighter Group's Schedule
  • 71st Laughing Rooks's 71st Events
  • Virtual Air Festivals's VAF Events

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Flight Simulators





Found 4 results

  1. 2.7.7 BETA WIP Overview These are my settings, and they are what work for me. Your settings may vary, there is no single right answer for this. Lots of things come together, Game settings, Steam Settings, WMR Settings, Windows config, BIOS/UEFI, to provide the final experience. If you want to play with these settings for your own benefit crack on. That said when you are either applying these settings or making changes to them do ONE change at a time and evaluate the result, and this is the bit that is going to hurt, don’t assume that it didn’t have an effect just because on you didn’t observe a direct impact… it’s like “Lego” it all builds on each other… In most cases the results will be fairly straight forward and observable, however, just change on the thing observe and then make a second change (this is tedious) but important. I use fpsVR for measurement. This guide is aimed at Intel, Nvidia, SteamVR WMR users, others you will be able to get some ideas. Methodology For 2.7 I wanted as clean a start as possible and so I renamed my old saved games folder, uninstalled all my mods, and the did a slow repair of DCS deleting any additional files. For the purpose of testing Steam VR started at 100% or (3168 x 3196). All framerate stabilisations are turned off, this because when you are in motion smoothing, it hides a number of things as it forces the frame rate to 45, smoothing out the frame rates to give you a good experience, but it wont help you understand what's going on, so the stay off for testing and on (enabled/forced) for game play. I then flew a single low level flight in the Caucuses from the F-18 instant action mission, with my normal programs running (TARGET, VR Neck Safer etc...), the aim here is to keep the variables low, and whilst its not "combat relevant". The point here is to provide as much headroom as you can for combat and to understand the impact on the CPU and GPU and so the deltas are very useful to that, albeit that some effects are greatly multiplied in combat., etc... it's a good guide to understanding whats going on. In combat there are much more intense hits on the GPU and CPU as the result of AI, mission events, additional units being rendered etc... Track replay is used for subsequent re-runs of the flight to establish a baseline the purpose of which was to see the delta, the change, that each thing I did inside DCS did or elsewhere on the frame times of the CPU and GPU that will drive the VR Response. The headset is stabilised throughout the testing on a stand, and if I use it, for something else like having fun, I re-baseline from the last measured known settings to make sure nothing significant has changed. I record the frametime with FPSVR with a hotkey starting and stopping at a similar point in the track (there is some variability here, but not enough to cause me concern) and then I take an average of the data produced for each column and call that "the number" . I'm generally quite suspicious of activity that produces less than 0.05 variance in ms as that could come from a number of random factors on the PC, where I get these I typically test them several times in a row and take the average. My headset operates at 90hz, 90fps that means that the frame time (the time that the computer spends processing each frame) needs to be under 11ms for both GPU and CPU for it not to be in some form of reprojection, a GPU Frame time of up to 22ms is acceptable as that will give me 45hz equivalent. My goal therefore is to reduce the frame times to as low a level as I can to provide as much headroom as possible to deal with edge cases and mission intensity. The Track used to test performance is here: https://1drv.ms/u/s!Ar2cEt5yMycgm6skZyUPKfQMjm4mKw?e=so7zI 45 or 90 I have a high end PC at least today(specs in my signature block), its not the absolutely top of the hill, but it runs really well and in the context of VR you have to make a choice, do you want MSAA or not. If you can live without MSAA you will get 90 more often than not in free flight, and 45 in some edge conditions (NOE inverted looking at the trees), the super carrier being an exception where even I still drop out of 45 when looking at an island on a crowded deck. If you can't live without MSAA you will need to accept 45 FPS, to maximise that Force On Motion Smoothing, in steam VR and turn on MSAA in game, there will be more edge conditions where you drop out of 45, but it is by and large a good experience. Certain maps (The Channel) may also provide a suboptimal experience with MSAA turned on. Currently I have MSAA set at x2, and I force Motion Smoothing on in Steam VR settings as this provides me the best overall experiene. 2-D Performance Comparison The question of 2D performance came up as potentially useful comparison; for the purposes of testing this was done on 2560 x 1440 monitor (at 144hhz, at full screen) in level flight (Instant Action -> F-18 -> Caucuses Free Flight , and was a straight and level flight over some 20-30 seconds, all other settings were unchanged from my defaults, which resulted in about 160-190 FPS in 2.7 which is a small but noticeable increase, of about 10% Current Base Line As this post is hellishly long I have included a summary of the current baseline data that I use against the current track that i use for testing: Frametime in ms Delta From Baseline Ver Test Baseline GPU CPU GPU CPU Changes 1 VR Preset 10.94 7.13 2 VR Preset Rebar 11.22 7.24 -0.29 -0.11 REBAR 3 Medium Preset 11.07 7.05 4 High Preset 20.41 9.25 22 Test 20 12.35 7.85 -0.51 0.30 Clear Water 25 Test 21 10.70 7.39 0.18 -0.04 Shadows Reduced Frame Rate Impact MOD 38 Test 25 10.72 7.44 -0.03 0.21 5690 baseline 80% CRM 54 Test 25 11.06 7.33 -0.36 0.06 baseline (clear sky) 65 Test 54 11.14 7.13 -0.07 0.20 New base line using 2.7.3, and Terrain Shadows Off/ Medium Cockpit shadows 68 Test 68 12.83 7.23 Baseline test no Shaders 75 Test 25 11.36 8.27 -0.66 -0.88 Baseline (as per Test 25) 82 Test 75 9.52 8.55 Average for Baseline 2.7.6, FSR1.1, Windows 11, Hotfix Shaders 97 Test 82 10.06 8.08 -0.54 0.47 2.7.7, FSR 1.2 Clear Water Shaders, Medium Water, No terrain shadows New baseline 100 Test 97 10.61 8.81 -0.55 -0.73 Shader Cache to 10Gb 104 Test 100 10.72 6.25 -0.11 2.56 Alderlake Hygiene Operating System I use the latest version of Windows 11 latest and drivers from WU, I know there is perceived wisdom out there that earlier drivers may be better, there is a reason that they are out there, if the only game you are using is DCS by all means roll back to something else, otherwise use the latest version. For AV I’m using Defender because frankly it’s more than sufficient. Game Mode is currently enabled. You need to make sure that you have your PC in a fit state to actually play DCS because frankly its very “picky” about whats going on, remove or minimise programs and services that take away CPU cycles my idle times on CPU are typically between 1% and 3% I found particularly things like the Lighting Service had a significant impact on CPU cycles there are a number of guides out there for this, and it is not my intent to rehearse them again here. Rather I suggest that you look at active processes and see if you need them or can safely disable them, YMMV, Caveat Emptor etc… but I also can’t state how important this is to success. Things I have done to improve CPU performance: Turn off HPET, this is a basic Hygiene function and can be applied safely to pretty much any Intel processor (though I personally found a number stability issues when using the other recommended perf improvement on thread separation, linked off that advice) Turn off Dynamic Ticks. I still run the Game Bar but I have turned off anything that smacks of instant replay (CPU overhead) here is a reg file to turn off Game DVR I do not have any hyperthreading enabled (well my processor doesn’t have them so that was easy to do) and I would strongly suggest disabling it for game play especially on older processors. I always make sure the game is running in Full Screen Mode with ALT-ENTER, and I have disabled the full screen optimisation for DCS.exe. I have also disabled hot plug support , a cause of stuttering, note there is now UI in game to support this I have my page file set to a 32968 to 65536 this is on my operating system disk (NVME) I have a separate SSD for DCS, this changed from fixed page file as DCS when using HIGH for textures, needs an absolute ton of RAM to decompress the textures When you are running the game, turn “stuff” off, your browser will have an impact as will other software you don’t’ need… I have found that RGB related code really slows stuff down, I have uninstalled iCue and disabled lighting service and Corsair services as examples, what you will need to do may be different. Disable Virtual Monitor Pre-Allocation, as per this guide, it doesn't seem to give me any performance benefit per-say, but it doesn't cause any harm, maybe an extra half second if I fire up a 2d monitor in the VR house (thanks to @shaun57for the reminder) other people have reported a frame time improvement, so it might be a function of the cards video memory allocation. Now Replaced with UI option in Windows 11. Turn off Virtualisation Based Security: Settings -> Security -> Device Security -> Core Isolation -> Select Off, which seems to be an issue causing a number of performance losses with Windows 11, normally I dont recommend turning off security features ... but in this case I do, it will cost you about 10% of your perf otherwise ( A great hardware unboxed video on this) mine was turned off, likely because I upgraded in place. CPU My specs are in my signature, but I would strongly suggest you look at overclocking clocking your CPU to the highest stable clock speed, and make sure your memory is using its XMP profile. I haven’t played much with AMD CPU’s but my experience of Intel tells me this is as much a function of the motherboard as it is the CPU, but if you have a K style CPU and sufficient cooling you should overclock it, you are quite literally leaving money on the table if you don’t and more importantly frame times. There are a number of guides out there for this, but you will need to do this in order to maximise your performance, it sounds scarier than it is, give it a go. Resizable BAR I wanted to redo some of the Rebar testing and I have installed the Release version of my BIOS, previous testing was done with a beta BIOS: Frametime in ms Delta From Baseline Test Baseline GPU CPU GPU CPU Changes 82 Test 75 9.52 8.55 Average for Baseline 2.7.6, FSR1.1, Windows 11, Hotfix Shaders 87 Test 82 9.67 8.54 -0.15 0.01 Rebar Off Test 1 88 Test 82 9.48 8.43 0.04 0.13 Rebar Off Test 2 89 Test 82 9.62 8.60 -0.10 -0.05 Rebar Off Test 3 90 Test 82 9.59 8.52 -0.07 0.03 Rebar OFF Average 91 Test 82 9.60 8.27 -0.09 0.28 Rebar On Test 1 92 Test 82 9.59 8.30 -0.07 0.25 Rebar On Test 2 93 Test 82 9.50 8.35 0.01 0.20 Rebar On Test 3 94 Test 82 9.56 8.30 -0.05 0.25 Rebar ON Average As you can see on the z370 chip set it enabling Rebar has a small performance improvement on , so I now leave it turned On, but either way its pretty close to margin of error. GPU I do run a slight OC on my 3090, its XC3 so it’s not built to OC with a power limit of 104 and a temp limit of 91 (it doesn’t go above 79 in game and is typically running at 2010 or 2025Mhz with a custom Voltage/Frequency Curve: Which both over clocks and under volts my GPU, to help manage power and temp, again there are more detailed guides out there for this. Windows Settings Process Priority To ensure your DCS.exe, vrserver.exe and vrcompositor.exe are working most efficiently with your CPU set their priority to High, you can do this manually, or via a script I do it via the registry, add the following keys to the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DCS.exe\PerfOptions "CpuPriorityClass"=dword:00000003 adding for the other two processes replacing dcs.exe with vrserver.exe and vrcompositor.exe respectively. Mostly this has an impact on stuttering rather than on sheer perf. HAGS Hardware Accelerated GPU Scheduling, my experience of turning this on is very “mixed”, it seems to disable automatic Motion Reprojection forcing you to have it on all the time, so I leave HAGS disabled for now. NVidia Control Panel Settings After re-reading and doing a lot of testing in a semi unstructured way, i went back to "basics" ish for my Nvidia control panel settings: these are the only changes I have away from the defaults and to be honest, I'm really not sure about some of these. And I may revisit the when I get the time. Suffice it to say set everything to default. Low Latency Mode ON Frametime in ms Delta From Baseline Test Baseline GPU CPU GPU CPU Changes 25 Test 21 10.70 7.39 0.18 -0.04 Shadows Reduced Frame Rate Impact MOD 75 Test 25 11.36 8.27 -0.66 -0.88 Baseline (as per Test 25) 82 Test 75 9.52 8.55 1.85 -0.28 Average for Baseline 2.7.6, FSR1.1, Windows 11, Hotfix Shaders 83 Test 82 9.61 8.65 -0.09 -0.09 NVCP Low Latency Mode ON Test 1 84 Test 82 9.69 8.70 -0.18 -0.15 NVCP Low Latency Mode ON Test 2 85 Test 82 9.60 8.30 0.01 0.34 NVCP Low Latency Mode ON Test 3 86 Test 82 9.63 8.55 -0.12 0.00 Average for NVCP Low Latency Mode On Also note whilst I have moved to Windows 11, all we are really interested in is the delta from the baseline. In this case functionally nothing, I'm not particularly GPU bound, it might make things very fractionally worse on my GPU, but TBH you aren't going to notice the impact on my hardware. VR Settings Windows Mixed Reality Portal Settings Disable Virtual Monitor Pre Allocation Windows -> Settings-> Mixed Relality -> Startup and Desktop -> Virtual displays for apps-> uncheck the box to create virtual displays. I leave the rest of the settings at their defaults. Open XR Developer Tools These at the time of writing have no effect on DCS, any effect you think you are seeing in DCS is pure placebo. WMR for Steam VR Settings I use the beta version of Steam VR and Windows Mixed Reality Portal for VR The changes I make for WMR for Steam VR Settings, I let SteamVR manage its Motion Reprojection for DCS and other VR games: x:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\bin\win64\OpenVRSettingsUX.exe Steam VR CRM vs PD Lets address a subject of confusion first In game PD vs Custom Resolution Modifier... the thing that has the most change on performance in VR is the total number of pixels processed by the CPU and GPU for any given mission. PD and CRM both adjust the total number of pixels differently Performance is directly proportional to the total number of pixels being processed by the CPU and GPU, increase the total number of pixels and clarity will increase and performance will decrease, however PD and CRM are not equal in the way the impact the total number of pixels generated. PD essentially multiplies each axis by the value in PD... Steam CRM actually increases the total number of pixels generated by the percentage value... this is an non equal relationship A PD of 1.0 and CRM 50% is the same as a PD 0.5 and SS 200% (1*1*0.5 and 0.5*0.5*2)... (thanks @imacken) I wrote this spreadsheet to help people understand... PDSSCalc.zip in summary it does not matter if you use PD or CRM, my suggestion is use 1 of them, because it is so easy to get confused and just misunderstand what is going on... I leave PD at 1.0 because I can get exactly the same effect by varying the SS rating in steam with much greater granularity of control. Jabbers has an excellent YouTube video on this. I have done many tests on CRM previously, but, this time I wanted to document just one: Frametime in ms Delta From Previous Test Baseline GPU CPU GPU CPU Changes 20 Test 20 12.35 7.85 Clear Water 24 Test 20 11.12 7.81 1.23 0.04 Custom Resolution Modifier for DCS to 80% 2836x2768 As you can see with these changes alone we are very nearly back to the performance of the VR Preset. My Steam VR Settings for DCS for game play are: with motion smoothing FORCED for some maps, and DISABLED for testing. I set the default headset resolution to 3168 x 3096 (which is 100% on my G2). Adding Standalone DCS into Steam VR If you are using the standalone version of DCS, you will want to add DCS to Steam, and let it know its VR capable (this shouldn't impact your ability to run DCS in Steam VR, but it might make things easier. - Start steam, in left bottom click on: in the bottom left of your screen. and Click on Add a non-Steam Game. - Then select browse , and browse to DCS.exe on your system: (if you use open beta and stable you will need to add both separately). Click Add Selected Program - You will see DCS in the library list. - Right click on dcs.exe in the library list (Make Sure you have Games selected), select properties, in new screen make sure to select 'include in VR library' in bottom of screen. You can now start SteamVR without dcs running and change the resolution for dcs in the 'per application video setting'. Steam VR 1.17.8 New Settings Steam introduced two new settings in version 1.17.8 these are FOV and Worldview; I am testing these against my test 26 baseline, for clarity I do not recommend using a change to FOV, the numbers below are just to understand the performance implications: FOV Does exactly what it says on the tin, reduces the field of view providing additional clarity in terms of performance Frametime in ms Delta From Previous Ver Test Baseline GPU CPU GPU CPU Changes 26 Test 21 10.70 7.39 Shadows Reduced Frame Rate Impact MOD 39 Test 26 10.72 7.44 -0.03 0.21 5690 baseline 80% CRM 40 Test 26 10.73 7.24 -0.02 -0.05 Steam Version 1.17.8 41 Test 26 12.11 7.34 -1.41 0.05 Steam Version 1.17.8 100%CRM 42 Test 26 11.92 7.28 -1.22 0.11 Steam Version 1.17.8 100%CRM 90% FOV 43 Test 26 11.78 7.21 -1.08 0.18 Steam Version 1.17.8 100%CRM 80% FOV 44 Test 26 11.19 7.33 -0.49 0.06 Steam Version 1.17.8 90%CRM 90% FOV 45 Test 26 10.61 7.37 0.09 0.02 Steam Version 1.17.8 80%CRM 95% FOV 46 Test 26 10.63 7.33 0.07 0.06 Steam Version 1.17.8 80%CRM 90% FOV So test 39 was really to baseline 5.690 against 5118, there were no significant changes so I continued to use 26 as a baseline, similarly with steam version 1.17.8 itself in test 40. In test 41 I wanted to bring it back to 100% to see how it performed and give me a sense of the visual acuity improvements. Broadly the FOV does what it say gives you improved clarity at the cost of decreased FOV, 95% is liveable with and produces some small performance differences... my view on this is you are basically "robbing peter to pay paul", and while there are some marginal performance benefits it doesn't outweigh the "cost" in FOV loss. If you are on lower spec hardware then this is something you should consider carefully though as a 1ms here and there can make a difference. World Scale The world view slider is not enabled by default, you have to scroll down to the bottom of the Manage Custom Video settings for DCS, and click on the Override world scale button to ON. I only ran two tests here I might do more, but probably not, in summary this kind of does what the IPD does in DCS VR settings, at 200% you look like a GIANT and at 50% you look tiny. The surprising thing for me was they BOTH have a very similar detrimental FT impact on the GPU, its not huge and I haven't really tested IPD in game to see which is going to be the better fit: Frametime in ms Delta From Previous Ver Test Baseline GPU CPU GPU CPU Changes 26 Test 21 10.70 7.39 Shadows Reduced Frame Rate Impact MOD 39 Test 26 10.72 7.44 -0.03 0.21 5690 baseline 80% CRM 47 Test 26 11.09 7.30 -0.39 0.09 Steam Version 1.17.8 80%CRM 200% World View 48 Test 26 11.12 7.22 -0.43 0.17 Steam Version 1.17.8 80%CRM 50% World View My summary on this is if you feel you are two big or too small play with it and see what works for you there is a small, likely proportional, impact on perf which ever way you flex the slider. But ultimately knock yourself out ... I will be leaving both these settings at default. Baselines I had a number of operating baselines throughout the 2.7 testing I have undertaken, and I want to put them out there to help people establish where my bar is, but I started with the presets in game, Medium, High and VR: Baseline GPU frametime CPU frametime GPU Usage CPU Usage 1 VR Preset 10.93687291 7.131605351 93.963211 29.032441 2 VR Preset + Rebar 11.22403073 7.23986064 93.077006 32.718599 3 Medium Preset 11.06820362 7.054850746 63.265991 21.526919 4 High Preset 20.41371732 9.249450549 77.694202 24.461538 Tests Tests and More Tests Using my initial Test 4 to establish a baseline I started adjusting in game settings, recording the average frame times using fpsVR one at a time: Frametime in ms Delta From Previous Test Baseline GPU CPU GPU CPU Changes 4 High Preset 20.41 9.25 5 Test 4 20.31 9.21 0.11 0.04 Civilian Traffic to Low 6 Test 4 19.58 9.25 0.72 -0.04 Shadows to Low 7 Test 4 18.94 9.15 0.65 0.10 SSLR Off 8 Test 4 15.64 8.76 3.30 0.39 SSAO Off 9 Test 4 15.66 8.58 -0.03 0.18 Clutter to 1500 10 Test 4 15.70 8.57 -0.03 0.01 Preload Radius to 150000 11 Test 4 15.68 8.60 0.02 -0.04 Chimney Smoke to 1 12 Test 4 15.77 8.59 -0.09 0.01 Ansio to x16 13 Test 4 15.14 8.13 0.63 0.46 Terrain Object Shadows to Flat 14 Test 4 14.90 8.10 0.25 0.03 Global Cockpit Illumination Off 15 Test 4 14.89 8.02 0.01 0.08 Use System Resolution 16 Test 4 15.02 7.94 -0.13 0.07 Fullscreen 17 Test 4 14.98 8.10 0.04 -0.16 Crop to Rectangle 18 Test 4 15.04 8.20 -0.06 -0.10 Ultra Clouds 19 Test 4 14.67 7.96 0.37 0.25 Ultra Clouds no 15,16,17 But use Alt-Enter N.B. Negative WORSE, Positive better You can see that my final position on adjusting settings in game has provided a considerable improvement in performance, the big surprises for me were: the difference in performance between ALT-ENTER and Use System Resolution + Full screen with Crop to Rectangle, which should be logically the same thing SSAO - OMG! turn it off in VR! I was going to use test 19 as my new baseline and then came out, so I re-ran the last test again and: Frametime in ms Delta From Previous Test Baseline GPU CPU GPU CPU Changes 20 Test 4 14.79 8.14 -0.11 -0.19 Ultra Clouds no 15,16,17 But use Alt-Enter as you can see there is a tiny degradation in performance, but, this could be from run time variance. In Game Settings The in game settings after Test 20 look like this, and yes Wake Turbulence is off! Forest and Scenery Details Factor sliders These do have an impact in terms of performance, but, it is very context dependent, they are dynamic, in the sense they can be applied in mission from the options menus. In some scenarios you benefit by reducing the forest detail...in some the scenery. The sweet spot I tested was forest 0.6 and scenery 0.9, which in my test produced a combined GPUframe time reduction of about 0.29ms. These sliders work as far as I can tell as a variable for the LOD for the scenery objects and trees. So the image looks slightly “worse/different” in practice this is because you are using the model that would be used for viewing the object at a further distance. Your own tolerance for this is likely to be as variable as the technical variable for when it really brings some benefit. So whilst I have noted them, I have not included them, they provide an “edge case” set of benefits, but not something that I could generically say is good. And in some scenarios just a degradation in quality for little or no benefit. Net net, I leave them at 1.0 and play with them if I get poorer performance than I like. MSAA x 2 vs x 4 MSAA x 4 has a GPU impact of just under 2.5ms in my standard test (so its definitely "worse") with a small amount of impact on the CPU 0.2ms . Shader Mods for Performance Improvement The next stage of the testing for was to understand what mods would have what level of impact on the performance of the game: Frametime in ms Delta From Previous Test Baseline GPU CPU GPU CPU Changes 20 Test 4 14.79 8.14 Ultra Clouds no 15,16,17 But use Alt-Enter 21 Test 20 11.84 8.15 2.95 -0.01 Kegetys Shaders 22 Test 20 12.35 7.85 -0.51 0.30 Clear Water 23 Test 20 12.81 7.93 -0.46 -0.08 IC Pass As you can see Kegetys shaders offer considerable performance improvement over the baseline, whatever version you are flying with, i don't fly much multiplayer, and I do like pretty water so I have chosen my Clear Water version of Kegetys shaders, there is a tiny measurable offset in performance, but like is say PRETTY! Shadows for Immersion and Performance Everyone loves shadows, but as we saw in test 6 they can have a pretty meaty performance impact between Low and High, but Low doesnt look very nice... I have focused on removing the majority of shadows except those in the cockpit and the shadow of your aircraft in flight that requires two separate MODS: Frametime in ms Delta From Previous Test Baseline GPU CPU GPU CPU Changes 22 Test 20 12.35 7.85 Clear Water 24 Test 22 11.12 7.81 1.23 0.04 80% SSS 25 Test 22 10.88 7.35 0.24 0.46 Shadows Reduced Frame Rate Impact.zip 26 Test 22 10.70 7.39 0.18 -0.04 Flat Shadow Removal MOD Shadows for Reduced Frame Rate Impact, is a another MOD from Kegteys, that I have fiddled with to give me medium shadows inside the cockpit, which gives a nice effect and The Flat Shadow Removal MOD (does exactly what it says on the tin) turns shadows off for virtually everything else, from @Mustang (setting terrain shadows to off and Cockpit shadows to medium has a similar effect) combined they save about 0.4ms on CPU and GPU time. At this point we have exceeded the performance of the VR Preset, with better visual acuity and visual immersion. Sharper Eye and performance impact The Universal Reshade Mod really improves the look of the game, it is a huge benefit to visual acuity is immense, however, I am seeing some significant performance impacts, I have the data but I can't claim to understand it why the performance impact is so large. I am seeing between 0.7 and 1.5ms GPU impact and around 0.2ms impact to CPU, which seems to have a disproportionate impact on performance up to 6FPS which is ... considerably more impact than I can explain from the data. There is little or no difference between Performance Mode and the standard mode of operation. Thanks to @Sr. and @zildac for their finding and advice on the thread for this. I have played with a number of settings but for me I keep the defaults and adjust the Sharpening Intensity to 1.2, I am playing with this but this seems to work for me. and the sharpening radius to 0.8. Since this was published an improved version is available for skyrim and some other games, however to get it to work for DCS you need to merge the two, there are some performance improvements. I have created a consolidation of the Sharper Eye changes Github version Sharper Eye Reshade.zip, YMMV, for convenience, I strongly suggest you do the work yourself to help you understand it, I am not the author etc... If you are using a MOD Manager to install this MOD (And I strongly recommend you use one, for any and all mods) you will need to make the changes directly to the ReshadePreset.ini file before you install the MOD, or you will need to keep reapplying these changes if you uninstall and reapply the MOD. At the moment I'm on the fence on this, on one hand PRETTY and on the other hand IMPACT, you need to play with this and make a determination for yourself if your machine can cope with the loading it causes. Update - Shimmering. This mod produces additional shimmering, I hadn’t really appreciated how much, until I turned it off after my latest band of testing. So it is clearer but the very sharpening nature of this produces a heat haze effect over a lot of the objects. As a result it’s OFF for the moment, I haven’t tried upping the MSAA to counter it but x4 in VR feels ... foolhardy... DCS MODS This section is unchanged from 2.5.6. If you are going to get DCS to run at its best, you will likely need to run some mods, I strongly recommend running a Mod Manager to apply them, I even use a MOD Manager to apply changes to saved games folders just so I can recreate them if it all goes horribly wrong. I use ModManFX by @Skypat, there is a version hosted in the DCS downloads as well, but, its not maintained. I still run Kegetys excellent VR Shaders MOD it improves performance just enough to get me in 90FPS more than less, or one of my variations of it to improve performance. I use low shadows as modified by this MOD, which was from @Kegetyswhich essentially turns off on non-terrain objects shadows and this mod from @Mustang which turns of the objects for trees , and pretty much everything else, the cockpit shadows set medium, and terrain shadows set to off, net effect is that you have your shadows in your cockpit, and your aircraft shadow And finally the VR experience MOD for the F-14 as it improves the look of the 14 and also the hanger I also modify my options.lua file to reduce the size of the Radio message text; I set it to 0.75 for the G2 The VR Scratchpad is really useful for making notes in game I use a Toggleable Zoom which is tremendously helpful for Visual IDing pf targets. This mod no longer works quite how it should with 2.7, and you need to delete the keyboard directory from the MODConfig - Keys - Instant Zoom keybind.zip I have included a copy of the modified mod here, YMMV etc... SkateZilla's DCS Updater app, so useful for managing updates and repairs to DCS and for me running scripts prior to DCS launching these except as noted have little or no impact on performance. Utilities & VR Apps I run the VRNecksafer app which is invaluable, in equalising the difference between the FOV that you can get in the real world and your ability to turn your head. Cannot recommend it enough. Viacom for Voice Attack, again I can't recommend this highly enough as a way to add immersion in game. Joystick Profiler is an application to help you manage joystick bindings in DCS, it enables you to easily get consistent behaviour for buttons across multiple aircraft and minimises the impact of changes to devices, the author is also working on support for other sims as well , this has no impact on performance what so ever... but it does enable me to dip into modules far more easily! Clouds So the Jitter is fixed in clouds which is fantastic news, however, unless they are set to ultra there is quite a bit of aliasing and stair stepping, especially when close to the horizon, or edge of a mountain side etc... however their is a significant performance hit associated with clouds, I have only tested light scattered clouds at the moment I will do a fuller test against other cloud types if I get a chance: Frametime in ms Delta From Baseline Ver Test Baseline GPU CPU GPU CPU Changes 55 Test 26 11.06 7.33 baseline (clear sky) 56 Test 55 12.76 7.53 -1.70 -0.20 light scattered clouds (low) 57 Test 55 12.92 7.72 -1.86 -0.39 light scattered clouds (standard) 58 Test 55 13.13 7.53 -2.06 -0.20 light scattered clouds (high) 59 Test 55 14.88 7.64 -3.82 -0.31 light scattered clouds (ultra) 60 Test 55 14.95 7.64 -3.88 -0.31 light scattered clouds (ultra)test 2 so whilst they are very pretty, they do come with a huge frametime cost. I would seriously recommend either turning off MSAA, or dropping to 50% resolution in order to compensate for the effect of clouds , if you cant deal with the horizon shimmer and have to run at ultra. If you can deal with the shimmer, then I would choose "standard" clouds as the current compromise... and the fix is almost as bad as the original problem. Clouds 2.7.3 Update I have changes a couple of settings, I am no longer using the flat shadows mod from @Mustangas this feature is functionally in the game fro a while now, whoops, set terrain shadows to off and cockpit shadows as desired. I also had to produce a new test track Frametime in ms Delta From Baseline Ver Test Baseline GPU CPU GPU CPU Changes 55 Test 26 11.06 7.33 -0.36 0.06 baseline (clear sky) 66 Test 55 11.14 7.13 -0.07 0.20 New base line using 2.7.3, and Terrain Shadows Off/ Medium Cockpit shadows the variance is so small that it is close enough to run time variance as far as I am concerned. Open FSR for Steam VR games Release Version 1.2 This mod can be found here Release FidelityFX SuperResolution for SteamVR games v1.2· fholger/openvr_fsr (github.com) it provides a modified binary which installed in the /bin folder of the DCS core game and the details can be found here: I did make a change to the config file, because i found the shimmer to great, to set the sharpness to 0.0 (e.g. game native) and the render scale to 0.80, I set the radius to 0.75 to get rid of the annoying circle, but you might want to fiddle with it . { "fsr": { // enable AMD FidelityFX Super Resolution "enabled": true, // Per-dimension render scale. If <1, will lower the game's render resolution // accordingly and afterwards upscale to the "native" resolution set in SteamVR. // If >1, the game will render at its "native" resolution, and afterwards the // image is upscaled to a higher resolution as per the given value. // If =1, effectively disables upsampling, but you'll still get the sharpening stage. // AMD presets: // Ultra Quality => 0.77 // Quality => 0.67 // Balanced => 0.59 // Performance => 0.50 "renderScale": 0.8, // tune sharpness, values range from 0 to 1 //"sharpness": 1.0, "sharpness": 0, // Only apply FSR to the given radius around the center of the image. // Anything outside this radius is upscaled by simple bilinear filtering, // which is cheaper and thus saves a bit of performance. Due to the design // of current HMD lenses, you can experiment with fairly small radii and may // still not see a noticeable difference. // Sensible values probably lie somewhere between [0.2, 1.0]. However, note // that, since the image is not spheric, even a value of 1.0 technically still // skips some pixels in the corner of the image, so if you want to completely // disable this optimization, you can choose a value of 2. // IMPORTANT: if you face issues like the view appearing offset or mismatched // between the eyes, turn this optimization off by setting the value to 2.0 "radius": 0.75, // if enabled, applies a negative LOD bias to texture MIP levels // should theoretically improve texture detail in the upscaled image // IMPORTANT: if you experience issues with rendering like disappearing // textures or strange patterns in the rendering, try turning this off // by setting the value to false. "applyMIPBias": true, // If enabled, will visualize the radius to which FSR is applied. // Will also periodically log the GPU cost for applying FSR in the // current configuration. "debugMode": false } } but the real question I suppose is what is the effect ... the answer considerable, there is a small amount of shimmer added at these setting but it is very manageable, and I cant see any personal loss of acuity... or again if its there its manageable Frametime in ms Delta From Baseline Ver Test Baseline GPU CPU GPU CPU Changes 55 Test 26 11.06 7.33 -0.36 0.06 baseline (clear sky) 66 Test 55 11.14 7.13 -0.07 0.20 New base line using 2.7.3, and Terrain Shadows Off/ Medium Cockpit shadows 67 Test 66 9.15 6.83 1.99 0.31 FSR for Steam VR games Alpha 1.2 That's a 2.00 ms GPU frame time improvement, thats significant. And it is staying on at present. Simplex Shaders V 2.1 A new variant of Shaders has been released, it is similar (slightly faster) to my IC pass variant it can be gotten from the link below: Frametime in ms Delta From Baseline Ver Test Baseline FPS GPU CPU GPU Usage GPU CPU Changes 69 Test 69 68.74 12.83 7.23 90.23 Baseline test no Shaders 70 Test 69 79.36 11.26 6.97 92.46 1.57 0.27 Simplex Shaders v2 71 Test 69 82.43 10.72 7.23 92.06 2.11 0.00 Kegetys Shaders 72 Test 69 82.22 10.84 6.98 92.69 1.99 0.26 Clear Water Shaders 73 Test 69 76.83 11.52 7.31 91.39 1.31 -0.07 IC Pass Shaders 74 Test 69 77.86 11.41 7.05 91.81 1.42 0.18 Simplex Shaders v2.1 This mod is IC Pass compliant with 2.1 and it claims less graphical artefacts, I honestly can't tell the difference between them, however 2.1 has significantly less performance than 2.0. The big advantage of these is that they dont require a lengthy shader rebuild, the first time you use a mission/map/model... that said the numbers speak for themselves. Hardware Upgrade I upgraded my motherboard and processor, I went to a ROG STRIX Z690-A Gaming Wifi D4, and an i-12700kf, everything else is unchanged. I went with the A because it maintain DDR4 RAM and while there are scenarios where DDR5 has a significant impact, almost none of them are in games. I used the AI Overclock onboard with the Z690-A and forced memory to its XMP profile Frametime in ms Delta From Baseline Ver Test Baseline GPU CPU GPU CPU Changes 100 Test 97 10.61 8.81 Shader Cache to 10Gb 101 Test 100 10.66 6.92 -0.05 1.89 Alderlake 102 Test 100 10.61 6.78 0.00 2.03 HAGS 103 Test 100 10.68 7.01 -0.07 1.81 HAGS 104 Test 100 10.72 6.25 -0.11 2.56 minus 3dmigimoto, new baseline so I screwed up when I was doing my initial testing, and was running with another mod which I was testing, and then retested .. so overall the Alderlake upgrade gave me 2.5ms of CPU frametime, so nearly a 1/3rd yikes... Conclusion After 2.7, initially my performance was all over the place, I had so many changes, I had to go back to zero (nearly), to see what had the most impact in the new world. If I'm not running AA I can hit 90FPS more often than not in my test, everywhere except the channel or over dense population areas in Syria where it drops to 45. I can usually maintain 45FPS with MSAA X2 everywhere except The Channel over built up areas and the flight deck of the super carrier cold start as examples. For clarity, I am currently forcing Motion Smoothing, MSAA is at x2, I am using FSR, I am still using Clear Water, I am not using Simplex or Sharper Eye. Overall, I would say that there is a net performance improvement with 2.7, largely masked, by people running motion smoothing. I know people are experiencing performance hits, and hopefully this guide will help to find areas of improvement. I would strongly suggest some of the Hygiene steps, including bringing DCS back to base, which doesnt need a reinstall. At the moment I have a solid set of performance, and I'm going to play the game some now.
  2. Hallo in die Runde, ich bin neu in DCS und jetzt auch in VR. Einige Dinge funktionieren nicht so wie ich das erwartet habe und kann das auch nicht nachvollziehen warum um es zu beheben. Ich hoffe auf etwas Unterstützung. Damit alle wissen mit wem und Was sie es zu tun haben: Bin seit 2004 anhalten in der Flugsimulation, nutzte FSX, Prepar3D und jetzt MFS. Mein letztes PC Spiel ist über 10 Jahre alt, seitdem nur noch Flight Sims. Ich war 10 Jahre beruflich (bis 2016) im Bereich PC Hardware Vertrieb, Einkauf und Systembau tätig, seitdem verfolge ich den Hardwaremarkt meist nur anhand Online News. Ich wollte seit ich mal die Oculus Rift DK1 ausprobieren durfte unbedingt in VR einsteigen. Nun hatte ich DCS immer stiefmütterlich behandelt, nie für interessiert oder ernst genommen (großer Fehler!). Bis ich zufällig darauf gestoßen bin das DCS in VR ganz gut performt. Kaum hatte ich DCS installiert musste eine VR Brille her. Die HP reverb (g1) habe ich günstig bei Ebay erstanden. Auf meinem System sieht es zur Zeit wie folgt aus: BeQuiet DarkPower Pro P9 750Watt Intel Core i5 6600K@4,7Ghz 32GB HyperX 2133@2800 EVGA GTX1070 FTW 500GB Samsung 970EVO m2 NVMe PCI-E 3.0 (System und MFS/Prepar 3D) DCS (RC) nicht Steam Version auf einer WD Green HDD Saitek X55 Die HDD Installation erstmal, weil auf der SSD kein Platz ist und es zum testen gedacht war. In Planung ist ein komplett neues System, demnach auch mit ausreichend SSD Speicher für DCS (m2 PCI-E), ich hoffe ende Februar eine RTX3060 ergattern zu können. Natürlich ist das für VR nicht gerade die optimale Lösung, aber 600€ für eine 8GB 3070 bringt es auch nicht (Wenn denn mal verfügbar), also wird das eine Übergangslösung. Die Reverb läuft zur Zeit in 1700x1668 (60%) und Bewegungsglättung "immer an erzwingen" lt. FPSvr mit 45-50 FPS und 97% GPU Last bei 7,8/8GB VRAM. Das ist alles erstmal so das es läuft und noch nicht großartig ausgelotet. Vorab, ich habe das komplette deutsche Forum zu dem Thema durchsucht. den VR Thread habe ich bis 2019 rückwärts gelesen, da davor mit DCS 1.5 und den alten VR Brillen sowieso noch alles anders war, bzw. nicht mehr repräsentativ. Kommen wir zu den Fragen: - DSC ist nach wie vor nur über Steam VR in VR zu nutzen? Anders startete es nicht in VR wenn nur die WMR Software aktiv war - Das Headset habe ich im Modus "nur im sitzen und stehen verwenden" zentriert in dem ich es auf meiner Sitzposition korrekt auf hatte und dann den zentrieren Button gedrückt habe. - Jetzt habe ich aber das Problem das ich in DCS jedes mal eine andere Kameraperspektive habe. Zuerst habe ich das Headset vor mir auf den Schreibtisch gelegt bei der Einrichtung. Beim ersten Versuch saß ich soweit hinten das ich beim links gucken die Kopfstütze vom Sitz vor meinen Augen hatte. Beim 2. Start hat es dann auf Einmal gepasst. Jetzt habe ich das Headset in der WMR Software von HP aufgesetzt und dann zentriert. Resultat beim 3. Start saß ich ungefähr genau zwischen beiden Positionen, jedoch viel zu hoch, so das ich das HUD nicht mehr lesen konnte da ich darüber hinweg geguckt habe. Weiter hatte ich das Problem das ich zwar ganz normal hoch, runter, rechts und links gucken konnte, aber die Bewegung im Raum, also wenn ich näher an die Instrumenten Tafel wollte, oder zur Seite näher an die Kanzel wollte waren die Achsen genau umgekehrt. Habe ich mich nach vorne gelehnt, ging der Körper im Spiel nach hinten, habe ich mich rechts näher zur Kanzel hin bewegt, ging der Kopf weiter von der Kanzel weg. - Wie kann ich die Kamera Position generell einstellen das ich weiter vorne oder hinten sitze, bzw. größer oder kleiner bin? In DCS habe ich nur die Funktion die auf dem Headswitch beim HOTAS liegt gefunden, aber das ist ja im Prinzip meine Kopfbewegung die das VR Headset bzw. auch TrackIR macht. Im MFS oder P3D gab es da separat eine Funktion für. - Sollte FPSvr nicht eigentlich mit aktivierter Motion Funktion (Bildglättung) konstant 90FPS anzeigen wenn ich min. 45FPS erreiche? DCS meldet beim Start auf jedem Fall das das Spiel nur mit halber Bildwdh. wiedergegeben wird. In den nVidia Einstellungen steht die Monitor Wiederhlg. Rate auf "feste Wdhg. Rate" und VSync steht auf "Adaptive- halbe Bildwdhlg Rate". In DCS ist Vsync aus. - Welche Tipps gibt es noch um vll. mit der Auflösung höher zu gehen und trotzdem die FPS zu halten? Mit anfänglich hoher Auflösung lief es optisch zwar flüssig, aber durch die geringe Hz Zahl wurde mir schlecht.
  3. So this was driving me insane... one of my MFD 's would consistently disappear... but, I couldn't find the conditions under which it would disappear, I thought I had a cabling problem ... nope... I thought it was that the script I was using to create 128 buttons in TARGET... nope etc... A little about my controller set up: Thrustmaster Warthog HOTAS which I configure using TARGET, to get a full 128 buttons MFG Crosswinds v2 3 x Thrustmaster Cougar MFD 1 x Razer Tartus (configured as a joystick button box, because I prefer discrete DX button presses, as it creates less confusion keyboard collisions etc) 1 x Stream deck (configured as a joystick button box, using vjoy, because I prefer discrete DX button presses, as it creates less confusion keyboard collisions etc) I obviously turned of vjoy first and thought that fixed it but then in game, nope it would not work, re scanned device etc... nope still nothing ... I start looking into the Game Controller UI in desperation. Clue 1 I noticed that my MFD2 wouldn't configure correctly via the Game controller UI (even though it would still work in game) it would just show as a joystick, but, labelled as the Tartus so I pulled each of the controllers in turn, until i got it up as MFD... turned out it was the Tartus Resolution 1 I changed the MFD from MFD 2 to MFD 4 (luck more than logic) in the Game Controller UI, with the Tartus unplugged, each MFD number has a different VID in windows, so i guessed it was colliding. Each MFD now showed up correctly as an MFD the the Game controller UI. I ran Target and low there were still three MFD's hurrah ... or so i thought... I get into game and the MFD3 has gone AGAIN... some muttering (well swearing) what the hell is going on. Clue 2 why the hell do i have VIVE controller listed in DCS. 2nd order diagnostics (when does the MFD vanish) ... after many stages of testing it MFD3 only vanishes once Steam VR starts only when i have one or more hand controllers active (assumption what if to do the game controller mapping in SteamVR they are mapping the controllers to a VID that just happens to have collided with the MFD, as the newer device they would overwrite the existing device and the MFD vanishes, only if you run TARGET Resolution 2 Change MFD 3 to MFD 8 to see if that works it does hurrah Are we nearly there yet... no we bloody aren't Turn back on vjoy that works, turn back on the tartus and OFFS the configuration of the MFD4 via the Game Controller UI has c*cked up again... note the device works in game but FFS I won't less this beat me... Resolution 3 Turn the Tartus off Move the MFD to 7 because that is next to 8 that will be safe right ... wrong ... well 5 is next to 4 ... wrong ... 6 hurrah! Finally Left MFD1 is fine, my Right MFD is set to MFD6 in the UI, and the Center to MFD 8... conclusion getting multiple MFD's to work with multiple joystick devices is a complete pain in the bottom, and it would be really nice if the manufacturers would use a mechanism of ensuring their virtual joysticks dont collide with each other...
  4. I have been getting frequent blue screens upon starting a A10C II mission in the Reverb headset (pc is fine but DCS freezes) and can only be fixed with a restart. I have never had any issues with DCS or the Reverb until now. I had a 2070 super and now 3080 with the same issue existing on both. I have also done a fresh Win 10 install after the 3080 installation due to a separate issue. I have no trouble in the OG A10c, AV8b or f18. Searches have yielded nothing..if anyone can help, I would be very very grateful! Captain Biscuit
  • Create New...