test content
Logo
What is the Arc Client?
Install Arc
Options
Boff slots AGAIN + loadouts *Team is investigating*
anothervisitor
Member Posts: 414 Arc User
Ok, I've had this issue before but I found a workaround then by not switching to another shuttle and keeping one build on it. Now even that no longer seems to work.
When I setup my ship equipment items, boffs, doffs and tray it saves fine on the first build I save. Then when I make a different setup on the same ship or any other ship and save that, everything goes to waste on the previous builds.
When I try to load one of the previous builds then all it loads are the boff stations and tray; the ship equipped items don't change at all and neither do the doffs on space duty. When trying to load a build on a diff ship it also doesn't drag in items that are currently on a different ship; nothing moves at all.
This renders loadouts totally UNUSABLE and I'm sick of it.
When I setup my ship equipment items, boffs, doffs and tray it saves fine on the first build I save. Then when I make a different setup on the same ship or any other ship and save that, everything goes to waste on the previous builds.
When I try to load one of the previous builds then all it loads are the boff stations and tray; the ship equipped items don't change at all and neither do the doffs on space duty. When trying to load a build on a diff ship it also doesn't drag in items that are currently on a different ship; nothing moves at all.
This renders loadouts totally UNUSABLE and I'm sick of it.
Tyr shall give me strength!
For the glory of Tempus!
I am the hands of Shar!
Flames of Kossuth, protect me!
Oghma, grant me knowledge!
Lolth commands, and I obey!
For the glory of Tempus!
I am the hands of Shar!
Flames of Kossuth, protect me!
Oghma, grant me knowledge!
Lolth commands, and I obey!
Post edited by anothervisitor on
0
Comments
Has worked just fine since then though, with an entirely new Loadout created for a different BOff and DOff layout with everything switching as it is supposed to.
When did you create the Loadouts giving you trouble? I'm wondering if the Loadouts are having trouble if a patch goes through, as that Loadout hadn't been touched in several days.
I tried to reinstall the game but that didn't help.
For the glory of Tempus!
I am the hands of Shar!
Flames of Kossuth, protect me!
Oghma, grant me knowledge!
Lolth commands, and I obey!
The tray icons do like to mess themselves up but as some one with a lot of bridge officers, ships and builds I gave up on using my tray for anything but captain and ship abilities a long time ago.
My big problem is that saved load outs keep forgetting bridge officers. Some times I save a load out and it loads just fine, then latter when I try to load it, it forgets one/some/all of the boffs. there are also times it fails to load them from the first attempt.
Even more frustrating, when I fix it and save it again it still doesn't remember the boffs when I re-load.
This feature broken on tribble, and broken when it went live. Many features in the past have been broken on tribble, and broken when they go live and have never been fixed. I do not want this feature to join that list. especially as loadout packs are a paid for service... not that half the other things you can pay for in the C-store are unbroaken.
Conclusion, the loadout system is broken, in one way, or another. I was waiting to make another loadout for my breen warship and im stucked until they fix it lol.
Now that is weird. There are 4 things being saved: boffs, doffs, tray and equipment.
For me the equips and doffs don't load, for you it is the boffs and tray.
I'm glad my boffs & tray still loads as the tray is the most annoying thing.
For the glory of Tempus!
I am the hands of Shar!
Flames of Kossuth, protect me!
Oghma, grant me knowledge!
Lolth commands, and I obey!
I didn't see any mention of this being fixed in the patch notes though, so I don't think it's 'back' so much as it just hasn't gone away yet and doesn't happen every time.
On all my characters except my Klingon who discharged a ship shortly after loadouts were put in, the loadout system works as expected.
On my Klingon, shared items stay dim whether I switch ships in sector space or the shipyard. Attempting to save new loadouts has not helped. Doffs also do not switch. Super frustrating
While i expected that this unseating would still happen now and then. I was really hoping i could use the loadouts to quickly get everything back to normal. Sadly it's not even doing that.
Fix it Craptic !! I spent money on this feature.
Appear weak when you are strong, and strong when you are weak.
Starting after the patch on Thursday, I dismissed my current Galaxy X and reclaimed it from the C store. Shortly there after all my ship load outs, Boff stations and active doffs got scrambled. After getting a about half my ships set back up as they should and saving the load outs. I'm running back to back STF's and I'm constantly having to reequip boff stations. Thats providing the load outs actually pull the required equipment from other ships.
Why do cryptic refuse to actually beta test anything properly? instead of rushing things into game. 1 week of testing on tribble wont highlight anything or give them time to fix anything that is worng. Especially the flaws in the programming that we're currently seeing.
Its bad enough that when ever we acquire a new ship the trays for our older ones get messed up. But I was hoping that the new load out system would solve that issue. But I'm guessing thats not going to be the case.
Oh , come on.. they just added this feature 3 weeks ago.. i hope cryptic is not so lazy to not fix this, because it is one of the most important things that will push the game forward.
Cryptic should prioritize the fix of this bug, but all we know that fixing the game is not how cryptic works, unfortunately.
I am just waiting this to be fixed so i can make a new loadout to use it for stfs.. ive been waiting for 3 weeks now. Dunno if just forget about it and just keep using my current build, its really desperating , sigh.
THIS. Lol, sometimes i think that this is wat is happening, seriously...
[4:58] [System] [TicketCreated] Successfully submitted ticket ID #2,361,535.
loadout did not work fixing it + half my powers did not load yes i know console powers dont save im on about ramming speed all of them that u click when under 50% hull did not load in to the right place + sector powers were not in the right place.
Thank you CF,
TBH it's annoying yes but even with the minor annoyance of switching and re setting up trays or Boffs it's STILL way faster to switch between ships.
I constantly switch my ships and sometimes I have no problems but sometimes I do but better 2 mins than 10 mins it took ME to switch to other ships.
Hope the fix comes soon - thanks!
And sometimes doing so is the only way to get the Devs attention; and get the bug ultimately fixed.
PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
There need a kick up the bum sometimes + if people stop reporting it t here might think its fixed it self
I know it. And thats why crypticfrost passed by to remind the op that this is already a known issue
Yeah, it doesn't work that way. All repeated reports do is clog up the reporting queue and waste Q&A's (and cfrost's) time. Reported bugs that are verified are prioritized and queued. They don't "expire" or get ignored or forgotten after a period of time.
If something takes a long time to get fixed it's either because 1.) the fix is complicated and resource intensive, 2.) the fix is better off being incorporated during an upcoming overhaul where it's much less likely to break something, or 3.) the resources required to fix it currently outweigh its priority, which unfortunately means it's unlikely to ever get fixed unless there are changed to its priority or the required resources to fix it (for example, during an overhaul of a related system).
So please, DO NOT continue to file reports for known issues. It doesn't in any way "get the dev's attention" or "kick them in the butt". It's detrimental, not helpful.
Erm.... xd.
U sure we are talking about the same game? :P
I know it's hard to imagine that Cryptic devs aren't lazy good for nothing layabouts that enjoy having bugs in their game and thrill at seeing all the hate for them flood the forums and chat channels, but um, yeah, it's really not the way things are :eek:
I know, shocking, right?
Im sick of bugs been ignored e,g the freighter captain out side ESD that was ment to be fixed in old patch notes + wot it says in my sig. Maybe if more people complained about bugs there would get more people on fixing them. but know most people ignore it some get pissed off n close the game and a few might get that annoyed that there uninstall the game.
Now if people dont wont to see the same old stuff being reported/asked for (connie) there dont have to have a look at them bits of the forum.
Thanks frost for the response just hope that this is not going to end up like meny other issuse like one of the khg helmets not showing in the tailor for some players.
The captain is pretty much spot on. All bugs that have been verified by QA are recorded in a database. Those bugs are triaged by leads and producers who assign them a priority for fixing. This priority is based upon a variety of factors such as the number of players affected or likely to be affected, how disruptive to overall game play the issue happens to be, does it affect something the player has paid real money for, how long it expected a fix will take and is the person(s) who can fix this issue working on something more important.
That last one is where most of the bottlenecks for fixes occur. Not every employee here can work on or fix every issue. Many things require the attention of a limited number of specialists whose time is constantly in demand for the development of new aspects of the game. This is the primary reason something doesn't get fixed. There are just a few employees who can fix the problem but they are required to work on other projects that have a greater affect on the game, and so they just do not have the time to get the fix done.
As a player since the 2009 closed STO beta, that's NOT how Cryptic's bug fixing work has come across, EVER. Players (and I'm one of them who have done so) file bug ticket after bug ticket, yet nothing is done; yet when we post; often a Dev's reply (when they do reply to bug posts, which before recently wasn't often) was - "I was unaware of <issue>; thanks."
For example, they finally have a fix on Tribble for the issue of zoning into a Borg Red Alert instance only to find it empty after 3 YEARS (and it's been brought up and reported since the Red Alert content came in game with Season 4. (I can only imagine the low priority it got to take 3 years to fix, and it is a major game mechanic that is played by many in game on a daily basis.)
So, yeah, pardon us for continuing to bring annoying bugs like this one to the Dev teams attention.
PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
Amazing then that Devs had posted that "they were unaware" of issues when in the same posts, players commented they had filed multiple in game bug reports. I realize you're trying your best, Frost, but your bug reporting and prioritizing system often appears lacking ( in comparison to a lot of other MMOs still on the market.)
PWE ARC Drone says: "Your STO forum community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
This is an example of that bottlekeck I mentioned. This issue required a specialist to fix, but before a fix could be made, that same specialist had to determine why the bug was happening, and then determine how best to implement a fix without breaking everything else that used the system. In this case, the system was map transfers, so a bad fix could break every map transfer in the game, which would make the game unplayable. All of this had to be done in between other demands that were given higher priority.
So it was a case of a potentially dangerous (for the game) issue that just took a lot of time, with a limited pool of time available.