"Multitude of threads"? Really? Where? 'Cause it sure hasn't been here.
These forums are barely active anymore compared to other locations. Pretty sure if we had access to the official figures we would see a drop off in usage in recent years. That's not to say players are leaving the game they are just moving from the main forums to other locations.
If you look at the main discord channels, reddit threads, in game chat, Twitter feeds pretty much all the main live streamers chats there are multiple threads all over. With a large amount of them starting up when this thread started up.
When this recent batch of lag started up all my different Star Trek Online feeds every single one pretty much had threads on lag all appearing in the same 24hours. I can name at least 3 streamers who where live streaming when the lag hit and there live chat was all full of people talking about it. Everyone in the streams experienced the same lag simultaneously all from many different world wide locations. That points to a problem with the servers.
EDIT: In fact I just logged in game and what is the first thing I see within seconds in the main chat.
xxxx: if you mean lag and rubberbanding, then yes :
bbbbb: i:rubberbanding and on ground i sprint like crazy and then move normal its weir
xxxx :server sent me a msg, hey, im wonky, and acting like it
I'll give an update on my own experiences: the issues were almost entirely gone today and yesterday.
I don't know what has changed or been done, but I haven't been suffering from rubberbanding or lag anymore.
Edit:
Forgot to add: I've mostly been playing Guillotine, twice a day for the event. And some stuff in the Dyson battlezones and on Defera for endeavours. Not much else, but Guillotine and Dyson are the places where the lag tends to be the worst in my experience, when it is present.
So I guess it's a good sign that I didn't experience any, even though I was playing that content.
[4:46] [Combat {self}] Your Haymaker deals 23337 (9049) Physical Damage(Critical) to Spawnmother
Hey folks, I get that lag is a pain for folks. Believe me I get it and I don't like anymore than you folks do. However attacking the dev team and such doesn't help. There's a thousand different things that can cause lag, some with your own rigs, some with the servers, and alot dependent on what's going on between your rig and the servers that's outside of both of your control. The internet is still largely wired, and all it takes is something going wrong on the route your rig takes between the servers and your rig to cause problems.
Now there are some things that you can try for now to potentially reduce lag and see if it's the route you're taking. You can try one of the proxy connections on the launcher itself if you already haven't, or try disabling it if you're using one now. You can also make sure that you're not limiting yourself artificially in your setttings such as taking the framerate cap off. I would also advise disabling on-demand patching as that can cause issues too. If you have a VPN you can try using it to route your connection a different way to get to the servers. If you're using an ethernet connection (hard lined) you can check your cable and make sure there are no issues with it. I had one die on me before and it was a pain in the aft shuttlebay until I got a new one. If you're on wifi, make sure your router/modem is up off the ground higher so the signal doesn't have to travel through so many objects to get to your rig and isn't next to any microwaves.
With that in mind I would advise folks to run tracerts and see what you can see with that. That will tell you what's going on along the route. Run them at different times of the day, especially if you're noticing lag. This can tell you where the most likely issues are.
I get that folks are frustrated, but you can voice your frustrations while still being civil and constructive.
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 9 ms 11 ms int-0-6-0-12.dtr01wrcsma.netops.charter.com [96.34.82.241]
4 9 ms 10 ms 11 ms lag-19.hcr01wrcsmarn.netops.charter.com [96.34.142.196]
5 9 ms 9 ms 11 ms lag-10.hcr02wrcsmarn.netops.charter.com [96.34.142.195]
6 13 ms 13 ms 14 ms lag-34.rcr01nwtwctac.netops.charter.com [96.34.142.202]
7 * 18 ms 21 ms lag-800.bbr01nwtwct.netops.charter.com [96.34.2.156]
8 19 ms 26 ms 22 ms lag-805.bbr02ashbva.netops.charter.com [96.34.0.137]
9 23 ms 20 ms 21 ms lag-802.prr01ashbva.netops.charter.com [96.34.3.89]
10 20 ms * * ae-10.edge5.WashingtonDC12.Level3.net [4.68.62.61]
11 * * * Request timed out.
12 30 ms 32 ms 36 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
13 37 ms 36 ms 33 ms 198.49.243.237
14 30 ms 30 ms 31 ms patchserver.crypticstudios.com [208.95.184.200]
As far as I know "request timed out" is quite common. It just means that the particular stop doesn't respond to a traceroute request so it's not necessarily indicating an error
As far as I know "request timed out" is quite common. It just means that the particular stop doesn't respond to a traceroute request so it's not necessarily indicating an error
Usually true, but sometimes it is an actual delay that reaches the timeout threshold, though it is rather rare. Also, the ones that do respond are usually set to handle ping packets last so while it does give a vague idea of the traffic load it is not necessarily what your game packets are dealing with delay wise.
The fact that it is an edge might make it a little more likely that it is a real delay causing the timeout since, despite internet standards, not all networks play well together. Akami is notorious for problems crossing over to other CDNs for instance.
Additionally, the hops with "netops" in the name are probably Spectrum network and they have (or had a few years ago, no idea if they cleaned it up yet) a reputation for odd bouts of lag and whatnot because they got too big too fast, and their network tends to get saturated faster than it should as a result.
It looks like crossing between Spectrum and Lumen (the network that STO apparently uses now according to the IP address) is adding ten to twenty ms just behind the Lumen edge router, which is not that bad though so if it is getting seriously delayed at one of the hops it would probably have to be one of the ones that did not respond to the ping for whatever reason (though as others have pointed out most of the time it just means they are set to ignore pings).
Here are my results from this afternoon. I live several hours north of Seattle and am happy with my numbers today.
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 2 ms 3 ms 3 ms 192.168.0.1
2 3 ms 3 ms 2 ms 192.168.1.254
3 7 ms 4 ms 5 ms <my IP address removed>
4 * 8 ms 8 ms seattle.bb.telus.com [154.11.15.109]
5 10 ms 8 ms 9 ms ae57.edge6.Seattle1.Level3.net [4.14.240.209]
6 * * * Request timed out.
7 72 ms 72 ms 72 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
8 114 ms 79 ms 112 ms 198.49.243.237
9 79 ms 77 ms 77 ms patchserver.crypticstudios.com [208.95.184.200]
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 3 ms 2 ms 3 ms 192.168.0.1
2 4 ms 3 ms 3 ms 192.168.1.254
3 7 ms 4 ms 5 ms <my IP address removed>
4 * * * Request timed out.
5 44 ms 10 ms 9 ms ae57.edge6.Seattle1.Level3.net [4.14.240.209]
6 72 ms 71 ms 72 ms ae2.3.bear2.Boston1.level3.net [4.69.159.189]
7 72 ms 75 ms 72 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
8 84 ms 82 ms 82 ms 198.49.243.237
9 78 ms 77 ms 78 ms patchserver.crypticstudios.com [208.95.184.200]
I'm mainly noticing it in space, but sometimes on the ground. When it's going on, like before, the game is "playable". But abilities are near 100% failing and going into cooldown on use. Sometimes there's rubberbanding.
Not in my experience. In fact, AFS InvalidEntityName was commissioned just a couple of hours ago.
I just got my AFS InvalidEntityName as well (the Alliance Rex Pilot Escort). Upon commissioning it disappeared. I had to relog to make it appear in my ship selector. So then I did a traceroute. It was fine (the same as the last one posted here in this forum a day or two ago).
Then there was the ability misfires in space just prior to claiming my ship. I really wish my Cannon Scatter Volley would work more often but I'm getting used to it at this point
I'm on the virtually no lag side currently, but had big rubberbanding and frequent ability misfires during the initial onset of *the lag troubles*. Ie. I'm fine but perhaps only because of favorable factors mitigating symptoms. I have consistent non-catastrophic timeouts around Boston with tracert and pathping tests.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 10 ms 13 ms res.spectrum.com
3 32 ms 31 ms 31 ms lag-61.lnclnebt02h.netops.charter.com [76.85.221.29]
4 13 ms 9 ms 13 ms lag-20.lnclnebt02r.netops.charter.com [24.169.242.22]
5 47 ms 53 ms 51 ms lag-31.rcr01hstqtx02.netops.charter.com [24.169.242.2]
6 55 ms 54 ms 50 ms lag-416.hstqtx0209w-bcr00.netops.charter.com [66.109.9.88]
7 * * * Request timed out.
8 * * * Request timed out.
9 91 ms 82 ms 86 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
10 91 ms 84 ms 82 ms 198.49.243.237
11 81 ms 84 ms 79 ms patchserver.crypticstudios.com [208.95.184.200]
Auggie's been arguing that the issue's been caused by the new boff powers from the Final Frontier lock box having no minimum CD and sometimes recharging instantly (can spam very aggressively), with use exasperating within-match lag and contributing to higher server load generally (per this hypothesis). But I've been using those without any ill-effects observed in myself or others. That said 1) I don't use macros and are limited in how fast I can activate these powers, so it could be worth someone else whose connection is *fine* testing new boff power exploits with well-set macros to see if they can upend their connection and 2) this may be entirely supplemental to wider lag issues and simply catching weak/marginal connections out.
Bipedal mammal and senior Foundry author.
Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
Looking for something new to play? I've started building Foundry missions again in visual novel form!
I'm on the virtually no lag side currently, but had big rubberbanding and frequent ability misfires during the initial onset of *the lag troubles*. Ie. I'm fine but perhaps only because of favorable factors mitigating symptoms. I have consistent non-catastrophic timeouts around Boston with tracert and pathping tests.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 10 ms 13 ms res.spectrum.com
3 32 ms 31 ms 31 ms lag-61.lnclnebt02h.netops.charter.com [76.85.221.29]
4 13 ms 9 ms 13 ms lag-20.lnclnebt02r.netops.charter.com [24.169.242.22]
5 47 ms 53 ms 51 ms lag-31.rcr01hstqtx02.netops.charter.com [24.169.242.2]
6 55 ms 54 ms 50 ms lag-416.hstqtx0209w-bcr00.netops.charter.com [66.109.9.88]
7 * * * Request timed out.
8 * * * Request timed out.
9 91 ms 82 ms 86 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
10 91 ms 84 ms 82 ms 198.49.243.237
11 81 ms 84 ms 79 ms patchserver.crypticstudios.com [208.95.184.200]
Auggie's been arguing that the issue's been caused by the new boff powers from the Final Frontier lock box having no minimum CD and sometimes recharging instantly (can spam very aggressively), with use exasperating within-match lag and contributing to higher server load generally (per this hypothesis). But I've been using those without any ill-effects observed in myself or others. That said 1) I don't use macros and are limited in how fast I can activate these powers, so it could be worth someone else whose connection is *fine* testing new boff power exploits with well-set macros to see if they can upend their connection and 2) this may be entirely supplemental to wider lag issues and simply catching weak/marginal connections out.
My experience matches yours so I am not convinced the powers are causing a problem. The powers came out over a week before the lag and rubbering started and when the server was at its peak there was no noticeable problem. Furthermore I heavily used the new powers and since the server restart have had no lag problems or complaints from players in my team. I had problems before the server restart.
My Hur'q Dreadnought is themed around Asteroids running 6 or 7 Asteroids linked to Mouse button 5 which cycles though Asteroids on click allowing me a constant stream of them. I stacked up Bridge officer cooldown and use the Asteroids as my primary weapon. If the powers are the problem I would have expected a build like this to experience lag/rubber banding but so far neither myself or my team mates are having any problems.
I couldnt even log in today, kept booting me out of the login screen and lagging out. Eventually got in a few hours later. I think the hamster wheel needs some greasing
I couldnt even log in today, kept booting me out of the login screen and lagging out. Eventually got in a few hours later. I think the hamster wheel needs some greasing
Lag, stuttering, and rubber banding has been horrible since the update 1 week before the new event update. So that's two weeks now. I think they tried to do an unannounced hot fix last friday, but no change, I know they said some text corrections in the store were the reasons for the patch, but probably more for trying to fix the janky game play.
I know whats wrong with it, it aint got no gas in it.
Lag, stuttering, and rubber banding has been horrible since the update 1 week before the new event update. So that's two weeks now. I think they tried to do an unannounced hot fix last friday, but no change, I know they said some text corrections in the store were the reasons for the patch, but probably more for trying to fix the janky game play.
I know whats wrong with it, it aint got no gas in it.
It could have also been targeted at a background issue *besides* frequently reported lag symptoms, identified or introduced with the Thursday maintenance. There's no reason why all maintenance tasks must deal with the same singular problem (because it's affecting enough players in the community to influence the zeitgeist).
Also, if Cryptic was shooting for a general fix for the lag then that'll be something planned for regular maintenance, not thrown in at the last second on a Friday (presumes a eureka moment and mad rush to the patch server without much testing. Ie. an unlikely scenario.)
Bipedal mammal and senior Foundry author.
Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
Looking for something new to play? I've started building Foundry missions again in visual novel form!
Issues have made it unplayable for me, you spend money and more importantly time and get these on going problems, I fear this may be an issue that will not be resolved any time soon? I do recall a similar issue some time back, which did go on for awhile.
Okay, I play through Peril Over Pahvo three times a day, for reasons. The only lag I've experienced so far has been when there are like seven different graphics-eating effects going on at the same time near me; other than that, smooth as glass. So while I don't doubt that some of you are experiencing lag, I really don't think it's server-side.
Okay, I play through Peril Over Pahvo three times a day, for reasons. The only lag I've experienced so far has been when there are like seven different graphics-eating effects going on at the same time near me; other than that, smooth as glass. So while I don't doubt that some of you are experiencing lag, I really don't think it's server-side.
I am 90% sure it is server side at least most of it is. When it happens it hits everyone at the same time/simultaneously no matter location Germany, UK, US then it simultaneously clears up for everyone at the same time which strongly points to it being server side.
It even happens in the Ship customisation screen with no graphic effects or bridge officer powers displaying.
So its most likely either you are not noticing lag that is there or its not there in your time zone/playtime. Its not constant lag, it comes and goes in waves. So it could very well be you just didn't notice it or it wasnt there for you. I have zero lag at around 7am to 10am GMT but tend to see more lag at 7pm to 10pm GMT which is when the server is busy again strongly pointing to server-side problems.
My playtime tends to be between 7pm and 9pm GMT (11am to 1pm Pacific). And several people have been complaining that the issue is constant, and denying the experience of anyone who says otherwise.
Is it possible that those times are simply busy times on your local networks? I have no idea which time zone you're working from, of course. (And if you're basing this on zone chat, remember that the only people complaining are those who are in fact experiencing lag; everyone else is busy flying their pretend spaceships or firing their little zap-guns. So this may not be a representative sample.)
Okay, I play through Peril Over Pahvo three times a day, for reasons. The only lag I've experienced so far has been when there are like seven different graphics-eating effects going on at the same time near me; other than that, smooth as glass. So while I don't doubt that some of you are experiencing lag, I really don't think it's server-side.
I used to have graphics related slow downs when playing STO. It was initially hard to differentiate between this sort of slow down, which for me was related to thermal throttling, and other types of lag. The picture became clearer after making sure I could display and/or graph various things such as my frame rate, internal temperatures, operating frequencies, and various types of system generated throttling.
Comments
me and nearly everyone in two trek discords Im in. yep totally just me buddy, not the multitude of threads popping up about it surely.
If you look at the main discord channels, reddit threads, in game chat, Twitter feeds pretty much all the main live streamers chats there are multiple threads all over. With a large amount of them starting up when this thread started up.
When this recent batch of lag started up all my different Star Trek Online feeds every single one pretty much had threads on lag all appearing in the same 24hours. I can name at least 3 streamers who where live streaming when the lag hit and there live chat was all full of people talking about it. Everyone in the streams experienced the same lag simultaneously all from many different world wide locations. That points to a problem with the servers.
EDIT: In fact I just logged in game and what is the first thing I see within seconds in the main chat.
xxxx: if you mean lag and rubberbanding, then yes :
bbbbb: i:rubberbanding and on ground i sprint like crazy and then move normal its weir
xxxx :server sent me a msg, hey, im wonky, and acting like it
Removed names to follow forum rules.
I don't know what has changed or been done, but I haven't been suffering from rubberbanding or lag anymore.
Edit:
Forgot to add: I've mostly been playing Guillotine, twice a day for the event. And some stuff in the Dyson battlezones and on Defera for endeavours. Not much else, but Guillotine and Dyson are the places where the lag tends to be the worst in my experience, when it is present.
So I guess it's a good sign that I didn't experience any, even though I was playing that content.
[3/25 10:41][Combat (Self)]Your Haymaker deals 26187 (10692) Physical Damage(Critical) to Orinoco.
when i use a vpn the game won't authenticate me
No ship is worth this much frustration, so I'll just go do something else now. Bye.
[3/25 10:41][Combat (Self)]Your Haymaker deals 26187 (10692) Physical Damage(Critical) to Orinoco.
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 9 ms 11 ms int-0-6-0-12.dtr01wrcsma.netops.charter.com [96.34.82.241]
4 9 ms 10 ms 11 ms lag-19.hcr01wrcsmarn.netops.charter.com [96.34.142.196]
5 9 ms 9 ms 11 ms lag-10.hcr02wrcsmarn.netops.charter.com [96.34.142.195]
6 13 ms 13 ms 14 ms lag-34.rcr01nwtwctac.netops.charter.com [96.34.142.202]
7 * 18 ms 21 ms lag-800.bbr01nwtwct.netops.charter.com [96.34.2.156]
8 19 ms 26 ms 22 ms lag-805.bbr02ashbva.netops.charter.com [96.34.0.137]
9 23 ms 20 ms 21 ms lag-802.prr01ashbva.netops.charter.com [96.34.3.89]
10 20 ms * * ae-10.edge5.WashingtonDC12.Level3.net [4.68.62.61]
11 * * * Request timed out.
12 30 ms 32 ms 36 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
13 37 ms 36 ms 33 ms 198.49.243.237
14 30 ms 30 ms 31 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
As far as I know "request timed out" is quite common. It just means that the particular stop doesn't respond to a traceroute request so it's not necessarily indicating an error
Usually true, but sometimes it is an actual delay that reaches the timeout threshold, though it is rather rare. Also, the ones that do respond are usually set to handle ping packets last so while it does give a vague idea of the traffic load it is not necessarily what your game packets are dealing with delay wise.
The fact that it is an edge might make it a little more likely that it is a real delay causing the timeout since, despite internet standards, not all networks play well together. Akami is notorious for problems crossing over to other CDNs for instance.
Additionally, the hops with "netops" in the name are probably Spectrum network and they have (or had a few years ago, no idea if they cleaned it up yet) a reputation for odd bouts of lag and whatnot because they got too big too fast, and their network tends to get saturated faster than it should as a result.
It looks like crossing between Spectrum and Lumen (the network that STO apparently uses now according to the IP address) is adding ten to twenty ms just behind the Lumen edge router, which is not that bad though so if it is getting seriously delayed at one of the hops it would probably have to be one of the ones that did not respond to the ping for whatever reason (though as others have pointed out most of the time it just means they are set to ignore pings).
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 2 ms 3 ms 3 ms 192.168.0.1
2 3 ms 3 ms 2 ms 192.168.1.254
3 7 ms 4 ms 5 ms <my IP address removed>
4 * 8 ms 8 ms seattle.bb.telus.com [154.11.15.109]
5 10 ms 8 ms 9 ms ae57.edge6.Seattle1.Level3.net [4.14.240.209]
6 * * * Request timed out.
7 72 ms 72 ms 72 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
8 114 ms 79 ms 112 ms 198.49.243.237
9 79 ms 77 ms 77 ms patchserver.crypticstudios.com [208.95.184.200]
Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
1 3 ms 2 ms 3 ms 192.168.0.1
2 4 ms 3 ms 3 ms 192.168.1.254
3 7 ms 4 ms 5 ms <my IP address removed>
4 * * * Request timed out.
5 44 ms 10 ms 9 ms ae57.edge6.Seattle1.Level3.net [4.14.240.209]
6 72 ms 71 ms 72 ms ae2.3.bear2.Boston1.level3.net [4.69.159.189]
7 72 ms 75 ms 72 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
8 84 ms 82 ms 82 ms 198.49.243.237
9 78 ms 77 ms 78 ms patchserver.crypticstudios.com [208.95.184.200]
I just got my AFS InvalidEntityName as well (the Alliance Rex Pilot Escort). Upon commissioning it disappeared. I had to relog to make it appear in my ship selector. So then I did a traceroute. It was fine (the same as the last one posted here in this forum a day or two ago).
Then there was the ability misfires in space just prior to claiming my ship. I really wish my Cannon Scatter Volley would work more often but I'm getting used to it at this point
2 14 ms 10 ms 13 ms res.spectrum.com
3 32 ms 31 ms 31 ms lag-61.lnclnebt02h.netops.charter.com [76.85.221.29]
4 13 ms 9 ms 13 ms lag-20.lnclnebt02r.netops.charter.com [24.169.242.22]
5 47 ms 53 ms 51 ms lag-31.rcr01hstqtx02.netops.charter.com [24.169.242.2]
6 55 ms 54 ms 50 ms lag-416.hstqtx0209w-bcr00.netops.charter.com [66.109.9.88]
7 * * * Request timed out.
8 * * * Request timed out.
9 91 ms 82 ms 86 ms PERFECT-WOR.bear2.Boston1.Level3.net [4.16.14.234]
10 91 ms 84 ms 82 ms 198.49.243.237
11 81 ms 84 ms 79 ms patchserver.crypticstudios.com [208.95.184.200]
Trace complete.
0 IntegrationTower [192.168.1.8]
1 192.168.1.1
2 res.spectrum.com
3 lag-61.lnclnebt02h.netops.charter.com [76.85.221.29]
4 lag-20.lnclnebt02r.netops.charter.com [24.169.242.22]
5 lag-31.rcr01hstqtx02.netops.charter.com [24.169.242.2]
6 lag-416.hstqtx0209w-bcr00.netops.charter.com [66.109.9.88]
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 IntegrationTower [192.168.1.8]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% res.spectrum.com
0/ 100 = 0% |
3 23ms 1/ 100 = 1% 1/ 100 = 1% lag-61.lnclnebt02h.netops.charter.com [76.85.221.29]
0/ 100 = 0% |
4 13ms 0/ 100 = 0% 0/ 100 = 0% lag-20.lnclnebt02r.netops.charter.com [24.169.242.22]
0/ 100 = 0% |
5 52ms 0/ 100 = 0% 0/ 100 = 0% lag-31.rcr01hstqtx02.netops.charter.com [24.169.242.2]
0/ 100 = 0% |
6 51ms 0/ 100 = 0% 0/ 100 = 0% lag-416.hstqtx0209w-bcr00.netops.charter.com [66.109.9.88]
Trace complete.
Auggie's been arguing that the issue's been caused by the new boff powers from the Final Frontier lock box having no minimum CD and sometimes recharging instantly (can spam very aggressively), with use exasperating within-match lag and contributing to higher server load generally (per this hypothesis). But I've been using those without any ill-effects observed in myself or others. That said 1) I don't use macros and are limited in how fast I can activate these powers, so it could be worth someone else whose connection is *fine* testing new boff power exploits with well-set macros to see if they can upend their connection and 2) this may be entirely supplemental to wider lag issues and simply catching weak/marginal connections out.
Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
Looking for something new to play? I've started building Foundry missions again in visual novel form!
My Hur'q Dreadnought is themed around Asteroids running 6 or 7 Asteroids linked to Mouse button 5 which cycles though Asteroids on click allowing me a constant stream of them. I stacked up Bridge officer cooldown and use the Asteroids as my primary weapon. If the powers are the problem I would have expected a build like this to experience lag/rubber banding but so far neither myself or my team mates are having any problems.
I know whats wrong with it, it aint got no gas in it.
It could have also been targeted at a background issue *besides* frequently reported lag symptoms, identified or introduced with the Thursday maintenance. There's no reason why all maintenance tasks must deal with the same singular problem (because it's affecting enough players in the community to influence the zeitgeist).
Also, if Cryptic was shooting for a general fix for the lag then that'll be something planned for regular maintenance, not thrown in at the last second on a Friday (presumes a eureka moment and mad rush to the patch server without much testing. Ie. an unlikely scenario.)
Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
Looking for something new to play? I've started building Foundry missions again in visual novel form!
It even happens in the Ship customisation screen with no graphic effects or bridge officer powers displaying.
So its most likely either you are not noticing lag that is there or its not there in your time zone/playtime. Its not constant lag, it comes and goes in waves. So it could very well be you just didn't notice it or it wasnt there for you. I have zero lag at around 7am to 10am GMT but tend to see more lag at 7pm to 10pm GMT which is when the server is busy again strongly pointing to server-side problems.
Is it possible that those times are simply busy times on your local networks? I have no idea which time zone you're working from, of course. (And if you're basing this on zone chat, remember that the only people complaining are those who are in fact experiencing lag; everyone else is busy flying their pretend spaceships or firing their little zap-guns. So this may not be a representative sample.)
I used to have graphics related slow downs when playing STO. It was initially hard to differentiate between this sort of slow down, which for me was related to thermal throttling, and other types of lag. The picture became clearer after making sure I could display and/or graph various things such as my frame rate, internal temperatures, operating frequencies, and various types of system generated throttling.