You can clearly see the values of HSV is 231,34,144
I don’t know if this is a bug or not because HSV only has values of 0-1 btw if this is a bug if any of you are regular please report it to the studio bugs category because I can’t report them
any help?
nope, i don’t get what you mean color3.new
Hue
Sat
Val??
then what is that?
?? same thing HSV 0-1 but that screenshot i showed you should be HSV(?) but in values 0-255+
HSV
is something totally different than what you are thinking of. The only thing that uses 0-1
as their parameters is Color3.new
, which condenses RGB
to a ratio of 1.
HSV
goes up to 255
fromRGB
goes up to 255
new
goes up to 1
This is another color
now the Hue is 337… above 255
Im putting the same HSV(Hue,Sat,Val) in to the script editor and it should show something like this:
sorry if this took your time long I’m a bit confused

359 isn’t a value for HSV, it only goes up to 255.
Hue is a main property of colors and even with Color3.fromHSV()
in Lua and what it does is that it ranges from colors like red, blue and to purple like you see in the Select Color property for choosing colors and ranges from 0 to 360 in range like a color-vision with 360 scopes. It’s kind of like this image:
From my understanding and the point of view of the problem, the HSV is showing correct values and nothing like an error due to Sat (Saturation) which ranges up to 255 and goes from colorful to dull and Val (Probably RGB) which is given a red, blue and green componets.
You can see this article and page on how Hue works in studio and in other situations.
@VegetationBush 359 and 360 are values of HSV, it’s confusing at most points but still it gives the same value like how Sat and Val are 255 at max.
Nothing is in error or anything, it’s how Hue works in programming and in the real-world to my colorful knowledge.
Thanks for the info! kinda bit confusing cus once again now it shows a warning “Invalid arguments to Color3 constructor” like the image above TOP’s reply
That is either is a studio bug or just an random error that is thrown because it isn’t well recognized by the script or that it hasn’t been updated too much, I’ll probably look into that and see if this is intentional or an error.
I don’t use Color3.fromHSV()
often nor Color3.fromRGB()
with parts and UI elements often, but understanding it and a bit of practice helps out a lot!