29 Apr 2007

Nebula2 support in Nebula3 + status update

I'm currently working on the low-level graphics subsystem, resource management and basic scene rendering code. I plan to do the next SDK release as soon as the Tiger tank from the Toolkit examples will render.

A few info tidbits until then:
  • Resource setup will be decoupled from the actual resource objects through resource loaders. This was an optional mechanism in Nebula2, but is now the only way to setup a resource object. This modular approach allows more freedom for 3rd parties to extend the Nebula resource management and makes the code cleaner and easier to understand (its a similar concept to Streams and StreamReaders/StreamWriters)
  • Asynchronous loading for all graphical resources will be supported right from the beginning.
  • Nebula2 binary file formats (nvx2, nax2, n2) will be supported directly through legacy loader classes. It is possible to remove legacy file format support by changing a #define to reduce the code footprint. This should make migration to Nebula3 much simpler, since Nebula2 asset tools can be used to create resources for Nebula3 in the beginning.
  • There is now a clear separation of per-model data (shared across all instances of a model), and per-instance data. Per-instance shader attributes must now be explicitly requested by the application. This allows the rendering code to perform more optimizations under the hood for instance rendering, and it makes the rendering code much simpler.
  • Access to per-instance data is much simpler, more intuitive and much more efficient (no more nRenderContexts).
  • Most per-instance data now persists between frames, and doesn't have to be recomputed every time an instance is rendered (which may be up to multiple times per frame). Nebula2 did this only when absolutely necessary (particle systems and skinned characters). Nebula3 increases the per-instance memory footprint slightly (which is bad), but simplifies the rendering code a lot, and reduces per-instance state switch overhead drastically (which is good).

3 comments:

Kim Hyoun Woo said...

Good news!
I also expect to run shadercompiler if it is possible. In the previous release, that stuff wasn't able to be run due to some break of xml input file.

And one more thing, I hope to see nebula2 code dump from RL. :-)

Cheers,

Eric said...

looks like the nonprogrammers will have some "eyecandy" soon. :] even though the features sound quite cool for me.
Resource setup and Asynchronous loading? Thats something to finally see "fluendly animated scene while loading"-thingy? ;]

Larry said...

Good to see the progress on Nebula 3, cant wait to get my hands on the next release.

I'v always wanted to ask you about the design of Entity Properties in Mangalore. I've been using Mnaglore alot lately and noticed that I cant attach more than 1 similar property on the same Entity and Property Attributes are attached to the owner Entity.

My thinking is, assume a Car, it has a set of tail lights and a set of headlights, would it make sense to attach 2 light properties, 1 for each set and to have the property own and control its attributes. I can then perhaps switch of Tails lights and leave headlights on etc...

The same could go for e.g. a Hoot sound and an Engine sound both of which could play at the same time therefore requiring two distinct sound properties.