createVehicleLocal

[Rommel92]

Code: [Select]

_ehID = player addEventHandler ["Fired", {
_s = "B_545x39_Ball" createvehiclelocal [0,0,0];
}];

Expected Results:
Player would see a bullet created at position at [0,0,0]
No other players would see it.

Actual Results:
Player see's a bullet created at position at [0,0,0]
All other players see the bullet creation at [0,0,0].

Tested with "UAZ_RU"

Expected Results:
Player would see a UAZ created at position at [0,0,0]
No other players would see it.

Actual Results:
Player see's a UAZ created at position at [0,0,0]
No other players see it.

---

Conclusion: Somehow bullets are special.
Despite advertisement of the contrary, the Fired EH is not GLOBAL.

[Doolittle]

Good find..

[DeanosBeano]

 i like things like this, always good to see people still delving so deep into the whole thing.

 If i may eliminate the possible to seek the impossible , may i ask without any insult intended .

Player see's a bullet created at position at [0,0,0]
All other players see the bullet creation at [0,0,0].

 your local fireguy is not firing a weapon that fires and actual B_545x39_Ball  is he ? Had to ask sorry .

 also just for test purpose Bullets are a simple set of co-ordinates not a model i believe , however a shell can use an actual p3d model , is result same  ?

 not sure what i aim to gain from my questions but i like all this kind of testing , sometime very useful things are obtained.

 

[Rommel92]

Haha.

No.

...



I believe you may be right with bullet not using a model, which could be its specialty, however it is still an entity that can be handled as an object.

I also must revoke the following statement:
Code:

Despite advertisement of the contrary, the Fired EH is not GLOBAL.


After speaking with Suma on the matter, he showed me that it is merely the effect of this script that is local, not the arguments. Little confusion was there at first. 

None the less; annoying bug, causes lag which shouldn't occur.


Edit by i0n0s:
Mixed edit and quote button...

[i0n0s]

Suma talked about addEventhandler or the script started by the handler?

[tcp]

Maybe the bullet just creates a "blast" that is broadcast globally. I would think all damage needs to be global.

[Planck]

I think all bullets and shells use the same model, apart from tracer ammo.

\ca\weapons\shell


Planck

[Rommel92]

Suma talked about addEventhandler or the script started by the handler?

The event of the handler, the Fired Event is global, but the arguments are local. All machines fire off the fired event handler, but it is not added globally when you add the script to the unit (stupid mistake really).

Maybe the bullet just creates a "blast" that is broadcast globally. I would think all damage needs to be global.

But players are capable of visually receiving the ricochets, I understand the concept, but if it was just damage, it would just be observed as to happen for no apparent reason; and there would be minimal desync if no damage occured at all (ie 90 bullets shot into the sky still causes small desync? No impacts.)

[i0n0s]

Ok @ Rommel,
so addEventhandler["Fire",...] has a global argument (unit can be on every client) and local effect since the handler only launches on the script where the handler was added.
Thanks for the cleanup, so the fire handler is not special to other events.

[Rommel92]

Yes that is correct, however the main issue here (as to which Suma has not given any insight to) is the bullets being broadcasted when they are created locally!?

 

[DeanosBeano]

 Maybe the bullet has a special init propperty itself, such as Simulation ="xxx" ,not at my gaming pc at the moment so not sure if simulation properties are applied to bulletcore or not.

[Planck]

Aye, bullet has simulation = "shotBullet";, shell has simulation = "shotShell"; in BulletCore and ShellCore respectively.


Planck