Post: #1

I used to compile the latest nightly.
At login, the following message is displayed in the console window.


17:38:1:Login 'Admin'
17:38:1:Setup_Start acct='Admin', char='*********', IP='***.***.***.***'
17:38:DEBUG:__ thread (4612) __ | # | _____ function _____________ | ticks passed from previous function start ______
17:38:DEBUG:>> 4612 | 0 | NetworkManager::processAllInput | +0
17:38:DEBUG:>> 4612 | 1 | NetworkInput::processInput | +0
17:38:DEBUG:>> 4612 | 2 | NetworkInput::processData | +0
17:38:DEBUG:>> 4612 | 3 | NetworkInput::processData | +0
17:38:DEBUG:>> 4612 | 4 | NetworkInput::processGameClientData | +0 <-- exception catch point (below is guessed and could be incorrect!)
17:38:DEBUG:>> 4612 | 5 | PacketChatButton::onReceive | +0
17:38:DEBUG:>> 4612 | 6 | CClient::Event_ChatButton | +0
17:38:DEBUG:>> 4612 | 7 | CChatChanMember::SetChatActive | +0
17:38:DEBUG:>> 4612 | 8 | CChatChanMember::GetChatName | +0
17:38:CRITICAL:"Access Violation" (0x80a8b), in SUB: NetworkInput::Message::ProcessMessage()
17:38:DEBUG:1:Parsing Packet len=85 id=0x34 [2016/09/11 17:38:50]
0 1 2 3 4 5 6 7 8 9 A B C D E F
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
0000 34 ed ed ed ed 05 00 01 b4 85 bf 00 09 00 0b 4b 4..............K
0010 4f 52 00 b5 00 00 00 00 00 00 00 00 00 00 00 00 OR..............
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 c8 12 .....
17:39:1:'Admin' commands 'go doom'=1


Operational problem does not occur.

Why, that the problem occurs in versions after August 27,

What is the meaning of the console message?

Clients are using 4.0.49.69.

Post: #2

I presume 4.0.49.69 is an SA enhanced client?
sphere is not 100% compatible with enhanced clients, but anyway, that error should not happen

here you can download all recent builds of sphere 56d, just click on the build, go to artifacts page and download the .exe
https://ci.appveyor.com/project/coruja74...ce/history
try test some builds starting with build 180, this will help us to find on which build the problem started, after we find the build number it will be easy to fix this error

Post: #3

Coruja, thank you answers and help.


I check the results

0.56.4.183 [Replaced redundant GetAccount () with m_pClient] until the warning does not occur.

0.56.4.184 [Replaced redundant GetClient () with m_pClient] The warning that occurs in later.
.
.
.
0.56.4.207 [Fixed: NPCs not looking around anymore after start wandering action] version that occurs warning.

Of course, that is achieved by warning on all account, not an admin account issue.

But only warnings occur, as it does not cause any problems in the operations. (Server crash or ETC)


If this can be resolved, I will ask for help when the next build.


P.S: Does Enhanced client vendor buy the issue can not be resolved?

Post: #4

so the build 183 is working fine and the problem started on build 184?
try add this test event on your char to check if it can make the error stop:

PS: I don't know if the vendor buy dialog is working on enhanced clients, probably not. It's not impossible to make it work because it's working fine on RunUO. But to be honest this thing already bring so many headaches to devs that we give up lol

Post: #5

coruja, thank you.

I used the event.
As a result, the issue has been resolved.
I tested several times under different accounts.
However, a warning message is no longer output.

Post: #6

try using the latest nightly build, I think this console error is fixed now

Post: #7

coruja, thank you.

I tried to test without using the Event as 0.56.4.210.

But, unfortunately, it had a problem with the console warning messages.

So, even now use the Event.

Post: #8

nightlys arent nightly? (havent updated in awhile)

Post: #9

(09-21-2016 08:27 PM)midikit Wrote:  coruja, thank you.

I tried to test without using the Event as 0.56.4.210.

But, unfortunately, it had a problem with the console warning messages.

So, even now use the Event.

I'm testing EC client 4.0.52.2 using build 210 here and it's working fine without errors. Are you sure that the error still the same? Or it's a new error?

(09-23-2016 01:53 AM)x77x Wrote:  nightlys arent nightly? (havent updated in awhile)

nightly builds still nightlies, but you can also get "instantly builds" directly from AppVeyor, which is the CI engine that we use to test all commits sent to sphere source code on GitHub

Post: #10

coruja, always appreciate the help.


Perhaps, it seems that the same error.

15:01:5:Login 'iwtt'
15:01:5:Setup_Start acct='iwtt', char='IWTT', IP='***.***.***.***'
15:01:DEBUG:__ thread (3836) __ | # | _____ function _____________ | ticks passed from previous function start ______
15:01:DEBUG:>> 3836 | 0 | NetworkManager::processAllInput | +0
15:01:DEBUG:>> 3836 | 1 | NetworkInput::processInput | +0
15:01:DEBUG:>> 3836 | 2 | NetworkInput::processData | +0
15:01:DEBUG:>> 3836 | 3 | NetworkInput::processData | +0
15:01:DEBUG:>> 3836 | 4 | NetworkInput::processGameClientData | +0 <-- exception catch point (below is guessed and could be incorrect!)
15:01:DEBUG:>> 3836 | 5 | PacketChatButton::onReceive | +0
15:01:DEBUG:>> 3836 | 6 | CClient::Event_ChatButton | +0
15:01:DEBUG:>> 3836 | 7 | CChatChanMember::SetChatActive | +0
15:01:DEBUG:>> 3836 | 8 | CChatChanMember::GetChatName | +0
15:01:CRITICAL:"Access Violation" (0xfff6317b), in SUB: NetworkInput::Message::ProcessMessage()
15:01:DEBUG:5:Parsing Packet len=83 id=0x34 [2016/09/23 15:01:05]
0 1 2 3 4 5 6 7 8 9 A B C D E F
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
0000 34 ed ed ed ed 05 00 01 cb 8d bf 00 09 00 0b 4b 4..............K
0010 4f 52 00 b5 00 00 00 00 00 00 00 00 00 00 00 00 OR..............
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 ...


P.S: Does drag and drop the problem of container and corpse is impossible to solve?