joshua goldberg

i know it's only a few steps away from the amazing throbbing torus, 

but i'm having a good time with it. client says he wants audio 

reactivity with an animation that looks like psychedelic water, i'm 

i know it's only a few steps away from the amazing throbbing torus,  
but i'm having a good time with it.  client says he wants audio  
reactivity with an animation that looks like psychedelic water, i'm  
going to try to give it to him!

trippy-ass-waterfall-sharing-is-fun

Hehe, yeah, I really dig this too - although, was it supposed to have 

some sort of texturing going on? On my system it's just a grey wash 

(which might have been the intended effect, dunno)

Joshua Kit Clayton skrev:
>
> Just in time for burning man! : )
>
> Nice one, thanks for sharing.
>
> -Joshua
Hehe, yeah, I really dig this too - although, was it supposed to have 
some sort of texturing going on? On my system it's just a grey wash 
(which might have been the intended effect, dunno)

I had tons of errors with it. I suspect relaunching max is in order, 

On Aug 23, 2007, at 2:02 PM, Andreas Wetterberg wrote:

> Hehe, yeah, I really dig this too - although, was it supposed to 

> have some sort of texturing going on? On my system it's just a grey 

> wash (which might have been the intended effect, dunno)

I had tons of errors with it. I suspect relaunching max is in order,  
but, too busy!

> Joshua Kit Clayton skrev:
>>
>> Just in time for burning man! : )
>>
>> Nice one, thanks for sharing.
>>
>> -Joshua
> Hehe, yeah, I really dig this too - although, was it supposed to  
> have some sort of texturing going on? On my system it's just a grey  
> wash (which might have been the intended effect, dunno)
>
> Andreas.

On Aug 23, 2007, at 11:34 AM, vade wrote:

> I had tons of errors with it. I suspect relaunching max is in 

There's a few loadbangs that are necessary (including some in 

> I had tons of errors with it. I suspect relaunching max is in  
> order, but, too busy!

There's a few loadbangs that are necessary (including some in  
subpatches). Try saving and re-opening.

On Aug 23, 2007, at 11:02 AM, Andreas Wetterberg wrote:

Sounds like you're on a machine without floating point texture 

support (e.g. Intel GMA 950 or older ATI/NVidia cards). If you put 

"jit.matrix 4 char 150 150" between the jit.normalize and 

jit.gl.texture in the texture subpatch, in order to convert the 

floating point gradient noise to char data before texture submission, 

>
> Hehe, yeah, I really dig this too - although, was it supposed to  
> have some sort of texturing going on? On my system it's just a grey  
> wash (which might have been the intended effect, dunno)

Sounds like you're on a machine without floating point texture  
support (e.g. Intel GMA 950 or older ATI/NVidia cards). If you put  
"jit.matrix 4 char 150 150" between the jit.normalize and  
jit.gl.texture in the texture subpatch, in order to convert the  
floating point gradient noise to char data before texture submission,  
I believe it should work on your card.

> On Aug 23, 2007, at 11:02 AM, Andreas Wetterberg wrote:

>> Hehe, yeah, I really dig this too - although, was it supposed to have 

>> some sort of texturing going on? On my system it's just a grey wash 

>> (which might have been the intended effect, dunno)

> Sounds like you're on a machine without floating point texture support 

> (e.g. Intel GMA 950 or older ATI/NVidia cards). 

Grr, you're right, Joshua. Thanks... this has been an on-going problem 

for me and my really high-end 8800GTS card... :-( I think I will gamble 

a bit and see if the latest driver update fixes it... *fingers crossed!*

> If you put "jit.matrix 4 char 150 150" between the jit.normalize and 

> jit.gl.texture in the texture subpatch, in order to convert the 

> floating point gradient noise to char data before texture submission, 

Well I'll be damned... now it really *IS* trippy! Brilliant.

Joshua Goldberg, remember the "@fsaa 1" on the jit.gl.render... makes a 

world of difference, at least it does here. No jaggies in sight. Heheh, 

I did some fiddling around and put a volume envelope follower on the 

[jit.op @op * @val 150] - oh lawd, that's fun, too! Thanks for sharing!

Joshua Kit Clayton skrev:
>
> On Aug 23, 2007, at 11:02 AM, Andreas Wetterberg wrote:
>> Hehe, yeah, I really dig this too - although, was it supposed to have 
>> some sort of texturing going on? On my system it's just a grey wash 
>> (which might have been the intended effect, dunno)
> Sounds like you're on a machine without floating point texture support 
> (e.g. Intel GMA 950 or older ATI/NVidia cards). 
Grr, you're right, Joshua. Thanks... this has been an on-going problem 
for me and my really high-end 8800GTS card... :-(  I think I will gamble 
a bit and see if the latest driver update fixes it... *fingers crossed!*
> If you put "jit.matrix 4 char 150 150" between the jit.normalize and 
> jit.gl.texture in the texture subpatch, in order to convert the 
> floating point gradient noise to char data before texture submission, 
> I believe it should work on your card.
Well I'll be damned... now it really *IS* trippy! Brilliant.

Joshua Goldberg, remember the "@fsaa 1" on the jit.gl.render... makes a 
world of difference, at least it does here. No jaggies in sight. Heheh, 
I did some fiddling around and put a volume envelope follower on the 
[jit.op @op * @val 150] - oh lawd, that's fun, too! Thanks for sharing!

This patcher (sent above @ 8/22/07 21:09) is causing the latest MAX Windows version to crash as soon as the Metro toggle is hit. Not sure if this is the right place to report this... I'm new to the forum.

This patcher (sent above @ 8/22/07 21:09) is causing the latest MAX Windows version to crash as soon as the Metro toggle is hit.  Not sure if this is the right place to report this... I'm new to the forum.


trippy ass waterfall- sharing is fun!