<bump>

Not sure if anyone is still having this issue..but, if so...

Please try compiling in full debug and run your server for a given period.

If you receive any debug assertion messages (with resulting server crashes,) please post them.

I only need a few instances of this occurring and pointing to a debug assertion as the cause of the crash.

Afterwards, you may return your server to it's original state.


Thanks!

Anyone ever get this one figured out? Are people still experiencing it with the latest source?

I've honestly not checked in a while. I'll pop on and head to CoM this evening. That was one zone I always had issues with on my server.

I am having this issue with RoF2 on peq. I am in pok and tranq. zoning between will mix up who can 'see' who

Seems the problem still exist. I wonder around when this actually started popping up. Knowing when the first people started seeing it will narrow down what source change caused it.

First report on PEQ was Feb 10th. Trevius commented it might be this change:-
https://github.com/EQEmu/Server/comm...55f3ca0585226c

But.. I think that change was reverted.

Definitely still happening out in the wild!

All my clients are using Titanium, so far its only been reported in Hate/Sky but I'd imagine it happens elsewhere too. Server is a basic 2core/4GB Win2008R2 VM, running the updated version of the Windows repack by Akkadius. I'll test with rezzing when I can later to see if that can force reproducing the error condition.

can you not see any npcs/clients at all or is it specific ones? In the older clients way back when they had the 4k spawn id cap we had to make sure the spawn id's went too high.

Most of that should be figured out in eqemu now, but that was the only reason that came to mind that *all* would be missing, simply the eq client is not parsing the bulk spawn packet correctly.

I believe its only specific clients/NPCs.

I actually saw both happen in Sky the other night on the 2nd island. Another player would pull, and no one but his players (he was boxing 3 or 4 that night) would see the mob. We couldn't target/assist to get a mob target let alone seeing it. We didn't really find a way around this one.

Also had the other where a player would drop from our instance of the zone, but could still see it talking in /say. Only a camp would fix that issue.

Had a player report it last night in Crushbone and Greater Faydark. One was using SoF and the other was Titanium. Since both were non-instanced zones it did cause me some pause.

Just so all the info is out there - my players are also reporting an issue with manastone usage and the health loss not being shown till the next server tick, and AOE mezzes not lasting a full tick before breaking either.

I can confirm this is occurring on Storm Haven and I have not even updated our source since like March/April of this year.

At least in one zone I can confirm (Valdeholm) it is happening to both myself and another player (though not all players seem to have the issue).

It is not MQ related
It is not client related (Same problem on UF->ROF)
It is not script related (disabled all scripts in zone).
You can not /target the clients who you can not see with GM commands.

Though I just assumed that this was fixed in later source update and not still occuring

Anything been done in zone versioning in a while? Sounds like some kind of zone/entity_list schism.

My EqEmu source is dated back to around January 2015. No changes I have made to my source could have caused this type of behavior, nearly positive. I am changing things related to mitigation, combat, spells, etc.

For reference: http://www.eqemulator.org/forums/sho...&postcount=267

That may give us a time-frame for when this actually started.


I seem to remember an issue about some changes to SoF+ appearance packs..and then it was reverted, or something?


EDIT: provocating, I think those changes were made after January 2015.