I don't use temporal spec either, but I do have the tree maxed. If that makes a difference I have no idea. All I know is that the warp in thing is happening with annoying regularity.
Speaking of bugs, the forums ate my message again when I tried to edit it.
Anyway, it was to say that it's not Temporal and its Continuity ability, since the bug happened on a Primary Temporal character but not on another, and my Primary Pilot one got subjected to the bug as well.
Speaking of bugs, the forums ate my message again when I tried to edit it.
Anyway, it was to say that it's not Temporal and its Continuity ability, since the bug happened on a Primary Temporal character but not on another, and my Primary Pilot one got subjected to the bug as well.
Just because I mentioned that maybe using the temporal spec tree or not might be why some get it and others don't, does not mean it's still not bugged. It just seems like an obvious place to look for the bug given the description of continuity, when it came out and when people started experiencing this issue.
Just had the worst bout of this bug I have ever seen while doing a Japori run. I warped out/in four straight times back to back to back to back.. it was insane.
Seriously Cryptic, move this problem to the front of the line and fix the TRIBBLE thing!
Just had the worst bout of this bug I have ever seen while doing a Japori run. I warped out/in four straight times back to back to back to back.. it was insane.
Seriously Cryptic, move this problem to the front of the line and fix the **** thing!
This keeps happening to me as well... where it does it 3-5 times in a row and it stops all my power activations. It also causes some of my powers to fail to activate, but puts the skill into cooldown.
just had this during a fel'kri story mission (the rescue Kahless mission) after using heavy torp suddenly my ship disappears and warps in but it doesn't break the tractor locks from 3 breen ships or the incoming torps that they launched before the bug triggered
Draal - FED, Saurian, LV60 - TAC
Mirak - FED 23c, Vulkan, LV60 - TAC
Ascaran Bloodclaw - KDF, Gorn, Lv18 - TAC
Melchiah - KDF, Gorn, LV60 - TAC
Ne'roon - KDF,Lethian, L60, TAC
Turel - ROM-KDF, Reman, 30, TAC
Elric - ROM-Fed, Romulan, L60, TAC
Richtor Belmont - FED 23c, Human,LV20, SCI
G'Kar - KDF, Gorn, L10
USS Sharlin NCC79713 B (part of sheridans access code) - T6, Hestia Class Advanced Escort
USS Babylon IV - T6 Krenim Science Vessel
USS Brakiri - T6 Elachi Escort
"I am Grey. I stand between the candle and the star."
"We are Grey. We stand between the darkness and the light."
While true, a moment to say "we're aware of it" would go a LONG way.
I thought I read somewhere on here that they are aware of it but don't have a clue what could be causing it. Can't remember where I would have seen that though, there's been a lot of these threads lol
I wonder if it's related to the Kolasi transformation problem. It's fine when just flying around but when you try to do anything when in siege mode the ship will periodically transform back and forth. It used to be quite a rare thing but now it seems to happen a few times a minute.
Only another 8 months to go and it'll be fixed. Usually takes them around 18 months to fix the tricky ones. .
Edit another 6 months not 8 to fix this.
Post edited by ussvaliant#6064 on
Hello rubber banding my old friend, time to bounce around the battlezone again, where are all my bug reports going?, out of love with this game I am falling, As Cryptic fail to acknowledge a problem exists, Shakes an angry fist, And from Support all I'm hearing are the sounds of silence.
I've been having it happen fairly often during the Breach now.
I think this started happening when they introduced the ability to switch starships without going to a spacedock, which was before AOY, and i think before the skill revamp.
But it seems to be triggering more often now for more people.
Harsh words about the devs not knowing what they are doing isn't far, Im sure they know what they are doing, they just got way to much to do, bringing sto out on console and letting people go. More work and less people I say is the problem but then I like you really dont know. Im sure they read this but if I was them and reading , I might place it on the bottom of my list of things to fix.
You want to use harsh words use it on the Suits, they make the call, Dev's do what they are told.
Harsh words about the devs not knowing what they are doing isn't far, Im sure they know what they are doing, they just got way to much to do, bringing sto out on console and letting people go. More work and less people I say is the problem but then I like you really dont know. Im sure they read this but if I was them and reading , I might place it on the bottom of my list of things to fix.
Sooo, they ignore it for, what, like a year now? And then, when ppl finally get fed up, and begin to say that "Uh, I dunno." is not really a valid excuse for a Dev, the Devs would then use said upsetment as a reason to push the issue to the bottom of their to-do list?! Nice circular logic!
While true, a moment to say "we're aware of it" would go a LONG way.
I thought I read somewhere on here that they are aware of it but don't have a clue what could be causing it.
And I hope you also read me stating somewhere that them saying 'that they are aware of it but don't have a clue,' is not really an acceptable reply for a Dev. :P Not when it's been over a year now, and really affects your gameplay.
While true, a moment to say "we're aware of it" would go a LONG way.
I thought I read somewhere on here that they are aware of it but don't have a clue what could be causing it.
And I hope you also read me stating somewhere that them saying 'that they are aware of it but don't have a clue,' is not really an acceptable reply for a Dev. :P Not when it's been over a year now, and really affects your gameplay.
"Don't have a clue" is dev speak for, "We can't repeat it on a consistent basic so we have no way to know where exactly to look for the problem". That's one of the reasons I've been trying to come up with things it could possibly be in the hopes they have a look at them. But yeah, it's a major pain in the TRIBBLE. I hate that Ragnarok mission and did it again the other night. It's bad enough as is but add in you suddenly going in a different direction or your perspective suddenly changing and it's enough to make one want to rage quit.
surely the devs must have a test server for debugging? however it would be better if. they get into the game and try to figure out the trigger under in-game conditions.
I've been getting the warp bug since at least 2-3 months into the console launch on ps4
Draal - FED, Saurian, LV60 - TAC
Mirak - FED 23c, Vulkan, LV60 - TAC
Ascaran Bloodclaw - KDF, Gorn, Lv18 - TAC
Melchiah - KDF, Gorn, LV60 - TAC
Ne'roon - KDF,Lethian, L60, TAC
Turel - ROM-KDF, Reman, 30, TAC
Elric - ROM-Fed, Romulan, L60, TAC
Richtor Belmont - FED 23c, Human,LV20, SCI
G'Kar - KDF, Gorn, L10
USS Sharlin NCC79713 B (part of sheridans access code) - T6, Hestia Class Advanced Escort
USS Babylon IV - T6 Krenim Science Vessel
USS Brakiri - T6 Elachi Escort
"I am Grey. I stand between the candle and the star."
"We are Grey. We stand between the darkness and the light."
I think its related to the speed we are pressing keys. When I do an alpha strike macro I tend to mash the key really fast and get rewarded with several fly'ins. If I press the key slowly it does not seem to happen, as much.
Comments
Anyway, it was to say that it's not Temporal and its Continuity ability, since the bug happened on a Primary Temporal character but not on another, and my Primary Pilot one got subjected to the bug as well.
Just because I mentioned that maybe using the temporal spec tree or not might be why some get it and others don't, does not mean it's still not bugged. It just seems like an obvious place to look for the bug given the description of continuity, when it came out and when people started experiencing this issue.
Seriously Cryptic, move this problem to the front of the line and fix the TRIBBLE thing!
This keeps happening to me as well... where it does it 3-5 times in a row and it stops all my power activations. It also causes some of my powers to fail to activate, but puts the skill into cooldown.
USS Sharlin NCC79713 B (part of sheridans access code) - T6, Hestia Class Advanced Escort
USS Babylon IV - T6 Krenim Science Vessel
USS Brakiri - T6 Elachi Escort
"We are Grey. We stand between the darkness and the light."
– Grey Council greeting
Edit another 6 months not 8 to fix this.
Hello rubber banding my old friend, time to bounce around the battlezone again, where are all my bug reports going?, out of love with this game I am falling, As Cryptic fail to acknowledge a problem exists, Shakes an angry fist, And from Support all I'm hearing are the sounds of silence.
On a different captain I did die when I got dropped off inside a closing relay in the shell game section.
I think this started happening when they introduced the ability to switch starships without going to a spacedock, which was before AOY, and i think before the skill revamp.
But it seems to be triggering more often now for more people.
You want to use harsh words use it on the Suits, they make the call, Dev's do what they are told.
Sooo, they ignore it for, what, like a year now? And then, when ppl finally get fed up, and begin to say that "Uh, I dunno." is not really a valid excuse for a Dev, the Devs would then use said upsetment as a reason to push the issue to the bottom of their to-do list?! Nice circular logic!
Same.
And I hope you also read me stating somewhere that them saying 'that they are aware of it but don't have a clue,' is not really an acceptable reply for a Dev. :P Not when it's been over a year now, and really affects your gameplay.
"Don't have a clue" is dev speak for, "We can't repeat it on a consistent basic so we have no way to know where exactly to look for the problem". That's one of the reasons I've been trying to come up with things it could possibly be in the hopes they have a look at them. But yeah, it's a major pain in the TRIBBLE. I hate that Ragnarok mission and did it again the other night. It's bad enough as is but add in you suddenly going in a different direction or your perspective suddenly changing and it's enough to make one want to rage quit.
I've been getting the warp bug since at least 2-3 months into the console launch on ps4
USS Sharlin NCC79713 B (part of sheridans access code) - T6, Hestia Class Advanced Escort
USS Babylon IV - T6 Krenim Science Vessel
USS Brakiri - T6 Elachi Escort
"We are Grey. We stand between the darkness and the light."
– Grey Council greeting