Itoo Software Forum

Forest Pack => Forest Pro (*) => Topic started by: DT on September 11, 2019, 05:16:35 PM

Title: Forest Pack Command Panel very slow to open.
Post by: DT on September 11, 2019, 05:16:35 PM
Well the title says it all. It doesn't matter if it's a fresh scene, with an empty forest pack object or a complex scene with an FP object with some trees. It takes at least 30(!!) seconds to open the whole command panel menu. Surely that's way too long?
Title: Re: Forest Pack Command Panel very slow to open.
Post by: Rokas on September 11, 2019, 07:50:40 PM
Hi

We had a case where some JAVA written application was running in the background and slowed Forest UI a lot for  some user.

Please try to close all running processes (check the icons in the Windows taskbar). And try Your scene again.
That seems to help for some of our users with similar problem. If that helps then start closed applications one by one and identify which causes the slowdown.
Thanks in advance for any further comments on this issue you can share with us / our user community (in case some user(s) will run into similar troubles).

Best regards,
Title: Re: Forest Pack Command Panel very slow to open.
Post by: JS3859 on September 17, 2019, 08:22:26 PM
hello , I have the same issue with 3dsmax 2020 and forestpack pro 6.22 i tried to stop most of the start up applications and besides i checked my pc if there any JAVA apps , but there is nothing , and the problem stil the same
Title: Re: Forest Pack Command Panel very slow to open.
Post by: Bobby Parker on September 17, 2019, 09:46:42 PM
Same here... a good minute before it opens.
Title: Re: Forest Pack Command Panel very slow to open.
Post by: JS3859 on September 18, 2019, 03:16:34 PM
any one of you guys solve this problem yet , please comment
Title: Re: Forest Pack Command Panel very slow to open.
Post by: Michal KarmazĂ­n on September 18, 2019, 04:39:53 PM
Hi,

Sorry to hear you're facing these troubles. Would you mind to specify your actual software configuration (also the OS & renderer versions used)? Up to now, we can't reproduce this problem here and any additional info is welcome. Meanwhile, please feel free to have visible just some roll-outs (these you are frequently using) - you can edit the Global Settings from the General rollout as desired (attaching screen-shot) to check if that helps. Thanks in advance for any further comments on this issue.

Best regards,