Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


wallworm last won the day on March 27

wallworm had the most liked content!

Community Reputation

4 Neutral

About wallworm

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  1. wallworm

    Upgrade Policy And Multithreading

    While I'm a general fan of node-based editors in many situations, and I do look forward to it in the context of GrowFX, I personally appreciate that Eduard and team have been adding new features into the current version. Many new features have saved my ass in the last year as they have been specific tasks I needed to solve and Eduard added them. I 'm personally highly thankful that new features have continued to come along. I look forward to V2. But for me I'm thinking that the node system itself is a big enough feature, by itself, to warrant a new version. I think that GFX has one of the best track records of customer support of any company I've dealt with--and a large reason for that is quick responses of features to solve customer problems.
  2. wallworm

    Surface Distributor > Vertex Color / UV Options

    That's awesome. You're great!
  3. wallworm

    Surface Distributor > Vertex Color / UV Options

    Furthermore, since you might be using masks from other channels (instead of channel 0, you might use another channel like a UVW channel instead), there should be a Channel spinner that defaults to channel 0 (which is the vertex color channel). Changing to channel 10, for example, will use the uvw coordinates as colors. For example, you can use Vertex Paint Modifier to paint vertex colors into channel 10 (or any channel).
  4. wallworm

    Surface Distributor > Vertex Color / UV Options

    I meant to add: So the Surface distributor would need a new Dropdown under the Use Vertex Color checkbox with these options: RGB (default and legacy) Red Green Blue
  5. wallworm

    Surface Distributor > Vertex Color / UV Options

    Eduard, Attached is an example scene. This is a simple example of how the vertex colors might drive a system (in this case, the base blue channel of the vertex colors is displacing the landscape down for the river). The other colors are not used to displace in this example, so are added to the second vertex paint. If you select the object GFX_Ecosystem1 there are three paths: WaterPlants(blue) BankPlants(red) Grass(green) What I'd like is that the distributors allow you to use just that channel for distributing--so in this case the waterplants paths only appear where there are non-zero blue values in the vertex colors. Etc. Notice also if you hit Render you will see that the materials are also using these as masks. (Open slate to see that the texture masks are using R/G/B sub-channels). If the surface distributor could use sub-channels like the material is using, it would make it very easy to populate the plants along the environment easily. Even more valuable is this method used in conjunction with the DataChannel modifier added in 2017.1. In that case, the vertex colors can be driven by the landscape topology--meaning that automatically we can make some kinds of plants only appear on vertical surfaces and others only on flat, etc etc. Having the plants and materials update automatically and together is what I'm looking at accomplishing. Hopefully this makes sense. GFX_vertex_color_example.zip
  6. It would be nice if we could use arbitrary map channels for the Vertex Color. Also, it would be nice if we could use specific rgb/uvw channels. For example, if I want to distribute just from the Red channel of vertex color (or X value in map channel 10).
  7. wallworm

    Object Reaction Graphs

    This works great. Thank you Eduard.
  8. Sometimes it's easy to forget all the exceptions. You can see methods of Structs in Max with showproperties. showProperties polyops :/
  9. Thanks. This helps a lot. Those methods didn't appear when using ShowProperties().
  10. I will share my script for this when done. This is awesome. Thank you again Eduard. A few suggestions/requests: Can we get a couple methods to access the paths/modifiers by index instead of name: gfx.getPath 1 And for the paths, accessing the distributors/modifiers by index as well? (gfx.getPath 1).getDistributor 1 (gfx.getPath 1).getModifier 1 The reason being easier to access dynamic properties by index instead of name. Also, it would be great if meshbuilders (and potentially after mesh modifiers) were also added to this setup. I'd like a few properties added to Path: (gfx.getPath 1).distributorCount --# of distributors in path 1 (gfx.getPath 1).modifierCount -- # of modifiers in path 1 (gfx.getPath 1).meshBuilderCount -- # of meshbuilders in path 1 Finally, how would I instance the parameters? For example, if I can get meshbuilder support, I'd like to be able to instance the meshes among all the paths.
  11. OMG, thank you Eduard!
  12. wallworm

    Object Reaction Graphs

    Thanks Eduard. We are using 2016/2018.
  13. wallworm

    Object Reaction Graphs

    Thanks Eduard Yeah I was grasping at straws with the length affects.
  14. Thanks Eduard. The more MAXScript access to the paths and sub-attributes, the better
  15. wallworm

    Object Reaction Graphs

    It would be nice if the Distance and Max Strength spinners in Object reaction had graph support. Right now I'd like to set a path to use ZERO object reaction until at the very end of the paths and then give it 100%. In this case, the direction is controlled by Spline Dir modifiers and then changes to Object reaction at the very end. I'm considering how to do this currently with affects but it's being problematic for me. If the strength/distance had graph controls, it would be easy to just set the values to 0 until end of graph. My current tests have been to add a Length Affects > Object Reaction Strength with a Factor at 0 for most of the Factor Graph and then setting it to 1.0 for end of graph. But the Object reaction seems to apply to the entire path.