test content
Logo
What is the Arc Client?
Install Arc
Howdy, Stranger!
Comments
-
I'm not sure what's going on with your window not showing up, but the first time you load the game, the loading screen will take a long time. It needs to compile shaders when you run it under WINE, but it saves them so you won't have to sit through it again until a patch adds or changes something in the shader code.
-
Hey guys. The shader mentioned in the error message is just something that's not used in DX9. So it fails to compile in DX9 mode. Granted, it's pretty silly to spit out an error message about something that can't do anything for the given mode, but it's just a benign error message and is probably unrelated to the UI issues…
-
Committed, merged, and waiting to be included in a release build. As always, remember to run with 2>/dev/null to reduce all the error spam from the raw input system (this error output actually slows down your frame rate). Good luck!
-
That answer I gave is unrelated to the main WINE problem, which is in gpu detection for shader compiling. There's no easy workaround for the problem that's keeping people from playing entirely under WINE.
-
Well, you aren't going to get much help about a Windows specific problem in a thread about WINE crashes. The instructions I gave were specifically for working around raw input issues in WINE because I believed you were running under WINE because you were posting about it in a WINE thread. Anyone who isn't having an issue…
-
Try with this command line parameter: "-enableRawInputSupport 0" Alternatively, you can force it to think it's running under a different WINE version. The game disables raw input support for versions of WINE early enough to not support it (earlier than 1.5.13, I think). So you can try this command line parameter:…
-
Update: I think I have a fix for this, but there's still no way it's getting in before the weekend. I will beg and plead to get it in ASAP starting Monday. Sorry for you guys who can't play over the new content over the weekend. I'll try to get this fix pushed through soon.
-
Sorry, guys. We changed up a bunch of stuff about how we compile shaders since the last release, and the WINE stuff never got tested. Mostly because our "Linux testing" setup consists of my (personal) old laptop and we've all been pretty busy the last few months so I haven't booted up the game on it in a while. I'll try to…
-
The Mac version of STO is using Transgaming's Cider, which is essentially a fork of WINE that's been super-optimized to games and is unfortunately pretty Mac-specific. Still, a lot of work on the engine to make it behave under Cider also improved generic WINE compatibility, such as the way the launcher no longer depends on…
-
There's an internal list of WINE related issues I've been hacking on. Testing on WINE 1.4, these things just don't work: - Shadows (the good looking ones, not the blob-under-your-feet ones). - Any depth-based graphical effect. - Raw Input support (supposedly added to WINE in 1.5.13). - Resizing the window sometimes spews…
-
You can safely dismiss that screen and check the little box telling it not to nag you for a month. The option to run with "default" settings really just means it won't mess with your settings that you have. The option to run in low-graphics WILL adjust your settings. It's on the bottom of the list of WINE related stuff to…
-
There are actually some situations where the default value can clobber what you put in the configuration. Rather than changing it in the config file, you can change it on the fly with: /gfxSetDefaultFOV <fov> Also, this value is your vertical FOV rather than your horizontal FOV that most games would use. So multiply it by…
-
Do any of your other graphics settings revert like this? We may have seen a similar issue happen only one time internally, where someone's window kept reverting to the same location and size on the screen, but haven't seen it again since then. You may be able to fix it by moving or renaming your GamePrefs.pref file (which…
-
Please keep separate issues to their own threads.
-
I've been addressing this issue in the other thread. http://nw-forum.perfectworld.com/showthread.php?146431-Alienware-M11x-AlienFX-shutting-off/page2 TL;DR: A fix is incoming that restores the settings correctly when the game exits.
-
Hey guys. I just fixed the bug where the Alienware lights would not going back to your own settings after you quit the game. It may take a little while to go through all the process of getting this fix to the live game, but I'll keep you updated. Unfortunately, there's still not a menu option to disable the game taking…
-
Because it's the same way I got the patcher/launcher for Star Trek Online and Champions Online to run. Just going through the motions typical for getting a Cryptic game running under WINE. The launcher is a sore spot in terms of WINE compatibility. The game itself also has the same list of things broken under WINE as STO…
-
I've had some luck with WINE 1.4. If you're not using WINE 1.5.13 or later, you need to add this to your command line: -enablerawinputsupport 0 You might want to add that line anyway because WINE's raw input support may be flaky. You can find this in the options on the launcher. To get the launcher/patcher working I used…
-
Environment-triggered lighting stuff are some of the initial ideas we had but haven't made it in yet. At some point, hopefully we can get that all hooked up and have some of the environment artists set up some nice moody lighting to take advantage of the hardware. I'm just afraid I can't promise this will happen right away…
-
We're looking into a solution for this now. Thanks for reporting it! To those of you who do keep the option on, there are a few in-game indicators hooked up to the Alienware lighting features, like low health and full action points. It just sets the keyboard to black when those aren't on. Hopefully we can get a fix in for…