irnlake Posted December 20, 2009 Report Share Posted December 20, 2009 Yes, bad opcode. Then, I get a series of TCP connection resets and a crash to desktop. This usually happens when I am changing areas or attempting to trade with a vendor. Happens some what at random. I am able to play for a bit, but no longer than 20 mins before I get bad opcode messages. Anyone else got this problem? Quote Link to comment Share on other sites More sharing options...
bondct Posted December 21, 2009 Report Share Posted December 21, 2009 Yes, bad opcode. Then, I get a series of TCP connection resets and a crash to desktop. This usually happens when I am changing areas or attempting to trade with a vendor. Happens some what at random. I am able to play for a bit, but no longer than 20 mins before I get bad opcode messages. Anyone else got this problem? I am gtting these random crashes as well... Quote Link to comment Share on other sites More sharing options...
Falstar [MOD] Posted December 21, 2009 Report Share Posted December 21, 2009 Yes, bad opcode. Then, I get a series of TCP connection resets and a crash to desktop. This usually happens when I am changing areas or attempting to trade with a vendor. Happens some what at random. I am able to play for a bit, but no longer than 20 mins before I get bad opcode messages. Anyone else got this problem? I've got this problem also. On the old forums there was a topic with just about the same title. Several things were suggested but I don't recall anyone saying they had a fix. I'm inclined to say it's due to an update as I didn't have problems till an update went through. (about a month now maybe?) I also see another topic with problems with N7 proxy in general. I also noticed it was prone to happen when I was gating, docking, or trading with vendors like you said. The 1st 2 make sense as those are sector changes, but I'm not sure what would cause a crash talking to a vendor, unless maybe it is the accessing of inventory? Recently I'm able to trade with vendors much better. I would suggest you post a screenshot of your n7 output, that way the team can see what opcode errors you are getting and when, and maybe that will shed some light on them. The only ones I have are from several updates ago. Quote Link to comment Share on other sites More sharing options...
irnlake Posted December 21, 2009 Author Report Share Posted December 21, 2009 Here, you see that sometimes there is no bad opcode before I get kicked off. I don't know why the ports would need to reset so often. I do notice a considerable increase in the time that it takes to load the maps and trade with vendors compared to several months ago. 20/12/09 09:26:58 MVAS thread running 20/12/09 09:26:58 Received Master login confirm, new UDP port is 3515 Avatar_id = 1073787145 20/12/09 09:26:58 <server> Master Login received - UDP sector port: 3515 20/12/09 09:26:58 >> Commence Login check 20/12/09 09:26:58 Sending Login packet - connection active 20/12/09 09:27:36 ---> Server handoff 20/12/09 09:27:37 Received Master login confirm, new UDP port is 3635 Avatar_id = 1073787145 20/12/09 09:27:37 <server> Master Login received - UDP sector port: 3635 20/12/09 09:27:37 >> Commence Login check 20/12/09 09:27:37 TCP connection on port 3500 closed gracefully 20/12/09 09:27:37 Sending Login packet - connection active 20/12/09 09:27:45 Sending StartAck to Server 45321 20/12/09 09:27:47 >> Login check: Login OK 20/12/09 09:31:25 Bad opcode through to Proxy: 0x4900 Length: 0xc21 20/12/09 09:31:25 Bad opcode through to Proxy: 0x6e69 Length: 0x7242 20/12/09 10:43:23 MVAS thread running 20/12/09 10:43:24 Received Master login confirm, new UDP port is 3635 Avatar_id = 1073787145 20/12/09 10:43:24 <server> Master Login received - UDP sector port: 3635 20/12/09 10:43:24 >> Commence Login check 20/12/09 10:43:24 Sending Login packet - connection active 20/12/09 10:43:33 Sending StartAck to Server 45321 20/12/09 10:43:34 >> Login check: Login OK 20/12/09 10:44:07 TCP connection on port 3500 was reset 20/12/09 10:44:07 Client connections terminated 20/12/09 10:44:08 Client has terminated. Sending termination signal. 20/12/09 10:44:07 TCP connection on port 3801 was reset 20/12/09 10:45:58 MVAS thread running 20/12/09 10:45:58 Received Master login confirm, new UDP port is 3635 Avatar_id = 1073787145 20/12/09 10:45:58 <server> Master Login received - UDP sector port: 3635 20/12/09 10:45:58 >> Commence Login check 20/12/09 10:45:58 Sending Login packet - connection active 20/12/09 10:46:07 Sending StartAck to Server 45321 20/12/09 10:46:08 >> Login check: Login OK 20/12/09 10:48:03 Bad opcode through to Proxy: 0x0000 Length: 0x0 20/12/09 10:48:03 Bad opcode through to Proxy: 0x0000 Length: 0x100 20/12/09 10:49:09 TCP connection on port 3801 was reset 20/12/09 10:49:09 Client connections terminated 20/12/09 10:49:13 Client has terminated. Sending termination signal. 20/12/09 10:49:09 TCP connection on port 3500 was reset 20/12/09 10:53:34 MVAS thread running 20/12/09 10:53:34 Received Master login confirm, new UDP port is 3635 Avatar_id = 1073787145 20/12/09 10:53:34 <server> Master Login received - UDP sector port: 3635 20/12/09 10:53:34 >> Commence Login check 20/12/09 10:53:34 Sending Login packet - connection active 20/12/09 10:53:35 TCP connection on port 3801 was reset 20/12/09 10:53:35 TCP connection on port 3500 was reset 20/12/09 10:53:35 Client connections terminated 20/12/09 10:53:39 Client has terminated. Sending termination signal. 20/12/09 11:03:02 MVAS thread running 20/12/09 11:03:02 Received Master login confirm, new UDP port is 3635 Avatar_id = 1073787145 20/12/09 11:03:02 <server> Master Login received - UDP sector port: 3635 20/12/09 11:03:02 >> Commence Login check 20/12/09 11:03:02 Sending Login packet - connection active 20/12/09 11:03:03 TCP connection on port 3500 was reset 20/12/09 11:03:03 TCP connection on port 3801 was reset 20/12/09 11:03:03 Client connections terminated 20/12/09 11:03:07 Client has terminated. Sending termination signal. Quote Link to comment Share on other sites More sharing options...
C Del[IS] Posted December 21, 2009 Report Share Posted December 21, 2009 This error indicates data corruption or loss. I experience this problem as well, and it is likely an issue on the server side. Try to bear with the server developers as they continuously work on the comms system. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.