GTAIV: PS3 version runs at 630p while 360 version at 720p


Recommended Posts

indeed, you gotta be pretty shallow to not buy a game for qualities other than its graphics, however this appears to be some guy who reckons its running at X res

I'm pretty sure we tried mentioning this when people tried to mutiny Bungie over it, but nobody listened then...

-Spenser

here is what its running at

PS3: 630p with 2xAA at FP16 Lighting

X360: 720p with 2xAA with FP10 Lighting

PS3 has a more softer image because it is being upscaled to 720p While you see more jaggies on the 360 version because it is being rendered natively at 720p.

I've also heard that the 360 version suffers from very minor framerate problems every now and then, so I guess that is why. I would rather the game run at ever so slightly less than HD quality, if need be, in order for the game to run at a silky-smooth framerate. Halo 3 was a beautiful game (obviously not the *greatest* graphically, but it was nonetheless pretty), and so is GTAIV, regardless of resolution.

I'm still getting the 360 version simply because I don't have a PS3.

I don't have a problem with it, but I've always felt it's lame that they can still stick "720p" "1080p" on the back of the box. Halo 3 did that. Upscaling does not equal HD at all.

Well if you want to get technical (and Bungie has mentioned this on their story about it), they render two buffers both at 640p, so you get 1280 rendered pixels and so they can easily put 720p on the back and not be twisting the truth.

(Info on that is here: http://nikon.bungie.org/bwu/index.html?item=147)

-Spenser

Seriously, who cares what they did to get it to look how it looks as long as it looks nice.

I mean, yeah its pretty cool to know the technical details, but if you think that this info makes one version superior/inferior that the other then ....

You can tell from the pixel. I know from my experience after having seen lots of pixels in my time.... Seriously though, I'm getting the 360 version and I don't care what resolution either is at... It's all about the gameplay for me

I've also heard that the 360 version suffers from very minor framerate problems every now and then, so I guess that is why. I would rather the game run at ever so slightly less than HD quality, if need be, in order for the game to run at a silky-smooth framerate. Halo 3 was a beautiful game (obviously not the *greatest* graphically, but it was nonetheless pretty), and so is GTAIV, regardless of resolution.

I'm still getting the 360 version simply because I don't have a PS3.

I've heard the opposite, I've heard that the 360 keeps it's framerate much better than the PS3 version does.

Source: http://kotaku.com/384422/which-version-of-...nd-360-versions

The Grand Theft Auto series has never been synonymous with a rock solid frame rate, something it generally seems to get a pass for. While GTA IV is smoother in general than it's predecessors, it can expectedly suffer during chaos. The Xbox 360 version seemed capable of achieving a smoother frame rate, peaking higher in certain circumstances, such as in confined spaces or during light traffic, but both versions seemed to regularly run at a similar clip.

So it's a tradeoff, smoother frames or smoother frame rate.

If the above theory of the PS3 being upscaled to 720p makes it look smoother, then surely anyone playing at 1080p wont notice any jaggies?

All the review quotes on each version on the technical side of things can be read here - http://www.neogaf.com/forum/showthread.php?t=286527

PS3:

wmplayer200804272348001sz1.png

360

243oopw.jpg

How do people tell what resolutions the games actually run at? :/ Some sort of software/hardware? Surely they don't zoom in and "count the pixels" ? :blink:

90 pixels... big deal, didnt notice it with halo, doubt i will notice it with GTA.

How do people tell what resolutions the games actually run at? :/ Some sort of software/hardware? Surely they don't zoom in and "count the pixels" ? :blink:

Yep, think thats exactly how its done... lol, sad really

How do people tell what resolutions the games actually run at? :/ Some sort of software/hardware? Surely they don't zoom in and "count the pixels" ? :blink:

That guy over at 3dGaming forum says that he is a developer and can figure out all that data including quantity and type of AA, HDR, etc just by looking at good picture of each version of the game running..., yes.... who would trust this guy right??? well, he appears to have quite the credibility over at those forums and after all he was the one that calculated the pixels on Halo 3...

90 pixels... big deal, didnt notice it with halo, doubt i will notice it with GTA.

Yep, think thats exactly how its done... lol, sad really

No, that's not how it's done. You would be lucky to come out with such an even number as 630 by counting by hand. It probably has something to do with using a capture card to feed an image into your computer straight from the game and having a program count the pixels for you.

Actually I take that back. Halo 3 was found out first using this method (which is far easier than counting 640 pixels):

Halo3nativereso.jpg

Easy math there (I guess what you're looking at is part of the sniper rifle).

-Spenser

No, that's not how it's done. You would be lucky to come out with such an even number as 630 by counting by hand. It probably has something to do with using a capture card to feed an image into your computer straight from the game and having a program count the pixels for you.

-Spenser

What? If the ps3/360 was outputting those pixels you wouldn't even need a program to "count" since the resolution information would already be in the "stream".

Anyway, the ps3 and the 360 will output 720, 1080, etc IN SPITE of the resolution the game is actually being rendered at. If there is an option to make the ps3 output at non-standard resolutions so as to "count" the pixels, let me know!

The games are just upscaled, when the rendering resolution is lower than 720. Knowing how the "upscaling" algorithms work should be enough to detect the actual rendering resolution if it's too obvious. Edit: Just seen that picture with the steps. Proves me point, as those steps are the result of a rather 'simple' upscaling technique.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Are you going to do performance benchmarks comparing all states? I'd be interested in seeing that in the next "part".
    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
  • Recent Achievements

    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!