Guys,
Logical or not?
Revit.ini has customcolors, hex value. We've got several defined, grey colors with equal r, g and b values. But today I added some pantone colors.
Opening Revit I noticed that the predefined colors are off, not correct. And I noticed that the R value and the B value were swapped.
Making the value correct again, and saving that color to its original position (thus altering the revit.ini file) resulted in a different hex value ... BGR instead of RGB (in HEX value of course).
Can you guys reproduce this?
To me it's quite confusing, a bug.
Tested on
18.2.0.51
20170927_1515(x64)
2018.2
Note: screencast added
AutoDesk don't document the Revit.ini colour format as being RGB, and in fact it doesn't seem to be BGR either, I tried to create some manually and got strange results. Best to create the colours in the front end to get the hex codes you need.
Isn't a hex color a translation of RGB,HSL,HSV or CMYK?
To my understanding it is, so I still think the revit.ini isn't perhaps buggy but perhaps 'unclear' in what to expect.
@MichaelWarwick7522: good to see you get wrong results too. And yes, for now I will go from front end to back end. I'm updating 2017 to 2018 and normally I would base my firm's update upon the same values used in the old version (2017 in this case). Never was an issue (or never noticed since majority are grey scaled equal values).
Perhaps someone @Autodesk could enlighten this issue? Still very strange behaviour.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.