Aston Martin Crash Test

[Housey]

Not sure what to make of this, but a computer car, ThemTube and crashing will probably go down well on this site.

 

[InvaderGIR]

Hahah...well I'm never getting in a computer generated DB9.

 

[ScoobyDoo69]

324km/h crash at the end.. ow lol.

 

[SoliD]

I think that man would have been cut in half, definitely fake!

 

[Janesy B]

Hmm, thats not real. I can tell by the pixels.

 

[[TR]SweetSpotOz]

.

 

[merlin]

Itchy beards at some of them, the limbo pole one was totally wrong and if someone would lend me theirs I'll reluctantly prove it.

 

[Felix Da Housecat]

Cancels order for new AM

 

[Hedge]

SCOOOTERRR!!!!

 

[shauncr91]

I didn't realise Aston Martin now made cars out of cake.

 

[PinkFloyd]

That's quite awesome

When are computer games going to have crashes like that?!

 

[--Mike--]

The rear wheels are obviously well secured since they never break off in any tests!!

 

[Begbie]

We all know Astons are industractable

 

[Skeeter]

That's quite awesome

When are computer games going to have crashes like that?!

I think this is more a demo if a crash physics system than anything to do with Aston Martin.

 

[PinkFloyd]

I think this is more a demo if a crash physics system than anything to do with Aston Martin.

Yeh I realised that bit

It's almost certainly pre-rendered at the moment though.

 

[Edward01]

James bond's held up better than that!!

 

[Mr_Sukebe]

Some clever work in there, particularly the physics involved and how different areas of the car has different levels of strength. I'm guessing it was produced by someone for their degree project, and they were working on animation or mech eng.

 

[Zogger]

Yeh I realised that bit

It's almost certainly pre-rendered at the moment though.

it does say that in the description

This car has been modeled in Rhinoceros. It was then exported to 3d studio, where it was textured and then made "simulatable". It was then simulated with reactor, which is a plug-in in 3d studio.

There are some 2100 parts in this car. There is an entirely different simulation-model behind the movement of this car. The simulation-model is invisible, and the visible model of the car is then linked to the simulation-model. The simulation-model is made up of 420 parts and 640 constraints, constraining the parts to each other.

To make a crash scene the car was then given an initial speed, and some obstacles were placed in its way. After this to scene was simulated, a process which took about 20sec / frame. This video has a frame rate of 30 frames / sec, so that means a 3-4 second long clip took about 40 minutes to simulate. The simulation is done by the computer and you cant influence it while it's being done.

Finally all clips are rendered. 30 frames / sec gives a total of 5400 pictures that had to be rendered for this video. The average rendering time per frame was about 10 minutes. That's a total of 54 000 minutes = about 40 days.

Part of the reason for the long rendering times was that this video was originally rendered in 1080p aka full HD (1920 x 1080), some clips, though, were rendered in 720p (1280 x 720). The longest rendering time for a single frame was over 6 hrs.

 

[NickXX]

That's a crap simulation. After today's track day at Bedford, we all know that the front wheels pop off the DB9 after hitting an object.

Object being a 997 Turbo in this case.

 

[Housey]

That's a crap simulation. After today's track day at Bedford, we all know that the front wheels pop off the DB9 after hitting an object.

Object being a 997 Turbo in this case.

Jesus, what happened there then?