The new NodeBox forum is live! Everything from support.nodebox.net moved here: sign in with the same email to pick up your old posts. Something not working? Write to forum-support@nodebox.net.

NodeBox 3

NodeBox 3.2.0 Released

1 reply Last reply

  1. NodeBox team

    NodeBox 3.2.0 is much more responsive when you drag a parameter, and it fixes the compound node. Download it from nodebox.net/download.

    • NodeBox caches every node's result and only reruns a node when its inputs, parameters or code change. Big networks stay smooth while you drag.
    • Rendering runs on a background thread, and memory stays bounded during long animations and exports.
    • Compound gives the same result as in 3.0 again. In 3.1 it could cut shapes in two.
    • The SVG import node handles more Illustrator files (thanks @zacaltair).
    • Reload (Cmd-R) picks up code changes, and imported files are reread when they change on disk.
    • UI tweaks: pasted nodes land where you're looking. Movie export lets you pick the frame rate. Handles keep their size when you zoom.

    Important: if you write your own Python or Clojure nodes:
    A function now runs only when something it depends on changes. Don't modify the objects you receive (clone them first). If your function reads the clock, the network, a device or unseeded random, mark it time-dependent:
    In Python:

    my_function.timeDependent = True
    

    In Clojure:

    ^:time-dependent
    
  2. edited

    Frederik,

    Yay! Version 3.2.0 is a wonderful improvement. Not only does it fix the compound error, it also implements all three of the UX fixes on my wish list.

    I made a quick network to confirm the UX fixes. MUCH better. Thank you.

    I also did a torture test for quick evidence that the upgrade to 3.2.0 didn't break anything. I used 3.2.0 to render my notorious Cartan Library Poster. Huge PNG here:

    cartan_node_library.png

    This image outputs the results of over 200 diverse demos, many of which test Nodebox in unusual ways. 21 of these demos call Python modules and one calls a Clojure module. The combined poster is as big as a PDF can be; as a PNG it weighs in at 12 megs.

    I am delighted to report that it rendered under 3.2.0 with no errors. I scanned the output and all the demos look correct to me (including one which broke under 3.1.0).

    The render time on my MacBook M3 Pro was faster than 3.0.52, but just a tad slower than 3.1.0:

    3.0.52. - 34 secs

    3.1.0. - 23 secs

    3.2.0. - 25 secs

    So everything looks good so far. I'll keep playing with it and if I run into any issues I'll let everyone know.

    Yay!

Know something that helps?

Sign in with your email address to reply. No password needed.

Sign in to reply