| | |
| Galatea wrote: This would be with Viewer 2.4. And I'd say it's definitely not a coincidence, I've been having on-again off-again packet loss problems all weekend, and when it's going on, I'll go for long periods where Cool VL Viewer simply cannot connect to the grid at all, no matter how many attempts I make. At the same time, the official Viewer 2.4 connects most of the time. Whatever they changed in the new viewer definitely makes it much more robust when it comes to establishing a connection. You're right about the speed, it's definitely not any faster at all once connected, but it reliably connects when Cool won't. If the problem starts while I'm already connected, Cool works just fine, but if I logout, I cannot log back in without switching to the official viewer. | |
| | |
This won't be a Cool VL Viewer specific issue (you would encounter the same issue with any of SL v1.xx viewers, Snowglobe or any TPV based on the former two), and knowing that v2.4 works better in your particular case doesn't mean much either: for example, if your issue is related to a bad MTU (which is still my guess), this could come from the fact that v2.4 sends smaller packets on login than what older viewers do, but this doesn't mean someone else (who would require an even smaller MTU than you would) wouldn't also encounter this kind of issue with v2.4... The *real* problem is with your network, not with the viewer...
Again, look at your MTU... Under Linux it is as simple as typing "ifconfig" and looking at the MTU used on your ethernet card(s), then, if it reports 1500 (the default), try lowering it to 1492 (which is the maximum value for the PPPoE or PPPoA protocols used to encapsulate the traffic for ADSL and Cable MODEMs). Under Linux, it's just about typing "ifconfig ethX mtu 1492" (where "ethX" is the network card on which your cable MODEM is connected, for example "eth0"). Under Windows, you'll have to Google for "MTU Windows" since it requires touching the stupid registry...
This is just an assumption you make based on your own experience, but that might prove wrong for anybody else. The Cool VL Viewer is perfectly reliable in normal conditions (i.e. with a non-broken network).
It *is* much trouble, since any change to the login procedure would make the Cool VL Viewer incompatible with OpenSim grids (LL is not worried any more with such compatibility and their v2 viewer is plain incompatible with OpenSim). Beside, I'd rather use my sparse free time to code more useful features (such as Mesh support)...
This simply says the viewer is waiting for a reply from the server, but to truly try and spot where the difference between v1 and v2 viewers could matter, I'd need *both* the logs for v2 and for the Cool VL Viewer... Don't bother yet: better concentrating on fixing your network, because this is where the cause for your problem will be found.