Scolring - Forum

fixed; i used shader material 07 from the shaders example, the one that does the bare minimum to render diffuse/bump
my winxp 32  p iv is happy now, but alas i think it is becoming to old to handle openspace, but i can still author some assets with it so it doesn't end up in a landfill, maybe i'll try to upgrade the gpu one more time.

http://ifam.net/openspace/shaderworkswithxp/web/

i somehow forgot how i got the room to work as a static, complex collision object aside from setting the room shape to collisiontree, but it works.:)

http://ifam.net/openspace/cyclopean_roo … index.html

now to stick one of my ogre montsers in it....use a normal map shader that also uses lightmaps, the glow compositor, and see if my older piv can handle it aside from the i3 i'm using to do openspace work on.

So the master scene would run on the server, responding to collision messages sent by the clients and then feeding back the object positions?

oops i see this demonstrated in the network.xos file, but i'll discuss that in another thread.

so i guess i could hook an elliptical up to an openspace scene and fly from usa to france and back if i go fast enough.

.....is there any timeline for shared objects and remote avatars, if i may humbly ask?:cool:

openspace uses ogre to render 3d objects and materials, including shaders. usually what you have is a .material file that refers to 2d image files (or 3d dds image files), and to other files with the .cg, .program, .frag, .glsl, .hlsl, .vp or .vs extensions.....if you look at the ogre3d site you can download examples of how materials and shaders work. ogre can render shaders with directx or opengl.

i haven't used the exporter in a few months....i think under winx that you have to install python and set the an environment variable pointing to the python installation directory in one of the control panel/computer dialogs...it is probably one one of those threads in the ogre forums.

just ogre fog

is there a timeline on integrating hydrax?  (which is very cool, I checked the demo out last night.)
that would make the use of a shader on a mesh obsolete.

Otherwise you would have to be dynamically tiling a bunch of plane meshes, and all of them would be moving up and down, I'd assume that they would have awful seam issues. And with the present method if you use a plane, you see its edges if you don't use fog.

-h