Differences

This shows you the differences between two versions of the page.

--- en:games:star_trek_armada_1:de-sync_and_crash_test [2024-02-28-17-14] – [Suspected Causes of Crashes] 7saturn
+++ en:games:star_trek_armada_1:de-sync_and_crash_test [2024-03-03-09-25] (current) – [IPX Server] 7saturn
@@ Line 58: / Line 58: @@
 == Known Facts SD+HE ==
 A test was conducted on map //2duel.bzn// (//On The Ready Line//), eight [[Negh'Var]] ships were destroyed one by one, by using [[Self-Destruct]]. While the Self-Destruct was already under way, [[Holo-Emitter]] was cast by an opposing ship, leaving the Negh'Vars affected by and destroyed while so. The result was uneventful each time. The Self-Destruct took its normal course of action.
+Another seemingly successful attempt was made by player //nic4747//, as shown in this video: https://www.twitch.tv/videos/2079696018 But this time it was [[Shadow]] vs. [[Cube]] and the Holo-Emitter was issued twice after issuing Self-Destruct.
 **Important notice**: Self-Destruct could not be cast, while already under the influence of Holo-Emitter. So in a normal match, the order can only be like casting Self-Destruct and then being affected by Holo-Emitter. This leaves an interesting edge case that could be a race condition: If the Self-Destruct is issued at the same time while Holo-Emitter is cast, the player using Holo-Emitter might get the information a tad to late, so that from their perspective they issue Holo-Emitter and the opponent still casts Self-Destruct. Maybe this is the cause for the reports of that problem. But this would imply, that this is a rather rare event, as hitting this exact time frame, while casting Self-Desctruct may be a problem, is highly unlikely.
 == Recommendation Self-Destruct While Affected by Holo-Emitter ==
+At this time, no recommendation can be given, except that maybe further testing is required. Test-Suggestion: A clean match, Shadow vs. Cube and the Holo-Emitter gets issued at least twice after issuing Self-Destruct on the Cubes.
+=== Changing Alert Status While Under the Influence of Holo-Emitter (Still Investigated) ===
+== Known Facts AS+HE ==
+A test was conducted on map //2duel.bzn// (//On The Ready Line//), two different [[Negh'Var]] ships were used to change the alert status (into random directions, simply pressing the buttons in a random order) while [[Holo-Emitter]] was already affecting them. The result was uneventful each time. The alert status was simply changed and the match went on.
+== Recommendation Alert Status Change While Affected by Holo-Emitter ==
 At this time, no recommendation can be give, except that maybe further testing is required.
 === Using Other Super Weapons (Rebutted) ===
@@ Line 72: / Line 79: @@
   - The [[en:gaming_platforms:world_opponent_network|WON]], which got shut down, so is not usable any longer.
   - TCP, which only works on the same network, making [[en:network_terms:VPN]] use mandatory for matches via the internet.
-  - IPX, similar to TCP but not available natively from Windows Vista on. See [[setting_up_matches#Using Ipx|]].
+  - IPX, similar to TCP but not available natively from Windows Vista on. See [[setting_up_matches#Using IPX]].
 There are currently efforts made to determine how reliable the IPX-via-UDP wrapping method in conjunction with [[https://github.com/solemnwarning/ipxwrapper|Daniel Collins']] wrapper and [[https://github.com/steveschnepp/ipxserver|A Perl RFC 1234 IPX server]] is.