Hey firstly, do you guys still use the bug tracker? If so ill start posting issues on there again.
I just found out then why sphere shows this error.
Code:
21:27:DEBUG:__ thread (5292) __ | # | _____ function _____________ | ticks passed from previous function start ______
21:27:DEBUG:>> 5292 | 0 | NetworkManager::processAllInput | +0
21:27:DEBUG:>> 5292 | 1 | NetworkInput::processInput | +0
21:27:CRITICAL:"Access Violation" (0xfffd5ba9), in Sphere::Tick() #3 "network-in"
This error is the result of the Ultima Online client being open when you start up sphere. I guess it cant access the right things or get the right permissions while UO is runnning.
Steps to re-create issue.
1) Open up sphere
2) Open up client and log in
3) Close sphere (or in some cases let it crash :] )
4) while the client is still hanging with the "connection lost gump" leave it be.
5) Open up sphere again (note. with the client still in the connection lost state)
6) this error will appear
Ps. I just found out if the client does not stay on the connection lost screen then the error does not appear.
Home
Forum
Downloads
GitHub
SphereWiki
Search
Discord Channel
Facebook
Twitter
![[+]](images/collapse_collapsed.gif)
