Itoo Software Forum
Forest Pack => Forest Pro (*) => Topic started by: Sketchrender on June 15, 2018, 11:00:39 AM
-
and it's stuck at 33% for 10 minutes.
V6
Worked fine yesterday.
I open the file this morning and the above kicks in.
any reason why? I con spinning nothing happening?
Help
Please thank you
phil
-
It might have been a temporary glitch. Have You tried to cancel and retry ? Is it always the same ?
-
Restarted , seems to have gotten rid of it.
-
Same problem here..... Restart didn't solve the problem. Stuck at 0 % for half an hour now :(
-
Thank You all for reporting.
In case of trouble downloading packages please cancel the operation and try again in few minutes.
-
Hey,
I have the same issue here.
When I try to open a scene in 3ds Max 2019 that I created with Forest Pro in 3ds Max 2017, ist says "Forest Pack is collecting Maps" and just stays at 50%.
I cannot say if this happens with every scene, I just figured it out with this one. And it only occurs in 3ds Max 2019. In 2017 the scene can be opened as usual.
-
Hi,
I could not replicate any misbehaving objects.
It would help us if You could send us your simplified scene (https://forum.itoosoft.com/faq/how-to-send-a-file-to-itoo-software/)
-
Mysteriously I too cannot replicate this issue today. Everything seems to be working just fine...
-
It would help us if You could send us your simplified scene[/url]
I'll send you mine after the weekend
-
same here.. I cant open anymore my scenes... stuck on "forest park is collecting maps"... opening on 3dsmax 2017, scene saved in 2017 too. Yesterday all was fine, no change in 3dsmax nor forestpack
-
Can you stop the collecting process, clicking the "Cancel" button in the progress bar, or does it freeze Max ?
If the this feature is causing problems, you can turn it off setting collectTexturePaths=0 in forestpack.ini, which is stored at:
C:\users\<user name>\AppData\Local\Autodesk\3dsmax\<max version>\ENU\en-US\plugcfg
-
Same problem hier.
"Forest is collecting maps" freeze at 20%... This is very annoying.
Max 2016, windows 7
-
What the "Collecting maps" process does, is to search recursively in all Library paths, for folders with name "maps".
Next, these folders are added to Customize->User Paths->External files. This is required so Forest can locate the library textures automatically, without you have to add all "maps" manually.
With the default libraries installed on the local drive, the checking process should not take more than a few seconds.
But if you have many library paths, with tons of folders within them, the process may take a while to respond.
It may even worse if you use Network paths, because there is a delay to locate and open each folder.
And if some of the paths is not accessible (for example, pointing to a missing network node), Windows may freeze some time until it reaches the timeout.
Unfortunately, since this problem depends exclusively of each particular Library configuration and infraestructure, there is not much we can do.
If you are experiencing this issue, we suggest to disable the collecting maps feature, as suggested above.
The folders in which Forest searches the maps, are those defined in Library Browser->Preferences->Paths.
-
This should be off by default. We just lost hours on end dealing with this.
People would lose less time and money using scripts like "Relink bitmaps" or "Collect Asset" to find the maps, rather then have your software search every folder on our network and local disks.
-
I understand your position, but our problem with this is that many of our users don't know these tools.
They just want to import from the Forest library and render (specially when using the standard libraries).
To alleviate the problem, for the next FP7 beta we moved this option to General->Settings, and added a new option to exclude the Network paths from the scan process (enabled by default).
I hope that helps.
-
This should be off by default. We just lost hours on end dealing with this.
People would lose less time and money using scripts like "Relink bitmaps" or "Collect Asset" to find the maps, rather then have your software search every folder on our network and local disks.
I agree with this.
-
This should be off by default now. Why am I dealing with this in April 2023??
-
This should be off by default now. Why am I dealing with this in April 2023??
We cannot set it off by default, because that would be a problem for our less experienced users.
Many of them doesn't know how to assign texture paths, or use the Relink tool. They just want to load the library assets and render.
Same applies for the render nodes, which require that texture paths are correctly configured.
Really this is a tricky issue, and i know it may be a problem for more experienced users.
We'll take a look to this again, to see if there is some way to solve the issue for both parties.
Thanks for your understanding.