FEZ launched today, and as expected with a PC launch, not to mention a company's first PC launch, we hit some bumps in the road.
First, a couple of common fixes or workarounds.
If you're having problems running the game at all, you should verify that :
- You have the latest available drivers for your graphics card
- You have at least 200Mb of free disk space
- You have tried running the game As Administrator
For Intel HD Graphics owners : some users of the 3000 and 4000 series have been able to run the game by updating their drivers.
If you still can't run the game, chances are your card is currently unsupported. We are, however, exploring the possibilities to make it work. This involved getting our hands on test hardware and seeing what are the roadblocks. It may take a while to get there, but rest assured that we'll try our best.
You'll want to follow this topic : https://getsatisfaction.com/polytron/...
If you're having a "sound subsystem" dialog error, you're not alone : https://getsatisfaction.com/polytron/...
Some people have found workaround involving headphones or changing their primary sound output device. See what works for you while we tackle the root problem.
We're taking a look at all the issues and prioritizing people are locked out of playing the game, but again we'll have to apologize and ask for your patience as we go through them, there's a lot to process right now.
A new patch is live on Steam right now, and will deploy to GOG and Humble in a day or two. Here's the changelog for v1.03, admittedly a small update :
- Fixed crash-on-load errors for systems with Turkish regional settings
- Fixed possible crash when accessing video settings
- Fixed wrong letterboxing when going fullscreen with some 16:9 resolutions
Thanks for your support, and hang in there!
Help get this topic noticed by sharing it on Twitter, Facebook, or email.
After getting the village pipe room anticube, I quit the game and then launched it later. Accessing the Leaderboards crashes the game every time (they worked earlier). Also now the anticube appears whenever I continue my game and I can farm them as many as I want. Not sure what I exactly did to trigger this, but thought to report this!
After the 1.03 update, the game freezes when I try to load my save file. It worked fine on 1.02. I currently can't play the game at all, even though I just played it for a few hours. Also, the letterboxing is still incorrect. I've choseen my native monitor resolution and I have a black border around the entire screen.
Savegames seem to have gotten corrupted by the last update. I guess it wasn't totally unexpected. When I went to select my save from yesterday, it said x% finished, x hours played. After selecting the savegame it wouldn't let me continue (the continue button was grayed out, could not be selected). So I started a new game. The completion % went back to zero, but the time spent playing remained at ~2h.
Two other things I wanted to mention. Could you post a changelog for future updates directly on Steam? I get a warm, fuzzy (fezzy?) feeling knowing what's changed or was fixed when an update comes out, right there on the spot. If it's too much trouble, guess I'll bookmark this site. And 2nd, Fez has no Steam Forum page. I don't know if this is something Valve needs to add or you need to request it. Anyway, just thought I'd throw that out there.
Enjoying the game so far. Thanks!
Mobile Intel(R) 4 Series Express Chipset Family (upgraded)
(10:03:47.206) [OpenAL] 32-bit OpenAL-Soft will be used
(10:03:47.323) [OpenAL] Available mono sources : 255
(10:03:48.117) [Version] INFORMATION : 1.02, Build Date : 01.05.2013 4:16
(10:03:48.285) [MonoGame] INFORMATION : OpenGL version 2.1.0 - Build 220.127.116.1169
(10:03:48.286) [MonoGame] WARNING : GL_ARB_framebuffer_object not supported : will use GL_EXT_framebuffer_object instead.
(10:03:48.288) [MonoGame] WARNING : No S3TC/DXT support : will decompress DXT textures at load time.
(10:03:49.679) [Intro] INFORMATION : First draw done!
The game does not run at all. Just "loading game..." screen and then crashes.
I hope you'll reach the sourse of the problem and solve it!
Btw, thanks for the game.
"If you're having a "sound subsystem" dialog error, you're not alone : https://getsatisfaction.com/polytron/...
Some people have found workaround involving headphones or changing their primary sound output device. See what works for you while we tackle the root problem."
Yes! Finally advice from a developer!
Was getting this problem after today's update
(21:44:27.955) [OpenAL] 32-bit OpenAL-Soft will be used
(21:44:30.635) [Unhandled Exception] ERROR : System.TypeInitializationException: The type initializer for 'Microsoft.Xna.Framework.Audio.OpenALSoundController' threw an exception. ---> System.NotSupportedException: No audio hardware is available.
at OpenTK.Audio.AudioContext.CreateContext(String device, Int32 freq, Int32 refresh, Boolean sync, Boolean enableEfx, MaxAuxiliarySends efxAuxiliarySends)
--- End of inner exception stack trace ---
at Microsoft.Xna.Framework.OpenTKGamePlatform..ctor(Game game)
at Microsoft.Xna.Framework.GamePlatform.Create(Game game)
at Common.Logger.Try(Action action)
I couldn't even get into the game. After updating XNA to version 4.0, I can play again. Just FYI.
 I still get the error (Error initializing audio subsystem. Game will now exit), but only after the first attempt to boot the game. If I boot the game a second time, it loads without issues. Previously, before I updated XNA, I couldn't get into the game at all. This error was not an issue before update v1.03.
Also, eff XNA. I still can't play Bastion (works inside a Virtual Machine running WinXP. Go figure.).
Sound Blaster Live! 5.1 (kX Audio Driver)
Intel Core2Duo E8400
This reply was removed on 2013-05-02.
see the change log
This reply was removed on 2013-05-02.
see the change log
"For Intel HD Graphics owners : some users of the 3000 and 4000 series have been able to run the game by updating their drivers.
If you still can't run the game, chances are your card is currently unsupported."
Hahahaha. Oh god.
It's the graphic card of almost every recent Macbook Pro. Tons of freeze, i'm pretty disappointed...
Maybe i'll able to play on the mac version, in 2050. :sic:
People need to chill. It's just one guy, and now Phil sounds like he's going to off himself.
As I've mentioned before, I still haven't played Bastion because it doesn't work... for whatever reason (I'm not in the mood to re-install win7 just to find out, or not find out and spend the next week re-installing all my shit). But I will, eventually. It's not like you payed $60 for the game (convert to other currencies at your leisure) and don't have other games to play. In the mean time, let Renaud sort things out.