3.4 extreme loading and bad quality

Quote from jlo

So to be clear, it is not in the current version that keeps alarming me when i start SKP? I should wait until a later update?

Good that its getting resolved either way.

Pardon me jlo I must have missed your post - Please indeed wait a little longer until this will be resolved with a preview or service pack.

Herbo , wishing I had better news right now but I'm afraid the fix for this specific problem has not quite made it into Preview 8. Be assured that our Devs are doing their best to resolve this entirely though as quickly as they can. Thank you for a bit more patience!

Yet another brief update: The fix for this problem will be included with our next upcoming service pack releasing soon - As always, you'll be notified via Enscape and this forum.

Demian Gutberlet

Will this be a service pack for 3.4 or addressed in the next release?

Quote from renderwiz

Demian Gutberlet

Will this be a service pack for 3.4 or addressed in the next release?

The service pack will be released for 3.4 - before our full release Enscape 3.5, in which this behavior will be resolved as well of course.

hi Demian Gutberlet just wondering when the service pack is out and when 3.5 is planned for

I'm not convinced that proxies are the only cause...

Have some large sites brought into Revit via InfraWorks > FormIt Pro > Revit. In Infraworks, I replaced some of the generic buildings with specific ones that were available in SketchP Warehouse. With 3.4, I'm getting many more situations where Enscape will crash while loading.

I've found that using the Temporary Hide in View of the site model works to launch Enscape and get the live rendering view. Then I can reset the temporary hide and the site comes in as desired. Renders and navigation seem pretty normal.

I don't have any items that are created as proxies between Revit families and the Enscape assets.

It's happening across several different models.

Quote from hbc_visual

hi Demian Gutberlet just wondering when the service pack is out and when 3.5 is planned for

The latest service pack we've released this Wednesday should resolve this behavior:

Enscape 3.4.3 Service Pack

You can acquire the update directly here as well.

Quote from eeblack

I'm not convinced that proxies are the only cause...

Have some large sites brought into Revit via InfraWorks > FormIt Pro > Revit. In Infraworks, I replaced some of the generic buildings with specific ones that were available in SketchP Warehouse. With 3.4, I'm getting many more situations where Enscape will crash while loading.

I've found that using the Temporary Hide in View of the site model works to launch Enscape and get the live rendering view. Then I can reset the temporary hide and the site comes in as desired. Renders and navigation seem pretty normal.

I don't have any items that are created as proxies between Revit families and the Enscape assets.

It's happening across several different models.

Display More

Please also try our latest service pack update and if that makes no difference, kindly submit a feedback report with your logs and we can investigate this behavior further too. Thanks a lot in advance, and let me know once you've submitted said report ideally.

Load times have improved quite a bit and love the sun adjustment feature. I'm still experiencing crashes about Five today alone and it generally is happening when adding lights to the model while Enscape is Running. I submitted the Log Info and plan to test a few other project files.

Additional note(s):

• When I have a material selected via SketchUp and open the Enscape editor I have to re-sample the material for the settings to appear. This was not the case in 3.2

Quote from jtubb

When I have a material selected via SketchUp and open the Enscape editor I have to re-sample the material for the settings to appear. This was not the case in 3.2

This has been an issue for many versions (I think it started in 3.3) and still seems to be the behavior in the latest previews, sorry to say.

Quote from andybot

This has been an issue for many versions (I think it started in 3.3) and still seems to be the behavior in the latest previews, sorry to say.

Then that makes sense - Hopefully, it gets fixed. It worked before so I imagine it's a very simple solution.

This bug was acknowledged by Demian Gutberlet

See post below.

Material Editor No Longer Starts with Currently Selected Material - Sketchup