Julien Bayle

I need to create a "square texture" apparently named as domemaster.

It relates to 5 camera lens-angle 90° oriented from within the center of a cube (top, back, front, right and left).

This rendering is deployed as a texture on a part of a disc (UV adjusted) and shot by another orthographic camera.

https://github.com/charlesveasey/MaxDomemaster

BUT, wouldn't it be possible to do that with a shader ?

Hi there,
I need to create a "square texture" apparently named as domemaster.

It relates to 5 camera lens-angle 90° oriented from within the center of a cube (top, back, front, right and left).
This rendering is deployed as a texture on a part of a disc (UV adjusted) and shot by another orthographic camera.

I found this:
https://github.com/charlesveasey/MaxDomemaster

domemaster-with-a-shader

- I need to capture (sample) the 5 textures rendered by my 5 cameras.

- I need to take these 5 and to "map" and adjust them on a circle and use this latter as the output (2048x2048 required)

cannot find proper information about that because I probably don't have the right keywords.

- I need to capture (sample) the 5 textures rendered by my 5 cameras.
- I need to take these 5 and to "map" and adjust them on a circle and use this latter as the output (2048x2048 required)
- shader based

cannot find proper information about that because I probably don't have the right keywords.


basic setup involves a jit.gl.node containing your geometry and 5 cameras, each camera with capture enabled and viewing transform set properly. the texture output of each camera goes to a separate jit.gl.mesh object with a shader to do the warping:

I may have another option BUT not sure it could work with max: only one camera capturing from (0,0,0) and oriented to the top and opening ... wide at 210° vertical X 360° horizontal... (reminding me a fish eye)

I'd really need to find a way to code the dome warping shader.

what information of my dome installation would I need to do that ?

I'd really need to find a way to code the dome warping shader.
what information of my dome installation would I need to do that ?


Yes it should be possible as a shader. (It might even be possible using jit.gl.pix, which also operates as a shader on the GPU), but you would still need the five faces rendered first, and the final pass creating the circle map probably isn't going to be much more efficient as a shader rather than how the domemaster patch has it. And if it simply that you need a texture output, the domemaster-example-syphon.maxpat patch gives this.

An interesting thing is to try to eliminate the 5 passes and render the entire scene dome-distorted in one shot, but this requires custom shaders on all geometry, possibly including tesselation. Not easy at all, but it has been done before. Maybe with the new nvidia multi-view gpus that won't matter much anymore... :-)

Yes it should be possible as a shader. (It might even be possible using jit.gl.pix, which also operates as a shader on the GPU), but you would still need the five faces rendered first, and the final pass creating the circle map probably isn't going to be much more efficient as a shader rather than how the domemaster patch has it. And if it simply that you need a texture output, the domemaster-example-syphon.maxpat patch gives this. 

An interesting thing is to try to eliminate the 5 passes and render the entire scene dome-distorted in one shot, but this requires custom shaders on all geometry, possibly including tesselation. Not easy at all, but it has been done before. Maybe with the new nvidia multi-view gpus that won't matter much anymore... :-)


so indeed the domemaster patch could be enough.

I'm very curious about some shader version of that.

If I'd only what to send that using syphon, should I absolute need that big 2048x2048 jit.window?

This is something I didn't figure out before.

Actually, I'd need only (and maybe) a small monitor as a pwindow. not even...

Graham,
so indeed the domemaster patch could be enough.
I'm very curious about some shader version of that.

If I'd only what to send that using syphon, should I absolute need that big 2048x2048 jit.window?
Apparently, I have too.
This is something I didn't figure out before.

Actually, I'd need only (and maybe) a small monitor as a pwindow. not even...


Perhaps add @capture 1 @dim 2048 2048 @adapt 0 to the [jit.gl.camera domemaster] object, and then take the texture output directly from its outlet. That way the jit.window size shouldn't matter.

should I feed the jit.gl.texture with the camera domemaster or directly the syphon output ?

should I feed  the jit.gl.texture with the camera domemaster or directly the syphon output ?


 from Charles Veasey and adapted it slightly:

But does anyone have a fisheye shader that would work in the example that Rob Ramirez gave in this thread?

I took the Syphon example of the Domemaster patches from Charles Veasey and adapted it slightly:


But does anyone have a fisheye shader that would work in the example that Rob Ramirez gave in this thread?

I pick up the thread of this topic - have someone made progress on a solution based on jit.gl.pix or other kind of shader solution to map content to a fulldome format context? i wonder if this would have better performance than the domemaster patch shared a while ago now and mentioned at the beginning of posts which uses at the final step ortho jit.gl.camera (lens Angle)

I pick up the thread of this topic - have someone made progress on a solution based on jit.gl.pix or other kind of shader solution to map content to a fulldome format context?  i wonder if this would have better performance than the domemaster patch shared a while ago now and mentioned at the beginning of posts which uses at the final step ortho  jit.gl.camera  (lens Angle)

?

domemaster with a shader ?