nope still broken on both my oddy's and galaxy's, saucer still disapears.
it goes quicker in zone sections however in battle it stays somewhat longer, on the oddy's however the acarius stays and doesnt disapear so it seems that one is fixed.
Did the Patch Notes for February 8th state that Pets were being fixed? If not, the revised Subject Title makes no sense
'But to be logical is not to be right', and 'nothing' on God's earth could ever 'make it' right!'
Judge Dan Haywood
'As l speak now, the words are forming in my head.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
this to me isn't really acceptable , for these are PAID for built in features of these ships and they are balanced to use these functions ,hell after months of this and not having the warp articulation for the intrepid t6 with little or no fix for the issues , this is the only game i play that has these recurring issues that NEVER get addressed for MONTHS . if i counted the amount of months certain effects work over how long they dont work these things may work for a month or 2 out of the year and remain broken for the rest of the ten months this is why at this point STO is a low game money priority . listen i expect small bugs here and there , but when it comes to players loose a function of something that comes from the store that what bought in good faith to have it broke and been broke for 6 plus months is poor Q & A and management of bug fixes .
Honestly guys? You're better off creating a thread at the ST:O reddit and link to this thread. It seems the Devs prefer to lurk there than here.
lol these are the "OFFICAL" forums , this is where these kind of reports belong not the hive of scum and villainy reddit is . if the DEVS dont come here then why have this forum at all??? hmm its bad management to say the least . just saying
I've been flying my Dreadnought in The Breach and as soon as I separate the saucer to fight Voth ships, it simply vanishes right away. It isn't a one-off, it happens every day. On the other hand, my aero shuttle hangs around when I am flying my Intrepid... it fires a few shots, unlike the saucer. After a few minutes, though, it seems to vanish into thin air.
I play with my kids daily, so I can observe their stuff, too. One uses a Dread, and one always flies an Intrepid (Pathfinder). When in Gon'cra, my daughter's aero shuttle frequently helps out pushing asteroids during Tug of War, but my son's saucer only lasts for seconds. I am pretty sure her shuttle vanishes before it should, so what triggers that is unknown - it goes away and she recalls it so she can launch it again later.
All of it is highly inconsistent (and frustrating). I keep getting all of our hopes up every time the patch notes say the problem is fixed. The patch notes are always wrong.
Another Patch day and no mention of even an attempt to fix this AGAIN. But we have more new ships coming....
Sorry Cryptic but no more money is going to c-store ships or promotional ships until this is solved, I know I am not alone in this feeling. If you guys have the time to create new ships then you should be able to have the time to fix this bug after all these MONTHS.
Ships like the pathfinder are sold on the basis of its console ability, I think its time some refunds were requested, we have been patient enough here.
I am really at a loss as to why this bug continues to persist and the lack of feedback coming from the devs just rubs salt in the wound. I have only bought two ships ever and I agonized over the purchase because I abhor purchasing something I will not like - I researched the ships as much as I could, got opinions in-game, etc. My Federation character has the T6 Adv Tactical Escort, which I got specifically to fly around in MVAM. It's been broken since about a month after I purchased it. I just cannot fathom letting something this big go for so long.
I know if I were to ignore a problem like this and/or not provide feedback to the MANY customers this affects I'd be fired and replaced.
This bug has really soured me on STO, and I hate that because I was really enjoying my shiny new ship and then boom.... I essentially wasted money on something I've barely ever gotten to use. Majorly aggravated :/
I, too, am STILL having this same issue with both my Fed Fleet Dread and my KDF Bortas'chu....it's unbelievably annoying, mainly for the simple fact that they know about this and have not fixed it... I guess the 'lesson learned' here is to severely limit Zen purchases (at least until the 'purchase' has been nerfed-free for year or so). I really don't want to spend cash on another 'bait-and-switch' purchase...
The Game itself is nothing. The playing of it...? Everything !!
this to me isn't really acceptable , for these are PAID for built in features of these ships and they are balanced to use these functions ,hell after months of this and not having the warp articulation for the intrepid t6 with little or no fix for the issues , this is the only game i play that has these recurring issues that NEVER get addressed for MONTHS . if i counted the amount of months certain effects work over how long they dont work these things may work for a month or 2 out of the year and remain broken for the rest of the ten months this is why at this point STO is a low game money priority . listen i expect small bugs here and there , but when it comes to players loose a function of something that comes from the store that what bought in good faith to have it broke and been broke for 6 plus months is poor Q & A and management of bug fixes .
The nacelles on the Intrepid are broken again? Talk about ghosts of bugs past, that was broken for a very long time seems like years ago.
In any case, STILL having this problem on all ships with separation pets that I have tried (I own most of them), haven't personally checked the Intrepid or Prometheus, but Galaxy and Oddy are definitely busted.
Witnessed a Sheshar separate in the Breach adv few days ago, and as predicted its assault craft flew away. Another day, saw an Odyssey with chevron separated, saucer nowhere in sight.
Please, can you look into fixing this issue?
I have a T5 Prometheus bought specifically for the separation console for the T6 Hestia. I cannot use it.
I have a T5 Ops Odyssey bought specifically cause I like the chevron separation, and purchased the megabundle that includes the T6 Odysseys to use the module on. I cannot use the ship as intended and its T6 starship trait doesn't work properly without it, or at all if using it in solo content.
I have a T5 Galaxy bought specifically for the saucer separation console that I bought specifically for both the skin and module to separate my T6 Gal-X. I cannot have access to wide beam phaser lance or boosted turn rate or saucer support because it does not work.
Please, fix this issue. I am being patient, everyone is being patient. It has been months now, and the issue isn't even being acknowledged.
Hi all! I'm very sorry that this issue has been so frustrating for so many of you. We've had a number of issues with non-hangar pets that have proven rather persistent.
But as it turns out, I'm not able to reproduce the behavior you all are describing in-house. So I wanted to point out one peculiarity with these powers:
After separating your saucer or summoning your non-hangar pet, the second activation of the power causes it to fly off and disappear (before reappearing and re-docking with your main ship). I know from experience that it's very easy to press or click a hotkey twice in the heat of battle, so I'd humbly ask that anyone with one of these powers check against this possibility before continuing.
If you've checked since the update on the 8th, and you're still seeing this issue, please post what type of ship you are using, and the exact context in which you are seeing this (map, in/out of combat, number of nearby players, etc).
Again, I'm sorry this has been so frustrating. I completely understand.
No - if i would click second time, then the pet flies away, then it returns and docks - thats not what happens - the pet just flies away... and stays away. After I click second time, the pets return and dock, but it does not work as separate entity... which is really frustrating, especially as all those Pets are on Zen-Store ships! (and Sheshar is from RD Promo - i think - so it's even more costly)
Edit:
And add Bortasqu variants to the problem too...
Hi all! I'm very sorry that this issue has been so frustrating for so many of you. We've had a number of issues with non-hangar pets that have proven rather persistent.
But as it turns out, I'm not able to reproduce the behavior you all are describing in-house. So I wanted to point out one peculiarity with these powers:
After separating your saucer or summoning your non-hangar pet, the second activation of the power causes it to fly off and disappear (before reappearing and re-docking with your main ship). I know from experience that it's very easy to press or click a hotkey twice in the heat of battle, so I'd humbly ask that anyone with one of these powers check against this possibility before continuing.
If you've checked since the update on the 8th, and you're still seeing this issue, please post what type of ship you are using, and the exact context in which you are seeing this (map, in/out of combat, number of nearby players, etc).
Again, I'm sorry this has been so frustrating. I completely understand.
Thanks!
Really? You think that all the players, that have this issue, are unable to press a button just once? o.O
If you can not reproduce this in-house, then maybe you should log in on the Holodeck server and check it there? From what I've heard, this issue doesn't happen on Tribble, so maybe it doesn't happen on your "in-house" server as well?
I recorded two short videos for you (as if nobody did it before...):
The first one is in the Sol-System, outside combat, the second one on The Cure Advanced-Map (don't know, I think it's "Sibiran-System" or something like that) INSIDE combat. The issue appeared both times. Checked it with my Galaxy-Dreadnought, but my Hestia suffers from this bug as well.
Everything was fine until the Winter event, which was three(!) months ago.
P.S. But I appreciate, that FINALLY one of the developers gives an answer. You should keep that behavior and stay in touch with the community more often.
Hi all! I'm very sorry that this issue has been so frustrating for so many of you. We've had a number of issues with non-hangar pets that have proven rather persistent.
But as it turns out, I'm not able to reproduce the behavior you all are describing in-house. So I wanted to point out one peculiarity with these powers:
After separating your saucer or summoning your non-hangar pet, the second activation of the power causes it to fly off and disappear (before reappearing and re-docking with your main ship). I know from experience that it's very easy to press or click a hotkey twice in the heat of battle, so I'd humbly ask that anyone with one of these powers check against this possibility before continuing.
If you've checked since the update on the 8th, and you're still seeing this issue, please post what type of ship you are using, and the exact context in which you are seeing this (map, in/out of combat, number of nearby players, etc).
Again, I'm sorry this has been so frustrating. I completely understand.
Thanks!
Thank you so much for your attention to this issue, I would also recommend parsing the damage of the non hanger pet, in most cases you will see it does zero dps and in some cases maybe up to 20dps. This is what I found parsing the Elachi Sheshar Assault craft in many different instances including both the red alerts and ISA on several occasions. Perhaps it should be tested on Holodeck if you are not getting the same results elsewhere. It always disappears in social zones (so does the D'kyr pet) and sometimes it follows me around in combat but without attacking anything.
If you've checked since the update on the 8th, and you're still seeing this issue, please post what type of ship you are using, and the exact context in which you are seeing this (map, in/out of combat, number of nearby players, etc).
I'm not especially put out by this (skip to the penultimate paragraph for what my deployable pet peeve is) but if it's for the greater good I'll try to reproduce it:
Qo'noS orbit (not combat):
I counted 6 other players on the instance that I could see
Klingon Bortasqu' pet flies away as soon as soon as the animation ends and the pet actually spawns.
Elachi Sheshar shows the same behaviour with both the Sheshar Assault Craft and the pets summoned with the Monbosh console.
Elachi Monbosh did not show this problem with the Sheshar console, but did exhibit the same issue with the Monbosh console, although they waited around a few seconds longer than the Bort's HoH'SuS pet.
Same behaviour with the S'ateth as with the Monbosh.
I don't have the S'golth since I got the S'ateth and I don't own the T6 version of the Monbosh (Ornash) to test with.
(It's worth pointing out while I'm on the subject that the Sheshar console only summons the Sheshar Assault Craft when used on the Sheshar itself. When used on other ships a S'golth appears instead; the item description needs correcting. It also doesn't play the warp-in animation when used on a ship other than the Sheshar.)
Krenn Temporal Destroyer pets spawn and despawn correctly. I included this one because I have an inkling the pets work in a similar way to the deployable ones. Sorry, but I didn't bother to test the Korath or the Paradox with this console for reasons I'll explain at the end.
Briar Patch (combat):
Just me and one other player on the map this time. Bortasqu' tested.
Bortasqu' pet remained and attacked the target as well as continuing to do so after I was inadvertently blown up. It seems some Feds have itchy trigger fingers after all.
Infected Space (combat):
A full team of five altogether. Elachi S'ateth tested.
Monbosh pets used on the S'ateth attacked enemies correctly but despawned shortly after. The Sheshar console pet worked somewhat better but also appeared to despawn at one point. It may have just been destroyed but I didn't see the disabled ship in the aftermath.
Crystalline Entity (combat):
A full team of five plus another five on the map. Monbosh tested.
Monbosh pets used on the Monbosh despawned shortly after appearing. I had no target selected so I assume this was why they did nothing before they left. Again, the Sheshar console pet worked somewhat better but definitely despawned (or rather vanished, there's no despawn animation either I think) this time, although it stuck around a lot longer than the Monbosh pets did before leaving.
I didn't test the Mannheim Device pets in combat or on other ships because I've seen them work in the past. I don't think there have been any issues with this console since you got rid of the past-present and present-future damage thing. That was a nice idea, by the way, but it didn't work out at all in practice.
I hope this helps, I realise it's far from comprehensive! Feel free to PM me if you'd like any specific tests done or if you want a quick round of PvP to see it in the flesh, so to speak. If you'll be trawling logs or some such I started this about an hour ago (2140 GMT) and just finished a few minutes ago.
If you're not worn out after that wall of text please consider what I hope is a simple change that would be a big QoL improvement as far as this sort of pet goes: have them despawn automatically when they're disabled or destroyed. There's nothing more irritating for me than forgetting that the pets are out of action, trying to respawn them but then finding you've only just started the cooldown because you didn't remember to despawn them manually ten minutes ago. It would be much, much less of a headache if they automatically despawned/returned when they hit zero health, much as regular carrier pets do.
For my next trick I'll finish off my one thousand test activations of the Dominion Command Interface; it's disabling Aux far more than random chance should allow and either failing entirely (or just not showing the graphic) in roughly 25% of the two hundred-ish tests I've done so far.
Earth orbit, out of combat. Tested both near and away from other players.
Sheshar, assault craft: disappears, does not dock
Sheshar, support craft: disappear, no warp-out animation
T6 Ops Star Cruiser, Aquarius: disappears, does not dock
T6 Ops Star Cruiser, chevron: disappears, does not dock
D'kyr, support craft: disappears, but DOES dock
I've seen similar behavior when attempting to deploy the Aquarius in combat in a Borg Red alert, but not quite consistently — my Aquarius did engage my target in a single instance, out of some 3-4 attempts in the past couple of weeks.
Comments
it goes quicker in zone sections however in battle it stays somewhat longer, on the oddy's however the acarius stays and doesnt disapear so it seems that one is fixed.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
I play with my kids daily, so I can observe their stuff, too. One uses a Dread, and one always flies an Intrepid (Pathfinder). When in Gon'cra, my daughter's aero shuttle frequently helps out pushing asteroids during Tug of War, but my son's saucer only lasts for seconds. I am pretty sure her shuttle vanishes before it should, so what triggers that is unknown - it goes away and she recalls it so she can launch it again later.
All of it is highly inconsistent (and frustrating). I keep getting all of our hopes up every time the patch notes say the problem is fixed. The patch notes are always wrong.
Sorry Cryptic but no more money is going to c-store ships or promotional ships until this is solved, I know I am not alone in this feeling. If you guys have the time to create new ships then you should be able to have the time to fix this bug after all these MONTHS.
Ships like the pathfinder are sold on the basis of its console ability, I think its time some refunds were requested, we have been patient enough here.
I know if I were to ignore a problem like this and/or not provide feedback to the MANY customers this affects I'd be fired and replaced.
This bug has really soured me on STO, and I hate that because I was really enjoying my shiny new ship and then boom.... I essentially wasted money on something I've barely ever gotten to use. Majorly aggravated :/
The nacelles on the Intrepid are broken again? Talk about ghosts of bugs past, that was broken for a very long time seems like years ago.
In any case, STILL having this problem on all ships with separation pets that I have tried (I own most of them), haven't personally checked the Intrepid or Prometheus, but Galaxy and Oddy are definitely busted.
Please, can you look into fixing this issue?
I have a T5 Prometheus bought specifically for the separation console for the T6 Hestia. I cannot use it.
I have a T5 Ops Odyssey bought specifically cause I like the chevron separation, and purchased the megabundle that includes the T6 Odysseys to use the module on. I cannot use the ship as intended and its T6 starship trait doesn't work properly without it, or at all if using it in solo content.
I have a T5 Galaxy bought specifically for the saucer separation console that I bought specifically for both the skin and module to separate my T6 Gal-X. I cannot have access to wide beam phaser lance or boosted turn rate or saucer support because it does not work.
Please, fix this issue. I am being patient, everyone is being patient. It has been months now, and the issue isn't even being acknowledged.
But as it turns out, I'm not able to reproduce the behavior you all are describing in-house. So I wanted to point out one peculiarity with these powers:
After separating your saucer or summoning your non-hangar pet, the second activation of the power causes it to fly off and disappear (before reappearing and re-docking with your main ship). I know from experience that it's very easy to press or click a hotkey twice in the heat of battle, so I'd humbly ask that anyone with one of these powers check against this possibility before continuing.
If you've checked since the update on the 8th, and you're still seeing this issue, please post what type of ship you are using, and the exact context in which you are seeing this (map, in/out of combat, number of nearby players, etc).
Again, I'm sorry this has been so frustrating. I completely understand.
Thanks!
Edit:
And add Bortasqu variants to the problem too...
Really? You think that all the players, that have this issue, are unable to press a button just once? o.O
If you can not reproduce this in-house, then maybe you should log in on the Holodeck server and check it there? From what I've heard, this issue doesn't happen on Tribble, so maybe it doesn't happen on your "in-house" server as well?
I recorded two short videos for you (as if nobody did it before...):
The first one is in the Sol-System, outside combat, the second one on The Cure Advanced-Map (don't know, I think it's "Sibiran-System" or something like that) INSIDE combat. The issue appeared both times. Checked it with my Galaxy-Dreadnought, but my Hestia suffers from this bug as well.
Everything was fine until the Winter event, which was three(!) months ago.
Thank you so much for your attention to this issue, I would also recommend parsing the damage of the non hanger pet, in most cases you will see it does zero dps and in some cases maybe up to 20dps. This is what I found parsing the Elachi Sheshar Assault craft in many different instances including both the red alerts and ISA on several occasions. Perhaps it should be tested on Holodeck if you are not getting the same results elsewhere. It always disappears in social zones (so does the D'kyr pet) and sometimes it follows me around in combat but without attacking anything.
I'm not especially put out by this (skip to the penultimate paragraph for what my deployable pet peeve is) but if it's for the greater good I'll try to reproduce it:
Qo'noS orbit (not combat):
I counted 6 other players on the instance that I could see
I don't have the S'golth since I got the S'ateth and I don't own the T6 version of the Monbosh (Ornash) to test with.
Briar Patch (combat):
Just me and one other player on the map this time. Bortasqu' tested.
Infected Space (combat):
A full team of five altogether. Elachi S'ateth tested.
Crystalline Entity (combat):
A full team of five plus another five on the map. Monbosh tested.
I didn't test the Mannheim Device pets in combat or on other ships because I've seen them work in the past. I don't think there have been any issues with this console since you got rid of the past-present and present-future damage thing. That was a nice idea, by the way, but it didn't work out at all in practice.
I hope this helps, I realise it's far from comprehensive! Feel free to PM me if you'd like any specific tests done or if you want a quick round of PvP to see it in the flesh, so to speak. If you'll be trawling logs or some such I started this about an hour ago (2140 GMT) and just finished a few minutes ago.
If you're not worn out after that wall of text please consider what I hope is a simple change that would be a big QoL improvement as far as this sort of pet goes: have them despawn automatically when they're disabled or destroyed. There's nothing more irritating for me than forgetting that the pets are out of action, trying to respawn them but then finding you've only just started the cooldown because you didn't remember to despawn them manually ten minutes ago. It would be much, much less of a headache if they automatically despawned/returned when they hit zero health, much as regular carrier pets do.
For my next trick I'll finish off my one thousand test activations of the Dominion Command Interface; it's disabling Aux far more than random chance should allow and either failing entirely (or just not showing the graphic) in roughly 25% of the two hundred-ish tests I've done so far.
Sheshar, assault craft: disappears, does not dock
Sheshar, support craft: disappear, no warp-out animation
T6 Ops Star Cruiser, Aquarius: disappears, does not dock
T6 Ops Star Cruiser, chevron: disappears, does not dock
D'kyr, support craft: disappears, but DOES dock
I've seen similar behavior when attempting to deploy the Aquarius in combat in a Borg Red alert, but not quite consistently — my Aquarius did engage my target in a single instance, out of some 3-4 attempts in the past couple of weeks.