In the latest Git version, Optiscaler cannot run together with DXVK on the Windows platform. #907
Labels
No labels
0.9
3rd party
bug
documentation
duplicate
enhancement
invalid
linux
master
question
undetermined
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
roman/OptiScaler2#907
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Game name and version:
TestDX112DXVK
Mods and mod versions used
OptiScaler_git_faa0b7b34b64b0913e3af415f1bb9506110fd739; dxvk-gplasync-lastTest(disabled async)
GPU
Intel Arc A770
OS
Win 10/11
Used automated or manual install?
If on AMD/Intel and Automated, used DLSS inputs?
Also please mention in description which upscaler inputs are used (which upscaler you selected in game settings).
Did you check the Wiki and Compatibility List?
Please describe the issue and steps to reproduce it
Using pre10 or slightly earlier versions works fine, but in newer versions there is an issue when calling CreateDXGIFactory.
I have attached
LogLevel=0andLogToFile=truein OptiScaler.ini, zip it if too big)OptiScaler.log

Test EXE
Main.txt
Used alone.
Intercepting IntelControlLib.dll resolves the issue.

Can you check latest master after
500369e23d?Dxvk 2.7 seems to be running fine on AMD now but dxvk-git is a mess and I don't know if we are to blame or some dxvk vs amd driver incompatibility that only shows up when Opti gets involved.
The latest version does not resolve the issue. At present, it still appears to be a problem with GpuInformation IdentifyGpu::getPrimaryGpuVulkan().
There are some issues with DXVK on Windows for sure. Master should be better now, even on Linux but dxvk-git on AMD on Windows is still a mystery to me
Does disabling getPrimaryGpuVulkan have a significant impact on the overall system?
Only a small change is needed to fix the issue, but it requires disabling getPrimaryGpuVulkan.
I may be able to get rid of getPrimaryGpuVulkan entirely now. Just need to be careful to not end up in a loop with DXVK. Imagine a vkCreateInstance call from the game -> we call DXGI to query GPU -> DXVK calls vkCreateInstance -> back to start.
How is the situation with the latest master? I've added some fallbacks and removed vulkan query entirely.
When enabling NVIDIA spoofing in
dxvk.confon non-NVIDIA GPUs,Vulkan_Spoofing.cppincorrectly adds the NVNGX Vulkan extension. It is hoped that more validation checks can be implemented.The issue has been fixed