Eduard

Hello Stefan, I answered you in a personal message. In the future, if you've similar questions, please write to us by email, we'll respond faster. Thanks!

Hi lukx, Thank you for helping us find this bug! Some changes were made in 3dsMax 2022 that resulted in these glitches when calculating path lines. We've updated version 1.9.9 SP10 for 3dsMax 2022, as well as version 2.0, which includes version 1.9.9 SP10. Thanks again!

Hello Pawel, Yes, if you want to upgrade to version 2.0 you need to login to your User panel account and renew your license. For more info please see our Maintenance Subscription FAQ. Thanks!

Hello HojjiPojji, Maybe you should try to create a Vray proxy? Will they work with forest pack? Thanks!

Hi Szymon, We've fixed this problem, and I've sent you an update by email, please check. Thanks!

We'll try to restore these MaxScript functions, but maybe it will change and will work as with nodes. It's just that the system has been completely changed, and now instead of different components we've nodes of different types with continuous numbering. Thanks!

Hi Trung, Ok, I sent you an educational license offer. Thanks!

Hi Diego, Please try to activate again, I've renewed your license to the latest date of beta version. Thanks!

Hi Diego, To download the 2.0 beta version, please open the Previous versions section: Thanks!

Приветствую! Ок, сделаем. Также можно будет добавить кнопку для выделения ноды, чтобы найти ее в редакторе, так сказать. И еще, меня просили добавить такой же менеджер для нод Value. Имеется ввиду ноды Public? Если да, то проблем нет, сделаем. Все-таки каждый параметр имеет свои лимиты, и можно будет их использовать. Но это будет работать только при создании новой ноды из какого либо параметра. Если просто подключать уже существующую ноду, то ничего изменяться не будет. Спасибо!

Hi Yang, We used the Cylinder Mesh with Radial offset curve. You can see this example: Dir_Twist_1.max Thanks!

Hi Timursq, I always recommend connecting Wind nodes to After Mesh Modifiers, most likely this is the problem. Please try the modified file: Thistle_A_07_1.zip Thanks!

Hi Solice and Jędrzej, I've sent you our offer for an educational license... Yes, you can use it for commercial work. With the release of version 2.0, we've introduced annual maintenance. This is for updates only, but the plugin will work even if your license expires. You'll be able to use, also download and activate versions released while your license was valid. After the first year of use, you can renew your subscription for the same price as an individual license. Thanks!

Hello John, Unfortunately, our product is implemented as a plugin for 3dsMax. But in the future we also plan to create a standalone application. Thanks!

Hi Gianni, Ok, I've sent you our offer for an educational license... Thanks!

Hi HHbomb, We've released this version, and now you can download it. Thanks!

Yes, you can use version 1.9.9, and there is no this bug. Thanks!

I don't know exactly how long it will take to fix this. As a solution, you can set Levels = 1 in the Path distributor node. But then you need to copy the path with all accompanying nodes, to keep the multilevel branches. Thanks!

Hi anujraghav, Yes you're right, it seems the new random system has some problems. We'll investigate this and fix it asap. Thanks a lot!

Hello schellicon, I've sent you a download link so you can try this version. I hope we'll release this version this week. Thanks!

Corona and FStorm renderers work with GrowFX Demo. VRay should work as well (but I haven't tested it now). Other renderers hopefully will work too, but I haven't tested it. You can try it yourself using their demo version. Thanks!

Hi tsuda, I checked the GrowFX full version, and it renders perfectly: But I checked in the demo, and due to limitation on converting to mesh, Redshift will not render the object. Thanks!

Hi INCO, I've sent you our offer for an educational license... Thanks!

Hi Terri, As I understand it, you need to set Turn axis = 180 degrees in the Path distributor settings. Thanks!

Hi Terri, I posted this in August 2020, so this fix is included in 1.9.9 SP10. Please send me your scene file, I'll check it. Thanks!