Jump to content

Can't select DLSS in VR


Go to solution Solved by Insonia,

Recommended Posts

Posted

Hello all.

I have HP Reverb G2 running DCS with OpenXR and MT binary. My PC has a 4090 and NVidia Drivers 545.84. If I start DCS in flat screen, DLSS is selectable. If I start in VR is greyed out. I disabled almost everything from OpenXR Toolkit, I tested with SteamVR also, but result is still the same. I attach my dcs.log.

Any suggestion is much appreciated.

Best regards.

dcs.log

  • Solution
Posted (edited)

your logs shows 

YOU ARE NOT RUNNING THE MT.

2023-10-21 16:26:55.034 INFO    APP (Main): Command line: "C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\DCS.exe" --force_enable_VR --force_OpenXR

 

You must use the steam launch select option to start MT:

Just few post below my original posts are "Enable VR in steam MT":

https://forum.dcs.world/topic/335510-i-cant-select-dlaa-option/?do=findComment&comment=5310038

 

Edited by Insonia
  • Thanks 1
Posted

@Topper81 Ensure Your GPU driver version is recent (say, above version 500).

If it is, try this:

  1. Run regedit.
  2. Browse to "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers".
  3. See if it contains a "TDRLevel" key: if it does, delete this key then reboot your PC.
  • Like 1

---

Posted (edited)

@Flappie @BIGNEWY

2023-10-22 18:35:17.680 INFO    DX11BACKEND (23688): NVIDIA DLSS not available on this hardward/platform., FeatureInitResult = 0x00000001, info: N

After some ref from "NVIDIA DLSS Super Resolution Programming Guide" and DLSS SDK

dx11backend.dll is somehow unable to capture the full "NVSDK_NGX_Result" string

The NVSDK_NGX_Result strings in your files were encoded as "UTF-16".

nullimage.png

but this line is UTF-8:

"NVIDIA DLSS not available on this hardward/platform., FeatureInitResult = 0x%08x, info: %ls"

And the "info:" part is where print the "NVSDK_NGX_Result"

i can safely assume the ed_vlogf() function is also can only print UTF-8 . So it was unable to print the UTF-16 string fully and only print the very first character "N.". 

info: N

This bug makes the user-end log incomplete. Make it impossible to troubleshoot with "NVSDK_NGX_Result".

I'm not sure if your team is aware of this?

Some refence:

Spoiler
typedef enum NVSDK_NGX_Result
{
    NVSDK_NGX_Result_Success = 0x1,

    NVSDK_NGX_Result_Fail = 0xBAD00000,

    // Feature is not supported on current hardware
    NVSDK_NGX_Result_FAIL_FeatureNotSupported = NVSDK_NGX_Result_Fail | 1,

    // Platform error - for example - check d3d12 debug layer log for more information
    NVSDK_NGX_Result_FAIL_PlatformError = NVSDK_NGX_Result_Fail | 2,

    // Feature with given parameters already exists
    NVSDK_NGX_Result_FAIL_FeatureAlreadyExists = NVSDK_NGX_Result_Fail | 3,

    // Feature with provided handle does not exist
    NVSDK_NGX_Result_FAIL_FeatureNotFound = NVSDK_NGX_Result_Fail | 4,

    // Invalid parameter was provided
    NVSDK_NGX_Result_FAIL_InvalidParameter = NVSDK_NGX_Result_Fail | 5,

    // Provided buffer is too small, please use size provided by NVSDK_NGX_GetScratchBufferSize
    NVSDK_NGX_Result_FAIL_ScratchBufferTooSmall = NVSDK_NGX_Result_Fail | 6,

    // SDK was not initialized properly
    NVSDK_NGX_Result_FAIL_NotInitialized = NVSDK_NGX_Result_Fail | 7,

    //  Unsupported format used for input/output buffers
    NVSDK_NGX_Result_FAIL_UnsupportedInputFormat = NVSDK_NGX_Result_Fail | 8,

    // Feature input/output needs RW access (UAV) (d3d11/d3d12 specific)
    NVSDK_NGX_Result_FAIL_RWFlagMissing = NVSDK_NGX_Result_Fail | 9,

    // Feature was created with specific input but none is provided at evaluation
    NVSDK_NGX_Result_FAIL_MissingInput = NVSDK_NGX_Result_Fail | 10,

    // Feature is not available on the system
    NVSDK_NGX_Result_FAIL_UnableToInitializeFeature = NVSDK_NGX_Result_Fail | 11,

    // NGX system libraries are old and need an update
    NVSDK_NGX_Result_FAIL_OutOfDate = NVSDK_NGX_Result_Fail | 12,

    // Feature requires more GPU memory than it is available on system
    NVSDK_NGX_Result_FAIL_OutOfGPUMemory = NVSDK_NGX_Result_Fail | 13,

    // Format used in input buffer(s) is not supported by feature
    NVSDK_NGX_Result_FAIL_UnsupportedFormat = NVSDK_NGX_Result_Fail | 14,

    // Path provided in InApplicationDataPath cannot be written to
    NVSDK_NGX_Result_FAIL_UnableToWriteToAppDataPath = NVSDK_NGX_Result_Fail | 15,

    // Unsupported parameter was provided (e.g. specific scaling factor is unsupported)
    NVSDK_NGX_Result_FAIL_UnsupportedParameter = NVSDK_NGX_Result_Fail | 16,

    // The feature or application was denied (contact NVIDIA for further details)
    NVSDK_NGX_Result_FAIL_Denied = NVSDK_NGX_Result_Fail | 17,
    
    // The feature or functionality is not implemented
    NVSDK_NGX_Result_FAIL_NotImplemented = NVSDK_NGX_Result_Fail | 18,
} NVSDK_NGX_Result;

 

Edited by Insonia
Posted (edited)
2 hours ago, Insonia said:

Can you enable DLAA DLSS in non-VR mode?

Have you installed any VR mods that enable FSR before ?(remove them)

@Insonia I think I havn't installed any VR mods.
I cannot enable DLSS in non-VR mode using "D:\Programme\Eagle Dynamics\DCS World\bin-mt\DCS.exe" --force_disable_VR" to start DCS World

image.png

Edited by Topper81
Posted (edited)

Do you not have to be using the beta version, your link is for the standard version. I could be wrong though.

Edited by Gogsie59
  • Like 1
Posted
4 hours ago, Gogsie59 said:

Do you not have to be using the beta version, your link is for the standard version. I could be wrong though.

You do need to be using Open Beta, yes, and I agree that the posters link would suggest they are on Release.  Having said that, I didn't think that Release had the option for DLSS even in the settings.  Definitely worth checking that you're showing "Multi-thread preview" before the version number on the main menu screen.

Posted (edited)

2023-10-22 18:35:16.250 INFO    DX11BACKEND (23688): NVIDIA API init OK
2023-10-22 18:35:16.252 INFO    DX11BACKEND (23688): AtiAPI_Initialize Error
2023-10-22 18:35:16.252 INFO    DX11BACKEND (23688): GPU count:1

And I noticed that the code normally shouldn't execute into ATI Initialize branch on a single NV GPU system. There is no "Display Driver Version" information in the logs.
mov     rcx, cs:qword_NVAPIstuff
test    rcx,rcx
jnz     doATIStuff
It means there are nvapi64 or NGX API errors (nullptr) to get into the ATI Initialize routine. which is contradictory to "NVIDIA API init OK". and GPU count:1.

The cause is unknown to me.

 

Users who share similar logs with @Topper81 probably need use DDU to do a full graphic driver uninstall. then make a clean graphic driver reinstall. Make sure no weird registry values remain in system and no modified/outdated dlls. Your case is too unique.

@Topper81Please direct contact with the developers. I cant do any further investigation.

https://www.digitalcombatsimulator.com/en/support/

Edited by Insonia
  • Thanks 2
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...