Integrating 3D models with photography
Interested in integrating your 3D work with the real world? This might help
# 16 31-03-2006 , 03:25 AM
Registered User
Join Date: Mar 2006
Posts: 13
Awesome.....thanks for both of yal's help. But I have another question, about the polygons. Would you suggest to work straight from polygon primitives, or is it okay to work with NURBS and then transfer to polygons?

,Pat

# 17 31-03-2006 , 03:35 AM
concorddawned's Avatar
Registered User
Join Date: Feb 2006
Location: Sydney
Posts: 184
Both have their strengths and weakneses Its probably a good idea to do some reading on both.

# 18 31-03-2006 , 03:42 AM
Registered User
Join Date: Mar 2006
Posts: 13
Sounds good......and sorry to bother everyone, but I got one more question that I asked in another area. But I have heard that render time for NURBS and Sub Div's in animations are crazy long (especially with it running 30 frames per second). Even with render layers, how long would you estimate for render time to be for, let's say, a 30 second long animation (about the length of a cut scene)?

,Pat

# 19 31-03-2006 , 03:47 AM
concorddawned's Avatar
Registered User
Join Date: Feb 2006
Location: Sydney
Posts: 184
Thats one i cant answer..

I havent heard of anything like that but who knows it could be true..

I guess its just how well you set up your mesh.

user added image

# 20 31-03-2006 , 03:53 AM
Registered User
Join Date: Mar 2006
Posts: 13
yeah I hear ya.....thanks for your help man

# 21 31-03-2006 , 03:58 AM
mtmckinley's Avatar
The Maya Mountain
Join Date: Aug 2002
Location: Seattle, WA
Posts: 8,245
for game art, it doesn't matter if you started with nurbs or not, so long as the final output is polygons it will work.

# 22 31-03-2006 , 04:06 AM
Registered User
Join Date: Mar 2006
Posts: 13
Cool....thanks a lot for the help. You'll probably see me again once I get the program.

,Pat

# 23 31-03-2006 , 04:31 AM
Registered User
Join Date: Aug 2004
Posts: 408

Originally posted by concorddawned
For times like these and the technology we have at hand, really this shouldnt be the case. I wish that hardware companys would put there ass into gear and make the hardware that can smoothly view high polycount characters.

Why do we have to suffer with low quality images...

user added image

Back in the GeForce 3 era we had "nonlinear polygon edges" from nVidia -- which joined "3DNow(here)!" in the pit of forgotten code because it was too damn hard to code.

Though -- allegedly PixelShaders4 (or 5) are ressurecting them... right when PerPixel lighting makes it unnecessary...

Perfect timing MS!

# 24 01-04-2006 , 06:54 AM
Registered User
Join Date: Mar 2006
Posts: 13
For gaming art, since I can work in NURBS and then convert to polygons at the end, will I loose any details if I fix it up good in Sub Div's and then convert to polygons? May be a stupid question.


,Pat

# 25 01-04-2006 , 07:07 AM
daffas's Avatar
Subscriber
Join Date: Dec 2005
Location: The States
Posts: 193

Sounds good......and sorry to bother everyone, but I got one more question that I asked in another area. But I have heard that render time for NURBS and Sub Div's in animations are crazy long (especially with it running 30 frames per second). Even with render layers, how long would you estimate for render time to be for, let's say, a 30 second long animation (about the length of a cut scene)?


my cpu is not the best and a 3 second fire animation that i did of this site took me 12 hrs and it still didnt finish all the way. i am also useing PLE.

# 26 01-04-2006 , 02:49 PM
mtmckinley's Avatar
The Maya Mountain
Join Date: Aug 2002
Location: Seattle, WA
Posts: 8,245

Originally posted by phornby
For gaming art, since I can work in NURBS and then convert to polygons at the end, will I loose any details if I fix it up good in Sub Div's and then convert to polygons? May be a stupid question.


,Pat

While it is true that you can do whatever as long as the end result is polygons, I can't help but recomend just trying to make it straight from polys to begin with. The reason I say that is because in the game industry, you are always given a polygon limitation and if you are converting from nurbs or subDs or whatever, the resulting polygon count you get is pseudo random. And I'd say definitely not the most efficient. Which then would result in a lot of time cleaning up the geometry.

So, personally, I recomend starting and ending with polygons for serious game art.

# 27 02-04-2006 , 12:46 AM
Registered User
Join Date: Mar 2006
Posts: 13
Thanks a lot for the help everyone, especially the advice about polygons.


,Pat

# 28 04-04-2006 , 05:52 AM
Subscriber
Join Date: Oct 2005
Posts: 7
polygons should be your sole focus until captain kirk decides to let the 3d industry use the uss enterprise's computer. mt. mick said it all. nurbs and subs are just not computational friendly at this present time for real time actions. its up to you the artist to turn those polys into life. the next gen stuff that the xbox 360 developers are doing is very impressive. just remember the talent starts with you.

# 29 09-04-2006 , 08:30 PM
Gamestarf's Avatar
Subscriber
Join Date: Feb 2006
Location: Netherlands
Posts: 165
Hi im wanna become a game artist to and im going to a follow a gaming adducation enxt year, and im working with polygons.
Cause i first used blender so im used to polygons.

By the way nice pics on your website mckinkley


Last edited by Gamestarf; 09-04-2006 at 08:35 PM.
# 30 09-04-2006 , 08:53 PM
MattTheMan's Avatar
Registered User
Join Date: Apr 2005
Location: Fairfield, CT
Posts: 2,436
I haven't read the entire thread, but, from my own research-

not that my raytracer is great (i havent posted this in the wip section b/c i think its insignificant) but I did write scripts for triangle raytracing, and, raytracing mostly is per pixel.

However, using a rather complex algorithm that I found on the web and adapted, I wrote triangle gourard shading for my raytracer. The results were dramaticly faster.

I didn't save any pics, but a triangle mesh w/ 150 triangles and standard raytracing (per-pixel shading) rendered just as fast as 7000 triangles gourard shaded. wow.

Well, to really test speeds, I did this: 30,000 triangle mesh (really hi-poly sphere user added image) normal raytraced = 6.5 minutes

And my triangle intersection method is VERY fast, as it uses baryocentric coordinates and no sqrt functions ( that take about 300x more than a + or -)(normal triangle intersection tests use 3 of those). Mine simply uses a bunch of plus or minus.

Now compare that to gourard shaded, which tests each triangle only once by using intersection caching(really simple really). Thats 30,000 triangles= 19 seconds.

And that's with no kind of spatial subdivision scheme- which generally improves rendering by thousands of times.

NOTE: I Didnt post thesse in my wip thread because i copied most of the code. The ones I did paste were entirely written by me.

So now, throw in an octree structure- takes about 1.5 seconds to calculate(for the 30,000 tris);

30,000 tris perpixel shading = 48 seconds(49.5 total)

30,000 tris gourard shading = 2.8 seconds(4.3 total)

So that's my opinion about per-pixel shading. but, I don't know how it works in games, that's just how my raytracer does it.


Live the life you love, love the life you live
Posting Rules Forum Rules
You may not post new threads | You may not post replies | You may not post attachments | You may not edit your posts | BB code is On | Smilies are On | [IMG] code is On | HTML code is Off

Similar Threads