Skip to content

Releases: rankynbass/wine-ge-xiv

Unofficial xiv-Proton8-26

04 Feb 06:40
a7c2e2d
Compare
Choose a tag to compare

Updated to Wine-GE Proton8-26.

This might be the last release of unofficial-wine-xiv-proton. GE is working on another project which will make Proton fairly universal, and as such, may not release any more versions of his custom wine. See the release notes for GE-Proton8-26 for more info. The compatibility rework is scheduled to be added soon, so once that's in, I'll work on adding the new ULWGL-Launcher to XIVLauncher. I've already figured out how to build Proton-GE with XIV patches, so we can even have a custom Proton version just for FFXIV.

Unofficial xiv-Proton8-25 (Camera bug fix?)

28 Dec 06:07
xiv-Proton8-25
a7c2e2d
Compare
Choose a tag to compare

Updated to Wine-GE Proton8-25.

Reverted proton-wine commit df43fd7, which seems to be the one that causes the camera bug in KDE. I don't know if this commit is actually needed for other environments. If you are not using KDE, and suddenly have issues, let me know.

Unofficial xiv-Proton8-24

21 Nov 04:52
87250d7
Compare
Choose a tag to compare

Updated to Wine-GE Proton8-24. If you are having problems with the camera (mostly affects KDE users), try version 8-12, or version 7-43 or earlier.

Unofficial xiv-Proton8-22

02 Nov 23:30
c06b8b5
Compare
Choose a tag to compare

Updated to Wine-GE Proton8-22. If you are having problems with the camera (mostly affects KDE users), try version 8-12, or version 7-43 or earlier.

8-12.2 Test release

16 Nov 04:52
c06b8b5
Compare
Choose a tag to compare

Test release to try and get haptic feedback working again.

Unofficial xiv-Proton8-21

25 Oct 00:06
487ca5d
Compare
Choose a tag to compare

Unofficial xiv-Proton8-20

16 Oct 23:50
83b8cff
Compare
Choose a tag to compare

Updated to Wine-GE Proton8-20. What happened to 8-19? It was a minor hotfix for 8-18, and was immediatly hotfixed again to make 8-20. So I actually never even saw it.

FSR is no longer enabled by default. You must specify WINE_FULLSCREEN_FSR=1. If you were already doing this, there's no real change.

Includes FSR and haptic feedback patches. In theory, DualSense controllers should work, although it may only work when they are connected via wire, not bluetooth.

For reference (taken from GE's release notes for Proton7-21 & 7-22)

WINE_FULLSCREEN_FSR=1: It will generate the 4 FSR resolutions for the current screen resolution and aspect ratio and add them to the list of resolutions
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE=mode: It will add only the resolution to the list and it will discard any resolutions larger than it. Modes are:
ultra — 1.3x scaling
quality — 1.5x scaling — At 3840x2160 (UHD or "4K"), render at 2560x1440. At 1080p render at 720p
balanced — 1.7x scaling
performance —2x scaling
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_CUSTOM_MODE=WxH: It will add the 4 FSR resolutions and mode WxH to the list of resolutions, it will discard anything larger than WxH, so any FSR resolutions larger than WxH will be discarded too.
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE= WINE_FULLSCREEN_FSR_CUSTOM_MODE=WxH: It will try to add only resolution and the custom WxH mode. It will still limit based on the custom mode. So if the resolution from is smaller than WxH it will be in the list but if it is larger than WxH it will be discarded.

Proton 8 is much different from Proton 7. If you have just upgraded from Wine 7 or Proton 7 and are having crashes, try deleting ~/.xlcore/wineprefix

Unofficial xiv-Proton8-18

15 Oct 18:52
5df9f1d
Compare
Choose a tag to compare

Updated to Wine-GE Proton8-18.

FSR is no longer enabled by default. You must specify WINE_FULLSCREEN_FSR=1. If you were already doing this, there's no real change.

Includes FSR and haptic feedback patches. In theory, DualSense controllers should work, although it may only work when they are connected via wire, not bluetooth.

For reference (taken from GE's release notes for Proton7-21 & 7-22)

WINE_FULLSCREEN_FSR=1: It will generate the 4 FSR resolutions for the current screen resolution and aspect ratio and add them to the list of resolutions
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE=mode: It will add only the resolution to the list and it will discard any resolutions larger than it. Modes are:
ultra — 1.3x scaling
quality — 1.5x scaling — At 3840x2160 (UHD or "4K"), render at 2560x1440. At 1080p render at 720p
balanced — 1.7x scaling
performance —2x scaling
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_CUSTOM_MODE=WxH: It will add the 4 FSR resolutions and mode WxH to the list of resolutions, it will discard anything larger than WxH, so any FSR resolutions larger than WxH will be discarded too.
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE= WINE_FULLSCREEN_FSR_CUSTOM_MODE=WxH: It will try to add only resolution and the custom WxH mode. It will still limit based on the custom mode. So if the resolution from is smaller than WxH it will be in the list but if it is larger than WxH it will be discarded.

Proton 8 is much different from Proton 7. If you have just upgraded from Wine 7 or Proton 7 and are having crashes, try deleting ~/.xlcore/wineprefix

Unofficial xiv-Proton8-17

03 Oct 23:12
59e8428
Compare
Choose a tag to compare

I've had this for a while, but forgot to post it. This is a WINE release, not proton. It is based on proton-wine from valve, but is de-protonified a bit to work as a normal wine build. GE patches are from GloriousEggroll, and XIV patches are from the XIVLauncher team.

Updated to Wine-GE Proton8-17.

FSR is no longer enabled by default. You must specify WINE_FULLSCREEN_FSR=1. If you were already doing this, there's no real change.

Includes FSR and haptic feedback patches. In theory, DualSense controllers should work, although it may only work when they are connected via wire, not bluetooth.

For reference (taken from GE's release notes for Proton7-21 & 7-22)

WINE_FULLSCREEN_FSR=1: It will generate the 4 FSR resolutions for the current screen resolution and aspect ratio and add them to the list of resolutions
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE=mode: It will add only the resolution to the list and it will discard any resolutions larger than it. Modes are:
ultra — 1.3x scaling
quality — 1.5x scaling — At 3840x2160 (UHD or "4K"), render at 2560x1440. At 1080p render at 720p
balanced — 1.7x scaling
performance —2x scaling
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_CUSTOM_MODE=WxH: It will add the 4 FSR resolutions and mode WxH to the list of resolutions, it will discard anything larger than WxH, so any FSR resolutions larger than WxH will be discarded too.
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE= WINE_FULLSCREEN_FSR_CUSTOM_MODE=WxH: It will try to add only resolution and the custom WxH mode. It will still limit based on the custom mode. So if the resolution from is smaller than WxH it will be in the list but if it is larger than WxH it will be discarded.

Proton 8 is much different from Proton 7. If you have just upgraded from Wine 7 or Proton 7 and are having crashes, try deleting ~/.xlcore/wineprefix

Unofficial xiv-Proton8-16

24 Sep 20:07
ac3570c
Compare
Choose a tag to compare

Updated to Wine-GE Proton8-16.

The build process has been updated, which took me several attempts to get working. Hint: make sure the buildbot submodule is up to date with the wine-ge-custom master branch.

FSR is no longer enabled by default. You must specify WINE_FULLSCREEN_FSR=1. If you were already doing this, there's no real change.

This is a WINE release, not proton. It is based on proton-wine from valve, but is de-protonified a bit to work as a normal wine build. GE patches are from GloriousEggroll, and XIV patches are from the XIVLauncher team.

Includes FSR and haptic feedback patches. In theory, DualSense controllers should work, although it may only work when they are connected via wire, not bluetooth.

For reference (taken from GE's release notes for Proton7-21 & 7-22)

WINE_FULLSCREEN_FSR=1: It will generate the 4 FSR resolutions for the current screen resolution and aspect ratio and add them to the list of resolutions
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE=mode: It will add only the resolution to the list and it will discard any resolutions larger than it. Modes are:
ultra — 1.3x scaling
quality — 1.5x scaling — At 3840x2160 (UHD or "4K"), render at 2560x1440. At 1080p render at 720p
balanced — 1.7x scaling
performance —2x scaling
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_CUSTOM_MODE=WxH: It will add the 4 FSR resolutions and mode WxH to the list of resolutions, it will discard anything larger than WxH, so any FSR resolutions larger than WxH will be discarded too.
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE= WINE_FULLSCREEN_FSR_CUSTOM_MODE=WxH: It will try to add only resolution and the custom WxH mode. It will still limit based on the custom mode. So if the resolution from is smaller than WxH it will be in the list but if it is larger than WxH it will be discarded.

Proton 8 is much different from Proton 7. If you have just upgraded from Wine 7 or Proton 7 and are having crashes, try deleting ~/.xlcore/wineprefix