Hazaatan Posted February 2, 2021 Share Posted February 2, 2021 I flew in to pick up some stuff at Alioth 17. Was waiting for the market to load up, then I got kicked from the game. Now when I try to log back in, the loading time is really really slow and I get kicked off the server before even loading up. Is this common? Is there a way to get back in? I have cleared my cache, but still not loading up. *FIXED* NQ got back to me and gave me these instructions: Thanks for reaching out.I'm sorry to hear about what you have experienced. To reduce lags and disconnects, please try these in-game graphics settings:1. Set Dynamic Shadow settings to Low (not None)2. Set Environment Shadow settings to Low (not None)3. Turn off Volumetric Clouds4 Reduce the number of thread counts to 2After this, delete your shader cache as well. To delete the shader cache, navigate to %localappdata%\NQ\DualUniverse and delete the file shader_d3d11.cache, then try to relog. Worked for me. Link to comment Share on other sites More sharing options...
fiddlybits Posted February 2, 2021 Share Posted February 2, 2021 I haven't had this issue at market 17 specifically, but have had issues logging in at a certain location. Here are some options: 1. Clear your cache using the upper right menu in the login screen and try logging in again. 2. You can ask NQ for a teleport to a different area in discord or the in game support channel. I think they require tickets with logs now for teleports, so make a ticket first and reference it in your request in chat. 3. If you do not have anything in your nanopack, another option is to select Force Respawn from the upper right corner menu on the login screen. If successful it will kill your character, clear your inventory of all items other than blueprints, schematics, scan results and compacted ship), and send you back to your nearest resurrection node. Link to comment Share on other sites More sharing options...
Hazaatan Posted February 2, 2021 Author Share Posted February 2, 2021 1 minute ago, fiddlybits said: I haven't had this issue at market 17 specifically, but have had issues logging in at a certain location. Here are some options: 1. Clear your cache using the upper right menu in the login screen and try logging in again. 2. You can ask NQ for a teleport to a different area in discord or the in game support channel. I think they require tickets with logs now for teleports, so make a ticket first and reference it in your request in chat. 3. If you do not have anything in your nanopack, another option is to select Force Respawn from the upper right corner menu on the login screen. If successful it will kill your character, clear your inventory of all items other than blueprints, schematics, scan results and compacted ship), and send you back to your nearest resurrection node. My problem is that my ship is the closest respawn point and the ship is parked at Alioth 17. I will make a ticket. Is this 'normal'? I still have to pick up things at the market... Thank you for the help. Link to comment Share on other sites More sharing options...
fiddlybits Posted February 2, 2021 Share Posted February 2, 2021 I've only had it happen twice personally. I don't know how common it is. Link to comment Share on other sites More sharing options...
Hazaatan Posted February 3, 2021 Author Share Posted February 3, 2021 *FIXED* NQ got back to me and gave me these instructions: Thanks for reaching out.I'm sorry to hear about what you have experienced. To reduce lags and disconnects, please try these in-game graphics settings:1. Set Dynamic Shadow settings to Low (not None)2. Set Environment Shadow settings to Low (not None)3. Turn off Volumetric Clouds4 Reduce the number of thread counts to 2After this, delete your shader cache as well. To delete the shader cache, navigate to %localappdata%\NQ\DualUniverse and delete the file shader_d3d11.cache, then try to relog. Worked for me fiddlybits 1 Link to comment Share on other sites More sharing options...
blazemonger Posted February 3, 2021 Share Posted February 3, 2021 So I take it NQ considers that bug resolved then as there is a workaround /s michaelk 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now