[fluxus] Hey dude.

[dave]

Hi Gerry,

I don't get the spinning off into the distance, but there is a
difference between 0.11 and 0.12 I noticed that might be being picked up
here, try enclosing the (boxen 256) call between a (push) and a (pop).

I think I'm keeping the top level transform state from the previous
frame, I've noticed this while doing other things - let me know if this
fixes it.

cheers,

dave

On Sun, 2007-07-01 at 10:35 +0100, Gerry Grainger wrote:
> sorry - that should read as (boxen 16) - it leads to slight glitching
> otherwise.
> 
> On 01/07/07, Gerry Grainger <nowhere.elysium at gmail.com> wrote:
>         sorry about that - I'll sign up to them a bit later on today. 
>         Here's a script that exhibits the problem: it worked fine
>         before hand, though.
>         
>         (clear)
>         (opacity 0.5)
>         (hint-wire)
>         (wire-colour (vector 0 1 0)) 
>         (line-width 1)
>         (define (box c)
>         (push)
>             (draw-cube)
>         (pop))
>         (define (boxen c)
>             (box c)
>             (translate (vector 0 1.5 0))
>             (rotate (vector 22.5 0 0))
>             (if (zero? c)
>                 0
>                 (boxen (- c 1)))) 
>         (define (render)
>             (boxen 256))
>         (every-frame (render))
>         
>         It's a pretty simple script - just arranging some cubes in a
>         nice pattern. Works perfectly on my laptop. However, it spins
>         off into the distance really, really fast on the big machine.
>         I've installed 32-bit ubuntu on there, so I wasn't sure if the
>         64-bit element of the hardware would make much of a
>         difference. 
>         Thanks for all this,
>         Gerry :)
>