Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Could not get a unique color for 255 #130

Closed
HenrikWerner opened this issue Dec 7, 2020 · 2 comments
Closed

Could not get a unique color for 255 #130

HenrikWerner opened this issue Dec 7, 2020 · 2 comments
Assignees
@StevenBorkman

Comments

@HenrikWerner
Copy link

I get this new log message "Could not get a unique color for 255" (using RC-0.6.0-preview.1). I found that this is printed in InstanceSegmentationCrossPipelinePass.cs and caused by InstanceIdToColorMapping.cs if the instance id is 255. But why is the instance id set to 255 (that is causing this error) and how can this be solved, so that the instance id is not 255?
@StevenBorkman
Copy link
Contributor

Henrik, thanks for the report. This is a bug and we have captured it and are going to work on a fix for this soon. The IDs are set programmatically and the ID for the 255th item added to a scene should certainly be supported. We will update this issue when we have a fix.

@StevenBorkman StevenBorkman self-assigned this Dec 8, 2020
@StevenBorkman
Copy link
Contributor

Hi Henrik,

I have added a fix for the issue that you discovered and it is now in our master branch. The current state of master is our 0.6.0-preview1 release along with this bug fix and some updates to the tutorial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StevenBorkman StevenBorkman

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@HenrikWerner @StevenBorkman