Infinite colours!

You seem to have forgotten that it has absolutely nothing to do with rendering. It takes up more space. Rendering it is irrelevant.

You would still be loading the new 24-bit property that wasn’t there before.

What are you copying and pasting some Wikipedia text here for?

[quote]Techante wrote:
What if everything loaded in Color3, and then only the infinite colours loaded once you got near to them?
You seem to have forgotten that it has absolutely nothing to do with rendering. It takes up more space. Rendering it is irrelevant.
Techante wrote:
So I guess the only way to do it then is to have some kind of settings where you can choose how many colours you have load.
You would still be loading the new 24-bit property that wasn’t there before.
Techante wrote:
Usually, true color is defined to mean 256 shades of red, green, and blue, for a total of 224 or 16,777,216 color variations. The human eye can discriminate up to ten million colors.
What are you copying and pasting some Wikipedia text here for?[/quote]

So is it possible to have one person load a different amount of colours to another person in the same server? Or would it have to be different servers?

Also there’s nothing wrong with copying and pasting, if it’s correct, so don’t start trying to start an argument about it.

He’s asking why the amount of colors the human eye can distinguish is relevant to the conversation.

Also, if you’re going to manually quote people, you can do [ quote=personname ] so it doesn’t appear as an anonymous quote.

[quote]
Well, this thread is about colors. [/quote]

This is a feature request for allowing infinite colors for baseparts. Color meta discussion is off-topic.

BrickColor is a property. It takes up 7 bits. If instead colors were to be represented by 24 bits, load time would increase because of the increase in information. What you seem to want is an optional button that says “pretend this property doesn’t exist for me” to get around that, which isn’t how things work.

[quote]Also there’s nothing wrong with copying and pasting, if it’s correct, so don’t start trying to start an argument about it.

[quote]The thing is that you just copied a block of text out of the wikipedia, didn’t check to see if “2^24” was formatted correctly, and pressed post.
Copying and pasting entire posts is also wrong and looks like a complete mess when you should instead be pressing “quote” to quote a post.[/quote][/quote]

Stop trying to turn every single thing into an argument, seriously, what is your problem? If you want an argument go somewhere else, because I’m just going to do the mature thing and walk away, goodbye.

You posted an apparently out-of-place block of text on this thread and didn’t bother to explain why, then started acting defensive about it. All I asked was why, only after continuing the on-topic discussion of the thread.

Here’s another idea, what about colour packs?
So there can be like a realistic colour pack, a saturate colour pack, a black and white colour pack, a sepia colour pack, and so on. That way you still have the same amount of colours, but just different ones. Or maybe you could make your own colours. Anyway, would that work, because it’s still the same amount of data to load right?

[quote] Here’s another idea, what about colour packs?
So there can be like a realistic colour pack, a saturate colour pack, a black and white colour pack, a sepia colour pack, and so on. That way you still have the same amount of colours, but just different ones. Or maybe you could make your own colours. Anyway, would that work, because it’s still the same amount of data to load right? [/quote]

I believe a pre-set pallet of colours would be fine, yes. But we’ve been over this already and the reason nobody wants people to set their own colours is because there’s a ROBLOX aesthetic that will inevitably be ruined by people with poor colour choices. As for having some kind of “Sepia” colour pack, the use cases for this is extremely low and not worth the effort.

It isn’t the same amount of data. Bits would be added to represent each set of colors, which, data wise, would be the same as just having more colors.

I don’t see why you couldn’t send the client an ID corresponding to a certain color and then when someone sets that color it just replicates to the client as the ID instead of the whole Color3 every time.

Send client ID and Color3
Client now associates ID with Color3
Now only replicate the new ID for the color instead of the Color3.

I’m not a member of Roblox Staff so I can’t know the implications of a system such as this on the client and server.
But, If I were working on my own game I would do something like this.

The best thing which could be done to provide more colors is to allow the BrickColor corresponding Color3 values to be changed. The current system with that forced inside of it would look structurally horrible, though, especially since BrickColor color codes are all over the place.

If the BrickColor set were an index 1 to 128 with a corresponding Name and Color value, and those were allowed to be edited, they would load once and then be referenced by every part in the game using one of those newly modified values in that set.

In short: Allow us to create a custom palette to reference. The client loads it when they join.

Custom color palettes would really make using things made by other people be a pain.

“Oh hey there’s this model I really want to use but the color palette doesn’t match mine”

Free models would then be harder to use since we’d have to adapt the model to the game’s palette which I don’t support.

Color selection should be universal across all games.

The only way to have more colors is to use more space or use different colors. It’s up to Roblox if they want to choose.

Ok then, so it looks like this won’t happen. We’ll just have to wait until roblox adds more colours. Oh well, I hope they add more colours soon.

But we literally just got a new color palette…

I know, but I don’t like the colours. They’re just too colourful and bright, and I think there could be a better selection of colours.

You can always use a mesh and set its vertexcolor if you’re willing to drastically impact load time.

I get not having 17 million colors but you could make 256 colors? There is already one bit assigned to enum of BrickColor. So wouldn’t having 256 colors have the same amount of bits? Or do we already have 256 colors and I’m missing something?

We now have 128 colors. 64 were just added.