Unable to connect to network (64)

[ZombieHunter]

I get this error on every startup. Won't start a new single player game. Why is it trying to contact servers for a single player game?

[Roderick]

The game sets up a server on your system and sets you as onliest player. That is how single player is handled. Many games who provides LAN do that because it doesn't make any different wether you play solo or in a party - the surrounding is the same.

If you get that message, check your firewall. It might be blocking the game from acting as server or doesn't allow you to connect to your own system.

[Vants]

I am having the same issue right now except it says Connection Lost (10), My firewall isn't blocking it. Anyone know how to get this game to work?

[ZombieHunter]

No the firewall allows everything for the game. Still same issue.

[Roderick]

You run Windows 10?

[ZombieHunter]

W7 64. And if it is setting up a LAN why wouldn't it allow that? LAN is usually trusted.

[Roderick]

Just trying to get to the issue. But I am running Win 7 64 bit as well and don't have any problems.
I had that message ONCE... but just rebooted my system and have never seen it again... :/

[ZombieHunter]

Hmm. Maybe I need to restart Steam or something. I can get past the message on second try but then in full screen it just flickers and in windowed it just goes black with the main menu barely visible in the background.

I know I've played this b/c I had a character. I deleted them trying to fix this but I know I've played it on W7.

[Roderick]

Maybe try the community patch... I know it fixes some memory problems in game... don't know about that particular issue, though.

[ZombieHunter]

Firewall off. AV disabled. Same issue. Looking at wireshark to see if I can figure out if it is trying to send some data. If all else fails I'll disassemble the damn thing and put NOPs where this code is.

[Roderick]

Is Sacred2.exe running in administrator mode?

[ZombieHunter]

Yep. Admin for both executables. I removed the client and server from the firewall and allowed Windows to pop up saying it they needed access. Also turned off DEP for both just in case it was trying to decrypt to a memory buffer and then jump to the start of the buffer and execute which DEP blocks.

I've verified all the addresses outgoing and incoming in WireShark and none of them are from the game. So unless it is sending over loopback or localhost (127.0.0.1) it isn't sending anything. So no reason to fail.

I might try to actually setup a MP game and see what wireshark shows. When it tries to connect to some hardcoded IP address Wireshark will catch it. Then I can find that constant in the disassembly and find out where it is used and kill the offending section of code. Maybe. I hate pouring through assembly code to fix a game. And if the EXE is encrypted I won't be able to save anything to it.

Annoying. If I had the source code I could fix it in a snap.

My suspicion is that the game renderer is throwing an exception and somewhere in the code the path it takes says it is a network failure when in reality it has nothing to do with that. If you try catch around a huge chunk of code and then say all errors from said chunk are X this tends to happen. It is extremely annoying to fix these issues even when you have the source code.

[Roderick]

That's a lot of dedication. :D
Well... "fix a game" might not hit it... since it is running for others well. And it was made for Windows XP. Can't imagine the amount of possible obstacles through that alone... ^^'

[ZombieHunter]

I'm on IPV6 but that should be handled way down inside of Windows so that can't be it. No clue why it is doing this.

I do have Tunngle so maybe I could setup a fake LAN game for single player to fool it into thinking it all works. Maybe the Tunngle adapter requiring highest priority is messing the game up. Who knows?

First time I get the error. Second time black screen in windowed mode and flickering in full screen.

EDIT:
Doesn't work at all. Disable PhysX and I get black screen, enable it and I get network error. Can't install legacy PhysX b/c newer installed. I suspect around July 2018 Nvidia deprecated legacy PhysX which is why I can't get it to work.

[Vants]

Though I am not tech savy, If you need some comparison or solutions with process of elimination help. Just ask; since I have similar issues with connection error (10).

For legacy physX, I have also tried installing via executable and replace and renaming the redlist phyx with the legacy version to hopefully trick the game (lol). None of which made any difference. Since you are able to provok a different reaction with the black screen zombiehunter would it work if you replace the redlist phyx like i did? ( I've not a clue )

[ZombieHunter]

I uninstalled it. It is a PhysX issue and even when I get around the connection error it goes to a black screen.