somazT
-
Posts
14 -
Joined
-
Last visited
Content Type
Forums
Blogs
Knowledge Base
Posts posted by somazT
-
-
Hi,
It seems that even with my high-speed broadband of 100 mbps, I try to login to SL, I get kicked out after 3-4 minutes. It happens independent of me being in any location in SL. What I have observed is the ping rate from firestrom/ SL viewer says it is above 600ms. But from Terminal is says the ping time is around 300ms all the time Please refer to the screenshots attached. Do you have any idea how to get it to work it back. Below are the ping statistics from terminal. I can see sometimes it takes more than 300ms server to respond.ping sim10291.agni.lindenlab.com
PING sim10291.agni.lindenlab.com (216.82.50.13): 56 data bytes
64 bytes from 216.82.50.13: icmp_seq=0 ttl=49 time=287.109 ms
64 bytes from 216.82.50.13: icmp_seq=1 ttl=49 time=286.667 ms
64 bytes from 216.82.50.13: icmp_seq=2 ttl=49 time=286.923 ms
64 bytes from 216.82.50.13: icmp_seq=3 ttl=49 time=286.980 ms
64 bytes from 216.82.50.13: icmp_seq=4 ttl=49 time=286.245 ms
64 bytes from 216.82.50.13: icmp_seq=5 ttl=49 time=280.403 ms
64 bytes from 216.82.50.13: icmp_seq=6 ttl=49 time=280.701 ms
64 bytes from 216.82.50.13: icmp_seq=7 ttl=49 time=280.199 ms
64 bytes from 216.82.50.13: icmp_seq=8 ttl=49 time=280.649 ms
64 bytes from 216.82.50.13: icmp_seq=9 ttl=49 time=341.514 ms
64 bytes from 216.82.50.13: icmp_seq=10 ttl=49 time=280.515 ms
64 bytes from 216.82.50.13: icmp_seq=11 ttl=49 time=280.682 ms
64 bytes from 216.82.50.13: icmp_seq=12 ttl=49 time=280.575 ms
64 bytes from 216.82.50.13: icmp_seq=13 ttl=49 time=279.830 ms
64 bytes from 216.82.50.13: icmp_seq=14 ttl=49 time=281.090 ms
64 bytes from 216.82.50.13: icmp_seq=15 ttl=49 time=284.893 ms
64 bytes from 216.82.50.13: icmp_seq=16 ttl=49 time=280.493 ms
64 bytes from 216.82.50.13: icmp_seq=17 ttl=49 time=281.629 ms
64 bytes from 216.82.50.13: icmp_seq=18 ttl=49 time=280.869 ms
64 bytes from 216.82.50.13: icmp_seq=19 ttl=49 time=280.672 ms
64 bytes from 216.82.50.13: icmp_seq=20 ttl=49 time=280.135 ms
^C
-
On 9/8/2018 at 12:28 AM, binder59 said:
i reside in the uk, did a speed test to servers in usa, got a ping time of 18 ms download speed 70 m bits, upload speed of 20 m bits my prob is when using firestorm, or any other view, when i visit certain regions on sl, i ge a ping of well over 600 ms, this seems to be problem with lag, can anyone give me info how to get this lower my connection is very good help would be appreciated, thank you
I am facing the same issue from here.
- 1
-
I am having this issue at the moment. I get logged out after 2-3 minutes stating the same dialog box. It has started to happen about 10 hours back and still continues. I have 100 MBPS broadband speed. It should be enough for SL I guess.
Do you have any remedy for it? If there is a remedy then please help me with it.
-
7 hours ago, animats said:
"Not responding to arrow keys" can happen after a failed region crossing where you were pulled off a vehicle. Don't think you're experiencing that, since you haven't mentioned vehicles.
Is your cursor over the main window? If it's over some dialog box or menu, the arrow keys don't move the avatar.
17 hours ago, Nalates Urriah said:There is a rare (now rare, once common) problem where you cannot move or TP. This usually happens at login. It is caused by the region failing to connect properly to the SL backend after a restart. Logging into a different region is the test for the problem. It has nothing to do with you, your computer or connection.
So, test for this problem first when you are sure move lock is off.
Unfortunately my cursor over main window. and oddly after i login i do a first TP from that location it works fine from there. I am able to move myself. Move lock was off all the rime.
-
Unfortunately my cursor over main window. and oddly after i login i do a first TP from that location it works fine from there. I am able to move myself. Move lock was off all the rime.
-
I have found out the underlying issue. it appears that when I first login to a place or my home location i am not able to move. but if i TP from there to some place else. I seem to move again.
-
I am using Mac os catlina. I have noticed that in windows machine i am able to move using firestorm using arrow keys.
Please help.
-
Hi ,
It seems my Avtar freezes. I can not move about in SL at all. I have checked out that my move lock is not enabled. so I should be able to move about. But I can not.
Please help me out.
-
Hi,
I am from India. I want to watch Netflix on SL at my SL home on TV with my friends from different country. Is there a way to do it ? if so please let me know how I can do it.
Thanks & Regards
-
It basically means with Lumiya gone now almost. the fantastic option to connect to 3 D view is also gone.
-
There should be something that can replace Lumiya in a better way.
-
2 minutes ago, seanabrady said:
To the best of my knowledge there are no other mobile apps for SL on Android. And as I understand it even Lumiya is no longer available in the Play Store.
Yes that I know. SL should provide options for mobile compatible viewer. even if it takes away few L$. but at times it can work to stay connected.
-
Hi,
I am looking for options to connect to SL from mobile. As I will be travelling and will not have my laptop with me .I have used Mobile grid (text only) client and Lumiya (text + 3 D). I have found Lumiya quite handy. But I am facing issues with Lumiya now as it is giving me problems. Is there something like Lumiya with 3 D capability for mobile that I can use. Please let me know.
You have been logged out ...
in General Second Life Tech Discussion
Posted
I tried with creating a new avtar and check it from there the issue still exists.
when i ping the server from terminal it is giving me about 300ms on average for ping.
ping sim10291.agni.lindenlab.com
PING sim10291.agni.lindenlab.com (216.82.50.13): 56 data bytes
64 bytes from 216.82.50.13: icmp_seq=0 ttl=49 time=287.109 ms
64 bytes from 216.82.50.13: icmp_seq=1 ttl=49 time=286.667 ms
64 bytes from 216.82.50.13: icmp_seq=2 ttl=49 time=286.923 ms
64 bytes from 216.82.50.13: icmp_seq=3 ttl=49 time=286.980 ms
64 bytes from 216.82.50.13: icmp_seq=4 ttl=49 time=286.245 ms
64 bytes from 216.82.50.13: icmp_seq=5 ttl=49 time=280.403 ms
64 bytes from 216.82.50.13: icmp_seq=6 ttl=49 time=280.701 ms
64 bytes from 216.82.50.13: icmp_seq=7 ttl=49 time=280.199 ms
64 bytes from 216.82.50.13: icmp_seq=8 ttl=49 time=280.649 ms
64 bytes from 216.82.50.13: icmp_seq=9 ttl=49 time=341.514 ms
64 bytes from 216.82.50.13: icmp_seq=10 ttl=49 time=280.515 ms
64 bytes from 216.82.50.13: icmp_seq=11 ttl=49 time=280.682 ms
64 bytes from 216.82.50.13: icmp_seq=12 ttl=49 time=280.575 ms
64 bytes from 216.82.50.13: icmp_seq=13 ttl=49 time=279.830 ms
64 bytes from 216.82.50.13: icmp_seq=14 ttl=49 time=281.090 ms
64 bytes from 216.82.50.13: icmp_seq=15 ttl=49 time=284.893 ms
64 bytes from 216.82.50.13: icmp_seq=16 ttl=49 time=280.493 ms
64 bytes from 216.82.50.13: icmp_seq=17 ttl=49 time=281.629 ms
64 bytes from 216.82.50.13: icmp_seq=18 ttl=49 time=280.869 ms
64 bytes from 216.82.50.13: icmp_seq=19 ttl=49 time=280.672 ms
64 bytes from 216.82.50.13: icmp_seq=20 ttl=49 time=280.135 ms
^C