GetLocalPlayer + SetUnitVertexColor = desync?

[Tyrande_ma3x]

Would this cause a desync? (I know there aren't any handles but still...)

        if GetLocalPlayer() == GetOwningPlayer(cast) then
            call SetUnitVertexColor(fir, 0, 0, 255, 255)
        endif

 

[Sevion]

No. But just to be sure, test it.

It's visuals so I don't think it should.

 

[Renendaru]

Only messing with handles desyncs, except for locally hiding units. (Though if a locally hidden unit does not effect any unit while hidden it is fine.)

 

[Bribe]

Anything interactive causes desyncs, though you'd be surprised what does and what doesn't constitute a desync.

Visuals are usually safe. I think you can get away with creating terraindeformations and weather effects. Texttags are definitely safe. The reason these ones are safe is because they have their own delegated handle stack so handles that actually affect gameplay don't get corrupted.

 

[Jesus4Lyf]

I think you can get away with creating terraindeformations

Ah, watch out if you use a physics system with these...
Actually, [LJASS]GetLocationZ[/LJASS] being used to move a unit by an amount can desynch just because natural terrain deformations are apparently unsynchronised (ie. a unit casts shockwave through a bunch of particles controlled by a physics engine, can desynch, apparently).

It is definitely safe to set a unit's vertex colouring to different values for each player. I don't know about calling it for one player, however.

 

[Tyrande_ma3x]

> I don't know about calling it for one player, however.
You mean it should be better to do something like:

    local integer r = 255
    local integer g = 255
    // blabla
    if GetLocalPlayer() ==  GetOwningPlayer(cast) then
        call SetUnitVertexColor(fir, r, g, 255, 255)
    endif

?

 

[Dinowc]

he probably meant this:

local integer red = 255.
local integer green = 255.
local integer blue = 255.
if GetLocalPlayer() ==  GetOwningPlayer(cast) then
      set red = 0.
      set blue = 0.
endif
call SetUnitVertexColor(fir, red, green, blue, 255)

 

[Troll-Brain]

Actually, GetLocationZ being used to move a unit by an amount can desynch just because natural terrain deformations are apparently unsynchronised (ie. a unit casts shockwave through a bunch of particles controlled by a physics engine, can desynch, apparently).

One day i tested with the lowest wc3 graphic configuration ever possible together with someone else with the highest.
And we had the same results comparing to our screenshots (R2SW(GetLocationZ...,10,10)).

I tested with different locations and an edited earth quake spell which was applied in the whole map (big radius).

But maybe it's not the same with a crap host and many players.

 

[Tyrande_ma3x]

he probably meant this:

local integer red = 255.
local integer green = 255.
local integer blue = 255.
if GetLocalPlayer() ==  GetOwningPlayer(cast) then
      set red = 0.
      set blue = 0.
endif
call SetUnitVertexColor(fir, red, green, blue, 255)

Silly me, wanted to type that but somehow I skipped the setting to 0. :nuts: