Help

tatsujb · March 9, 2015

How do I change a teamcolor in theparticle.fs shader to another shade?

tatsujb · March 9, 2015

.

tatsujb · March 9, 2015

old irrelevant problem said:
I'm INCHES, guys, INCHES from finding the solution!

having reverted to UBER's code (in particle_unit.vs):
Code:
v_SelectedState = vUVAndExtra.z;
for distinguishing selected states.

I MANAGED TO GET THREE DISTINCT STATES.

.....but the third is mouse-over when the unit is already selected.

here's my current setup i put green in to distinguish the three:
Code:
    //toogle apperace between selected, unselected and mouseover
    //for body (is either ipi or pip depending on how light or dark) (basically team color) :
    vec4 body;
    if (v_SelectedState > 1.4)
            body = White;                        //selected + mouseover
        else if (v_SelectedState > 0.9)
            body = v_ColorPrimary;      //selected
        else                    
            body = Green;                         //unselected

    //tiermarker (+ border when color is dark) (blue or tier marker) :
    vec4 tiermarker;
    if (v_SelectedState > 1.4)
            tiermarker = Black;                //selected + mouseover
        else if (v_SelectedState > 0.9)
            tiermarker = White;               //selected
        else                    
            tiermarker = Green;               //unselected

    //outer (Red)
    vec4 outer;
    if (v_SelectedState > 1.4)
            outer = v_ColorPrimary;       //selected + mouseover
        else if (v_SelectedState > 0.9)
            outer = Black;                           //selected
        else                    
            outer = White;                          //unselected

    //and highlight (black):
        vec4 highlight;
        if (v_SelectedState > 1.4)
            highlight = v_ColorPrimary;  //selected + mouseover
        else if (v_SelectedState > 0.9)
            highlight = Trans;                     //selected
        else                    
            highlight = Green;                    //unselected
So what can we conclude from this? : well first off : all v_selected_state returns three possible values :

1.5

1.0

0.5

problem is we don't want SELECTED + mouseover, we want UNselected +mouseover.

and changing values around isn't going to change what those values mean for the states.

So in the other file

if (vUVAndExtra.z > 0)
v_SelectedState = 1;
else if (posAndScale.w > 48.5)
v_SelectedState = 0.5;
else
v_SelectedState = 0;
Click to expand...

permitted me to distinguish between selected and unselected but never got to the last else.

why?
Click to expand...

tatsujb · March 8, 2015

paging @SXX, @DeathByDenim , @proeleert , @bgolus , @jorgenpt , @mkrater , @UberGaf , @varrak ,@sorian, @Col_Jessep , @tHeTrOpHySyStEm , @YourLocalMadSci , @brianpurkiss, @wondible , @cptconundrum , @bsergent , @liquius , @killerkiwijuice , @Alpha2546 , @Fr33Lancer, @yarmond

zx0 · March 8, 2015

posAndScale.w > 48.5
Click to expand...

What's that?

Cause I think it's icon scale =52.

tatsujb · March 9, 2015

.

tatsujb · March 8, 2015

zx0 said: ↑

posAndScale.w > 48.5
Click to expand...

What's that?

Cause I think it's icon scale =52.
Click to expand...

apparently it doesn't do nothing because when I change the value to 52 (and yes leave the > it's weird i dunno why it works) then the selected = TRUE becomes 0 (the last else)

tatsujb · March 9, 2015

.

zx0 · March 8, 2015

Mouseover but not selected: vUVAndExtra.z < -1.0 vUVAndExtra.z == -2.0
Mouseover and selected: vUVAndExtra.z > 1.0 vUVAndExtra.z == 2.0
No mouseover but selected: vUVAndExtra.z > 0.0 && vUVAndExtra.z <= 1.5 vUVAndExtra.z == 1.0

No mouseover, not selected: vUVAndExtra.z < 0.0 && vUVAndExtra.z >= -1.5 vUVAndExtra.z == -1.0
Feature: vUVAndExtra.z==0.0

edit: 1.0, not 1.5

bgolus · March 9, 2015

The above is correct.

-2 = hover
-1 = default
1 = selected
2 = hover & selected

I use abs(v_SelectedState) > 1.5 in the original shader, but abs(v_SelectedState) == 2.0 would of worked as well. In certain implementations of GL floating point numbers can drift a little, so == 2.0 can sometimes fail when it shouldn't, so using greater than at the halfway ensures it works 100% of the time.

tatsujb · March 9, 2015

@bgolus
@zx0
OMGOMGOMGOMGOMGOMGOMGOMG

thannnnnnk youuuuuuuuuuuuuuuu!!!!!

I would've never guessed it.

tatsujb · March 9, 2015

EDIT: nevermind figured it out using an ugly (but blatant) hack :

// gauge closeness of team color to black
if (luma > 0.30)// if team color is too dark invert border color and tier two marker color
{
pip = White; // temporary test to show that turning into white works
ipi = White;
border = White;

}
else if (luma > 0.12)
{
pip = tiermarker2; // in this mode tiermarker (pip) (blue) gets white when selectedand and unselected but black when mouseover
ipi = body; // ipi (yellow) receives body color
border = outer; // border (red) recieves outer color
}
else if (luma > 0.07)
{
pip = tiermarker; // in this mode tiermarker (pip) (blue) gets black when selected and and mouseover but white when unselected
ipi = outer; // ipi (yellow) recieves outer color
border = body; // border (red) recieves body color
}
else
{
pip = Black; // temporary test to show that turning into black works
ipi = Black;
border = Black;
}
Click to expand...

Help

tatsujb Post Master General

tatsujb Post Master General

tatsujb Post Master General

tatsujb Post Master General

zx0 Well-Known Member

tatsujb Post Master General

tatsujb Post Master General

tatsujb Post Master General

zx0 Well-Known Member

bgolus Uber Alumni

tatsujb Post Master General

tatsujb Post Master General

Share This Page

Help

tatsujb Post Master General

tatsujb Post Master General

tatsujb Post Master General

tatsujb Post Master General

zx0 Well-Known Member

tatsujb Post Master General

tatsujb Post Master General

tatsujb Post Master General

zx0 Well-Known Member

bgolus Uber Alumni

tatsujb Post Master General

tatsujb Post Master General

Share This Page

Useful Searches