Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating from 0.96 to 1.0 #940

Closed
IanTrudel opened this issue Feb 27, 2019 · 10 comments
Closed

Migrating from 0.96 to 1.0 #940

IanTrudel opened this issue Feb 27, 2019 · 10 comments

Comments

@IanTrudel
Copy link

I am migrating my games from 0.96 to 1.0 but the new script reports File not found in wine prefix. Is there anything wrong?

WINEPREFIX=/home/ian/Games/Steam/steamapps/compatdata/645630/pfx /home/ian/Workspace/dxvk-1.0/setup_dxvk.sh install
/home/ian/Games/Steam/steamapps/compatdata/645630/pfx/dosdevices/c:/windows/system32/dxgi.dll: File not found in wine prefix

WINEPREFIX=/home/ian/Games/Steam/steamapps/compatdata/645630/pfx /home/ian/Workspace/dxvk-1.0/setup_dxvk.sh install --without-dxgi
/home/ian/Games/Steam/steamapps/compatdata/645630/pfx/dosdevices/c:/windows/system32/d3d10.dll: File not found in wine prefix
@doitsujin
Copy link
Owner

doitsujin commented Feb 27, 2019

This happens when a previous dxvk install deleted the original fake-dlls created by wine. The new script no longer does this and instead creates a backup, but for that reason it will also fail if the files don't exist.

Run wineboot -u on your wine prefix once, after that, it should work fine.

Edit: I see you're using Proton, in that case you should put the files into steamapps/common/Proton 3.16 Beta/dist/lib64/wine/dxvk (x64) and ...../dist/lib/wine/dxvk (x32), rather than changing individual wine prefixes. The setup script is not intended to be used with Proton.

@IanTrudel
Copy link
Author

Run wineboot -u on your wine prefix once, after that, it should work fine.

This fixes the issue. There is also a noticeable performance improvement coming with 1.0. Thank you for your amazing work.

Edit: I see you're using Proton, in that case you should put the files into steamapps/common/Proton 3.16 Beta/dist/lib64/wine/dxvk (x64) and ...../dist/lib/wine/dxvk (x32), rather than changing individual wine prefixes. The setup script is not intended to be used with Proton.

Will it be necessary to remove the previous DXVK installation in those individual wine prefixes?

@doitsujin
Copy link
Owner

Will it be necessary to remove the previous DXVK installation in those individual wine prefixes?

Probably, yes.

@IanTrudel
Copy link
Author

Alright, will do. Thank you.

@IanTrudel
Copy link
Author

DXVK_HUD reports that the previous version is still in effect. What am I doing wrong?

20190227220820_1

@IanTrudel IanTrudel reopened this Feb 28, 2019
@misyltoad
Copy link
Collaborator

You should uninstall using the script/method you installed with.
If that was the wineverb you may be out of luck without some manual bodging.

It may be easier to create a new wine prefix.

@IanTrudel
Copy link
Author

This is not working.

The steps I have taken based on your feedback:

  • Installed DXVK to Proton 3.16-7 Beta default prefix.
  • Uninstalled a game (SNOW 244930). Made sure the prefix was deleted.
  • Installed the game, applied the workarounds to ensure it works.
  • Ran the game, still v0.96.

And then...

  • Installed DXVK in the game's prefix.
  • Ran the game, still v.96

@doitsujin
Copy link
Owner

doitsujin commented Feb 28, 2019

  • Installed DXVK to Proton 3.16-7 Beta default prefix.

You're not supposed to install it into the default prefix, but copy the files (by hand) to the path that I mentioned above. That's the directory where all the wine libraries etc. are stored, and they are shared with all prefixes.

In practice, this works even without rebuilding the prefixes themselves, although you might need to restore those that you previously installed an older DXVK in.

@IanTrudel
Copy link
Author

My apologies for giving you so much troubles. I had followed your instructions but it was not working, hence turning to alternative solutions. It turns out that my Proton installation might have been the problem. I deleted the directory, forced Steam to reinstall it and then installed DXVK 1.0 according to your instructions. This however works out perfectly.

Thank you for your time. Very much appreciated.

@doitsujin
Copy link
Owner

Good to hear that you got it to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants