Hey just wanting to get some feedback on the error code viper I've been repeatedly getting the past few days. Mostly it has occurred when trying to return to orbit. There's also been a great deal of lag in audio as well as general gameplay from time to time since TTK launch. I have the digital copy of Destiny, a wired AT&T DSL connection with all the necessary ports forwarded, and a static IP for ps3. I've also tried putting the ps3 on IP passthrough which doesn't appear to make any difference as far as overall gameplay is concerned. I've been considering pinging to optimize the ps3/router MTU size because of lag and/or packet loss but am not sure that's worth the time. Any help/suggestions on these issues would be greatly appreciated.
-
Edited by political_poison: 2/5/2016 7:02:27 PMJust thought I would give this thread an update in case anyone else experiences similar issues and stumbles across it. The viper codes have stopped occurring when I go back to orbit. The only thing I have done differently is force quit everytime I am done playing. On a side note, I decided to do the ping test after all and changed the MTU size on my router from 1500 to 1458. This seems to have tremendously helped with the lag in audio and gameplay I was experiencing.
-
Does it occur when you are trying to go to orbit with a group, or will it occur when you are returning solo? Will it do both? (I'm from funds group)
-
You basically lost connection. Most times Viper is received when switching back and forth from Destiny and other apps/games without closing out Destiny. Be sure to force quit Destiny when you're done playing. If you are getting the Viper error in-game, try clearing your console's cache: https://www.bungie.net/7_Clearing-cache-on-a-console/en/Help/Article/12539