Batman: Arkham City Gets Extra Technical Tricks on PC

Don't know what all the hate with GFWL is about, it never have me any problems in Batman AA. But isn't GFWL going away and tuning into Xbox something or another?

I've had several login issues and infinite loop login failures. That was a couple years ago, though.
 
Thats actually quite wrong. You can do all your physics in OpenCL.
But one has to ask, if nVidia's going to do your physics for you, why would you dedicate man hours to doing physics.

Same goes for 3D. In fact I think we should be thanking nVidia, NOT Rocksteady for bringing goodies to the PC :(

Actually no, he's right you're wrong.

Physx isn't just an API. Its an API with libraries that contain sophisticated algorithms for calculating physics which take millions of dollars of investments to develop, improve, and perfect. Just because you choose to use opencl doesn't mean you have any algorithms for the physics. Opencl is a vehicle for getting the processing done where you want, and it itself has nothing to do with physics.

So physx could run on opencl or cuda, but opencl is not a replacement for physx.
 
I only copied over what was under the SaveData director; I did not backup any of the Live files.

/shrug

maybe a game update or one of the live updates has changed that then. Back when that happened to me though I had to restart.
 
Um, yes, you can. I have reinstalled Batman AA on Steam and loaded my old saves and it worked.

The trick?

You see, in the My Documents or My Games folder or wherever the files are put, it makes a directory named with seemingly random characters. You may have seen this. All you do is let the game create the new directory (it will not be named the same as your previous saves) and you copy your save files INTO the directory that the game creates.

Voila. It worked for me.

Everything I looked at a year ago when I had a nearly complete save said it was impossible. Sadly I don't have that save anymore.

God so much misinformation. AMD drivers didn't support AA on surfaces using the particular format the development used for motion blur effects. The necessary driver support came months later after the game shipped. If they didn't lock it out, THEIR ADDITION would've caused corruption and increased user support issues for their partner, the developer, and obviously that's not good. The motivations were not terrible as you say. That said, it would be fair to argue that they should've left it in and let users hound AMD into fixing it.

Ah thanks for that clarification. I'll have make a mental note to remember that.
 
Play it in 3D Surround with PhysX, there's you're difference.

So I'm going to miss out on the migraine it will induce?

I'll take the collectors edition, console version please, and from what I can find, there isn't a collectors edition for PC.

I love my PC, but I shall wait until it goes cheap on STEAM, maybe they will bundle it with the original for $20 sometime, I'll have to invest in a 360 controller.

In the meantime it will be fine on the PS3.
 
I have an nVidia card and will buy this title day one. I do feel it's bullshit that AMD users are not supported with half of the visual goodies. Physx was more than "Flying paper!" as one dude stated. It actually added to the game with Scarecrow with the explosions and bricks and steam, then there was also his cape that didnt simply drape over his frame, it moved lifelike. The effects weren't overdone, they made the game look and play great.
Than this could not be ported to OpenCL is a shame.
 
So I'm going to miss out on the migraine it will induce?

I'll take the collectors edition, console version please, and from what I can find, there isn't a collectors edition for PC.

I love my PC, but I shall wait until it goes cheap on STEAM, maybe they will bundle it with the original for $20 sometime, I'll have to invest in a 360 controller.

In the meantime it will be fine on the PS3.

I could NEVER play this game with a controller. I tried it on a 360 pad once and it felt like shit.
 
I meant THAT this could not be ported to OpenCL or any open format is a shame.
 
I have an nVidia card and will buy this title day one. I do feel it's bullshit that AMD users are not supported with half of the visual goodies. Physx was more than "Flying paper!" as one dude stated. It actually added to the game with Scarecrow with the explosions and bricks and steam, then there was also his cape that didnt simply drape over his frame, it moved lifelike. The effects weren't overdone, they made the game look and play great.
Than this could not be ported to OpenCL is a shame.

physx didn't add much to the game, but replaying it without makes it visually a bit more stale.
 
Everything I looked at a year ago when I had a nearly complete save said it was impossible. Sadly I don't have that save anymore.
Even though my save was a completed game, I still raged about it before I figured out how to get it to work. One reason why I still do not like GFWL. I hate it more on Steam games. Although on Fallout New Vegas on Steam it doesn't run GFWL, unlike basically every other GFWL game that I have like DoW2.
 
Even though my save was a completed game, I still raged about it before I figured out how to get it to work. One reason why I still do not like GFWL. I hate it more on Steam games. Although on Fallout New Vegas on Steam it doesn't run GFWL, unlike basically every other GFWL game that I have like DoW2.

Fallout: New Vegas is a Steamworks title not a GFWL one.
 
the game does play WAY better with a mouse a keyboard.

I was really impressed with the controls.
This is one of the examples of a controller game done right, in my experience. I adored playing it with my logitech controller, which looks like a PS3 controller. I imagine it'd be trash on an xbox controller but that's because I really dislike the xbox controller itself :D
 
So I'm going to miss out on the migraine it will induce?

Fortunately for me 3D doesn't cause me any physical issues. But even not counting 3D Batman AA on my sig rig blows away the 360. Saying that it doesn't look and play significantly better on the PC is just wrong, though the PC needed to make the difference isn't average.
 
AMD has its special AA which is "vendor locked", but whinge and moan when the other team do similar things. It really really annoys me that they sit around doing absolutely nothing and then when anyone else (intel/nvidia) supports developers and helps them produce games/tech and makes something good happen AMD sits and waves its underdog card and cries and pisses and moans because it was too lazy to do anything.

What the hell are you talking about? Driver code is *extremely* different from game code. Nvidia can do whatever they want to AA in their drivers, add all the extra features they want, that's awesome. The batman thing was a vendor ID locked *GAME CODE* change that was otherwise standard DX code. AMD has, to the best of my knowledge, *NEVER* done anything similar.

Also, citation for "too lazy to do anything". AMD has a developer relations program. They *DO* talk to developers. The *DO* work with developers. They may not make it into a giant PR show like Nvidia, and their program may not be as large, but what you are spewing out is nothing but pure FUD.

It's a buisness. Not a gentlemens club. Anyway AMD was offered CUDA (and still is) but they turned it down for whatever reason. Even though things like tesselation were adopted by everyone.
In other words, I like their technical stuff but I hate their business stuff.

Did you even bother to read what I said? I told you exactly why they wouldn't want to support CUDA, and why consumers are better off because of it. Tessellation was developed by AMD, Nvidia, Intel, and Microsoft (among others) jointly. It does not unfairly benefit any particular vendor or chip architecture.

Youd prefer openCL, which is controlled/owned by Apple inc.?

Nope. I prefer the Open CL that is controlled/owned by the Khronos Group of which AMD, Nvidia, Intel, Apple, ARM, and TI are members (to name a few). OpenCL stopped being an Apple controlled API 3 years ago, but who cares about facts, amirite?

Neither OpenCL (royalty free) nor Physx (royalty free) nor Havok (propriety) are open source. But all with the exception of havok are free to use.

I never brought open source into this. I don't particularly care which one is open source, that is irrelevant to the discussion at hand.

Multiple threading is down to the developer. If they have coded it in a way that it doesn't use multiple threads, it wont do so.

Not so simple. I've toyed with PhysX. Nvidia's own multithreaded demos *do not benefit from multiple threads*. While multiple threads are created, they do not help. In fact, they site almost completely idle while the main thread grinds to a halt. PhysX absolutely *sucks* at using multiple threads out of the box. Is it possible to get it to work well with multiple threads? Perhaps. But when the multithreaded samples, demos, and documentation fail to utilize multiple threads, it's disingenuous to blame game devs at that point.

x87 and SSE are just different ways of doing things.

True, but irrelevant. x87 is outdated and slow, which is the point. It is not just "different", one is clearly superior - and it isn't being used by PhysX.

Just because something is compiled in SSE and not x87 does not mean it will suddenly be 300x faster and should you so wish you can compile CUDA in SSE (but this might cause calculation errors). But since SDK 3.0 it has compiled in SSE by default, and offered automatic multithreading support, removed lots of the old ageia code and was released 3 months ago. So should be ancient history by now :p

Compiling in SSE != leveraging SSE to it's fullest. The compiler does a crappy job of leveraging SSE. Whether or not Nvidia has actually enabled the vectorization path for SSE yet or not, I do not know. But simply compiling to use SSE over x87 is still not using the SIMD part of SSE (which is the whole point of SSE).

But that article pretty much repeats what I said. CPU PhysX as delivered by Ageia and currently used by most games sucked, and Nvidia is/was busy re-doing it.

Although now it sounds like I need to go play with PhysX 3.0, to see if they've fixed their multithreading problems.
 
Fallout: New Vegas is a Steamworks title not a GFWL one.
I know, but the box says Games For Windows on it, so I thought that it was GFWL like Fallout 3 was, but when it didn't use it, I didn't think about it.

I got the Collector's Edition for $30 at Gamestop a few weeks ago and just registered it on Steam, which I wanted to do anyway, but it was still $50 for the regular version on Steam.
 
What the hell are you talking about? Driver code is *extremely* different from game code. Nvidia can do whatever they want to AA in their drivers, add all the extra features they want, that's awesome. The batman thing was a vendor ID locked *GAME CODE* change that was otherwise standard DX code. AMD has, to the best of my knowledge, *NEVER* done anything similar.

Also, citation for "too lazy to do anything". AMD has a developer relations program. They *DO* talk to developers. The *DO* work with developers. They may not make it into a giant PR show like Nvidia, and their program may not be as large, but what you are spewing out is nothing but pure FUD.
This article, posted by someone arguing the same position as you earlier in this thread, http://www.hexus.net/content/item.php?item=20991 explains that NVIDIA's senior technical marketing manager of EMEA, Lars Weinand, claims AMD could have but didn't participate. AMD's senior manager of developer relations, Richard Huddy, said this in response, "
It’s also worth noting here that AMD have made efforts both pre-release and post-release to allow Eidos to enable the in-game antialiasing code - there was no refusal on AMD’s part to enable in game AA IP in a timely manner.

Now I don't expect the PR guy at AMD to know that UE3 doesn't actually have in-game AA, but I do expect people on this site to know the difference between what he's saying and what actually happened. This is your source. From hexus.net, from AMD's PR executive, and it doesn't even say what you think it does.

AMD certainly does the same thing. Every time you see an AMD badge on a software product you know it's been tuned to AMD hardware. In fact, why aren't they making their catalyst drivers available for my 460? I want to use some AMD features on my card but they're unfairly locking me out from Crossfire.
 
Now I don't expect the PR guy at AMD to know that UE3 doesn't actually have in-game AA, but I do expect people on this site to know the difference between what he's saying and what actually happened. This is your source. From hexus.net, from AMD's PR executive, and it doesn't even say what you think it does.

The one misunderstanding here is you. Batman *DOES* have in-game AA. Just because it is UE3 engine does not prevent in game AA. In fact, the GOTY edition removed the vendor ID lock from the game code, and surprise surprise the AA path worked fine on AMD cards.

Again, to be perfectly, 100% clear. Batman has an *IN GAME* AA setting that was implemented using *STANDARD DIRECTX* but was guarded by a vendor ID lock. You seem to think that UE3 == no in game AA, which is not true. Many UE3 games don't have in game AA, true, but Batman was not one of them. We are talking completely about GAME code here, *nothing* to do with driver features.

But here, maybe some screenshots will finally get you to understand what we are talking about:

http://www.hardocp.com/image.html?image=MTI1NTg4NjU5MDdkSGZvS05ZZ21fM18xX2wuanBn (taken from http://www.hardocp.com/article/2009/10/19/batman_arkham_asylum_physx_gameplay_review/3 )

Notice the 4th setting there? You know, the one labeled "MULTI SAMPLE ANTI-ALIASING"?

People actually went so far as to spoof the vendor ID of AMD cards to that of Nvidia and benchmarked the CCC setting vs. the in game setting. Surprise surprise, the ingame setting resulted in better performance: http://forums.anandtech.com/showthread.php?t=2096214
 
I understand what you are talking about clearly enough. It's not my lack of understanding that is the issue here. The reality is that the only reason AA is available in Batman is because nVidia put it there. They can put it in their drivers or the game or on a dongle and no matter what else is true, AMD and AMD's customers' opinions about it are noise to me. I'm glad that AMD finally got around to getting in-game AA working for its customers. It's not as if nVidia doesn't want you to have it and certainly not is customers. I don't regularly ask people what kind of video card they have unless they are expressing a need for support.



If they had made it available for everyone to use regardless of platform, who would be liable if something went wrong with an AMD card?

BTW, I followed one of your links but I read the discussion rather than just skimming google links and picking things that seem to buttress my argument. I don't know if that's what you did, but it seems like it when you post a link and it completely obliterates your own argument...

this goes into history of AMD's similar behavior when it came to DX 10.1 and their code in Assasin's Creed. Unlike Batman, AMD's code in AC actually produced a detrimental gaming experience to nVidia players--missing particles, light bleeding, and performance degradation.
http://www.brightsideofnews.com/new...-nvidia-vs-eidos-fight-analyzed.aspx?pageid=3

and look at what it quotes:
http://hardocp.com/article/2009/11/03/resident_evil_5_gameplay_performance_iq/10
read the synopses about AMD and its shoddy development for an otherwise impressive product
 
There are lots of rabid fanbois online, but I swear I believe team red takes the cake.

Buy a nvidia card or stfu about how far they go to make their cards superior, or be happy fapping over benchmarks with your AMD cards.

Nvidia always has an advantage there, and yet it only matters when a AAA title you want to play comes out.
 
I understand what you are talking about clearly enough. It's not my lack of understanding that is the issue here. The reality is that the only reason AA is available in Batman is because nVidia put it there. They can put it in their drivers or the game or on a dongle and no matter what else is true, AMD and AMD's customers' opinions about it are noise to me. I'm glad that AMD finally got around to getting in-game AA working for its customers. It's not as if nVidia doesn't want you to have it and certainly not is customers. I don't regularly ask people what kind of video card they have unless they are expressing a need for support.

Dude, wtf? AMD didn't have to do anything to support it. The code that was shipped in game worked just fine with AMD's. Nvidia provided standard directx code to a game developer that included a vendor id lock. Again, game code is *extremely* different from driver code. If this would have only been a driver feature, then there would be no problem.

If they had made it available for everyone to use regardless of platform, who would be liable if something went wrong with an AMD card?

If direct x game code breaks your AMD card, it's AMD's fucking fault. There is *zero* ambiguity as to whose fault that would be.

BTW, I followed one of your links but I read the discussion rather than just skimming google links and picking things that seem to buttress my argument. I don't know if that's what you did, but it seems like it when you post a link and it completely obliterates your own argument...

this goes into history of AMD's similar behavior when it came to DX 10.1 and their code in Assasin's Creed. Unlike Batman, AMD's code in AC actually produced a detrimental gaming experience to nVidia players--missing particles, light bleeding, and performance degradation.
http://www.brightsideofnews.com/new...-nvidia-vs-eidos-fight-analyzed.aspx?pageid=3

Really? Did you try reading the article (that I didn't link, but whatever)?

There are only two conclusions you can make. The First one is the subject of this analysis, Batmangate. After carefully reviewing statements released by all sides, talking to developers, there isn't much left. Forum members on Batman: Arkham Asylum Forums and AMD themselves all changed the vendor ID on their cards and got equal functionality as the one experienced on nVidia cards. This happened at the time when nVidia members both claimed that Batman AA code is proprietary to Eidos and that no vendor ID locks is implemented in the code. "Hands in a cookie jar" is the only parallel we can draw here.

and look at what it quotes:
http://hardocp.com/article/2009/11/03/resident_evil_5_gameplay_performance_iq/10
read the synopses about AMD and its shoddy development for an otherwise impressive product

What does this have to do with the discussion at hand? There were driver bugs, they got fixed.
 
Your position that it was so simple and obvious is undermined by the twin facts that AMD didn't provide its own solution for Batman nor for any other UE3 title.

The articles being bandied about are very clear that AMD wrote to Eidos asking them to alter the code nVidia had developed to allow their cards to use it. Eidos said they were legally obligated to leave the code alone but that AMD could provide their own code.

I'm not sure how you get from those set of facts to being irate toward nVidia. Not that it matters since nVidia doesn't care about your opinion since you're an AMD customer and I care less then nVidia does.
 
Be more interested if it came with OpenCL support instead of PhysX.

Nice to know that Rocksteady is still okay with screwing AMD card-users over.

Well you wanna cheap out and buy a second rate card to save a few bucks the play with the hand you're dealt. my cheap ass samsung phone don't support no iphone apps. ya hear me complain? no! so boo fuckin hoo to you. maybe next time you'll buy nvidia who spend the cash to work with game developers or whatever shady backroom deals they have going works for iphones. end of the day they have the superior hardware/drivers/support therefore they're the best. you should've factored more than fps vs $ when buying your graphics card. you've only yourself to blame.
 
You shouldn't be asking game developers why nothing runs on ATi hardware you should be asking AMD why they're not getting game developers on-board supporting their hardware. you expect these companies to spend money coding their games to support ATi's proprietary features when nVidia would be paying/supplying hardware to exclusively support their features to give them the edge in the market? if AMD isn't aggressive enough in this integral part of being a graphics card producer that's their own fault. they should realise that without software hardware is totally useless, so many electronic device manufacturers fail for this very reason. look at betamax superior format but it died cas they refused to licence porn. start realising its a fault with the overall ATi product not you being victimized by game developers.
 
You shouldn't be asking game developers why nothing runs on ATi hardware you should be asking AMD why they're not getting game developers on-board supporting their hardware. you expect these companies to spend money coding their games to support ATi's proprietary features when nVidia would be paying/supplying hardware to exclusively support their features to give them the edge in the market? if AMD isn't aggressive enough in this integral part of being a graphics card producer that's their own fault. they should realise that without software hardware is totally useless, so many electronic device manufacturers fail for this very reason. look at betamax superior format but it died cas they refused to licence porn. start realising its a fault with the overall ATi product not you being victimized by game developers.
Payola supports developers, in a way, but it's bad for gaming as a whole. I think it would be better for gamers if developers would figure things out on their own rather than accept millions from a single graphics card manufacturer to cripple it on their competitor's devices.

If a developer refuses to make sure a game runs right on half their customer's machines just because one card maker didn't dump a bunch of cash in their laps, they are just shitty developers.
 
Fortunately for me 3D doesn't cause me any physical issues. But even not counting 3D Batman AA on my sig rig blows away the 360. Saying that it doesn't look and play significantly better on the PC is just wrong, though the PC needed to make the difference isn't average.

Oh it definitely looks better than the console versions, but for some reason they don't make an initial collectors release for the PC, you had to wait around for the GOTY edition (no Batarang version for us), consoles get an awesome collectors box set, and then the GOTY edition, I'll get the PS3 version for the limited collector set, and then spring on the STEAM sale when the GOTY is about, and hopefully bundled with AA.
 
Extra details ... ya just like Physx, and the first game, with the flowing cape, fog, and papers .... I'm not getting my hopes up.
 
Back
Top