WhiteCoreSim / WhiteCore-Dev

WhiteCoreSim - Software to create your own virtual world
BSD 3-Clause "New" or "Revised" License
26 stars 34 forks source link

Duplicate of avatar remains in location after teleport if other avatars are present. #157

Closed stormsonweathers closed 8 years ago

stormsonweathers commented 9 years ago

Hello again, There's seems to be a duplicate glitch that involves an avatar that teleports (like returning home, etc) if another avatar is present, but a copy of the avatar remains and replicates the movements of the recently teleported one.

This is on the current build as of 09/13/15.

greythane commented 9 years ago

Hi Storm, Could you provide some more details on this error? i.e. How are you checking on the copy avatar etc.? I assume you have multiple avatars logged in to multiple regions? The error occurs when you teleport from region A to B? Which viewer are you using? (Probably not a problem but worth checking) System.. Windows, linux, Mac, setup : grid/standalone : Dtatbase (MySql/SqLite)

And anything else that may be useful to reproduce the problem G

stormsonweathers commented 9 years ago

Hello, I was checking with multiple Windows machines running the latest Firestorm Viewer on the same network with different avatars. I've also had some friends log in and they to have noticed similar events using different viewers such as Singularity.

On the technical side for the server: The database is set for Mysql/MariaDB on OpenSUSE with 8gb in a VM setting while WhiteCore - the latest as of today - is running on Windows 7 Professional also on a VM with 16GB in standalone mode. (Both VMs are running on top of Hyper-V using Windows Server with 64GB of total RAM and two 3Ghz 4-Core Xeon Processors)

The error occurs either on multiple regions or the same one (there is one megaregion and several 256x256 standard regions; same result)

fly-man- commented 8 years ago

At the moment, can't replicate this issue. However placing this on the top of the 0.9.4 issue list

emperorstarfinder commented 8 years ago

I haven't seen this issue reproduce as of yet. I am guessing this might have either resolved itself or has been fixed in updates to date.