Rage PC players report bugs
Rage on the PC is suffering from early bugs, including texture problems, frame rate issues, audio stuttering, and outright crashes.
Rage is launching today for all platforms, and unfortunately for some players, its PC version doesn't seem to be all smooth sailing. Users have been chiming in with a variety of bugs, from texture blinking and audio stuttering to the occasional outright crash.
Texture pop-in, artifacts, frame rate issues, and audio stuttering seem to be the most common complaints, while others report crashing after the intro video, when exiting the Arc, or a simple failure to start the game.
"Everyone, make sure you have latest Nvidia/Ati drivers to play Rage," id Software's John Carmack said on Twitter in response to early backlash. A Radeon driver update was expected to fix some of the bugs, but at least for Rock Paper Shotgun, the problems persisted.
The user video below (via the Steam forums) shows some of the texture pop-in issues in action:
The console versions have yet to receive the same level of complaints. Shacknews has contacted Bethesda regarding the bug reports and inquired about plans for a patch. We'll update as more information becomes available.
-
Shacknews
replySteve Watts posted a new article, Rage PC players report bugs.
Rage on the PC is suffering from early bugs, including texture problems, frame rate issues, audio stuttering, and outright crashes.-
[deleted]
-
Between the texture pop-in and the flickering, the game is pretty unplayable for me.
I'm sure they'll get it all sorted out in time, but I never thought I'd be having buyer's remorse over an id game. :\-
ikr Reading about things like this makes me wish Carmack would go and choke out Robert Altman like he did Jace Hall.
-
no doubt a lot of this is due to incompetence on the end of the player. out of date drivers, etc.
-
if that's the case, why don't we hear this about more titles? seems like it's more likely a mix of the usual percentage of people with crud in their systems, and then some actual stability problems
-
-
Most recent drivers here, and I am incompetent in regards to many things, but not about my pc (for I am an IT professional, well versed in the operating system and security).
If you actually have the game and are having zero issues with it, well that's great for you. You are lucky bastard and I'm a little jealous. But there are a pretty large amount of people having issues with this, and throwing them all (or even "a lot" of them) under an incompetence rug seems a little silly.-
I'm having no problems here on my PC version. No noticeable texture pop in or crashes or anything like that. My only complaint on the game is actually low-res textures (rumored to be fixed with a high-res texture patch for PC), and you can see the grid on everything as faint black lines (easily fixable by the devs). VERY minor grumbles that in no way hinder my gameplay.
-
[deleted]
-
-
http://twitter.com/#!/CatalystCreator/status/121248985557118976
All - don't use the current Rage performance driver - package includes very old OGL files, that's why you're seeing corruption etc.
So even with the RAGE-specific latest catalyst drivers, there's still major issues. I don't think you can pin that on the player. -
AMD's drivers released today for Rage are actually broken (though they should be fixed shortly). That's not always the case.
-
Let me put it delicately - I've worked in IT for 15 fucking years. My system is clean as fuck and up-to-date as hell. And Rage crashes like a motherfucker and I've tried every god damn thing I can think of to make it run better. And before the crashing it looked like this ( http://steamcommunity.com/id/mrwolf710/screenshot/560921086997134298?tab=public ). Thankfully the drivers from yesterday evening fixed that.
But I'm still pissed as hell that I spent $60 on this game and can't play it. So far the furthest I've managed to get is the door to the first dungeon. Then it locks up and crashes to desktop. And that's if the game gets that far. If I try to hit F5, or Esc or the Start button on my 360 controller the game just flat locks up.
Over the last month I've probably put 100 hours of gaming in on 5 or 6 different games so my system is just fine. It's Rage that's the problem. I wanna kick myself in the balls for buying this before release.-
No doubt your ego is larger than you understanding of PC software/hardware. Clown.
-
your* (why doesn't Shack have an edit function for typos?)
-
-
-
Temporary fix for ATi flickering issue
Installing the latest ATi OpenGL drivers completely fixed the flickering issues for me.
http://support.amd.com/us/kbarticles/Pages/AMDCatalystOpenGL42BetaWin.aspx
For those of you insinuating that this is people w/ outdated systems/drivers, you are incorrect. ATi already tweeted that they know the issue is because they mistakenly packaged an old OpenGL version into the latest ATi Rage performance hotfix.
My guess is that installing these beta drivers overwrites the old OpenGL package that was installed w/ the Rage performance hotfix.
let me know if it works for you!
5770 ; 11.10 beta drivers + the above linked hotfix
8gb
i5 2500k-
-
They're supposedly adding that to the Rage drivers they put out earlier today in a fixed driver at some point.
-
-
Okay, great. Tagged for later!
-
-
are you at the 11.10 version of the drivers? i also have vsync forced in the ati control center
-
-
I'm not fucking touching this game until next week. I have dropped the loot for it, because I can never put my money where my mouth is, but I know better with AMD by now.
-
-
-
-
-
[deleted]
-
Minecraft and Space Pirates and Zombies both crash with this new driver. They both worked fine with the previous hotfix driver.
-
-
-
[deleted]
-
For what it's worth, it's playing nicely for me now on a 560Ti + i5 2500k. So here's a rundown of what I've tweaked... might be helpful for anyone who hasn't already encountered these suggestions.
There's often still some noticeable flicker from texture popin if I spin around, but I'm hesitant to go poking around at more stuff until I know more about the actual effects of these suggestions that are being posted everywhere.
Roughly in order of importance:
* Driver
As far as I can tell, the latest official (WHQL) NVidia driver does not support OpenGL 4.2. You need one of the more recent beta drivers (285.27 or 285.38). I installed 285.38 and the tearing has been reduced; I'm guessing that the special vsync behavior that Rage tries to do is an extension that is only supported in OpenGL 4.2. Didn't notice any bad effects from the beta driver yet.
* Command-line tweaks for "feel"
These should be self-explanatory:
+cvaradd g_fov 20 +set com_skipIntroVideo 1 +m_smooth 0 +m_rawinput 1
* Video settings
Enabled GPU transcoding. Can't really tell that it helped, but it didn't hurt.
I'm running with fairly minimal AA (2x) at the moment; I may try to bump it back up now that I've tweaked everything else.
* Cache
I saw some posting about Rage failing to create a necessary cache directory, so I experimented with that. Reportedly this directory should be "id software/rage" under %localappdata%. I didn't have that, so I created it. I also added the command-line option:
+fs_cachepath "C:\Users\\AppData\Local\id software\rage"
Hey presto, a gigabyte cache file of some sort has appeared there. Could be important, but I haven't isolated this from the other tweaks to see if it had any good effect on its own.
There are also several other suggested command-line options being posted everywhere that I haven't used yet:
+fc_maxcachememoryMB 1024 +ik_enablesmoothing 0 +image_usecompression 0 +jobs_numthreads 4 +mem_phymemblocksizem 3072
Some examples about why I'm not in a rush to try that stuff out: The file cache is already a GB in size, so what purpose does setting fc_maxcachememoryMB to that value serve? ik_enablesmoothing sounds like it messes with the inverse kinematics system, why would I want to do that? I can guess at what image_usecompression and jobs_numthreads do, generally speaking, but details would be nice, and I have no idea about mem_phymemblocksizem.
Undoubtedly a wiki explaining everything will sprout up sooner or later, but I'll probably be done with the game by then. :-)-
Sigh... Shacknews and the less-than symbol. My example of the fs_cachepath setting was supposed to have a placeholder inserted in there to represent where my username is, but the Shack has eaten that part. Anyway you get the idea; the string in the quotes should be the filepath for the cache folder.
-
-
-
[deleted]
-
mods please INF this!!!!!! this is "NEWS"????
-
I have a little project im going to write a post-bot that replies to all shacknews news posts with "this is news?"
-
randomize if it puts news in quotes or not
-
-
-
-
-
-
Im a massive PC fan but honestly PC fans dont help themselves.
It's day one, before any video drivers have been released and already people are on their soap box with the usual "Console Port", "Sell outs", "You suck and I hope you die ID"
Seriously sort it out, no one will want to make PC games witht he amount of attitude they get as developers, day one running 100% with all the tech in games these days just doesnt happen.
At least give the devs a chance to patch and for a new set of drivers from Nvidia/AMD.-
It's based on standards and expectations. If a game is being sold for real cash, people rightfully expect it to work. Else it's still in alpha/beta. Also, if needing drivers that are still glowing hot off the factory line is something that is to be expected from now on, that needs to be communicated in advance because it's not up to established standards.
-
-
I had really bad pop-in textures, flickering, and artifacts, but installing the updated AMD drivers for my 6870 has fixed most of my issues. The pop-in is still there but its just barely noticeable now.
My only problem is that the game freezes/crashes when I'm attempting to load the first race.
-
What I don't get is that he's recommending that PC users upgrade to the latest driver available now (even BETA) in order to resolve these problems. But considering how long RAGE has been in development, surely they've had the game running decently on PC for quite awhile (hopefully?) assuming the use of older Nvidia and AMD drivers???
