Jump to content

Doggo

Members
  • Posts

    18
  • Joined

  • Last visited

Posts posted by Doggo

  1. Hi everybody,

    For Pimax users I've seen openxr/steamvr/changes, etc so I thought I would post what is  working for me.

    Hardware: I9-9900k, 64gb RAM, RTX 3090, Pimax 8Kx at 75hz (could never get it to work 90hz)

    Pitool 1.0.1.280, Firmware 2.1.255.299
    Panel: Native, 75hz

    Game setting: FOV Large, RQ 1, FFV close, parallel off, smart smoothing off, compulsive smooth close, hidden area mask checked.

    SteamVR:

    Motion smoothing on, resolution custom @ 5060x3160. 

    Nvidia 3D settings:

    Image scaling: off

    Antostropic filtering, app controlled

    FXAA, Gamma: off

    Antialiasing: app controlled

    Max Frame rate: OFF --- this one seemed to solve any CPU bound frame issues.

     

    DCS:

    Everything is set to max/ultra (shadows are low), and my PD is 1.2.

    Very acceptable frame rates for me. 

     

     

  2. On 3/16/2021 at 6:02 AM, BIGNEWY said:

     

    No,

     

    we are saying we are looking into it. Fact is user or server connections with packet loss are creating the problem. We dont have any control over that, we can only tweak the network code to try and mitigate its effects, and that is what we will do. 

     

    thanks

    Is it pure loss, or jitter and reassembly?

    A hotfix for debug/stats to drop in server log files would be helpful for ALL of us.

  3. Hello all,

    I have searched for other TACAN reports, and I have seen TACAN/ICLS go bent on MP servers such as Hoggit/TTI.

     

    I fly with a group of folks (CSG-2), and we've seen this happen more often when multiple player units connect to CVN's TACAN.

     

    Scenario; F-14 and F/A-18 units (20+) return from mission within +/- 20 minutes. Heading to carrier all flight leads if not all AC tune TACAN to CVN.

    TACAN will go sour.

     

    We have tried various methods for resetting TACAN/ICLS on the carrier (trigger), and will be trying methods via the LUA interpreter directly this coming weekend. 

    Anybody have guidance, or is ED already looking at this?

    Thanks,

     

    Doggo.

  4. Hi there,

     

    Was away for a few days.

     

    Ran DCS Updater, saw I was getting integrity check errors on some IC servers.

     

    On further inspection, DCS_Updater is showing acccess violations.

     

    Looks like it's downloading to the new _downloads directory under "DCS World", but unable to move the files to their destination directory.

     

    Anybody seeing this issue?

     

     

    Snip of the log below.

     

     

     

    # -------------- 20200724-155608 --------------

    E:\DCS World\bin\DCS_updater.exe

    # C0000005 ACCESS_VIOLATION at 9C170170 00:00000000

    00000000 00000000 0000:00000000

    9C170170 CB8EB6D0 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9C15B873 CB8EB700 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9C15A624 CB8EB750 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9C15949D CB8EB780 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9C158255 CB8EBCB0 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9BBF02DD CB8EC580 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9BBEF507 CB8EC5B0 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9BC3C424 CB8EC5F0 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9C19C675 CB8EC640 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9C156700 CB8EC670 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9C14F66C CB8EC720 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    2A1CF476 CB8FED60 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlCaptureContext2()+4A6

    9BC3BACC CB8FF7F0 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9BC52005 CB8FF830 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    9C162E34 CB8FF860 0000:00000000 E:\DCS World\bin\DCS_updater.exe

    28C46FD4 CB8FF890 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14

    2A17CEC1 CB8FF910 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

    MiniDump written to E:\DCS World\autoupdate_crash-20200724-155608.dmp

  5. Hello,

     

    While VR performance has improved, night lighting issues seem to cause headache inducing problems.

     

    There are two issues:

     

    Issue number 1 -

    See attached "night test.miz", in Persian Gulf (or any map) Lighting shimmer will render in one eye, but not the other. This seems to increase if bank angles are obtuse and not perpendicular to ground. Zoom in will resolve the issue.

     

    https://drive.google.com/file/d/1E-uSYWCDqt6TGtAcjwbxcu7_cM7MMXsm/view

     

    The link above is a very good example of what this looks like.

     

    Issue number 2 -

     

    NVG overlay with wide FOV. Without 3DMigoto mode, the NVG overlay is >70 degrees outside of your FOV. 3Dmigoto is required to bring the NVG goggles back to viewable area.

     

    With previous release, 3DMigoto and settings below would remove the "shimmer", then last 2.5.6 OB, while VR performance was hateful, at least night worked ok.

     

     

    Level set of:

    Pimax 5K+ , PITool V1.0.1.258, firmware V2.1.255.255

     

    DCS World Pitool Settings:

    Large FOV

    Render Quality: 1.25

    GPU Catalyst: 0.00

    Fixed Foveated Rendering: Conservative

     

    Compatible with Parallel Projections: Off

    Turn on Smart Smoothing: On

    Hidden Area Mask: On

     

    SteamVR Settings: Render resolution 38% - 5352x2536

    SteamVR HOme: Off

    SteamVR Motion Smoothing: Off

     

    DCS Graphics;

    Textures: High

    Terrain Textures: High

    Civ Traffic: Off

    Water: Medium

    Visib Range: High

    Heat Blur: Low

    Shadows: Low

    Resolution: 1920x1440

    Aspect Ration: 1.333_

    Res of Cockpit Displays: 513 (or 1024)

    MSAA: Off

    Depth of Field: Off

    Lens Effects: None

    Motion Blur: Off

    SSAA: Off

    SSLR: OFF

    Preload Radius: Max

    Clutter/Grass: 500

    Antistropic Filtering: 16x

    Terrain Object Shadows: Flat

    Cockpit Global Illumination: On

    Messages Font Scale: 1

    Scale Gui: 1

    Vsync: On

    Pixel Density: 1.5 (will turn this to 1.2 for performance)

    IPD: 56

     

     

    Attached is a Persian Gulf Mission: "night test"

     

    Very re-producible with Pimax. Not certain about other headset manufacturers.

     

    Myself and a couple of other Pimax users have tried every permutation of settings. Too much deviation causes issues with SuperCarrier, so I would prefer to keep the changes down to a minimum as this appears to be an engine rendering problem.

     

    Please advise.

    Night Test.miz

×
×
  • Create New...