Erentar – User talk

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
m (Text replacement - "killzone_kid" to "Killzone_Kid")
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== waypointAttachVehicle ==
== waypointAttachVehicle ==


Please see ingame help description. It clearly states that it is vehicle that is attached to the waypoint. It is the same principal as for [[triggerAttachVehicle]] The vehicle is attached not the other way round. Also the note from Karel is outdated and not true any more, so please if you want to keep it, put it in discussions for the page for historic keeping [[User:killzone_kid|killzone_kid]] ([[User talk:killzone_kid|talk]]) 00:12, 5 January 2019 (CET)
Please see ingame help description. It clearly states that it is vehicle that is attached to the waypoint. It is the same principal as for [[triggerAttachVehicle]] The vehicle is attached not the other way round. Also the note from Karel is outdated and not true any more, so please if you want to keep it, put it in discussions for the page for historic keeping [[User:Killzone_Kid|Killzone_Kid]] ([[User talk:Killzone_Kid|talk]]) 00:12, 5 January 2019 (CET)
Actually note is already there [[User:killzone_kid|killzone_kid]] ([[User talk:killzone_kid|talk]]) 00:14, 5 January 2019 (CET)
Actually note is already there [[User:Killzone_Kid|Killzone_Kid]] ([[User talk:Killzone_Kid|talk]]) 00:14, 5 January 2019 (CET)


:Thanks for the heads up!
:Thanks for the heads up!
:The edit i did was for clarification. The text "Attaches vehicle to waypoint" reminds of "attachTo", and may sound like the vehicle is going to be at the same position as the waypoint. In fact, both the waypoint and the vehicle stay where they are, but the vehicle in this case gets specified as the target of the waypoint, which the unit will follow. So practically, the waypoint is attached (ie. follows) the vehicle. I made this edit based on the sqf reference provided by BISimulations for VBS, which states "Attached waypoint automatically follows the vehicle/unit it is attached to." which is exactly what the command does. This is the reason why i think "Attaches a Waypoint to the given Vehicle or Unit. Attached waypoint automatically follows the vehicle/unit it is attached to." is clearer and less confusing than "Attaches a vehicle Object to the given Waypoint." <span style="color:#0078F0"> erentar </span> 02:03, 5 January 2019 (CET)
:The edit i did was for clarification. The text "Attaches vehicle to waypoint" reminds of "attachTo", and may sound like the vehicle is going to be at the same position as the waypoint. In fact, both the waypoint and the vehicle stay where they are, but the vehicle in this case gets specified as the target of the waypoint, which the unit will follow. So practically, the waypoint is attached (ie. follows) the vehicle. I made this edit based on the sqf reference provided by BISimulations for VBS, which states "Attached waypoint automatically follows the vehicle/unit it is attached to." which is exactly what the command does. This is the reason why i think "Attaches a Waypoint to the given Vehicle or Unit. Attached waypoint automatically follows the vehicle/unit it is attached to." is clearer and less confusing than "Attaches a vehicle Object to the given Waypoint." <span style="color:#0078F0"> erentar </span> 02:03, 5 January 2019 (CET)
:: I understand how this could be confusing if you think of this attachment in terms of attachTo, however this assumption is wrong and the aim of the command is to provide synchronisation of the vehicle and waypoint and not a physical attachment, even if waypoint takes the position of the vehicle. The waypoint has a property that keeps track of the attached vehicle and not the other way round, this is why a vehicle is attached to the waypoint and not waypoint to the vehicle. While the implementation is a mess, it still better for the description to indicate the actual functionality and not assumed one. [[User:Killzone_Kid|Killzone_Kid]] ([[User talk:Killzone_Kid|talk]]) 20:57, 6 January 2019 (CET)

Latest revision as of 17:52, 18 February 2024

waypointAttachVehicle

Please see ingame help description. It clearly states that it is vehicle that is attached to the waypoint. It is the same principal as for triggerAttachVehicle The vehicle is attached not the other way round. Also the note from Karel is outdated and not true any more, so please if you want to keep it, put it in discussions for the page for historic keeping Killzone_Kid (talk) 00:12, 5 January 2019 (CET) Actually note is already there Killzone_Kid (talk) 00:14, 5 January 2019 (CET)

Thanks for the heads up!
The edit i did was for clarification. The text "Attaches vehicle to waypoint" reminds of "attachTo", and may sound like the vehicle is going to be at the same position as the waypoint. In fact, both the waypoint and the vehicle stay where they are, but the vehicle in this case gets specified as the target of the waypoint, which the unit will follow. So practically, the waypoint is attached (ie. follows) the vehicle. I made this edit based on the sqf reference provided by BISimulations for VBS, which states "Attached waypoint automatically follows the vehicle/unit it is attached to." which is exactly what the command does. This is the reason why i think "Attaches a Waypoint to the given Vehicle or Unit. Attached waypoint automatically follows the vehicle/unit it is attached to." is clearer and less confusing than "Attaches a vehicle Object to the given Waypoint." erentar 02:03, 5 January 2019 (CET)
I understand how this could be confusing if you think of this attachment in terms of attachTo, however this assumption is wrong and the aim of the command is to provide synchronisation of the vehicle and waypoint and not a physical attachment, even if waypoint takes the position of the vehicle. The waypoint has a property that keeps track of the attached vehicle and not the other way round, this is why a vehicle is attached to the waypoint and not waypoint to the vehicle. While the implementation is a mess, it still better for the description to indicate the actual functionality and not assumed one. Killzone_Kid (talk) 20:57, 6 January 2019 (CET)