SUGGESTION: Increase reticle color range from 0-255 to 0-500

---

@fartnitepalyer wrote:

@Zkepz 

do you even play the game...?

As I already said 5 times, going for 512 instead of 255 does nothing except add more brightness to the reticle, it makes it stand out more. Thats all there is to it.

maybe don't talk in forums if your opinion is based entirely on speculation.

---

Read the answer again and check up what that means before you say anything.... And yes I probably played a few thousand hours more then you....

@DoYaSeeMe 

crosshair color resulting in missing textures and server crashes, huh? got any proof? oh wait of course you don't because it's not true.

you don't even know what gldsrc or even something as basic as a cvar is. 🤨

Players have used "irregular" values for 90 days and there was not a SINGLE issue reported with them. And by irregular I mean people used crosshairs like "-60000 50000 -60000".

The only "issue" those are causing is they make your crosshair unusuable and you can't see *.

I myself - like many others - have a config file with which I constantly swap between different colors, including very wierd looking ones, just to try it out. again, there wasnt a single issue.

If you think setting a command for your reticle colors could make textures disappear you have a fundamentally wrong understanding of how games or in fact anything in the world works.

Respawn just decided they dont want any groovy looking reticles and choose to go the "safest" route which is limiting it to the values given ingame.

So stop making silly things up and pretending you know anything about how the game works just to be contrarian. jesus..

@Zkepz 

I am nearing or above 4000 hours at this point, so I doubt that 🙂

and you clearly don't understand how this game works either.

Again, same for you:

Stop making silly things up and pretending you know anything about how the game works just to be contrarian.

---

@Zkepz 

I am nearing or above 4000 hours at this point, so I doubt that 🙂

and you clearly don't understand how this game works either.

Again, same for you:

Stop making silly things up and pretending you know anything about how the game works just to be contrarian.

---

Ok ill bow in the dust im only up on 3K somewhere, hard to calculate since shitloads of my hours been on the PS4 and you cant really get the hours there. Still all these hours mean diddle when it comes to explaining why 500 is a wrong value for color config.

But I have more then 30 years of professional programming experience and yes I manipulated gfx cards and made games too. I merely tried to explain how the colors work and why 255 is a value they defined as max and it makes no sense going above. Reason its not as clear as you want is its not a on screen defined color, its a color inside the world recalculated by the influence of the reflections and other colors captured by the camera rendering the scene. Going outside these values makes no proper sense and how overflows are handled by the game engine before it draws as a pixel on your screen have side effects, and why you might get some interesting results with some "interesting" values designed to overflow the original limits. I can do a proper bitwise explanation for you and how the different techniques used from 4bit to 32 bit pixels (ref 24bit color RGB, those last 8 bits of the 32bit pixel is just an alfa channel) but I dont think that is appropriate content on this forum, i will however give you the easy lowdown, just understand that 24 bit colors represent RGB which is the common color coding used in game engines most significant byte (a byte is 8 bits and 8 bits cannot hold higher value then 255) is for red values 0-255, least significant byte is for blue values and ofc the middle byte is green. When a value is more then 255 for any of the given bytes how these values are packed into the pixel color can influence side effects, for instance extra bits adding to the more significant byte or values exceeding 8 bits just get tossed so you actually get a lower value but ofcourse to understand exactly how this works you need to research the binary number system.

What might give you the results you are after is getting access to the alfa channel of the 32bit pixel to adjust the transparency of the reticle using by definition invalid values to access it is a side effect not a feature, so before you try belittle people do your research properly.... Btw alfa channel means transparency adjustment, which again means how your defined color blends with the background when rendered, that again might influence your brightness immensly.

@Zkepz 

ok so basically you know a lot more about programming, but that doesn't mean you know how Source Engine works and I am not really sure what you are even trying to say.

Did you even experiment with reticles (values outside of 0-255) yourself before it got fixed to see the result or is everything you say just speculation? 😕

And did you read the part where I said that people "abused" this "exploit" for the past 90 days and nothing happened?

When I say, nothing happened, I mean it.

NOTHING malicious happened. Except that the reticle just becomes useless when you use stupid high values.

Again, all I am suggesting is to increase the limit a bit so we can get brighter reticles.

Because the only difference between a 255 255 255 and a 512 512 512 reticle is, the latter is more "saturated" (ie the glow effect is more prominent) and brighter. It's the same color otherwise and there are no bugs or issues.

So all these comments really just come out of nowhere and it's painfully obvious none of you guys even experimented with the values before they got locked.

I know what happens because I have used Source SDK which the Apex engine is based on, its not the Source engine. The modifications to Source SDK is substantial as well so its hardly comparable anymore, and as I explained exposing the alfa channel for adjustment will give you the exact same effect without the possible side effects you can get using values vastly out of bounds (you can even get the correct color and have control on the visual brightness). I even explained how it can happen that values from out of bounds rgb values bleed into the alfa channel because this is underlying bit operations sent to the graphics card.

I chose to only watch people breaking the TOS on YouTube so I know what it did and the result, but I keep within the TOS because I do not want to get banned. I also explained it for you. Manipulating the alfa channel with different colors can create the effect of having negative of background or create the color with full glow as its the transparency adjustment of the reticle itself. Using mechanics exploiting overflows and not legal values is asking for problems, we have enough of those already in the engine. The benefit of doing it the proper way is that you can actually experiment glow on the proper color and get it the way you like instead of all kinds of strange effects outside of control.

Edit: I recon the default alfa channel is at a value around 80-90%, that is why you cant get the full color glow on your screen after render...

@DoYaSeeMe 

I bet its lonely up there, on your mountain.

Again this is just a suggestion, there is literally NOTHING wrong with it. Everyone used way higher and even negative values and there was no resulting issues for the game that negatively affected anyone except the individual user.

@DoYaSeeMein fact I have and you clearly haven't. the game just ignores them and uses default values.

but thats not really relevant tho is it?

again, it would hurt nobody if the upper limit was increased to 512.

@fartnitepalyerI don't waste my personal time fiddling with config files. I have enough on my plate as a game developer.

Expanding the threshold for the RGB values beyond their normal range is a very improper way to get what you need. Not only that it can cause issues (you don't actually have access to all the code behind to see what other things are / can be applied in certain circumstances on those values), but fiddling with game files is not for everyone and should never be. A lot of players can't even access them anyway, so it's a bit unfair as well.

If you think there's real advantage from going over those limitations, then request for a bit of control over the opacity and blend modes for the reticle (multiply - lighten / darken). These would be just a couple of extra sliders in the UI, pretty easy to fiddle with for everyone.

What the hell happened in the forum. People were literally just getting neon reticles not negatively impacting other players gameplay... The only reason this got removed was because like everything else fun respawn takes from the game is because console players can't do it... Y'all need to chill and touch some grass before getting so hot headed about everything