PDA

View Full Version : NP1013, I FOUND A WAY!



Gloomrise
May 13, 2016, 04:08 PM
Hey everyone, so I know a lot of people have had problems with PSO2 crashing after about 30 seconds in the game, with error code NP1013 escorting them out. Although there are many different theories as to why this happens, the most prominent theory would be a Gameguard error. This is DEFINITELY the problem. I spent three days trying to resolve the issue, and complaining to both Sega and Gameguard crossed my mind, but eventually I figured it out.

Number 1: I know it sounds crazy, but delete the Gameguard folder. It's usually located in the Pso2 file. If you delete this, you would basically be taking away Gameguard's food. I use the food example because the program thrives on files it already has, so delete its files, and make it go hungry.

Number 2: Make sure the tweaker is up to date. The problem never left until I finally agreed to get version 3.0.8.2, even though the only update was a Spanish and Russian patch. Don't worry about redownloading anything if you do get 3.0.8.2, because all of the information carries over, as long as you don't delete anything except Gameguard.

Number 3: Make sure you have all the patches that are necessary, but DO NOT fix the Gameguard errors. If you fix the Gameguard errors, it will restore the files that you previously deleted, and Gameguard will be up and running again. You already deleted Gameguard's food, so make sure it doesn't go to Wal-Mart for more.

After researching and doing a lot of things that didn't fix the problem, THESE actions led to my game being uninterrupted by error code NP1013. Now, I'm playing the game perfectly fine. I really hope this helps you guys! If not, I'm sorry.

Qualia
May 13, 2016, 04:53 PM
I ran into this last night, restarted my computer, and everything was fine.

Flaoc
May 13, 2016, 04:56 PM
uhh ok?

Variant
May 13, 2016, 06:18 PM
Er, it's not so much theories about why, we actually know exactly why it throws the error.

I think I've actually documented out in another thread that the issue is GameGuard finding random shit and throwing a NP1013. We've actually confirmed this by looking at the GameGuard logs.

It's also inconsistent, because sometimes it'll say something along the lines of:

GAMEHACK DETECT: Chrome.exe

or

GAMEHACK DETECT: C:\Program Files (x86)\Cheat Engine.exe

or

GAMEHACK DETECT D:\Downloads\PSO2 Tweaker.exe

etc...

or it'll just not do anything and it'll be OK.

Some people say that deleting GG and reinstalling it works (maybe it's been rolled back to a previous version?), but it's so inconsistent it seems like confirmation bias (fwiw, I didn't do the GG delete thing and I haven't gotten NP1013'd in the past few weeks).

GG is just a shitty excuse for security anyway. Causes a bunch of trouble and in the end doesn't really even stop anything for the trouble it causes, I wish SEGA would just drop it and actually figure out a better client-server architecture so they don't need to rely on shitty client-side security solutions.

HentaiLolicon
May 13, 2016, 06:57 PM
Just use vanilla client. About chrome, i advise to use 64bit version.

MDashK
May 13, 2016, 07:00 PM
I personally use Waterfox (the 64-bit variant of FireFox) and NEVER had any issue in all these years.
Also, DISABLE Flash in FireFox/WaterFox. FLASH CAUSES ISSUES AND CRASHES!
And no, you don't need FLASH active for YouTube. YouTube has been using HTML5 for a LONG time now.

Gloomrise
May 13, 2016, 07:05 PM
I agree. The game runs fine, and there are practically no reasons to put THAT much security on it. The worst that can happen is that someone accesses your account, but other than that, I play a lot of games that don't rely on clients other than the security you put on your own account.

Gloomrise
May 13, 2016, 07:10 PM
Yeah, I heard that background apps and certain programs can conflict with games. Especially when you're using Javascript, Flash, and Chrome.

Variant
May 13, 2016, 07:41 PM
GG doesn't like that Chrome runs in a sandbox, so that's why I assume it gets triggered (it used to do this aggressively a while back and the way to get around it was -nosandbox).

It's stupid. Because sandboxing is a safety feature in chrome :/

HentaiLolicon
May 13, 2016, 08:04 PM
Well, chrome's sandbox of 64-bit ver works in harmony with GG now.

TaigaUC
May 13, 2016, 10:33 PM
http://s2.quickmeme.com/img/9c/9c8962243dc6e34e81384148cfbb9a14b14a08cec665a5ee77 e3d697eaa38206.jpg

wefwq
May 13, 2016, 10:50 PM
Somehow, it managed to be less helpful than average "update your driver" advice...