me thinks you found a bug that i also found when coloring text on screen.

with the textprint object, when you define different colors in script for say 3 text prints all in one loop, only the last one defined is used for all the text print from that object.

I'm guessing something similar is happening here where only one defined color is used per script loop.

I would suggest separating each color into it's own loop like this.

 iShaderFloat3Set(OBJ_0,"cColor", 0.55, 0.39, 0.66);
wait for half a sec or use a counting loop like
counter1+=0.01;
if(counter1>0.4)iShaderFloat3Set(OBJ_22,"cColor", 1.0, 1.0, 1.0);
if(counter1>0.8)iShaderFloat3Set(OBJ_44,"cColor", 0.0, 0.60, 0.30);

if(counter1>2.0)counter1=0;

and run this loop maybe every script cycle if it works or needs to be every script cycle.



everything's a bug...  right... 3DRAD is at fault for every failing that we can imagine...

maybe, the fault lies in ourselves, and not in 3DRAD...

the height of absurdity is to imagine that the first thing that someone does when confronted with a problem is to throw up their hands and assume that the fault must be in something beyond their control... yet so many people's minds operate in this fashion...

i never will understand this...



there's nothing wrong with RAD here...

first of all, i must assume that the original poster is trying to change the color of a skinmesh, and not that of a car object...

if this is indeed the case, then a quick review of the system shaders and how to apply them should clear up his confusion...
the skinmesh must use a user_shader_type...  0014, 0015, etc... the default shaders won't work with the function he is using...


second... the code...
you need to take the instructions out of the init clause... it must happen each main loop cycle...

i think that both of these facts are documented...


--Mike

You can define the colours for objects as Mike says, must be called within main loop and only on a _user shader.
For textprints if you use separate textprints you can define as many colours as you like in one loop, but I think you are trying to change the colour of ONE textprint multiple times in a loop - the colour only changes at the end of a loop so this can't be done (afaik), I wouldn't necessarily call it a bug, more just the way RAD works

my point stands..

you cant define different colored text printed on screen at the same time using one  text print object.

of course you can change the text print objects color runtime.. but not in a way that would define multiple text colors printed on screen at the same time with only one text print object.

i suggested the loop timing process because i came across an issue with animated sprites ( frames) not being changed and displayed during each script cycle.

for instance, i have a program im working on, when you click a screen button ( sprite) in script it's set to change animation frame.

Then the program downloads a file from the internet.

Problem is the sprite frame is updated properly before the download begins, but all this happens in one script loop.

So apparently the sprite frame update doesn't get applied to the sprite and it's not seen on screen till the file download completes.

So i found out that if change the sprite frame then apply a timed delay of a few engines cycles to allow the change on screen to be seen, then do the file download..

The button works as i wanted it to.

I blame the file download function for interrupting 3drad till it finish's.

That was what was going through my head when i suggested using a timed loop to allow 3drad to full process the colors for each object before moving to the next object.

With the textprint object this can or will cause color flickering.

Thanks All for help.

if I try use them in main loop can't change color because always show current color.also I use Shader 0016 for change skin Mesh Color. I Need set one color in first run that will could change colors.

Hi beha....... This should help

n_iron