DangerDog wrote on Sep 27, 2011, 12:28:Releasing the mod tools would be a colossal undertaking for them, also due to the complexity of the game engine used you would never be able to figure out how it all works.

Complicated?

It cant be more complicated than writing a mod for Doom3. And id made *zero* docs for qeR: that was all community-based.

^Drag0n^ wrote on Sep 26, 2011, 14:33:Are these really new "drivers" or just setting profiles wrapped in the same old driver.

Why a game requires special drivers is beyond me. Adhere to the API standard(s): quit taking shortcuts.

^D^

Yes these are new drivers, not just a profile.

Learn how drivers really work and do some profiling with various games/apps and it will be more clear why you need special optimizations. A good place to start is the Mesa codebase or any of the open source linux 3d drivers.

I get that. Even been in those shoes.

I'm just not endorsing the, "screw how the driver is, I'm doing it this way," philosophy, and relying on nvidia/ATI to patch out a new driver for your game, just to ensure that it works correctly without stuttering, skipping, or just plane having shitty framerates. This CAN be addressed at the application level. Using a recent example: Deus Ex and stuttering. Special driver? No. Game Engine patch? Yes. Got 3 of them, in fact. Problem solved. Without a new driver for "Deus Ex Compatibility."

My point? 90-95% of games run out-of-the-box without graphics performance issues. Making a horrible user experience out of the box is ALWAYS a bad plan, even if it is fixed with a patch later (be it by the studio or a hardware vendor). RELYING on the 3rd party to ake your program run well is ALWAYS the worst, last option. The only reason they are getting away with it here is because BF3 will probably sell millions of units worldwide, and a shitload of hardware along with it.

necrosis wrote on Sep 26, 2011, 14:27:You do understand that just firewalling it does not fix the issues right? People have had issues with it just existing. I was one of them till some patches fixed my problems. But others still had tons of issues.

No I didn't know about those issues, I was responding to Elessar's troubles. That would suck. It does make me wonder what sort of deal they've reached with Microsoft to include GFWL. Because it does nothing useful in the game, and it's not designed to be DRM.

I had similar issues with Fallout 3 and DLC. Pissed me off to no end. I ended up just buying the GOTY CD about a year later just to get out of the issues I was having. I literally leaped for joy when Zenimax said they were switching to Steamworks for New Vegas. I've literally had zero problems with Steam. A few inconveniences? Yes (i.e. the PC validation), but overall so much better.

GFWL is just a steaming pile of offal that should be bagged and buried in the desert.

saluk wrote on Sep 24, 2011, 01:22:How in the heck will you know what you can click on in the sea of static objects?

It's not that hard. There are only a few object types that you can interact with in any given level and they're pretty recognizable. I played through the game with the object highlighting disabled and I didn't have any issues.

I guess that's why the whole sepia / hilight thing never bothered me. If you go back and replay, before you're augmented, that filter isn't there--it's an aftereffect of the augmentation. I just took it as such. I thought it was kind of cool, actually, as drivers /shooters glasses are amber to increase contrast by eliminating low frequency light.

Look, the boss battles are weak, we ALL get it, but just drop two level 2 Typhoons on the Bosses and move on. Seriously. I spent more time loading the game the first time I played it than I did on all of the bosses. Combined.