Recent Posts
61
RailClone Pro (*) / Re: Compatible Versions ?
« Last post by Ricousto on April 08, 2024, 11:19:34 AM »Thanks a lot !
I totally understand but yeah, it would be a great point to find a "universal" way to share all librairies regardless of the version used
Cheers
I totally understand but yeah, it would be a great point to find a "universal" way to share all librairies regardless of the version used
Cheers
62
Forest Pro (*) / Re: Updates and more efficient handling of scattering
« Last post by iToo on April 08, 2024, 10:33:47 AM »Hi,
I'm sorry you had a bad experience using Forest Pro. We'll will try to attend each one of these issues:
Please, send us the minidump when it crashes. This is the only way we have to identify the problem.
Using minidumps we could solve recently a couple of issues related with IPR. One of them was fixed by Chaos (fix should be included in their latest builds), and other in our side (it will be included on next FP update).
Interactive Render modes are very tricky, because 3DS Max (and plugins) have not a standard mechanism to support them.
So each render engine implements their own methods, and it's a continuous work of trial and error adding workarounds (both in Forest and the render engine).
Sorry, i don't understand this. What limit do you mean exactly ? Does Forest show any message about that ?
You can find a detailed explanation about what Density Limit means here.
This limit was introduced to avoid to create huge distributions. Anyway, you can disable it setting Distribution->Image->Max.Density to 0. Same from Display->Render->Max Items.
Initially Forest was designed to use this distribution mode (using images), because it's more efficient to scatter large areas:
a) We can create separated scattering threads, each one rasterizing a row of the image.
b) When applying Camera limit, it let us to remove large areas of the image (outside of the camera frustrum), without rasterizing them.
Other scattering plugins use a different method, with a fixed number of scattered items. But doing this, each item must be checked with the bitmap, the camera and the spline, and then decide to use or discard it.
We evaluated to include this method as an alternative mode in 'Distribution'. But it would be confuse for users, because it's very similar to the current procedure, and Forest has many options in the interface already.
in the other hand, we cannot remove or replace the original 'image' mode, because we must keep compatibility with existing scenes.
That is not normal. Does it happen each time you open the interface, or only the first time ?
Depending of that, it would a problem with the own interface, or the license loading (which is done only one time).
We know there was a problem of slow interface related to Threadrippers and dual CPUs (as described here). But it should not happen with current CPUs.
I'm sorry to hear that.
We continue working on the plugin and improving it, but unfortunately we also are limited by some factors (as compatibility with the existing work, or issues related with render engines).
Quote
I've been working on a project heavily featuring Forest Pro for a large landscape with a vehicle driving along a road. It is a very painful experience.
I'm sorry you had a bad experience using Forest Pro. We'll will try to attend each one of these issues:
Quote
Maybe I'm just not that efficient at using it but I find that it crashes Max a lot when using Vray IPR. Any small change will just instantly crash Max, mostly related to the forestcolor shader.
Please, send us the minidump when it crashes. This is the only way we have to identify the problem.
Using minidumps we could solve recently a couple of issues related with IPR. One of them was fixed by Chaos (fix should be included in their latest builds), and other in our side (it will be included on next FP update).
Interactive Render modes are very tricky, because 3DS Max (and plugins) have not a standard mechanism to support them.
So each render engine implements their own methods, and it's a continuous work of trial and error adding workarounds (both in Forest and the render engine).
Quote
For animations it is very hard to know if the entire animation will feature an error as the view changes...will the forest max limits be reached? Surely some kind of checker for an animation should be included to make sure this doesn't happen otherwise you have to manually check frames. It is hard to know which frame might pass the threshold.
Sorry, i don't understand this. What limit do you mean exactly ? Does Forest show any message about that ?
Quote
Another annoying issue is, why am I getting dialogue telling me to change X & Y density rather than allowing me to up the items. I have 256gb on my pc and I'm not really understanding why there would be such fixed limits on the amount of items displayed at render time.
You can find a detailed explanation about what Density Limit means here.
This limit was introduced to avoid to create huge distributions. Anyway, you can disable it setting Distribution->Image->Max.Density to 0. Same from Display->Render->Max Items.
Quote
Finally, the way that forestpro always seems to have worked is it will even take into consideration an item in the black part of the mask. Surely after all this time the code could be made more efficient and improved upon. It seems like ForestPro hasn't really evolved much at all over a number of years.
Initially Forest was designed to use this distribution mode (using images), because it's more efficient to scatter large areas:
a) We can create separated scattering threads, each one rasterizing a row of the image.
b) When applying Camera limit, it let us to remove large areas of the image (outside of the camera frustrum), without rasterizing them.
Other scattering plugins use a different method, with a fixed number of scattered items. But doing this, each item must be checked with the bitmap, the camera and the spline, and then decide to use or discard it.
We evaluated to include this method as an alternative mode in 'Distribution'. But it would be confuse for users, because it's very similar to the current procedure, and Forest has many options in the interface already.
in the other hand, we cannot remove or replace the original 'image' mode, because we must keep compatibility with existing scenes.
Quote
I am of course only listing these frusrations because I would like to see improvements but it really has been a series of crashes and waiting times with this plugin....including the interface which can take over 15 seconds to appear sometimes...
That is not normal. Does it happen each time you open the interface, or only the first time ?
Depending of that, it would a problem with the own interface, or the license loading (which is done only one time).
We know there was a problem of slow interface related to Threadrippers and dual CPUs (as described here). But it should not happen with current CPUs.
Quote
With such high subscription prices and the amount of customers you have I'm somewhat dissapointed with how Forestpro works these days.
I'm sorry to hear that.
We continue working on the plugin and improving it, but unfortunately we also are limited by some factors (as compatibility with the existing work, or issues related with render engines).
63
Forest Pro (*) / Re: 3dsmax2025 >>> release time:
« Last post by ENJAMIN on April 06, 2024, 03:40:21 PM »we know - vantage ius so tempting tho yu reaslise ? & why do i now have two forum accounts - was my original oner to annoyoing? sorry 
64
RailClone Pro (*) / Re: Compatible Versions ?
« Last post by iToo on April 06, 2024, 10:00:19 AM »Hi,
Due to the Autodesk licensing policy for third-party developers, we have licenses only for the latest 3DS Max release, and five versions before.
At this moment, that includes Max 2020 to 2025 (our license of Max 2019 just expired... we must update our documentation).
We can provide compatibility with old Max versions (as 2013), just compiling the plugins with the appropiate Max SDK.
Although we cannot test them or provide support, at least the plugin is available for customers who need it.
But libraries is a different issue. Since they are saved using Max files, we have not way to create them for old versions.
Some RC libraries were created years ago, and are compatible yet. But latest libraries (and the revamped ones) load only with recent Max versions.
We are working to create a custom portable format, and migrate all libraries. That will solve this limitation completely. But it will take some time yet.
Due to the Autodesk licensing policy for third-party developers, we have licenses only for the latest 3DS Max release, and five versions before.
At this moment, that includes Max 2020 to 2025 (our license of Max 2019 just expired... we must update our documentation).
We can provide compatibility with old Max versions (as 2013), just compiling the plugins with the appropiate Max SDK.
Although we cannot test them or provide support, at least the plugin is available for customers who need it.
But libraries is a different issue. Since they are saved using Max files, we have not way to create them for old versions.
Some RC libraries were created years ago, and are compatible yet. But latest libraries (and the revamped ones) load only with recent Max versions.
We are working to create a custom portable format, and migrate all libraries. That will solve this limitation completely. But it will take some time yet.
65
Forest Pro (*) / Re: 3dsmax2025 >>> release time:
« Last post by iToo on April 06, 2024, 08:29:01 AM »Hi, we're working on it.
Our plan is to release Forest 9 beta very soon, together a RailClone update, both with support for Max 2025.
Our plan is to release Forest 9 beta very soon, together a RailClone update, both with support for Max 2025.
66
Forest Pro (*) / 3dsmax2025 >>> release time:
« Last post by ENJAMIN on April 06, 2024, 01:37:08 AM »gday
as usual we will keep annoying you
as usual we will keep annoying you
67
Forest Pro (*) / Updates and more efficient handling of scattering
« Last post by steve3duk on April 06, 2024, 12:12:59 AM »Hi there,
I've been working on a project heavily featuring Forest Pro for a large landscape with a vehicle driving along a road. It is a very painful experience.
Maybe I'm just not that efficient at using it but I find that it crashes Max a lot when using Vray IPR. Any small change will just instantly crash Max, mostly related to the forestcolor shader.
For animations it is very hard to know if the entire animation will feature an error as the view changes...will the forest max limits be reached? Surely some kind of checker for an animation should be included to make sure this doesn't happen otherwise you have to manually check frames. It is hard to know which frame might pass the threshold.
Another annoying issue is, why am I getting dialogue telling me to change X & Y density rather than allowing me to up the items. I have 256gb on my pc and I'm not really understanding why there would be such fixed limits on the amount of items displayed at render time.
Finally, the way that forestpro always seems to have worked is it will even take into consideration an item in the black part of the mask. Surely after all this time the code could be made more efficient and improved upon. It seems like ForestPro hasn't really evolved much at all over a number of years.
I am of course only listing these frusrations because I would like to see improvements but it really has been a series of crashes and waiting times with this plugin....including the interface which can take over 15 seconds to appear sometimes...
With such high subscription prices and the amount of customers you have I'm somewhat dissapointed with how Forestpro works these days.
I've been working on a project heavily featuring Forest Pro for a large landscape with a vehicle driving along a road. It is a very painful experience.
Maybe I'm just not that efficient at using it but I find that it crashes Max a lot when using Vray IPR. Any small change will just instantly crash Max, mostly related to the forestcolor shader.
For animations it is very hard to know if the entire animation will feature an error as the view changes...will the forest max limits be reached? Surely some kind of checker for an animation should be included to make sure this doesn't happen otherwise you have to manually check frames. It is hard to know which frame might pass the threshold.
Another annoying issue is, why am I getting dialogue telling me to change X & Y density rather than allowing me to up the items. I have 256gb on my pc and I'm not really understanding why there would be such fixed limits on the amount of items displayed at render time.
Finally, the way that forestpro always seems to have worked is it will even take into consideration an item in the black part of the mask. Surely after all this time the code could be made more efficient and improved upon. It seems like ForestPro hasn't really evolved much at all over a number of years.
I am of course only listing these frusrations because I would like to see improvements but it really has been a series of crashes and waiting times with this plugin....including the interface which can take over 15 seconds to appear sometimes...
With such high subscription prices and the amount of customers you have I'm somewhat dissapointed with how Forestpro works these days.
68
Forest Pro (*) / Re: ForestPack display count doesn't work with limit to visibility enabled
« Last post by ZO6039 on April 05, 2024, 07:51:26 PM »Ah, ok, this what I usually do. But I thought there is a checkbox in FP somewhere to keep FP hidden until render.
69
RailClone Pro (*) / Compatible Versions ?
« Last post by Ricousto on April 05, 2024, 05:39:35 PM »Hi,
Many models are taken from 3ds max 2018 (20000) in the Railclcone library.
It's indicated that Railclone is compatible with 3ds Max 2013 - 2024 (official support from 2019).
I understand that it is an official support from 2019 but for all that, the models come from 3ds max 2018.
So my question is relatively simple, why aren't the models in the library compatible with the same versions of 3ds max for Railclone (i.e. max 2013-2024) ?
Thanks
Many models are taken from 3ds max 2018 (20000) in the Railclcone library.
It's indicated that Railclone is compatible with 3ds Max 2013 - 2024 (official support from 2019).
I understand that it is an official support from 2019 but for all that, the models come from 3ds max 2018.
So my question is relatively simple, why aren't the models in the library compatible with the same versions of 3ds max for Railclone (i.e. max 2013-2024) ?
Thanks
70
Forest Pro (*) / Re: ForestPack display count doesn't work with limit to visibility enabled
« Last post by Michal Karmazín on April 05, 2024, 12:34:36 PM »You can simply hide it (for example, by using the Hide Selection) or use the Forest Lister for these purposes to manage the Display - Build - Disable Object option (accessible also by Maxscript $.disabled = on / $.disabled = off). I hope that helps.
Best regards,
Best regards,
