Enscape Create View Skp Shadows ON

I just recently discovered that when you use the Enscape “create view” it turns on skp shadows in the view. I did not realized this and so I am trying to edit things with enscape running and shadows in skp. I thought my video card was crashing but it was just trying to do too much. Now that I know this it likely solves many of my crashing / ridiculously slow problems that I could not understand prior to realizing this is how enscape views are created. I never have shadows turned on in my skp scenes so it did not occur to me that this could be the issue.

I am wondering why it does this? I can’t see what the value of it would be? Regardless I hope it is something Enscape considers changing in the future, but it is an easy fix now that I realize the problem.

It’s been asked for before; Seemingly the connection between SU and Enscape (the API) only allows a limited amount of information to be set/passed between them.

When you click on the button to create the view in SU it does not immediately activate this scene, so you can (if you have the Scene tray-dialogue open) un-tic all the boxes except ‘camera location’.

(BTW “Shadow Settings” also contains the time-of-day setting, so if this was changed in Enscape it will have to remain ticked to keep it within SU, even if you don’t want any of the other settings on the Shadows tray-dialogue to change.)

Thanks for your post @Gadget_1 . :slight_smile: As he mentioned, @dvsone1440 , this behavior is persistent due to technical limitations I’m afraid. I hope that Gadgets information is an additional help to my reply. Let me know if there is anything else I can help you with! :slight_smile:

Understood.. I found that post after I posted this. Its only an annoyance once you udnerstand the behavior.. It was just not understanding it that really caused issues.. would be good if there was a way to highlight it for new users.. pop up maybe or something that warns people. I was crashing for days not noticing the shadows were on.

@dvsone1440 Thanks for your feedback. I’ve added it to our knowledgebase agenda.