Hi
@DANO70 , re FG084B & C
Yep, in fact i was purposely trying to labour the initiation of the secondary shader
by using a random mounting texture which had to be resized by iStripper. On my rig, resizing seems
to delay shader initiation a tad rendering some larger textures, & this can vary the effect between plays.
If you have stutters, you can eliminate the call for a
source random mounting texture altogether
The texture node will grab the set size shader instead & that might well run smoother for your rig ;-)
Worth a try anyway,
You could do it by say, substituting the original early lines of FG084B with this ..
clip {
id: Clip
deny: top, glass, cage
}
texture {
id: WallTexture
//source: ETImages/Plaftexrot01/
size: 1920, 1080
pos: 0, 0, 0
shader: fragment,Shaders/Syntopia/Menger JourneyETModSlower.fsh
}
framebuffer {
id: TunnelWalls1
source: WallTexture
}
..and including a repeat declare of same shader in the Tunnel2 framebuffer
framebuffer {
id: Tunnel2
source: Tunnel1
pos: 0, 0, 0
hotspot: 0.5, 0.5
size: 1920, 1080
shader: fragment,Shaders/Syntopia/Menger JourneyETModSlower.fsh
}