Whenever I scroll through explorer, and sometimes selecting a script by right clicking a script’s tab and pressing “Show in Explorer”, I get this error:
I also had this error before all of this happened, and it happens right after I join the team create session (alone, i’m the only one online on it)
Everytime I scroll, the error pops up again in output window. Some instances can be selected and some instances cant,
I’ll admit, my pc is pretty low end, 4GB ram installed
This also seems to happen consistently on this place only, out of all other places.
My studio settings:
Expected behavior
I would expect that explorer works normally as i scroll through it, or whenever I press “Show on Explorer” after rightclicking a script’s tab, etc.
1 Like
Is there anywhere I could share the placefile privately?
Hi, thanks for the report!
- Have you ever seen this error without Team Create?
- How often does this happen?
- What is your Explorer version (it can be seen in the title bar)?
Also, you can PM the place file to me.
1 Like
- So far, no
- It has only started happening today, but it happens really frequently. Almost every other time
- Its v0.25
Everytime I upload the file it fails, but I’ll keep trying again
1 Like
Got the same error again on a Team-Create enabled place
I suspect this has to do with how changes are synced in team create? Nobody was editing at the time though, and I immediately got the error upon joining
Note that it says “Double connection with Edit” at first
This was in a different place but under the same group
Same issues as I stated, scrolling will spam the output log. I realized though that scrolling, selecting and expanding / collapsing instances have different tracebacks, so maybe that will help
Selecting:
Expanding and Collapsing:
Scrolling (or when explorer window is resized horizontally, happens whenever I change the other views’ sizes, and explorer’s view):
Expanding and Collapsing trigger a Scrolling traceback right after as well
We’re pretty sure we fixed this. Thanks!
1 Like
So far I’ve not encountered it again while using the new explorer!
1 Like
