23 replies to this topic

[Marc]

Hey all

We're releasing this to you early so you can possibly get started on something and then migrate to the final file once it's been finished. If you've been to other renderer's shader sites, then this should be familiar to you.

Basically the file has been built to provide a fairly neutral environment. This will allow for standard presentation of all shaders submitted using this method. We'll probably put up some rules to follow in the coming days. For now though, feel free to download the file and try it out.

Thanks
the odforce guys

--- the files follow here ---

Attached Files

•  odforce_shaderball_h8_v3.otl   103.4K   722 downloads

[vmuriel]

Good initiative.

[Ratman]

Hey Marc, cool file, though i'm having issues with the otl.

Once i install it and open a new scene and apply my shaders, the textures stop working , it all works fine from your scene files provided, but it goes awry on me once i open the otl on another scene.

Other than that it's pretty cool

[Marc]

Hey Ratman

This is all expected to be used from within the example file. We'll be posting the rules of use in the next couple of days. But basically if you want to submit a shader then everything in the file should be identical apart from the shaders (and any cops/vops you need of course).
There will probably be some upgrades to the file in the near future anyway, so this is just for playing with .

[Jason]

I've made a small update to the shaderball scene.

*/ Basically, I've contained everything into the single OTL - all textures are embedded.
*/ I've added displacement shader support - no longer should it be necessary to Allow Editing to use displacement shaders
*/ Improved the shadow quality a bit
*/ The name of the shader is derived via expression from the actual shader name. You can change this behaviour if you want to.

I've updated the original post at the start of this thread with the new OTL.

[photex]

Jason, on Jul 11 2007, 07:21 PM, said:

I've made a small update to the shaderball scene.

*/ Basically, I've contained everything into the single OTL - all textures are embedded.
*/ I've added displacement shader support - no longer should it be necessary to Allow Editing to use displacement shaders
*/ Improved the shadow quality a bit
*/ The name of the shader is derived via expression from the actual shader name. You can change this behaviour if you want to.

I've updated the original post at the start of this thread with the new OTL.

noice!

Are we going to end up with a version separate for H9?

[Jason]

photex, on Jul 12 2007, 03:59 AM, said:

noice!

Are we going to end up with a version separate for H9?

Yeah, I think we should - just a Material slot and we're done,  (rubs hands!)

[crunch]

Jason, on Jul 12 2007, 10:45 AM, said:

Yeah, I think we should - just a Material slot and we're done,  (rubs hands!)

You probably also want to be able to select geometry:  teapot, sphere, hair, volume, etc.  But yeah, should be a wee bit simpler.

[michael]

different geometry is 'on the list'

we wanted to just get something started that would give everyone a solid start - so that people could make shaders and share them with the community in a standard way...
this scene will evolve as time goes on - so keep offering suggestions!

[Marc]

As for different geometry, we're aiming to build a single piece of geometry that can be used to represent 90% of the shaders that people will build. Any special shaders for things such as hair, fx shaders etc can have the geometry modified by the shader writer, but otherwise one of the rules that we're busy writing is that nothing must be changed in the scene other than what applies directly to the shader.
That way we get a consistent presentation of all shaders so people know what they're getting.

We're basically modeling ourselves after these guys and it seems to work for them :
http://mxmgallery.maxwellrender.com/
http://www.vray-materials.de/

[dee900]

When rendering, I get pink walls characteristic of a missing texture.  I haven't looked into why the v_walls diffmap reference into COPs isn't working properly.  (This is on Windows, v8.2.13)

[dee900]

Marc, on Jul 13 2007, 02:44 AM, said:

We're basically modeling ourselves after these guys and it seems to work for them :
http://mxmgallery.maxwellrender.com/

The Maxwell people have put a lot of thought into their ball.  Why not just use it (with attribution)?