Nvidia has stated that their translation of Ageia's physics engine to CUDA is almost complete. To showcase the capabilities of the new tech Nvidia ran a particle demonstration similar to Intel's Nehalem demo, at ten times the speed. "While Intel's Nehalem demo had 50,000-60,000 particles and ran at 15-20 fps (without a GPU), the particle demo on a GeForce 9800 card resulted in 300 fps. In the very likely event that Nvidia's next-gen parts (G100: GT100/200) will double their shader units, this number could top 600 fps, meaning that Nehalem at 2.53 GHz is lagging 20-40x behind 2006/2007/2008 high-end GPU hardware. However, you can't ignore the fact that Nehalem in fact can run physics."
and 2k10, 2k11, 2k12, 2k13, 2k14, 2k15, 2k16, 2k17.
in 2018, the EA CEO will make an official communicate on how the pc market is saturated and in decline, and will stop the franchise. the modding community will happily mod the first one until 2m1. console users instead will stubbornly buy the new one each year until eternity, inflating console market usage and lolling about their platform superiority.
Super-soakers Online! Cloth and liquid simulations determine who got wet, how wet, and whether or not that means they're out!
Only if everybody else is using the same brand of physics accelerator, or if some physics API specification makes some guarantees about the output given the inputs. Otherwise, simulations run on multiple machines fall out of sync. A compromise solution is to use coarse particles for game logic and finer particles for iCandy.
Huh? The local physics computations are only being used for presentation and local extrapolation. The server recomputes the relevant physics anyway, and can re-sync everyone periodically. That's how FPSes work to reduce lag--they do local extrapolation, and the server periodically snaps everyone back in line. It sometimes leads to what John Carmack calls "paradoxes" where locally displayed events get undone, but it works.
So, if some portion of your local physics calculation is purely for local presentation (e.g. game outcome doesn't depend on exactly how dirt particles fly around or boobs bounce, but you want it to look realistic), the server doesn't need to reproduce any of that to model the game correctly. Your screen might look different than someone else's, but in an immaterial way. For the super-soaker example, the server will still compute actual "wetness," possibly with a simplified model that skips computing the goosebumps and most of the dripping water.
The local physics computations are only being used for presentation and local extrapolation. The server recomputes the relevant physics anyway, and can re-sync everyone periodically.
Using how much bandwidth per particle?
For the super-soaker example, the server will still compute actual "wetness," possibly with a simplified model that skips computing the goosebumps and most of the dripping water.
That's kind of what I meant by "use coarse particles for game logic and finer particles for iCandy."
To what extend does this contain real physics as opposed to "game" physics. Cuda maps to linear algebra fairly well but most phyics is second order (either algebraically or as differential equations). Are they actually trying to implement those or are they just making things that "look right" but really don't obey physics. I recall that in the original Toy Story there is only one place they used "real physics". When the jump rope is thrown off the balcony (for the army men to descend), they used real phys
I recall that in the original Toy Story there is only one place they used "real physics". When the jump rope is thrown off the balcony (for the army men to descend), they used real physics to model it's tangled fall. But thye later sent it was not a good idea to use the real physics. Not only was it harder but it didn't really look right and could not be easily tweaked. So all the rest is pretend physics.
What people perceive a situation to look like and how it would realistically look have drifted a lot. Due partially to the real life rarity of those situations and Hollywood/Video games distortion of it. We all expect shot guns to be massive overkill at medium to short ranges when in reality they don't hit that hard. We expect all explosions to involve flames. We expect bullets to hit with far more kinetic force then they do. We expect a whole lot of things that just don't happen in real life. It doesn't h
We expect bullets to hit with far more kinetic force then they do.
What are you talking about? I was just playing this game the other day where I shot a guy in the chest with my 9mm several times. He hardly moved when I shot him, and it took like 20 shots to finally take him down.
You obviously don't remember what it was like when 3D cards first came out. There were many games that were Glide only. Meaning that you had to have a 3DFX graphics card to run them. Back when sound cards first came out, this also happened. You had to have a sound blaster, or Adlib, or Gravis ultrasound, and again only certain cards would work with certain games, I imagine that physics cards could probably work in the same way. Require that you use a certain physics card, or you don't get to play the g
The best news about this is that it implies that if hardcore kit kills with it, then at least budget hardware (that many people have already!) can do it acceptably. That means finally seeing games that REQUIRE physics acceleration.
It'll be like 1996 all over again, only from a physics not graphics perspective. That, and there might be a new Duke Nukem game due out within the next 12 years.
So, physics should work on Linux, having been ported to CUDA already, and CUDA being cross-platform, but the question is if any Linux games will actually support and/or make use of it.
id seem to make all their games for Linux, and they also like using random accessories like that USB flak jacket thing that simulates you getting shot (by quickly puffing up pockets of air with pneumatic compressors). No doubt Quake 5 or whatever will support it at least.
Don't get me wrong, I am a HUGE fan of linux, I use it on all my computers. However, there is no point in releasing drivers for this in Linux because the only use would be physics accelerated games, which won't be ported to Linux anyway. Any program that would use accurate physics in Linux already uses the CPU to calculate it.
Don't get me wrong, I am a HUGE fan of linux, I use it on all my computers. However, there is no point in releasing drivers for this in Linux because the only use would be physics accelerated games, which won't be ported to Linux anyway.
The *only* use?? Geez, I'd like to get my hands on the API to write some physics educational/demonstration software. Or just create physically accurate simulations for kicks. We don't *have* to rely on others to write software for us.
Just because you don't currently have a use for this, doesn't mean nobody ever will.
That's okay - somebody else already posted the answer - this thing'll use an established mechanism (CUDA). I don't know what that is, but after this card hits the market, I'll probably start to find out.
Is a particle motion simulator a abnormally easy test case?
When I was getting up to speed on IBM Cell programming, IBM had a programmer's tutorial (excellently written, btw). The example problem they used for their chapter(s?) on code tuning were a particle simulator. It was a wonderful example problem, because it showed how to vectorize a program. But then when we went to vectorize our own algorithm, it didn't fit the Cell's vector programming instructions nearly as cleanly, so in the end we didn't get nearly the performance increase due to vector instructions as did the particle simulator.
So I'm thinking that just even though CUDA can do a good job with particle motion simulations, we shouldn't remotely assume that it's good for particular algorithms for which each of us is responsible.
Yes, particle systems are easy (in terms of physics), because they are essentially just moving points with varying velocities and accelerations... Such a simulation is easy to vectorize (eg: update the position of all points in parallel by performing lots of additions at the same time). Actually useful collision detection of say, convex volumes with rotational velocities, with the volumes being stored in a 3D space partition (eg: kd-tree or BSP tree) will likely prove significantly more difficult to parallel
That's exactly why I'm skeptical of CUDA in general. Rendering graphics is one of those "embarrassingly parallel" operations, where for every frame rendered, each triangle, vertex, and pixel is independent of the others. I don't know much about physics processing, but I'm guessing it's the same. Simply throwing say, 4x more hardware at the problem gives you pretty much the ideal 4x speedup. Once you introduce random data dependencies into the problem, though, parallelization is much harder and you don't get the same speedups.
There are a lot of easily-parallelizable problems out there, which is great...but then again, there are a lot of not-so-easily-parallelizable problems out there too. I don't think CUDA would do any better than a general-purpose CPU on the latter class of problems.
Anyone care to explain why there's such a big difference between a GPU and a CPU? I keep hearing how GPU's are this and that much faster than a CPU at calculations like graphics, physics and such, so naturally I assume there's a big difference that makes us still chose the x86 and x64 CPUs as the main processors of a PC. What are the limitations; why can't just the libraries be ported for GPUs instead of CPUs and why don't we then just run all calculations on a GPU, if they are anything from 2 to 50 times faster?
It just seems to me that if a graphics card can calculate physics then it would also be able to do pretty much all the same types of calculations that a regular CPU can do, but I am obviously missing a big part of it.
CPU's are general purpose processors that perform a lot of different functions. GPU's are highly specialized ASICs [wikipedia.org] designed to do one or two things very, very quickly.
CPU = Jack of all trades, master of none; GPU = the highly trained specialist.
Except that GPUs aren't highly specialised anymore; the latest generation of Nvidia cards are basically just a large number of general-purpose CPU cores.
Particle systems are about as perfectly a parallel problem as it's possible to get- and not only that, the calculations are generally very straightforward with few (if any) general CPU control structures (branches, loops, etc).
As a result, the massively parallel hardware on a GPU that exists to render many triangles/pixels/shader programs/etc at once can be exploited to calculate updates for many particles at once. The CPU is at an inherent disadvantage because it is only leveraging a small subset of it's full capabilities.
The CPU is very good at *lots* of different tasks. The GPU is phenomenally good at a very specific set of tasks. Physics just happens to fit within that set.
In its most basic definition, a GPU is just a CPU that's been highly specialized towards graphics. It can't do anything that a CPU can't also do, it just is able to do particular things much faster. Basically, they take a lot of the common tasks that graphics require of a processor, and they put really efficient ways to do it directly into the hardware, and they put a whole lot of them.
Think of a CPU as a big tool box. There's something in there for every task, including a screwdriver that can be used to put screws into things. Then next to it, you have a big cordless 18 volt drill (The GPU). Way easier to drive screws with that than the manual screwdriver in your toolbox. But when you need to drive a nail instead, yeah you could bash it in with your screw gun, but it's easier to go back to your toolbox and find a hammer.
I guess that would make a physics processor the nail gun. Or something...
A GPU excels at massively parallel tasks. Stuff like rendering, raytracing (yes! a GPU can raytrace!), DCTs,... essentially, a GPU is a stream processor that maps a function (a shader) on independent entities (pixels, or vertices). Applying a complex formula millions of times, each time with a different set of coefficients? -> GPU. GPUs fail at tasks where lots of synchronization or frequent branching is necessary. Stuff like game logic, for instance, or state machines. Your typical office application is
Simple reason: On my Mac Pro, I have 8 3GHz CPU's. Consider that the baseline.
I have 2 8800GT cards to drive the 30" and 2x23" (rotated, one each side of the 30":-) monitors. That gives me 224 1.5GHz stream processors in the GPU. Even harmonising GHz, thats 8 compared to 112, and its a lot easier to get a parallel algorithm running efficiently on a GPU than on multiple CPU's due to differing hardware designs...
Now stream processors aren't quite the same as general purpose processors, but the way they're imp
Wow, that has to be the worst car analogy I have ever read on Slasdot. Instead of comparing on specialization of hardware (minivan vs drag-racer might have been a winner), you went down some sort of bandwidth path. I don't even know what the "re-fuel", gas vs electric thing equates to.
They should test physics systems with spheres on irregular ground, with uneven (coefficient of kinetic friction), and changing wind.
I always liked to test on the hard cases (see my web site) but, in fact, what game developers and animators want is not realistic physics. The game people want "infinitely destructible environments", where you can blow up anything. And, of course, eye candy. The animation people want physics they can direct, where the starting and ending positions are specified but what happens in the middle might be automated. So most character motion in video games is spliced-together motion capture bits, hand animation, and a bit of physics now and then.
Most game physics engines today cheat on the hard cases, but by now, they usually cheat
in ways that don't do something blatantly nonphysical.
My original goal, back in 1996 when I was working on this, was to get to a two-person fighting game with real martial arts. The physics engine we had was good enough, although in the era of 200MHz CPUs, a bit slow. But
a control system that can do a judo throw against an uncooperative opponent is still out of reach. Worse, controlling a physically realistic martial arts character through a game pad is just hopeless. Play would be like a typical day at the dojo: "You lost your center. Your left foot should have been further forward when you tried that throw." "Yes, sensi". Work out three times a week for a year, and you get to be halfway decent. As a game, that sucks.
So I created the "ragdoll falling downstairs" cliche as a demo, licensed the technology to a middleware provider, and went on to other things.
Forgive my naivety, but is there such thing as netsted particles?
Full objects, made of "bound particles" (polygons that when constrained to eachother act as an object) but that whole object can be a particle?
Then if destroyed the resultant triagles themselves become particles?
I ask in that I would like to know if a whole seemingly static scene can really be generated/destroyed/interacted with as if everything were particles...
I dont know much more than you about the current situation, but in the interviews of The Force Unleashed (360/PS3 versions), thats pretty much how they described their physics engine... so I'm guessing its not a new idea. Something about all of the objects being made of "molecules", and the physics engine had information about these "molecules" and how to break/bend/move them.
It's great that they can do all this physics stuff on the GPU, but they seem to be forgetting the other thing you need that for; graphics. Games like Crysis don't exactly leave room on the GPU to do anything but graphics, and throwing physics into the mix will only make things worse.
I don't think it will push it out any.....this is one less system that the designers / coders need to account for.....eventually, technology will catch up with DNF and we can simply click a "do it" button and have DNF be released.
Wow ! That's more than 4 times faster than the human brain can detect. Now if I only knew why a frame rate this high is needed. Anybody?
It's not needed. But it's useful for comparison.
Nehalem only got x frames per second, but nVidia Magic Goodness 9800 Large Numbers GTX got y FPS, where y > x, can show that nVidia MG9600LNGTX > CPU.
Also, presumably this won't be used to run 50,000 particle games at 300fps, but much more complicated simulations (infinitely destructable environments, not line
It's just particles (Score:3, Interesting)
This is just a particle system. Smoke, snow, rain, and maybe water look better, but it apparently has no influence on gameplay.
Re:It's just particles (Score:4, Funny)
Parent
Re:It's just particles (Score:5, Funny)
Parent
Re:It's just particles (Score:5, Funny)
Parent
Spoiler (Score:3, Funny)
Re:It's just particles (Score:5, Funny)
(.)(.)
(')(')
(.)(.)
Much faster
(:)(:)
So fast they're a blur
(|){|)
Parent
Re:It's just particles (Score:5, Funny)
in 2018, the EA CEO will make an official communicate on how the pc market is saturated and in decline, and will stop the franchise.
the modding community will happily mod the first one until 2m1. console users instead will stubbornly buy the new one each year until eternity, inflating console market usage and lolling about their platform superiority.
Parent
Sync between machines with different cards? (Score:2)
Re:Sync between machines with different cards? (Score:5, Informative)
Huh? The local physics computations are only being used for presentation and local extrapolation. The server recomputes the relevant physics anyway, and can re-sync everyone periodically. That's how FPSes work to reduce lag--they do local extrapolation, and the server periodically snaps everyone back in line. It sometimes leads to what John Carmack calls "paradoxes" where locally displayed events get undone, but it works.
So, if some portion of your local physics calculation is purely for local presentation (e.g. game outcome doesn't depend on exactly how dirt particles fly around or boobs bounce, but you want it to look realistic), the server doesn't need to reproduce any of that to model the game correctly. Your screen might look different than someone else's, but in an immaterial way. For the super-soaker example, the server will still compute actual "wetness," possibly with a simplified model that skips computing the goosebumps and most of the dripping water.
--JoeParent
Using how much bandwidth? (Score:3, Informative)
The local physics computations are only being used for presentation and local extrapolation. The server recomputes the relevant physics anyway, and can re-sync everyone periodically.
Using how much bandwidth per particle?
For the super-soaker example, the server will still compute actual "wetness," possibly with a simplified model that skips computing the goosebumps and most of the dripping water.
That's kind of what I meant by "use coarse particles for game logic and finer particles for iCandy."
Re: (Score:2, Funny)
real physics? (Score:3, Interesting)
I recall that in the original Toy Story there is only one place they used "real physics". When the jump rope is thrown off the balcony (for the army men to descend), they used real phys
Re: (Score:3, Interesting)
I recall that in the original Toy Story there is only one place they used "real physics". When the jump rope is thrown off the balcony (for the army men to descend), they used real physics to model it's tangled fall. But thye later sent it was not a good idea to use the real physics. Not only was it harder but it didn't really look right and could not be easily tweaked. So all the rest is pretend physics.
What people perceive a situation to look like and how it would realistically look have drifted a lot. Due partially to the real life rarity of those situations and Hollywood/Video games distortion of it. We all expect shot guns to be massive overkill at medium to short ranges when in reality they don't hit that hard. We expect all explosions to involve flames. We expect bullets to hit with far more kinetic force then they do. We expect a whole lot of things that just don't happen in real life. It doesn't h
Re:real physics? (Score:4, Funny)
What are you talking about? I was just playing this game the other day where I shot a guy in the chest with my 9mm several times. He hardly moved when I shot him, and it took like 20 shots to finally take him down.
Just like real life.
Parent
Re: (Score:3, Informative)
Duke! (Score:5, Funny)
It'll be like 1996 all over again, only from a physics not graphics perspective. That, and there might be a new Duke Nukem game due out within the next 12 years.
I couldn't find anything specific - will nVidia... (Score:5, Interesting)
Re:I couldn't find anything specific - will nVidia (Score:5, Informative)
So, physics should work on Linux, having been ported to CUDA already, and CUDA being cross-platform, but the question is if any Linux games will actually support and/or make use of it.
Parent
Re: (Score:3, Insightful)
Re:I couldn't find anything specific - will nVidia (Score:5, Informative)
Parent
Re: (Score:2)
Re:I couldn't find anything specific - will nVidia (Score:5, Insightful)
The *only* use?? Geez, I'd like to get my hands on the API to write some physics educational/demonstration software. Or just create physically accurate simulations for kicks. We don't *have* to rely on others to write software for us.
Parent
640K RAM is enough for anybody, right? (Score:2, Insightful)
That's okay - somebody else already posted the answer - this thing'll use an established mechanism (CUDA). I don't know what that is, but after this card hits the market, I'll probably start to find out.
Re:I couldn't find anything specific - will nVidia (Score:5, Informative)
Anyone ever tell you that a lot of scientific types use Linux on their workstations? They do.
Parent
Re:I couldn't find anything specific - will nVidia (Score:2)
FIrst you need a Windows version that won't crash. (Score:5, Funny)
Parent
Is particle motion a fair test case? (Score:5, Informative)
When I was getting up to speed on IBM Cell programming, IBM had a programmer's tutorial (excellently written, btw). The example problem they used for their chapter(s?) on code tuning were a particle simulator. It was a wonderful example problem, because it showed how to vectorize a program. But then when we went to vectorize our own algorithm, it didn't fit the Cell's vector programming instructions nearly as cleanly, so in the end we didn't get nearly the performance increase due to vector instructions as did the particle simulator.
So I'm thinking that just even though CUDA can do a good job with particle motion simulations, we shouldn't remotely assume that it's good for particular algorithms for which each of us is responsible.
Re: (Score:2, Interesting)
Actually useful collision detection of say, convex volumes with rotational velocities, with the volumes being stored in a 3D space partition (eg: kd-tree or BSP tree) will likely prove significantly more difficult to parallel
Re:Is particle motion a fair test case? (Score:5, Interesting)
That's exactly why I'm skeptical of CUDA in general. Rendering graphics is one of those "embarrassingly parallel" operations, where for every frame rendered, each triangle, vertex, and pixel is independent of the others. I don't know much about physics processing, but I'm guessing it's the same. Simply throwing say, 4x more hardware at the problem gives you pretty much the ideal 4x speedup. Once you introduce random data dependencies into the problem, though, parallelization is much harder and you don't get the same speedups.
There are a lot of easily-parallelizable problems out there, which is great...but then again, there are a lot of not-so-easily-parallelizable problems out there too. I don't think CUDA would do any better than a general-purpose CPU on the latter class of problems.
Parent
So (Score:3, Funny)
Re:So (Score:5, Informative)
Parent
Experts please explain something (Score:5, Interesting)
It just seems to me that if a graphics card can calculate physics then it would also be able to do pretty much all the same types of calculations that a regular CPU can do, but I am obviously missing a big part of it.
Experts, continue!
Re: (Score:2)
CPU = Jack of all trades, master of none; GPU = the highly trained specialist.
Re: (Score:2)
Re:Experts please explain something (Score:5, Informative)
As a result, the massively parallel hardware on a GPU that exists to render many triangles/pixels/shader programs/etc at once can be exploited to calculate updates for many particles at once. The CPU is at an inherent disadvantage because it is only leveraging a small subset of it's full capabilities.
The CPU is very good at *lots* of different tasks. The GPU is phenomenally good at a very specific set of tasks. Physics just happens to fit within that set.
Parent
Re:Experts please explain something (Score:5, Informative)
Think of a CPU as a big tool box. There's something in there for every task, including a screwdriver that can be used to put screws into things. Then next to it, you have a big cordless 18 volt drill (The GPU). Way easier to drive screws with that than the manual screwdriver in your toolbox. But when you need to drive a nail instead, yeah you could bash it in with your screw gun, but it's easier to go back to your toolbox and find a hammer.
I guess that would make a physics processor the nail gun. Or something...
Parent
Re: (Score:3, Informative)
Applying a complex formula millions of times, each time with a different set of coefficients? -> GPU.
GPUs fail at tasks where lots of synchronization or frequent branching is necessary. Stuff like game logic, for instance, or state machines. Your typical office application is
Re: (Score:3, Informative)
On my Mac Pro, I have 8 3GHz CPU's. Consider that the baseline.
I have 2 8800GT cards to drive the 30" and 2x23" (rotated, one each side of the 30"
Now stream processors aren't quite the same as general purpose processors, but the way they're imp
Re:Experts please explain something (Score:5, Funny)
Parent
Re: (Score:3, Funny)
Why particle systems? (Score:5, Interesting)
Those are the kind of problems that force programmers to use approximations when using a physics engine.
The next step is really abstracting the physics from the development, not having pretty water.
Re:Why particle systems? (Score:5, Interesting)
They should test physics systems with spheres on irregular ground, with uneven (coefficient of kinetic friction), and changing wind.
I always liked to test on the hard cases (see my web site) but, in fact, what game developers and animators want is not realistic physics. The game people want "infinitely destructible environments", where you can blow up anything. And, of course, eye candy. The animation people want physics they can direct, where the starting and ending positions are specified but what happens in the middle might be automated. So most character motion in video games is spliced-together motion capture bits, hand animation, and a bit of physics now and then.
Most game physics engines today cheat on the hard cases, but by now, they usually cheat in ways that don't do something blatantly nonphysical.
My original goal, back in 1996 when I was working on this, was to get to a two-person fighting game with real martial arts. The physics engine we had was good enough, although in the era of 200MHz CPUs, a bit slow. But a control system that can do a judo throw against an uncooperative opponent is still out of reach. Worse, controlling a physically realistic martial arts character through a game pad is just hopeless. Play would be like a typical day at the dojo: "You lost your center. Your left foot should have been further forward when you tried that throw." "Yes, sensi". Work out three times a week for a year, and you get to be halfway decent. As a game, that sucks.
So I created the "ragdoll falling downstairs" cliche as a demo, licensed the technology to a middleware provider, and went on to other things.
Parent
Oh really? (Score:5, Funny)
In fact, I can.
nested particles (Score:2)
but is there such thing as netsted particles?
Full objects, made of "bound particles" (polygons that when constrained to eachother act as an object) but that whole object can be a particle?
Then if destroyed the resultant triagles themselves become particles?
I ask in that I would like to know if a whole seemingly static scene can really be generated/destroyed/interacted with as if everything were particles...
Or is this how things are already done??
It just seems to me that super-particles is
Re: (Score:2)
Real Physics engine goal (Score:5, Funny)
Re: (Score:3, Funny)
What about graphics? (Score:3, Interesting)
Re: (Score:2)
Layne
Re: (Score:3, Informative)
Wow ! That's more than 4 times faster than the human brain can detect. Now if I only knew why a frame rate this high is needed. Anybody?
It's not needed. But it's useful for comparison.
Nehalem only got x frames per second, but nVidia Magic Goodness 9800 Large Numbers GTX got y FPS, where y > x, can show that nVidia MG9600LNGTX > CPU.
Also, presumably this won't be used to run 50,000 particle games at 300fps, but much more complicated simulations (infinitely destructable environments, not line