Itoo Software Forum

Author Topic: Updating to FP7 (from 6.xx) has completely killed all of my existing scenes  (Read 388 times)

Richard7666

  • Newbie
  • *
  • Posts: 7
Anything with FP in it is now unusably slow while the FP objects are visible. I suspect there has been some change (I notice that all my objects are now permanently visible rather than just in the current camera's FOV) so maybe something to do with that?
Unfortunately, trying to toggle 'limit to visibility' causes Max to hang.

These scenes all worked fine yesterday.
3ds Max 2020


Any pointers much appreciated,



Thanks :)
« Last Edit: March 14, 2021, 07:07:13 AM by Richard7666 »

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3699
    • iToo Software
Hi,
We have changed the camera system in FP7, and now the plugin doesn't link to a Camera object, but get the view data directly from viewport or render.
Anyway, the "Limit to Visibility" feature should work in the same way. There is also a checkbox to enable it on viewport.

Please, would you send us a simplificated scene to check it ?

Carlos Quintero
iToo Software

nubo

  • Newbie
  • *
  • Posts: 20
I'm experiencing an issue with Vray stuck updating instances while rendering.

Tested on 3DSmax Design 2015 + Vray 3.7 and 3DSmax 2018 + Vray 5.
Same result in both cases, scenes that were previously rendering properly with FP 6.x are now unable to get through this "updating instances" phase.
Also tested with material override on everything and with displacement globally turned off, so it's got to be related with the plugin.
Worth noting, that we used camera limit to visibility on many FP objects.

Moving to older version for now.

Best regards,
Przemek

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 3122
    • iToo
I'm experiencing an issue with Vray stuck updating instances while rendering.

Best regards,
Przemek

Would you please send us a Your scene to check it ?

Rokas
iToo Software

FI6242

  • Newbie
  • *
  • Posts: 20
we have same problom here max 2021 vray5

b.r.
ran

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 3122
    • iToo
Hi please, send us Your scene to investigate, we have not got any yet.
Rokas
iToo Software

Ramboll

  • Jr. Member
  • **
  • Posts: 67
Same with us. Scene keeps freezing after updating to FP7, simple operations like hide/unhide and saving the scene now seem to put MAX in freeze, sometimes for 1 or several hours. Will try to downgrade again

Ramboll

  • Jr. Member
  • **
  • Posts: 67
After downgrading I seem to have lost all my custom FP objects, the FP objects are now empty...?
I see that FP7 messes up my old scenes in many ways, evewn loading and saving. After downgrading everything works faster

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3699
    • iToo Software
Quote
After downgrading I seem to have lost all my custom FP objects, the FP objects are now empty...?

I'm afraid that Custom Edit objects are not backward compatible with FP6. We have to modify the save format to add new parameters.

We continue investigating the performance issue that several of you reported, but until we could not reproduce it.
Please note that we may be dealing with different problems here. I suggest you create separate posts for each issue, and please send us your scenes as requested above.

Thanks,

Carlos Quintero
iToo Software

JG9382

  • Newbie
  • *
  • Posts: 6
So am I right in assuming from the above post, that FP7 is NOT backwards compatible with FP6?
That seems like a critical piece of information, did I miss this in the documentation?

If someone with FP7 opens and save a max file - when someone with FP6 opens the scene, all the forest objects are gone.
Is there a work around for this or suggestions? If the scene is saved again in 6 you lose all the objects.  :o

Cheers

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3699
    • iToo Software
As general rule we don't provide backward compatibility. It may work or not, depending of the changes, but is not supported.

In this case, FP7 objects using Custom Edit mode are not compatible with FP6, because the items save format is different (include more values).
Unfortunately there is not workaround. To make it compatible, we should save the items in both formats (FP6 and FP7), duplicating the size in file. We have not plans to do it.

But usually new versions includes many other changes (i.e. new 3DS Max parameters), which may cause unexpected behaviours.
For this reason we don't test or support backward compatibility. Also this is considering only the immediately previous versions... but there are tons of FP releases, with multiple differences between them.

On the other hand, we just published Forest 7.0.8, which should solve all issues commented in above posts. But if there is some problem yet, please tell us.

Carlos Quintero
iToo Software

Richard7666

  • Newbie
  • *
  • Posts: 7
Hi,
We have changed the camera system in FP7, and now the plugin doesn't link to a Camera object, but get the view data directly from viewport or render.
Anyway, the "Limit to Visibility" feature should work in the same way. There is also a checkbox to enable it on viewport.

Please, would you send us a simplificated scene to check it ?

Simply because I only have one workstation and can't afford to be out of action, I might leave it to someone else with similar issues to send a scene.
 I've reverted to FP6 in the meantime.
Will send a scene if I have time.

Sounds like my issue was this one that you've fixed in 7.0.8
Fixed continuous updating of Interactive Render when using Camera->"Limit to Visibility".
   * This bug would also affect general performance when camera clipping is enabled on viewport.
« Last Edit: March 19, 2021, 11:46:44 PM by Richard7666 »