Jump to content

Ardy Lay

Resident
  • Posts

    1,846
  • Joined

  • Last visited

Everything posted by Ardy Lay

  1. I watched, uhm, Superbowl 13. (I am not Roman.) Now I want to know what "coffee pads" are.
  2. Oh, and that "tool" is setting up TCP flows and TLS application connections to perform a "latency test", so take that into consideration.
  3. Hmm, a couple of under sea communications cables got damaged and are out of service. Maybe this has resulted in some congestion in same places on the Internet. Congestion delays can be highly variable. There is also a pretty sizeable outage on a terrestrial path in the US midwest that definately is causing some congestion.
  4. Looks like maybe @animats has been here.
  5. I got abducted by aliens today. I was so enthusiastic about it that they got suspicious and brought me back, so you are stuck with me.
  6. The next sign down states that unattended children will be given candy and a puppy.
  7. ... or your neighbor's dog, or that tree over there. Almost exclusively happened when the user did not keep SL in foreground while the viewer was baking textures. Sometimes it snagged an image of part of another program on the desktop! I remember seeing an Excel worksheet on a friend one day. She was not yet aware until I started reading it to her!
  8. Un-Deliverable Packet? Yeah, I know the Internet uses "best effort" algorithms to deliver most traffic. "Best-Effort" traffic is pretty much the first to be discarded when a queue's capacity is exceeded, and that happens constantly on the very "bursty" Internet. I am very much aware of this as I have been forced to resort to leased Ethernet private lines to connect remote sites. No amount of VPN and "predictive algorithms" and "forward error correction" applied by the person previously doing this work had been successful at getting the UDP data through intact. When you are dealing with real-time, live, audio and video transport and don't have the luxury of delaying delivery until the lost packets can be resent, as is done with "reliable" UDP transports like SRT, you find other ways to succeed, or you fail. End-to-end QoS is only available on "engineered paths" that currently cost more than "private lines". Sometimes the simplest solution is the one that works. You can take that both ways. Zal's tactlessly delivered missive has some evidence that they have "been there, done that", at least theoretically. I once got angry at being ignored on the same topic and rezzed a commercially available avatar head on the floor to demonstrate the problems caused when update traffic is sent to many agents. One seemingly benign object was scripted with texture and geometry changes in such a way as to generate many "full updates" per second. Multiply that by the number of agents present and BOOM, outbound network traffic volume increased to saturation at the simulator, and there were only 40 main agents and 12 child agents at the time. I later repeated the deed using the same object and saturated a simulator with only 25 agents present, but it took slightly longer for people to realize something wasn't right. There are many details to consider. Most people have a tendency to preach their pet problem or solution as the truth, but I suspect that, with all the various capabilities of client devices and network paths being used, multiple solutions will have to be implemented as none will remove all the causes the way my one solution removed the one cause on my point-to-point application.
  9. I am getting too old for this sort of workflow multiplicity. Perhaps there should be a warning: "Don't bother remembering how this works because it will never be required of or available to you again." I don't know. Maybe that's okay these days. So much of the stuff I have had to learn over the years is much more difficult for me now because someone put a "wrapper" around it that I don't understand so now I cannot do what I have learned without breaking stuff for the people that only learned the wrapper.
  10. See BYOIPv4. Maybe Linden Lab has some? Oh, looks like LL was using addresses belonging to Level 3 and Metronet. Ow.
  11. I am reading network equipment documentation about Quality-of-Service configurations and keep finding myself wondering about the terminology used. For example, why is "Best-Effort" used to describe the traffic class that gets the worst service?
  12. I just tell them to grow all their own food. They either go away or say something weak like "That's different!"
  13. Hmm, there's Windows Defender Firewall, which is not what was mentioned, and there is Windows Security, which does allow exclusions: I do not have any exclusions defined and I do not have any of the symptoms people keep saying are caused by not having exclusions defined. I suspect those symptoms appear if the hardware takes longer to do things than mine does. By many people's standards, I spend an insane amount of money on hardware.
  14. Runs fine on my computer with Windows 11. When I am having issues, I look at the forum and so are other people, so I just chill for a while as the world burns or whatever then try again later. Now, "runs fine" doesn't mean I am perfectly happy with what I consider "bugs", but, I tend to write bug reports then forget them.
  15. Windows 11 indicates Second Life Viewer is not HDR content. I thought it was.
  16. Wow. I came back and looked at my post with a machine that doesn't do HDR at all and ... oh wow. Yeah, that snapshot is HOT with color on it. I am going to have to keep this in mind. My snapshots are TOO POWERFUL! Oh well. I am a cartoon character, after all.
  17. We can finally properly model darkness as a lack of light.
  18. This is usually what I do but I am also spending most of my time or parcels where I set the environment. It sure doesn't hurt to try. Do make some effort to adjust your display for good contrast and color and look at some calibration samples before judging Second Life rendering. I find that most of the computers I have been asked to fix have been monkeyed with to not stress unprotected old eyeballs on white web pages.
  19. Hmm, perhaps I should increase the size of the "Disk cache." Texture memory: 15296MBDisk cache: Max size 1638.4 MB (100.0% used) Oh, I see. It's set to 4096MB and just hasn't gotten there yet or has purged textures that haven't been used for a bit.
  20. I should probably add that I am not using your monitor to view Second Life. I am using my monitor. That can make a huge difference! This setting is very colorful. Like, it's Kodachrome advertisement colorful, and that is quite deliberate. I use a monitor rated for HDR-1000 that has been color-calibrated recently. It looks so good compared to what I was using that the old monitors got relegated to back-office work.
  21. I don't feel like I am having troubles with it. Second Life Release 7.0.0.580782 (64bit) Release Notes You are at 217.1, 168.2, 61.6 in Lusk located at simhost-0492fe10b030d1133.agni SLURL: http://maps.secondlife.com/secondlife/Lusk/217/168/62 (global coordinates 255,705.0, 256,680.0, 61.6) Second Life Server 2023-06-09.580543 Release Notes CPU: 13th Gen Intel(R) Core(TM) i9-13900K (2995.2 MHz) Memory: 32509 MB OS Version: Microsoft Windows 10/11 64-bit (Build 22621.1992) Graphics Card Vendor: NVIDIA Corporation Graphics Card: NVIDIA GeForce RTX 4080/PCIe/SSE2 Windows Graphics Driver Version: 31.0.15.3168 OpenGL Version: 4.6.0 NVIDIA 531.68 Window size: 1919x1169 Font Size Adjustment: 96pt UI Scaling: 1 Draw distance: 64m Bandwidth: 10000kbit/s LOD factor: 4 Render quality: 5 Advanced Lighting Model: Enabled Texture memory: 15296MB Disk cache: Max size 1638.4 MB (100.0% used) J2C Decoder Version: KDU v7.10.4 Audio Driver Version: FMOD Studio 2.02.13 Dullahan: 1.12.4.202209142021 CEF: 91.1.21+g9dd45fe+chromium-91.0.4472.114 Chromium: 91.0.4472.114 LibVLC Version: 3.0.16 Voice Server Version: Not Connected Packets Lost: 2/5,319 (0.0%) July 25 2023 15:27:26
×
×
  • Create New...