First, I would like to start off by saying I am using the Beta (4008) and I know that bugs are expected (No complaints there)!
- Crash: I am not sure what causes it to happen, but sometimes World Machine 4008 hangs (I can still interact with the UI sometimes, but none of the views update). Usually this results in needing to kill the program myself, or a crash.
- Crash Recovery: After a crash, reopening the project (Previously saved version) will often fail to update any views other than the node graph. If I lock a node for viewing, it shows. If I unlock the node again, I lose all visibility on previews and such.
- Miscellaneous: Not sure if this is related to any of the above, but in the console I get a lot of “libpng warning: bKGD: invalid” messages.
- Macros: Macros are great, but I wonder if I am just missing something, or if they are not as full featured as the base nodes. I would like to request that they become more in line with the base nodes.
- Base nodes can have an offset in the top right corner, where Macros cannot.
- Base nodes can change the upper bound of distance/elevation above the project maximum. I feel like these are pointless inputs for Macros since scalar works from 0.0 - 1.0 (And you can imagine them working between minimum and maximum range). If there would be a way for us to match the expected input (Advanced Noise, for instance, has a value that works from 0 km to 1024 km, even if the project is much less) so the macro UI can match the internal UI, that would be awesome. Currently we can’t have a set range for distance/elevation, which is odd for a program that generally works with units (km or m) instead of normalized input.
- Base nodes can have a mask input on the bottom, macros cannot?
- We are missing inputs that the base nodes have (Specifically, integer input without a slider).
I feel like macros should kind of mimic the included base node format so the community can possibly help expand “the arsenal” available, while leaving usability consistent.
Just some ideas, and if any of this is present already… I may have just missed it and I apologize!