Coding for the new 3D system....
Posted 07 May 2011 - 01:09 PM
Arial: As has already been said. GM isn't a 3D package, if your after that... your probably in the wrong program. It has simple 3D to let you get to grips with it, but for now we certainly aren't thinking about extending what's already there. Importers/exporters/converters take considerable time and resources, and we have enough to do. Sorry.
Posted 07 May 2011 - 08:09 PM
Could that potentially draw a level with 200000+ without lag poly's using the New 3d system?
In Mike's blog he mentions that the test he released for us has '19,683 cubes merged into a single 236,196 polygon mesh at 96fps rather than 4'
I'd expect it to be even faster in a level where you could implement a lot of culling/won't be drawing poly's behind the camera and that sort of stuff.
So yes, you would be able to have a (comparatively) very high poly levels, with mike here is encouraging us basically to try have higher poly models, too (and cut down on those draw calls!)
I imagine now that animation would be faster to have different 'frames' of each animation model saved, rather than the draw 8 parts transformed&stacked to move together.
Posted 08 May 2011 - 11:24 AM
Alright guys, you've made enough fun of Arial. Cut it out, and let's keep it on track, please.
Or will new 3D function be added in gm8.2?
So, in short, with the addition of static modelling, we should:
- Use static models in preference to dynamic (obviously)
- Make large (static) models in preference to more smaller models
- Make two models in preference to one model colour-blended in two ways
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users