Closed hilts-vaughan closed 3 years ago
Note: It works if I...
So, I am inclined it's something to do with the driver + prefix; is this worth chasing down or should I just blow the buggy prefix away?
Works fine here, and HTTPS errors are not a DXVK problem.
I see. Since it's seemingly something to do with the prefix / driver combination, I don't particularly need this fixed nor do I expect you to (especially since a fresh install works on the newest drivers). However, it takes a lot of disk space to keep a working install and the old prefix around.
Is there any information you want from the old prefix, not working under those drivers? If not, I will just submit a report to Nvidia and then blow the prefix away. I just didn't want to do that if there was valuable debugging information in it that you may want to look at.
There's nothing I can do here anyway, if the exact same DXVK code works fine on a different wine prefix then DXVK simply isn't the reason why it's not working.
When running FFXIV from Lutris on
nvidia 495.44-2
, I appear to get one of two possibilities:This is working with WINE's D3D implementation and does not cause the freeze (i.e: turning off DXVK), though the frame rate is awful. =) However, I can login. Re-enabling DXVK will cause the game to no longer boot again.
Reports with no log files will be ignored.
System information
Apitrace file(s)
N/A; will look into how to make one for the launcher
Log files