Jump to content

Ansariel Hiller

Advisor
  • Posts

    3,276
  • Joined

  • Last visited

Everything posted by Ansariel Hiller

  1. If any, it's within the BB3 network, which is a different company than Level 3. But since 3BB is apparently a network provider in Thailand, it's more that the ping time increase from hop 9 to 10 is the oversea connection from Thailand to the US. And a "high" ping time is not an indicator for region crossing fails. Instead, you should run a constant ping to one of the regions the disconnect occurred and check the packet loss to determine if it's a network issue or not.
  2. Which can easily be caused by an overseas connection and looks exactly the same if you do a trace route from Europe.
  3. It's just the old best-effort without any safety ropes region transfer mechanism that causes it: The current region sends your viewer the connect URL of the new region, then it shuts down it's circuit with your viewer. If your viewer then fails to connect to the region for whatever reason (network issue on your end, on your ISP's end, somewhere on the route to LL, within LL's network itself...), you're doomed as the current region already closed the connection and you get timed out after 60 seconds since you didn't receive any updates from any simulator at all. It's a typical case of LL under-engineering to leave out a fallback mechanism here.
  4. It's timing out on some hosts because they don't reply to ICMP ping messages. This doesn't have any effect on region crossings at all. Apart from that I have no clue what you are actually trying to say.
  5. Probably not. The only changes that were necessary were to change all API URLs from HTTP to HTTPS. The API itself didn't change at all.
  6. It currently still uses SL Share, but will be back to using the original Flickr upload code that was in place before LL came up with SL Share - you know, the one that uses the "constantly changing API" that LL couldn't keep track with, but magically still works without changes for over 7 years... 😂
  7. You can tweak as much as you want in the nvidia control panel since the way SL renders graphics causes the CPU being the bottleneck. If you run a tool like GPU-Z, you will see the GPU is pretty much idle. Worst offenders in terms of performance are the calculations involded rendering avatars and all the rigged meshes, since SL does of course NOT make use of the computing power of the GPU and uses the CPU for that instead. That's why you see terrible performance in places with many avatars around - running it 4K making it worse since you might end up having to render even more avatars that are in sight, but is actually bad because of all the unoptimized content and the hundreds of 1024x1024 textures "professional" creators have to slap on every face of their creations, leading to constant swapping out and rescaling of textures.
  8. There is no possible "ERROR -101" as result of clicking on the "Login"-Button. You are probably seeing this on the login screen itself. Did you try clicking the actual login button?
  9. If it did work before, it's a broken Windows installation and the file WER.DLL is missing.
  10. The Python icon is flashing because LL's auto-updater tool that is started before the viewer is written in Python. It probably has a pending update downloaded it now wants to install but can't because you don't have sufficient permissions. That's why it's asking for somebody having admin permissions on your system to do it. How/where/why it happens for you? I don't know. Make sure you have system administrator permissions on the account you're logging into OSX.
  11. Always this greedy greedy Discord app using 0.2% CPU and 80MB RAM...
  12. Sorry, but somebody awesome took me away already - and it's not Jessica. Kinda shame tho, because I probably could have learned how software engineering and development really works since obviously everything I learned in the last 20 years must have been total nonsense then...
  13. At least we now know somebody has no idea about how software engineering works...
  14. At least we have dedicated beta testers - unlike other viewers that constantly release untested stuff...
  15. Given I have merged pretty much all LL development viewers on frequent basis, we could toss builds with the latest stuff at ya within a few hours - unless you don't want to be beta tester and run untested stuff...
  16. As you might know our repository is publically accessible at all time - not just a drop of a ton of commits after release or after asking for it several times - so specific people making other viewers and usually yanking unreleased code into their own can continue doing so.
  17. Right now I am thinking of adding a "Blackline Alert" into Firestorm that makes a siren go off at ridiculous high volume... 🤔
  18. Didn't know your last two "releases" were betas. Now excuse me, I got something to do... /me starts scanning... 😁
  19. That explains the missing source code of the last 3... 4... releases?
  20. Well... apparently another closed-source release then... 😕
  21. What about the source code for this release? 😇
  22. Those are so called jellydolls. Increase the maximum avatar complexity value in (advanced) graphics preferences.
  23. Java isn't working in any browser - you are probably talking about JavaScript. But that's usually not a problem with the browser but with whoever created the JavaScript.
×
×
  • Create New...