simulator - http setup - Missing EstablishAgentCommunication messages
tracked
Monty Brandenberg
[ Making this its own issue as work is happening in multiple areas. Import and link to SRV-607 work. ]
The EAC message is passed between simulators then up to viewers to establish an HTTP path from viewer to a simulator with an EventQueue and caps. Reports in a forum as well as my own traces are showing loss or delay of EAC messages.
This contributes to making adjoining regions inaccessible or incomplete and degrading the overall experience.
Log In
Lisa Hyandi
Hello
Being redirected to this discussion by Oatmeal answer to a ticket opened by me. I want to share with you all the experience i had to live 5 tiemes yesterday and other times before .
and i want to be sure that this effect is related to the techncal dicussion here..
Please look in the gyazo how the boat ahead (me) drops its speed to 0 upon entering hte sim while thge boat below passes teh border without any issue..
Question is .. Why does it happen to a specific agent and not to the otheragent that crossed the same borfder briefly after me? My agents stops for a couple of seconds tehn the boat slowly restart like and has to gain speed again, the other agent crosses smootly
Why my agent suffers of this effect more than others in the last few months?
Lisa Hyandi
Any news about a possile ETA for the fix to this issue?
Provided that what we discuss here is realy the cause of my issue (speed dropping to 0 after entering a sim and tehn boat having to re-. accelerate , so very differnet from the normal "stop on crossing" issue) .. can we continue to have our race becomin totally a random game and not being decided by skill?
And a big quetion remain.. Why statisticaly in the alst 4 months i am the one that exsperience this issue more in weekly races in our area....
How can a signle avie experience this problme more or less thean anothe avie in the same crossing situation?
And why it only ahppesn during races with many boats crossig in sequence or even alone, but it never happen during pratice with les boats around the sim?
In any case any possibl ETA for a fix?
I cannot open a suport ticket because they say to me that the issue is the hands of developers.. so my only chance to ask an ETA is here
Thank you for you for your attention
Lisa
animats Resident
Discussion:
I've been putting more checks in my Sharpview to catch this and get more info. Neighbor regions are listed with their state. Most regions are in "Live" state, but the region ahead, the one that's not visible, is listed as "Connected" in red. That means it's stuck waiting for EstablishAgentCommunication.
The happy path for region startup is documented (by reverse engineering) in the Wiki
Sharpview has explicit states for regions. This helps when thinking about the problem. The C++ viewers are not as explicit internally.
- Idle -- Idle state - no connection.
- Discovered -- login or EnableSimulator received.
- Connected - RegionHandshake received
- SeedCapabilityReceived - EnableAgentCommunication received, or teleport/login
- CapabilitiesReceived - the essential capability URLs have been received.
- Live -- fully connected and operating normally
- Fault -- timeout or unrecoverable error. Region becomes hole in ground.
This is not official LL terminology.
When a neighbor region starts to come up, it normally progresses through the states to
Live
in under a second.This bug causes the state changes to get stuck at Connected
for a full minute. It's possible to display a region in that state, even though it's not fully up. and the C++ viewers have a workaround to do this. But that region doesn't receive events; its event poller is not live yet and anything that uses the event poller (which includes some PBR data and further region crossings) or any capabilities other than ViewerAsset
(does voice need a cap in a non-agent region?) will not work. So that's no longer a valid workaround.Related:
* On rare occasions (perhaps once a hour) the
EstablishAgentCommunication
message never comes at all. No idea why.* Sending the agent into a region stuck waiting for
EstablishAgentCommunication
will usually make the region live within a second or two.* It's possible to be stuck in what we call
Discovered
state. This means the viewer was sent EnableSimulator
but there was no followup beyond that. This seems to happen with regions out at the limit of draw distance, perhaps briefly in range. This seems to be mostly harmless. Approaching such a region with the agent causes it to come up normally.
Signal Linden
tracked