Ridge Racer 7 vs Ridge Racer 6 Exact Screenshot Comparison

joemutt - 1145 days 16 hours ago

Is it the hardware?
Is it the developers?
Is it a fake?

What type of ammo will the fanboys use?

Agree(1) | Disagree(0) | Report

4me2 - 1145 days 14 hours ago

"Thanks Microsoft"

You're welcome.

Agree(0) | Disagree(0) | Report

power of Green - 1145 days 14 hours ago

How many games does it take! lol, it's the third game this month not counting this one although it might be fake. Dev's are coming out of the closet telling the world the truth. You know Devs will probly add extra effects and detail with ports, they have that choice with the 360.

Agree(1) | Disagree(3) | Report

Jenzo - 1145 days 2 hours ago

COD 3 in 60 fps with rumble, or in 30 fps without rumble? Hard choice if you're a retard.

Agree(2) | Disagree(2) | Report

kmis87 - 1145 days 14 hours ago

Since when does the ps3 have less memory available for the gpu? Last time I checked they both had 512MB.

And could you give me a link to where a dev actually says that Gears can't be made to run on a ps3 (don't give me the one where the blogger takes the quote from a dev about how it can't run on a 256MB machine and sticks it in after he poses the question to imply that a dev actually said that, when in reality the interview with the dev had nothing to do with ps3).

Agree(4) | Disagree(1) | Report

Watapata - 1145 days 1 hour ago

Additionally, PS3 games seem to have far more onscreen at one time than 360 games as a general rule...

Agree(0) | Disagree(1) | Report

zypher - 1145 days 12 hours ago

"And Motorstorm is a joke"

i think you're the first person that's said that. weird. even the most diehard 360 fanboys concede that Motorstorm looks gorgeous and cool. its also weird that you refer to Resistance and it's "muddy and dull" graphics, but say nothing about the fact that at least one site's review crew gave it a higher score than both COD 2 and COD 3, and only 1/3 of a point lower than the 360 golden-child GOW. sure, Resistance is about the only worth-while game in the PS3's launch lineup, but what system has ever launched with many worth-while games? initial PS3 games may not look $200 better than 360 games, but they are hardly sub-360 in quality, as this comparison tries to imply.

Agree(3) | Disagree(2) | Report

kmis87 - 1145 days 12 hours ago

You're a moron if you believe that the devs can't access all the RAM. Your claims are about as dumb as if I was to say that the 360's cpu can't access its RAM because it isn't directly connected to it, and that this necessarily means the 360 will have worse physics, ai, particle effects,etc. And the 360 can't exactly use 512MB of RAM for textures either, there are other things that use system RAM.
I'd also appreciate a link, just one, where a developer makes the claims that the ps3 gpu can't use the RAM, or that Gears couldn't be made to run on a ps3. Since there are apparently 10 of them that wouldn't be asking much.

Agree(1) | Disagree(2) | Report

Karibu - 1145 days 11 hours ago

And you're funny Topgamer.
You know very well why PS3 doesn't use 512 ram for graphics... and neither X360. Cpu need some too.
You say RSX can use only 256 textures and the games look almost the same?? What? Does PS3 have something magical texture ram in it??
Or are you saying RSX is more powerfull that graphics card in X360??
Oh yeah, there's still that 60fps1080p difference...
Why you and other Xbots need to compare whole time GOW to PS3 titles?? Whole year and thats what you got? One boring game, with detailed characters. Sure, let's make Recistance also 4 vs. 4 game. Oh my god how much better than GOW it would look. Or lets put only 4 cars in Motorstorm and take away terrain formation, physics and sh1t.

Agree(2) | Disagree(3) | Report

Karibu - 1145 days 11 hours ago

my left testicle that you didn't understand a word you just copy pasted.

Agree(2) | Disagree(2) | Report

kmis87 - 1145 days 10 hours ago

Could you please give a link that isn't from a Microsoft employee? Also, could you give the links that I asked for, not this other link.

"In this interview, Matt Lee attempts to present a more technical look into the PS3 compared to Xbox360. He is definitely on the development side to things so I assume he holds enough completely knowledge of computer hardware and what hardware means to software. He’s written DopeWars, worked on an MMO for PC called Mythica, and straight from there moved to the Game Technology Group in Microsoft where he now advises other developers on how to write efficient code for Xbox360.

Matt was asked at some point during the interview to explain the Xbox360 architecture. I have already familiarized you with the Xbox360 architecture but you should compare it to his. In this section he made note about AltiVec(VMX-12 instruction set because he was asked to explain it. Matt answered and mentioned some of the additions to the VMX-128 instruction set which were either specific to Direct3D. He also said that the best way to multithread a game has not been decided yet.

When asked about if the Xbox360 hardware had anything to help accelerate physics, Matt pointed out the VMX-128 instruction first, then fell back to the symmetrical cores, 6 hardware threads to spread out the code, unified memory architecture, and even goes further to say the GPU could be used to accelerate physics because it is a math monster and architected reasonably well to handle general purpose calculations.

After saying this about his hardware, he had more to say about the PS3 when asked about it:
When asked about the Cell architecture he specifically says the Cell isn’t designed for gaming as much as Sony would have us believe and immediately focuses on the SPEs. He attacks it for not having branch prediction – which is true, but when you look at the stream/SIMD/vector processing paradigm, branches are rare. Whenever it can’t be avoided, the SPEs have minimal hardware to allow software hints to avoid the penalties of doing so. It seems to me that IBM/Sony/Toshiba went out on a limb to make sure the SPEs did what they needed while avoiding things that cause performance hits.

He also says that the SPEs are poorly suited to run most game code – wait a second, define “most game code” for us Matt. On the screen, general-purpose code takes up the most volume and even takes up the most space in memory. But in execution time, most game code isn’t general purpose and branch heavy.

Additionally, the 8 operational cores of the Cell, with 2 threads on one core provides for more thread space for parallelizing games. But I guess he forgot to give Playstation 3 the same consideration after mentioning the space to spread code across 3 cores.

He then says(in typical MS fashion) a line similar to “it can only do this” and points out that the SPEs are only good for serialized streaming math code that digital signal processors typically do. He may be right in what it is good for, but he is wrong if he thinks it is the only thing they are good for. Use your own judgment on what the SPEs are good for by understanding what they do, and understanding the things developers have processors do to solve them.

His next attack goes at the memory architecture (local store) of the SPEs and he says the lack of automatic cache coherency (traditional cache behavior) seems as if it would cause a lot of overhead to work with, having to copy results to system memory through DMA transactions. The problem with this statement is that he is restricting the operational nature of the SPEs to writing results of computations to system memory. This is far from the truth as it isn’t by any means a necessary action SPEs have to take and is less than optimal in many situations as all 7 SPEs and PPEs would be sharing 25.6GB/s bandwidth. An approach that works far better is using the most out of the element to element communication bandwidth on the EIB, and only accessing system memory when necessary. SPEs are also likely to output data to other input/output devices such as the graphics card, sound hardware, or to other elements to use in a typical game scenario. Writing out to system memory for communication and processing game data is merely the easiest approach in developer’s eyes as it changes the information passing approach to information sharing which is automatic. The fact of the matter is that the SPE local storage has the speed of a traditional cache, but requires manual control. This makes it harder to use, but allows the execution speed to be deterministic and constant and could possibly even exceed the efficiency of a traditional cache if it used that way purely. Assuming there is no need for this level of control, developers can fall back to letting compiler or middleware tools handle the SPE local storage for them.

Matt then moves focus to the PPE and says that the Cell lacks the VMX-128 enhancements. That is true, but why does he isolate that part of the Cell and ignore over 40% of the Cell’s die space? Considering the SPE instruction set is dedicated to vector processing, and is considered a superset of the functionality provided in VMX, the SPEs could be called a VMX enhancement too. It just breaks compatibility and goes down it’s own path for accomplishing the goals. The difference is like apples and oranges - except there are 7 SPEs, and 3 VMX-128 enhanced units.

He also quickly mentions that the single PPE in the Cell has half of the cache size, but fails to mention that Xbox360 is splitting this cache with 3 cores that do not have explicit control over the cache coherency. If the Xbox360 cores were actually running independent threads working on independent data, the behavior of the cache would be very unstable and each core would need to take an piece of the pie – dividing the cache size by 3. The Cell’s PPE is the only consumer of it L2 cache unless access is granted through the PPE’s execution. Additionally, each SPE has its own cache speed memory. I’m failing to see how on chip memory is actually a limitation for the Cell, but not for the XBox360. I guess the Xbox360 advantage needs to be qualified as 512kb of extra automatic cache. Whatever that means next to the extra 1280kb of total on-chip memory in the Cell is up to the developer’s ability to put it to good use.

He also says that all of the “work” has to be crammed onto the PPE in addition to the base PS3 functionality that will be available anywhere. The only “work” that has to crammed on the PPE is the work developers feel is better suited to run there rather than the SPEs. Rendering commands by far don’t have to come from the PPE as any core inside the Cell has equal access to other elements inside the Cell and out. Sending rendering commands is equivalent to any communication with the FlexIO bus. Additionally, he doesn’t know where the system level functionality were the console is placed, and the last official indication of this is that an SPE is used for that purpose.

Matt moves on and states that porting will be difficult (which is true – conversion from SIMD to general purpose and reverse and reconsidering how to use the bandwidth efficiently on both platforms). He says this in a manner which strongly implies that general purpose processing is what is needed and is more easily relocated inside the Xenon. I find it rather difficult to even concoct a reasonable scenario where relocating code between cores(keeping same thread pairings) provides any significant performance difference. Granted in the Cell, code may not be easily movable between an SPE and PPE, does it actually matter?

One of the ugliest pieces of information Matt shares is related to the RSX. He was very direct in mentioning that the audience that actually cared about the 512MBs of shared memory was the developers, and it is important to note that this is the only audience that would care for this since it is as a matter of developer ease, and not performance gains. What he said that was completely wrong was the “you'll never see a PS3 title with more than 256MB of textures at any given time, due to the split graphics and system memory banks” comment. Perhaps he was thinking of the PC world where the bandwidth between system RAM and CPU and video RAM and GPU is in the single digit GB/s order of magnitude. Thus textures in system memory will make a game drag if they are accessed frame by frame. Unlike a PC, the Cell and RSX are able to communicate with 35GB/s bandwidth, and the Cell has 25.6GB/s bandwidth to its XDR RAM. This translates to 25.6GB/s bandwidth between the RSX and system memory. More importantly, this extra bandwidth is coming from a separate bus than video memory meaning that developers might actually want to do this intentionally to increase total bandwidth to the RSX. Rest assured, Matt and Microsoft’s insight is that developers will never want to have split memory banks because it’s just that much easier to share bandwidth and not have to consider the difference. I firmly believe in the causes of developer ease, but I also believe that when making a console to appeal to gamers through performance, hardware comes first.

He finishes up his technical breakdown with his overall belief on the performance difference and calls it a “wash” due to theoretical peak performance numbers that Microsoft ran in the past. I think he is referring to that information in the previously mentioned IGN article which is rather skewed. When you compare theoretical peak processing performances, the Xbox360 is actually twice outdone in floating point operations and many other mathematical operations. I think he means to say that practical performance might be a wash if he anticipates developers will not take advantage of the Playstation 3’s power.

Of course, Matt does make sure he states that Microsoft’s development tools a years ahead of the competition. This scale is in terms of ease of use as power in a development tool is hard to quantify and isn’t ultimately responsible for the quality of the code that comes out. Technically C# is 20 years ahead of C++ and 30 years ahead of C, but that doesn’t prevent C/C++ from doing all of the same things and possibly even more that their successors."

http://ps3forums.com/showth...
I can copy and paste too, btw. Specifically read that paragraph about having more than 256MB of textures at once.

Agree(5) | Disagree(3) | Report

Watapata - 1144 days 23 hours ago

TopGamer, whether with this sceenname or another, you have never once posted what you refer to as "facts" backed up by a single unbiased source, as fanboys(you included) on either side would want to put it. Every time someone that works for, or with, Sony has said something good about the PS3 you and others have jumped all over it saying its inherently biased, but then go and use Microsoft sponsored articles or interviews with Microsoft as an uniased source. Simply put this is hypocritical, and additionally the world does quite work that way. In reality next to no one on this site, and next to no one in the gaming community (note I'm not referring to the industry, but the community) understands tech specs at all, and yet they rant and rave on a daily basis as if they do, when it is ENTIRELY easy for any hardware company to manipulate what is presented to show what they want. I can assure you Microsoft has done this every time, just as I can assure you Sony has done the same. Likely each to similar degrees. Additionally, any developer is going to support what they prefer to work on and claim that is best, so listening to the dev's isn't necessarilly any better. Look at it this way, it'd be comercial suicide to "insult" the platform you are working on...I'd say its fairly evenly split as to dev's praising one console over the other, with the exception of online capabilities. Also, assuming the 360 OS takes up an equal ammount of RAM or more compared with that for the PS3, the PS3, as kmis87 pointed out is actually better of than the 360 when it comes to RAM because the RSX can access its dedicated 256 just as fast as the 360 GPU can, while accessing the Cell's dedicated 256 at a higher bandwidth. Sony has never stated, and neither has any dev I might add, that a special workaround is needed. This has just been assumed, but considering that Sony explicitly stated from the beginning that this sort of communication was their goal, from a hardware perspective it doesn't make any sense to think that its at all complicated, or non optimal. In fact, its better from a performance point of view to have it organized this way than for the CPU to constantly have to route its data through the GPU whether to read or write from the RAM. When its all said and done though, none of this matters and ammounts to nothing more than posturing by people looking to validate a several hundred dollar purchase they made (this applies to both sides). Why don't you stop with your holier than thou attidue towards anyone that happens to be supporting the PS3 and accept that people will enjoy their PS3 when they get one. That applies conversely to anyone trying to imply that its impossible to enjoy playing the 360 as well.

Agree(0) | Disagree(0) | Report

nambo - 1144 days 22 hours ago

I'm not sure where this guy get's his info, but he sounds pretty informed.

He states that "When you speak to developers privately, they express a stunning level of frustration. Repeated delays in the delivery of online APIs, delays in coming-up with online testing kit, incomplete or missing libraries, promised features that are never delivered. The list goes on and on. They have to deal with the bloat of the OS, which eats up nearly 100 MB of memory (and one SPU), and provides very little functionality to the game. In comparison, the OS for the Xbox is rumored to only use up 3.5 MB." That only leaves 412MB for games, and if it's true that 64MB's are dedicated to the browser then that's 164MB's! Around 32% of the PS3's memory going to non-gaming functions.
Again, don't know if this is true, but it's an interesting read.
http://www.innerbits.com/bl...

Agree(0) | Disagree(0) | Report

xbox360migs - 1144 days 22 hours ago

Have you ever worked on programming for the PS3 or the 360? You seem to be well advised and I am just curious.

Agree(0) | Disagree(0) | Report

Watapata - 1144 days 17 hours ago

nambo, if I'm not mistaken, the 64 MB used is the only thing reserved while a game is in use, its not specifically for the browser, its for the operating system and is used primarily by the browser when not in a game.

Agree(0) | Disagree(0) | Report

BadTaste - 1145 days ago

How old are you 10? and yes you are Achira.

Agree(2) | Disagree(0) | Report

Jenzo - 1144 days 20 hours ago

In denial...Even if Ken Kutaragi told you that the PS3 has worse graphics than the 360 you would'nt believe him. You'd probably kill him and go: "He was a clone! He was fake!?", until you believed it.

Agree(0) | Disagree(0) | Report

bung tickler - 1144 days 23 hours ago

while your comment might be a nice one, please dont type in all caps. PLEASE!

Agree(0) | Disagree(0) | Report

Ugly American - 1144 days 21 hours ago

I hate to be the one to break it to you, but as of right now, the 360 has better graphics. That may change this Friday, but wake up and smell the chainsaw exhaust.

Agree(1) | Disagree(0) | Report

Deceased - 1144 days 22 hours ago

Actually in your link the PS3 screen is at the bottom (top right hand corner of bottom pic screen says PS3), so Ride Racer 6 looks better than Ridge Racer 7. The 360 version has better lighting, water, textures, etc...

http://boardsus.playstation...

As you can see the 360 pic in the link above matches the more colorfule pic in the top of your link. PS3 got PWNED.

Agree(1) | Disagree(0) | Report

Watapata - 1144 days 17 hours ago

actually deceased, those are both pics of RR7 on PS3, one in 720p and one in 1080p as demonstrated on another article on this site...

http://www.news4gamers.com/...

Agree(0) | Disagree(0) | Report