Hello GOG-fans and customers!

Just wanted to let interested folks know, that FEZ is fully working with Linux and WINE. Just installed it today using "PlayOnLinux" and WINE version 1.5.29. Only some winetricks were needed at all:

dx9 (and special libraries)
directx9
vc2005
vc2008
vc2010
xna31
gdiplus (for the setup-routine)

It works very good at all: I'm using a virtual desktop on a notebook with nVidia-optimus, using the bumblebeed-daemon.
So having fun with FEZ.

It is funny, it works on Linux, which is not advertised, and not work on Windows, which is advertised :-(

Very cool, thanks for testing this. I was going to reboot in XP and install SP3. Instead I'll just play in Wine.

Thanks for testing, nice to know! Downloading now.. Also sitting with a bumblebee setup here :) - only annoyance would be the huge amount of libraries needed to install then thing o.o

(Wine 1.4.1 on Debian Wheezy x86_64)

While testing patch 1.05 I noticed that using mono results in less native dependencies:

$ winetricks gdiplus
$ wine setup_fez_2.0.0.2.exe
$ wine patch_fez_2.0.2.4.exe
$ winetricks mono210

I created an entry in the Wine AppDB: FEZ GOG.com
You might share your experience and/or solutions to help other players.

I did not need any winetricks at all (well, I used winetricks sandbox; but it shouldn't matter).

Just keep dll overrides to the default and wine will install mono during the creation of the wineprefix. The setup will install xact and the game will work properly.

(wine 1.5.29)

You're right.
I built the current Wine version from source, tested FEZ, and queued an entry in the AppDB.

I usually write a "Linux playability" thread in each gog game I own, but here I think it would be redundant. What do you think?

The audience is at GOG, therefore a thread on the message board makes sense.
But it's nice to have an entry in the Wine AppDB (overview over versions, distributions, bugs, workarounds - and direct links between applications and bug tracker entries).

I've made a PlayOnLinux script for Fez. Just check the "Testing" box when looking for it in PoL's games list. If you have an issue with it, let me know.

Am I the only guy having problems installing the universal update over WINE? I seem to be getting errors when I attempt to run the updater. I am under Arch Linux 64-bit

Tried 2.0.0.2 to 2.0.3.5 (re-downloaded) and 2.0.2.4 to 2.0.3.5 (existing installation).
Both work with Wine 1.4.1 on Debian testing 64-bit (with winetricks gdiplus mono210).
I almost always use "env LANG=C winetricks sandbox winemenubuilder.exe=disabled" (after setting WINEPREFIX) to initialize the prefix and do not use spaces in paths (just c:\game\). Some installers/patches don't like to bee run from root (c:\) so i move them to c:\inst\.

since we are in topic I usually use those two scripts:

First one to initialize a wine environment in the current directory (lets call it ~/games/dd)
------ >8
#!/bin/bash
set -e

STARTPWD="`readlink -e "$PWD"`"

export WINEPREFIX="$STARTPWD"/wine
export WINEDLLOVERRIDES="mscoree,mshtml="
export XDG_CONFIG_HOME="$WINEPREFIX"/xdg_conf
export XDG_DATA_HOME="$WINEPREFIX"/xdg_home
export XDG_CACHE_HOME="$WINEPREFIX"/xdg_cache
export WINEARCH=win32
export LC_ALL=C

wineboot -u
winetricks sandbox
8< -------

And I copy this second one in the directory (~/games/dd) to start the application when I need it.
------ >8
#!/bin/bash
set -e

STARTPWD="`readlink -e "$PWD"`"

export WINEPREFIX="$STARTPWD"/wine
export WINEDLLOVERRIDES="mscoree,mshtml="
export XDG_CONFIG_HOME="$WINEPREFIX"/xdg_conf
export XDG_DATA_HOME="$WINEPREFIX"/xdg_home
export XDG_CACHE_HOME="$WINEPREFIX"/xdg_cache
export WINEARCH=win32
export LC_ALL=C

#change the next lines to start your application
cd "$WINEPREFIX"/drive_c
bash
8< ------

Of course it is not universal, for example FEZ needs mscoree left to the default, but it is a good starting point.

I prefer using LC_ALL instead of LANG because the locale checks the variables in this order: LC_ALL, specific one (e.g., LC_TIME), LANG and gets the first available. So using LC_ALL you are sure that only the C locale will be used.