Support FAQ:修订间差异

添加243字节 、​ 2024年5月20日 (星期一)
无编辑摘要
无编辑摘要
无编辑摘要
第192行: 第192行:


== Strange graphics when moving with Motion Prediction enabled ==
== Strange graphics when moving with Motion Prediction enabled ==
# In the Diablo 2 in-game Video Options (ESC Menu), change the Lighting Quality to High
# In the Diablo 2 in-game Video Options (ESC Menu), change the Lighting Quality to Medium or High
# Also try turning Perspective Off in the same options menu
# Also try turning Perspective Off in the same options menu


== Strange color shifts ==
== Strange color shifts ==
第555行: 第553行:
Try creating games on different game servers. If you continue to receive the same error then it is likely that the game server you were originally in crashed.  
Try creating games on different game servers. If you continue to receive the same error then it is likely that the game server you were originally in crashed.  


The realm server still thinks your character is in-game because the game server did not report you leaving the game since it crashed. Therefore, the realm doesn't let your character into another game.  
The realm server still has your character and stash tagged as in a game because the crashing server could not log you out. The realm will not allow the character/stash into a "second" game at the same time. Because the shared stash is used by all characters in a "mode" (HC Ladder | SC Ladder | HC Non-ladder | SC Non-ladder), any characters within the same mode may also experience the FTJ issue.
 
While rare, this does unfortunately happen and the only fix is to wait for the game server to restart and let your character out of the void.  This can take anywhere from a few minutes to a few hours depending on when the server restarts.
 


The only fix is to wait for the game server to complete its scheduled restart and report that you are not logged into it. There's no way to check when this is going to happen, but a general estimate can be based on the time the server said it had left when you created your game.


== Unable to connect to Battle.net ==
== Unable to connect to Battle.net ==