[Error Code=7:0:0:1026:101] Character stuck in loading screen in Divinity Reach

[malevolence.9487]

Hi, my Necro is stuck in Divinity Reach loading screen :anguished: all my other characters works no problem, only my Necro is stuck.

 

I did try the -repair parameter and it did repair but didn't solve the issue, any suggestions?

[Healix.5819]

Try guesting to popular servers in an attempt to get into different instances. You can use -maploadinfo to see more details on the loading screen, noting the IP to determine which instance you're in.

 

If you can't get into a different one, you'll need to use a VPN. Assuming you have the same problem as other recent complaints, you're unable to access specific IPs. For more details, you can trace the IP to see how far it goes (cmd.exe > tracert #.#.#.#).

 

If only the one character is stuck however, and you're able to access the same map/IP with other characters, then contact support. There have been cases where characters have become bugged, which only support can fix.

[chaox machine.1534]

> @"Healix.5819" said:

> Try guesting to popular servers in an attempt to get into different instances. You can use -maploadinfo to see more details on the loading screen, noting the IP to determine which instance you're in.

>

> If you can't get into a different one, you'll need to use a VPN. Assuming you have the same problem as other recent complaints, you're unable to access specific IPs. For more details, you can trace the IP to see how far it goes (cmd.exe > tracert #.#.#.#).

>

> If only the one character is stuck however, and you're able to access the same map/IP with other characters, then contact support. There have been cases where characters have become bugged, which only support can fix.

 

What is the reason though that we are unable to access specific IPs? If you ping these ip's they just time out after amazon something.

[Healix.5819]

> @"chaox machine.1534" said:

> What is the reason though that we are unable to access specific IPs? If you ping these ip's they just time out after amazon something.

 

They ignore pings, so you can't actually ping them (though you could TCP "ping" them). As for not being able to access certain IPs, I can only guess. Either your ISP or the networks aren't routing it properly, or it's a problem on Amazon's end. You can tracert the IP to see the route, some of which won't respond due to ignoring pings.

[malevolence.9487]

Hi all, I didn't have time to try yesterday at all, but today, it works..... :) , so no idea what was causing the issue. Thanks.