Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-7314] Large delay for vehicle object crossing certain border #15044

Closed
sl-service-account opened this issue Sep 18, 2014 · 13 comments
Closed

[BUG-7314] Large delay for vehicle object crossing certain border #15044

sl-service-account opened this issue Sep 18, 2014 · 13 comments
Labels
project:BUG

Comments

@sl-service-account
Copy link

sl-service-account commented Sep 18, 2014 •
edited by sl-issues-importer bot

Dec 2014 UPDATE. This bug is back, in Valmorel/Egan/Obersdorf sims.
Behavior is NOT 'Expected' !
KF.

Steps to Reproduce

  1. Standing watching the carriage pass by
  2. Riding the carriage

Actual Behavior

Object GSLR-Carriage V4.7 GSLR (A KFM-driven vehicle running on the GSLR track) ateempted to cross from region Purple to region Periwinkle at Northing 160, and did not cross correctly. Two instances were observed: (Times in Z, on 9/18/14, about 2pm SLT.)

  1. No carriage rider. Carriage hit crossing in Purple at 20:55:17. It appeard to continue in straight line across Perewinkle. At 20:56:59 it appeared at border in Periwinkle and continued on track correctly. See attached client log Firestorm_1.log
  2. Kitto Flora riding on Carriage. Carriage hit crossing in Purple at about 21:10:28. After a couple seconds the client view changed to KF in sitting pose floating in air high up, -300 west of perewinkle and travelling west. no carriage in sight. At 21:11:20 KF view changed to standing on GSLR track at the border, in Periwinkle, Carriage not in view. The Carriage appears to have survived but was a long way to the west. See attached client log Firestorm_2.log

Expected Behavior

Smooth instantaneous crossing of the border.

Other information

Being discussed with Simon Linden.
This problem has been observed twice before.

Details of one: (it was 'fixed' by restarting the regions)
Case #: 01995537
Northbound Okemo Canyon -> Okemo Gorge
Westbound Perwinkle -> Maroon
Moving object (VEHICLE or KFM-driven) drifts on as ghost in destination region. After 2 - 3 minutes appears in destination region.
Avatars can cross normally.
Sim type is SLserver -> RC LeTigre

Attachments

Original Jira Fields
Field Value
Issue BUG-7314
Summary Large delay for vehicle object crossing certain border
Type Bug
Priority Unset
Status Closed
Resolution Expected Behavior
Reporter Kitto Flora (kitto.flora)
Created at 2014-09-18T21:45:41Z
Updated at 2014-12-19T00:31:56Z 
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2014-09-18T17:29:12.145-0500',
  "Is there anything you'd like to add?": "Being discussed with Simon Linden.\r\nThis problem has been observed twice before.\r\n\r\nDetails of one:  (it was 'fixed' by restarting the regions)\r\nCase #: 01995537\r\nNorthbound Okemo Canyon -> Okemo Gorge\r\nWestbound Perwinkle -> Maroon\r\nMoving object (VEHICLE or KFM-driven)  drifts on as ghost in destination region. After 2 - 3 minutes appears in destination region.\r\nAvatars can cross normally.\r\nSim type is  SLserver -> RC LeTigre\r\n\r\n\r\n",
  'Severity': 'Unset',
  'System': 'SL Simulator',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'Object GSLR-Carriage V4.7 GSLR (A KFM-driven vehicle running on the GSLR track) ateempted to cross from region Purple to region Periwinkle at Northing 160, and did not cross correctly. Two instances were observed: (Times in Z, on 9/18/14, about 2pm SLT.)\r\n1. No carriage rider. Carriage hit crossing in Purple at 20:55:17. It appeard to continue in straight line across Perewinkle. At 20:56:59 it appeared at border in Periwinkle and continued on track correctly. See attached client log Firestorm_1.log\r\n2. Kitto Flora riding on Carriage. Carriage hit crossing in Purple at about 21:10:28. After a couple seconds the client view changed to KF in sitting pose floating in air high up, -300 west of perewinkle and travelling west. no carriage in sight. At 21:11:20 KF view changed to standing on GSLR track at the border, in Periwinkle, Carriage not in view. The Carriage appears to have survived but was a long way to the west. See attached client log Firestorm_2.log',
  'What were you doing when it happened?': '1. Standing watching the carriage pass by\r\n2. Riding the carriage',
  'What were you expecting to happen instead?': 'Smooth instantaneous crossing of the border.',
  'Where': 'Purple <1,60,30>',
}
@sl-service-account
Copy link
Author

Simon Linden commented at 2014-09-18T22:29:12Z

Kitto - can you please do this with the latest SL viewer? I need to have the viewer logs match up to the same source code, so Firestorm isn't usable for me. There may also be an update bug here so it's important that we're looking at our latest version. Thanks!

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-09-24T16:12:11Z

9/23 Periwinkle and Purple were restarted, but the delay continued.
Pandora/Chamonix border is exhibiting same problem.
9/24 Periwinkle and Purple were restarted again at around 7:12am, the delay persists but is in the eastbound direction!

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-09-24T21:49:10Z

Log for 2:38pm 9/24/14

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-09-24T21:49:28Z

9/24 Problem is also happening at Periwinkle -> Maroon westbound.
Logged one crossing using latest SL viewer.
Carriage departed Periwinkle border at 2:38pm (21:38 Z)
Carriage appeared in Maroon at 2:41PM
SecondLife.log attached.

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-09-26T16:24:43Z

Result of some testing 9/25 and 9/26, with Ana (anaimfinity)
More border crossings where the same problem exhibits:
Effect is directional! Listing is "FROM -> TO"
Pandora -> Chamonix
Pandora -> Mimas
Pandora -> Callisto
Nolidae -> Sabre
Tawhaki -> Sido
Ess -> Clear
Barton -> Sugarloaf

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-09-30T21:05:20Z

This morning's sim code update/restart cleared all the above listed bad border crossings.
New border with same problem:
Melanthia -> Xanthorhoe

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-10-03T19:39:36Z

New border with same problem:
Gamma -> Coronal. Delay is very long or possibly infinite.

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-10-05T03:05:21Z

Another border with the same problem:
Koni -> Tieut

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-10-05T03:25:41Z

Also:
Koni -> Noguri
Koni -> Megi
Koni -> Noul

@sl-service-account
Copy link
Author

Daria Linette commented at 2014-10-08T20:44:06Z, updated at 2014-10-23T18:40:46Z

Other regions with same problem since 07/oct/14 restarts:
Shipton -> Triphosa
Burnott -> Knot [Edit: fixed]
Knot -> Burnott [Edit: fixed]
Pini -> Lappet [Edit: fixed]
Melanthia -> Xanthorhoe [Edit: fixed]

@sl-service-account
Copy link
Author

Daria Linette commented at 2014-10-15T17:43:44Z, updated at 2014-10-28T07:10:41Z

Two more problematic sim crossings found:
Shark->Ginsberg [Edit: fixed]
Arches->Foxglove [Edit: fixed]

Seriously, the grid has turned into a real minefield. Using a vehicle is no longer an option. Better fix it ASAP :-(

@sl-service-account
Copy link
Author

Daria Linette commented at 2014-10-23T19:13:01Z, updated at 2014-10-28T07:13:58Z

The latest restarts solved some issues (see above) but new crossings with problems appear:
Engrailed->Mullein
Gluphisia->Nessus->Anilis (infamous double sim-crossing on the SLRR, now totally impossible to perform)

Dear admins, don't you find a bit abusive to let this ticket rot since september 18th, despite Kitto provided you the requested SL log on 24th and a truckload of regions where the problem could be easily reproduced has been quoted here? I do!

@sl-service-account
Copy link
Author

Kitto Flora commented at 2014-10-30T16:00:41Z

This problem with region crossing gets 'fixed' when the problem region is restarted. Comment from Simon Linden at a Sim meeting was to the effect that 'we are not going to spend time on a bug that can be fixed by restarting the sim'.
So the cure now is to ticket every occurrence of this problem, and reference 'Jira BUG-7314' each time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
project:BUG
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sl-service-account