I did apply all the fixes, including adding the cache file and trying numerous different config alterations, none of which completely solved the problem. Carmack can say whatever he wants but he knew he was selling garbage on launch day and he only says he regrets focusing on consoles to save face. The only question I have is why are you acting as an apologist for a guy who gimped the base he built his success off? Seriously, look up shoddy console port in the dictionary and you'll see a picture of RAGE.JC_Spot
---Apologies, and flaws
I'm not an apologist for id, I defend what they did right, and I criticize them for what they've done wrong (just as I do with Blizzard, or any other of my favorite devs).
It's flawed, sure, but it's not broken in the ways you go after, but these things are:
- TERRIBLE, disjunct, meaningless story
- Gimmicky racing crap(hold handsey)
- Big technical limitations holding back any hopes of texture quality
- Clearly mismanaged development/developing in a vacuum/ivory tower
- Extremely minor bug of vsync turning off when you alt tab.
- Lied about giving us idStudioand 64bit client(disgusting lie)
- Disabled console commands(WTF)
- Dumb currency system making ammo needlessly scarce in a game that's got such superb gunplay that all you want to do is shoot.
- Launching w/o texture cache setting (see 4)
- Uniteresting level design
- Inconsistent texture quality(due to surface area and the mega texture)
- Horrible boss design
- Mouse movement in menus for some people(including me) is messed up as hell(same with any id game)
- No mod support
What's good about Rage?
- Stable
- Consistent art style
- Beautiful animations(some of the best in any game)
- Great gunplay
- Great sound
- Good VA
Wow... such an ardent defender I am.
At the time of Rage's release, and even now, it was extremely uncommon to have >1gb ofvram, that game's tech would require about 2 to make a visually notable increase in its texture quality above the current consoles and need 2 more to cache up enough textures to prevent constant popping every time you turn around. I don't personally see it as a very good tech, it's too limited in my eyes.
And yes, at QuakeCon he was clearly reserved about the game in many ways, so he knew there were flaws, but he didn't know the launch was going to fall flat on its face though, that was all on AMD. He warned constantly that PC had issues with overhead, throughout interviews, and that it'd have popping issues that the console versions(specifically the 360) wouldn't have due to non-standardized memory arcitecture(which I can't confirm as the truth). He wasn't selling garbage, he was selling id quality mismanagement. (lol)
---A brief history of id
id is screwed up in many ways, ever since Doom3(even Q3A tbh) they've been mismanaging the hell out of their development and doing so from an ivory tower. Q3's success was a luck of the draw, they hit a time where people wanted a MP only fps, but that wasn't good development, it was a rush job. I don't know what you were expecting out of Rage, but you shouldn't have had your bar so damn high considering id's history of crappy development and never making a game worth better than 8.5.
---Porting
But, Rage isn't a shoddy port, it's a very solid port, but a port none the less. There's nothing in the rules of porting that says "You must make the game substantially better on the new platform". Sure you can 'expect' and feel 'entitled' to a better port, 'cause id was a PC first dev, but that's not in the rules.
Rules of porting: The game must work and it's nice to have additional features
BioWare's ports are all kinda lazy, they take away the ui/mechanics for gamepads(odd as hell) don't update the textures and don't support modding(which I hate)
HaloCE is a pretty lazy port, the animations are baked at 30fps, so if you have hardware to push 60 well, sad day for you, it'll look like crap.
If you want to know the dictionary entry for a 'bad port' well, here it is.

Log in to comment