Ross FiveSidedBarrel Blog - All Comments

re: Video Tutorials Now Available

Imaginationseven7 — Sat, 31 Mar 2012 18:05:36 GMT

Great I will go over all these tutorial

Thanks :)

re: Editor Development: Content Pipeline Options

Dean Wadsworth — Fri, 06 May 2011 15:21:00 GMT

OMG!!! Thats awesome!! w00t can't wait

re: Editor Development: Content Pipeline Options

JohnK "bobthecbuilder" — Wed, 04 May 2011 14:48:33 GMT

Hi Wagmance,

The new "Generate Light Map Coordinates" option will automatically create a second uv channel for you if one does not already exist.

If one does exist the processor preserves it, so you can override the automatically generated channel with your own. :)

Even better the channels are calculated per-mesh - which means you can export a huge scene from your modeling app, manually unwrap one or two meshes, and SunBurn will leave those channels intact, but still unwrap all of the other meshes.

Let me know if this helps!

re: Editor Development: Content Pipeline Options

Wagmance — Wed, 04 May 2011 00:41:48 GMT

Looks great! :D

Im just wondering, will we still need to create a second UV Channel in our Models before they are exported?

And if a Model already has its Lightmap Coords set, can we choose to override them?

re: Editor Development: Content Pipeline Options

JohnK "bobthecbuilder" — Tue, 03 May 2011 17:59:01 GMT

Hi Darkside,

*All* modeling apps are supported by SunBurn.

The XSI Support option is only there to allow using XSI shaders via their XNA connector plugin.

re: Editor Development: Content Pipeline Options

Darkside — Tue, 03 May 2011 14:07:59 GMT

Just noticed, only XSI support :-(. Where's the Blender love?.

Still great though, I know some people who will be happy

re: Editor Development: Content Pipeline Options

Darkside — Tue, 03 May 2011 14:05:22 GMT

Saw them hit the YouTube channel next week, great stuff as usual. keep it up! :-D

re: Editor Development: Content Pipeline Options

Tom — Sun, 01 May 2011 08:16:13 GMT

Nice :) Saw you mention it on Twitter at some point - great stuff :)

re: Editor Development: Content Pipeline Options

JohnK "bobthecbuilder" — Sun, 01 May 2011 01:17:43 GMT

@Philippe, haha - good guess! Yes, you win the ability to automatically generate your light map uvs (when SunBurn 2.0.15 is available). ;P

re: New Documentation: Video Tutorials

Aredhel — Sat, 30 Apr 2011 22:30:56 GMT

Awesome job and very professional work, too. Please keep them coming :)

re: New Documentation: Video Tutorials

Aredhel — Sat, 30 Apr 2011 22:29:47 GMT

Awesome job and very professional work, too. Please keep them coming :)

re: Editor Development: Content Pipeline Options

Philippe Da Silva — Sat, 30 Apr 2011 19:02:24 GMT

@ John: I know, I know! It's the built-in LightMap UV generation! Did I win something?! :p

Philippe

re: Editor Development: Content Pipeline Options

JohnK "bobthecbuilder" — Sat, 30 Apr 2011 14:44:21 GMT

Hi Ross, looks great! It was an awesome week, so many new features implemented. :)

@all, I think the processor options in that screen shot might hint at an awesome new unannounced feature. ;)

@Tom, not currently - but you can modify the processor / importer options for each asset (models and ... "other" assets.. ;) in the repository separately.

Prior to this all models used to the same setting (from the repository processor).

@Filip, the importers / processors are pulled from the content project the repository is located in. This ensures the repository has access to those shown in the drop-downs and any one selected can be used by the pipeline.

Let me know if this helps!

re: Editor Development: Content Pipeline Options

Filip — Sat, 30 Apr 2011 09:34:15 GMT

Hmm, where do you get the list of processors and importers? Will I have to reference dll's to the project to be able to pick let's say sgMoting one or is there some kine of configuration file? :)

re: Editor Development: Content Pipeline Options

Tom — Sat, 30 Apr 2011 08:24:31 GMT

Sweet :) Will this open the doors for per-material-slot compression options at some point? I'd like my diffuse to be compressed, but the processor should leave normal maps alone, as he simply can't handle them...at all. Or perhaps something based on texture names with suffixes.