Startup warning: Viewer state type conflict

   4188   11   3
User Avatar
Member
30 posts
Joined: April 2015
Offline
Hi Everyone!
I've been experiencing the following warning on startup in the Console since the last few builds:

= = = Resources registration = = =
Viewer state type conflict: labs::ruler
Conflicting viewer state: C:/Users/xxxxx/Documents/houdini19.0/SideFXLabs/19.0.659/SideFXLabs19.0/viewer_states/ruler.py
Colliding with: C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs19.0/viewer_states/ruler.py

Viewer state type conflict: viewportmeasuretool
Conflicting viewer state: C:/Users/xxxxx/Documents/houdini19.0/SideFXLabs/19.0.659/SideFXLabs19.0/viewer_states/viewportmeasuretool.py
Colliding with: C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs19.0/viewer_states/viewportmeasuretool.py


Clearly it has something to do with duplicate python files. Does anybody know which one is safe to delete?

Thank you.
User Avatar
Member
8041 posts
Joined: Sept. 2011
Offline
I think you have two installs of labs. The one in your documents folder is probably the older one, since the launcher now installs labs in the launcher folder.
User Avatar
Member
30 posts
Joined: April 2015
Offline
jsmack
I think you have two installs of labs. The one in your documents folder is probably the older one, since the launcher now installs labs in the launcher folder.

That's what I thought but chickened out on acting on it. Thank you!
User Avatar
Member
3 posts
Joined: Feb. 2020
Online
I'm getting a similar message with 19.5, except it looks like it's colliding with itself?

Viewer state type conflict: viewportmeasuretool
Conflicting viewer state: C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs19.5/viewer_states/viewportmeasuretool.py
Colliding with: C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs19.5/viewer_states/viewportmeasuretool.py
User Avatar
Member
11 posts
Joined: June 2019
Offline
Im getting this too in 19.5.303

For me its all the kinefx stuff colliding with itself.
Edited by dunnieboy - Aug. 5, 2022 09:37:41
User Avatar
Member
11 posts
Joined: Nov. 2018
Offline
Does anyone know how to fix this?
this issue is freezing my software.
User Avatar
Member
203 posts
Joined: May 2021
Offline
Same happening here. I tried 19.5.303 and 19.5.349.

Viewer state type conflict: labs::ruler
Conflicting viewer state: C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs19.5/viewer_states/ruler.py
Colliding with: C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs19.5/viewer_states/ruler.py

Viewer state type conflict: viewportmeasuretool
Conflicting viewer state: C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs19.5/viewer_states/viewportmeasuretool.py
Colliding with: C:/Program Files/Side Effects Software/sidefx_packages/SideFXLabs19.5/viewer_states/viewportmeasuretool.py
User Avatar
Member
203 posts
Joined: May 2021
Offline
dunnieboy
Im getting this too in 19.5.303

For me its all the kinefx stuff colliding with itself.

Try installing python 3.7 version of 19.5.303. That removed all the kinefx errors for me but I'm still getting errors of 'Viewer state type conflict: viewportmeasuretool' and 'Viewer state type conflict: labs::ruler'

Edit. The stream of errors came back again.
Edited by proceduralist - Aug. 22, 2022 10:32:48
User Avatar
Member
1 posts
Joined: Oct. 2015
Offline
Any further update on this? I'm seeing the same self collision thing thing in 19.5.303.
User Avatar
Member
203 posts
Joined: May 2021
Offline
christopher_lemon
Any further update on this? I'm seeing the same self collision thing thing in 19.5.303.
Same happening with me. Tried installing and running Houdini 19.5.352 but still the same issue.
User Avatar
Staff
445 posts
Joined: Feb. 2018
Offline
I added a fix for the next 19.5 daily build. It looked like these type conflicts were wrong, although I wasn't able to reproduce them. The fix should avoid reporting false type conflicts.
User Avatar
Member
203 posts
Joined: May 2021
Offline
mabelzile
I added a fix for the next 19.5 daily build. It looked like these type conflicts were wrong, although I wasn't able to reproduce them. The fix should avoid reporting false type conflicts.

Thanks a lot! No errors popping up in 19.5.355.
  • Quick Links