mattieserver
mattieserver
Thanks for reporting this. I will look into what could cause this but i am not sure if i will be able to provide a solution as the graph itself...
It is indeed vis.js, or only the network part (vis-network). I believe I used the latest version, unless they released a new version in the last week.
I managed to reproduce the bug, but only if i have set the custom field 'coordinates' for some devices. Do you use that custom field?
All devices are stacked on top of each other then. I will check if i can use another solver, now its 'forceAtlas2Based'.
I cannot change the physics to another type because then the coordinates within the plugin would be 'incorrect'. So it seems like we are stuck.
Hi, I will add an extra option do always save the coordinates. The coordinates are not enabled by default because the custom field that is needed. In my use case,...
Hi, I will add support for this in the next release (so for netbox v3.3)
See the documentation from [netbox-docker](https://github.com/netbox-community/netbox-docker/wiki/Using-Netbox-Plugins)
This is similar to #23 , but i can currently not provide a fix
@martydingo , can you check if your issue is resolved?