Jump to content

fab.13

Members
  • Posts

    263
  • Joined

  • Last visited

2 Followers

Personal Information

  • Flight Simulators
    DCS for now, and tried all of them since Mission Delta on ORIC ATMOS ;-)
  • Location
    France - Marseille

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. True Very good exprience, no more ghost in multi-player Well Done Please try to keep like that, as possible, along upcomming patch...
  2. Hello, We tried a multiseat fly on Mirage F1 BE I joined a Mirage F1 BE in rear seat, the plane was already moving on taxi. The problem : Instruments in rear seat were all off and no engine sound ( same state has before starting engine.. ) Then when the pilot has take off, Engine sound just started and instruments become alive one by one while flying... strange ! When the pilot landed, the engine sound stopped and instruments too, as when i joined the rear seat Taxi in rear seat seem to have bug ? We didn't met such problem in previous version of DCS How to reproduce : - start a Mirage F1 BE as a pilot - then an instructor join the rear seat : no sound, no instrument and sound alert ... - take of : synchronization start
  3. Hello, True, I had to disable HT in the first release of MT in 2023 "give a try " was intended for player that met stutters at this time to test that option ( i was not alone ... ), not a recommandation. From few release after summer, i remade some test with a bench track and it was better with HT ON ( but with no shadow ) Now with the last release delivered in Feb 2024, DCS is very smooth and i could have increment resolution in VR in my quest 2 ( x1.3 ) : great !
  4. Hello interesting… You got a bench method of your DCS machine I’ll test that on my side
  5. Stutters could have a windows root cause Flappie has written in this forum all windows settings to allow best DCS VR experience about DCS, try ´vr settings’ tab or lowest settings ( texture resolution and AA technics to off , no shadow )
  6. On my side, i launch DCS from the shortcut on monitor screen (DCS mt version) and not from within the headset … check that you are using the DCS multithread version now you get an error, you shoukd provide the DCS log to DCS support, or post here too
  7. Maybe vram caching, so not managed by DCS itself Anyway, if your game experience is good and better with your tunning, don’t look too much at monitoring and play
  8. Did you try a another VR ( free) Game ( pc vr game with link ) ? Last time i got black screen in headset was due to agressive settings in link, so i suggest to reset all settings to default and run without external tool or Mod ( no ODT): stock stack And check that ´unknown source game’ is on in occulus home
  9. Hello check OpenXRruntime is enabled in occulus home reduce bitrate with ODT ( dynamic byte rate should be good as a first choice ) check Windows Swap file is enough ( virtual ram )
  10. Intel I5 10600k 6 cores 12 threads 5gz 1080ti Quest2 64 GB ram windows 10 I’ll try some quadview settings in a next test It is not a problem because 2.9 works very well for now ( 72 hz no stutters )
  11. So Quad View works on Intel I5 10600k 1080ti Quest2 FPS are not as good as without QuadView, maybe missing some CPU power on my rig...( default quad view setting, just turbo mode off ) So i removed it I prefer settings same as @Chapa ( no AA and Render Resolution Up , very smooth and clear ) @Granny you should be able to test QuadView The log file of quadview in '...\AppData\Local\Quad-Views-Foveated' indicate it's working 2024-01-26 20:35:53 +0100: Session is using quad views 2024-01-26 20:35:53 +0100: Edge smoothing: 0.20 2024-01-26 20:35:53 +0100: Sharpening: 0.70 2024-01-26 20:35:53 +0100: Turbo: Disabled
  12. Let’s check the change log of the wiki I found this chapter about foveated redering and supported graphic cards: https://mbucchia.github.io/OpenXR-Toolkit/ So i'm confusing Foveated Rendering in OpenXR Toolkit and QuadView Let's try quadview with my 1080ti !
  13. Hello QuadView need 2000 nvidia series minimum as indicated in docs when i tried ( tested a long time ago on my 1080ti ) let’s see if a commit has added support to 1000 series
  14. Hello @Granny Here my settings from various stack, i'll update it... BIOS settings: - XMP and DDR RAM with low latency - no virtualization - enable virtual threads ( 6 physical cores -> 12 threads ) - i don't remember everything Windows 10: - you need the more RAM & VRAM free and low CPU : - check with Windows Task Manager, CPU should be under 3 or 4 % ( 1%-2% on my rig ), so disable some services and auto started application you don't need - check free physical memory while playing DCS ( some mission or mutiplayer server ask nearly 28-30 go RAM ) - disable windows auto update ( it take CPU and Network ) - disable HAGS - disable XBOX GameBar - disable memory compression - disable some MS assistant - exclude DCS directory from antivirus ( and "saved games\DCS* " too ) - power managment to maximum performances - disable usb devices power saving - stop every tool about performance : it take CPU ! - you get a clean windows and nothing more and with CPU load in background and RAM free... Nvidia Control Panel: - Specific DCS settings with Power Maximum Performances, textures quality performance, ultra low latency, 1 pre-rendered frame, no msaa, no fxaa ( max perf ) - i don't remember my nvidia driver version Occulus Debug Tool: - Specific DCS settings with "low resolution mirror" to 800 * 600, PD to 1.0, fov 0.9 x 0.9 ( depend about your Quest 2 mask ) - Quest Link : Low curvature, enable Dynamic BitRate Occulus HOME: - quest setting resolution to 1.2 - check cable link speed ( i get 2.5 gb with a standard usb-c cable ) DCS: - DCS OpenBeta stock with no mods - start with "VR Settings" : every textures low, no effects, no msaa , no asitropic , no shadow etc... ( max perf ), PD to 1.0 - disable HotPlugIn 1) start ODT first and check setting 2) start occulus home 3) connect your quest 2 and check resolution settings and everything ok in the occulus world ( smooth ) 4) Start DCS MT version 5) check in a free flight in caucasus with no weather effect : on my rig a get a smooth experience 72 fps , no stutter and no blurry 6) check on aerobatic server : a get smooth experience 72 fps, sometime some stutter when a new arcraft appears ( depend about the livery ! ) 7) change settings one by one ( Occulus Resolution or DCS : AA settings , Shadow, and Textures Resolution need more resources than other ... ) In my experience, windows 10 or 11 tuning is the most important step, I cannot get a good experience without freeing ressources at maximum and permanently ( CPU & RAM background reduced as much as possible ) ( DCS would need a real-time OS or DOS ...: dedicated ressources ) When checking performances while playing DCS MT in VR : CPU is about 80% and GPU about 90% and VRAM Full ... Good Luck !
  15. Hello, i run DCS on a corei5 10600k ( 6 cores ) and a 1080ti and Quest2 i ´ll share to you in few hours my settings that i’m very happy with ( fps and quality balance ) and external tools ( ODT, NvCP, windows tunings )
×
×
  • Create New...