@Comegalletas said in why i cant log in to the game its say " An unexpected error occured" [NP1002] please i need help:

Hi @M1kuCh4n I do have Windows 10 Pro Insider Version 2004 (SO compilation 21292.1010) do you know any way to fix this ? (besides the obvious complete windows wipe out to a non Insider version)

Thanks inm advance !

Not at the moment, no. And INCA sounds like they are taking a look at this issue. I'm still looking for Windows Insider's documentation since there is no publicly-available resources as to why GG got tripped, possibly an internal Windows mechanism and/or GG internal allowed Windows version whitelist.

I'll report back if I manage to make a breakthrough.

I do notice the behavior of PSO2 decided to nuke itself if you are dual-booting (mine was the case of Windows 10 and macOS). Don't know if that is the same situation in your case but still something to look at.

Interesting, since NP1002/NP0 can still be tripped even if Core Isolation is off.

Are you running any Insider build of Windows by any chance?

What version of Windows are you using?

Apparently Insider build of Windows (Windows 10 Insider and Windows Server 2022 Insider) causes GameGuard to spit out NP1002 and NP0.

@coldreactive The game engine is still running under DirectX 9, so I'm guessing the SEGA devs themselves aren't having a lot of options on their table without rebuilding the game from scratch.

Judging from the anti-cheat solutions perspective, they won't "port" or create a native version to other OS without getting the greenlight from the publisher itself - which is SEGA for a sole reason: Hugh manpower and resources investment for a "small" fanbase won't cut it (even though macOS and Unix-based users are lots).

Funny how myself and my IT team have to provide VDI (Virtual Desktop Infrastructure) solution to some customers that requested this requirement just to play PSO2 for some reason. At least it works, for now.

@coldreactive If my current findings are correct, first GameGuard looked for bootstrapping info (CPUID flags, listing running processes and match against an internal blacklist), secondly it begins to check for any "suspicious" programs by scanning the entire memory range for the duration of the game. I managed to login, screwing around for a while before GG unexpectedly terminate PSO2 (keep in mind during this time, I did install VMware Tools. Things when back to normal after uninstalling that).

As for Wine/Proton won't work, possibly 3 reasons:

• Incorrect mapping of memory due to how Unix-based OS restrict access to currently running memory map.
• Wine/Proton have debuggers (winedbg and Wine's personal implementation of Windows Debugging API) that can attach to processes to backtrace games' codes during runtime. This alone already set a giant red flag for SEGA.
• Patching GameGuard can only fix the problem temporary, since it is designed to work exclusively with Windows. Until INCA decided to man up and release a Linux version of their "anti-cheating solution", I doubt we can play without GG screaming NP1013 and nuke PSO2.exe to orbit.

It's true that Wine/Proton isn't "emulators", but it isn't ready to game, especially if that particular game have anti-cheat in-place IMO. So virtualization is currently the only way to circumvent that without getting yourself deep into technical issues.

I think the main reason why SEGA implement this is just trying to stop entry-level cheaters and bots for using obvious tools like Cheat Engine, ArtMoney,.... Obviously SEGA and INCA knew quite well that they can't stop people that knew what they are doing (trust me when I say the game client itself isn't the only piece of software where you can directly connect to SEGA servers.). The larger the system, the more vulnerable it becomes.

Since we are approaching the grey zone between perfectly legal conversation and sensitive stuff, I'll leave the players to figure it out for themselves.

TL;DR: SEGA probably afraid of reverse-engineering the game's code and/or cheating in their system, so they ban anything that is suspicious. "Better safe than sorry" mentality.

@MisutaaUrufu said in PSA: Virtual Machines Are Blocked By SEGA (Mac, Linux):

@TricolorBloom74 this is a problem for Mac users. GPU passthrough does not exist on the macOS platform. Parallels Desktop 15 provides Metal GL translation, turning Windows GPU calls into Apple's own Metal graphics library, which yields significantly improved performance, provides eGPU support, and allows for proper DirectX 12 support. Other VM applications are not designed for this (as it would require writing a graphics driver just for Macs in a new language only supported on newer hardware. Parallels has no worries as it is a Mac only program).

It's nice to know at least Linux users have a "way around" it, but it's still a workaround, not a solution.

There is no bypass as of the release of Big Sur (11.0), and Apple already tighten by forcing third parties to use their Hypervisor.framework as the base of operations.

So I suggest getting yourself a bare-bone hypervisor (a certain VMware hypervisor or other open-source Type 1 hypervisors), do some PCI passthrough, modifying config as needed, install Parsec and be done with it.

After a couple of testing, GG only checks by looking at CPUID mask (Task Manager, and probably using blacklist to terminate if found any strings matched as virtualized), MAC address of the ethernet card and the presense of VMware Services (found in VMware Tools).

Sauce: I do sysadmin for a living.