I've brought up the issue with map load-times to our software and net team. This is affecting STO as well as NW for high-pop maps, so we're checking into it and the way new zones are spun-up.
There are several threads about this in the bug forum and none of the devs or community managers says a word. Yet when someone posts a thread about it in the general forum, even though it is against the rules, someone finally takes notice. Discord would be so proud for having things not making sense per usual.
Hate venting like this, but it is rather frustrating. This has been going on since the start of "New Dawn".
There are several threads about this in the bug forum and none of the devs or community managers says a word.
Some of the Bug Hunters have brought it up in the registry and have commented on a few of the threads in the Gameplay Bug Reports section, however I'm not going to waste my time answering every single little thread written by someone who can't be bothered to see if its already been posted or not.
Ten soldiers wisely led will beat a hundred without a head. - Euripides
I no longer do any Bug Hunting work for Cryptic. I may resume if a serious attempt to fix the game is made.
There are several threads about this in the bug forum and none of the devs or community managers says a word. Yet when someone posts a thread about it in the general forum, even though it is against the rules, someone finally takes notice. Discord would be so proud for having things not making sense per usual.
Hate venting like this, but it is rather frustrating. This has been going on since the start of "New Dawn".
Technical bug forums, including the bug hunters group won't always gets a response. The developers who are focused in that area are too busy actually working on debugging to verify and investigate it. Keep in mind that "Saying a word" actually has significant implications both positive and negative, especially before an investigation actually takes place. At best it acknowledges that we read a post. At worst, it sets up an expectation for acknowledging every single report that comes in and the validity of every piece of information along an extremely long and complicated pipeline for Q/A and debugging. What if it's something to do with Nvidia drivers? What if it's a null bug? What if it's only affecting EU users?
The reason why I responded to this is because it's a significant enough impact that's taken enough hold that I feel the need to respond at this stage in the investigations. As far as understanding the nature of the beast itself, I'm hesitant to respond further until I understand more concepts about the cause and function of the bug. Is it a software issue and inherent to a client build involving these maps? Maybe it's a network issue? Maybe it's related to the spin-up of a new zone on these maps and the spin-up time is impacted somehow. These all take serious testing. The last thing I'd rather do is just "Hey I acknowledge this is an issue!" and then shrug it off and ignore it. If I commit to something like fixing this, I damn well have my teeth in it and the expectation that I'm going to hunt it down to the end of the earth.
There are several threads about this in the bug forum and none of the devs or community managers says a word. Yet when someone posts a thread about it in the general forum, even though it is against the rules, someone finally takes notice. Discord would be so proud for having things not making sense per usual.
Hate venting like this, but it is rather frustrating. This has been going on since the start of "New Dawn".
Technical bug forums, including the bug hunters group won't always gets a response. The developers who are focused in that area are too busy actually working on debugging to verify and investigate it. Keep in mind that "Saying a word" actually has significant implications both positive and negative, especially before an investigation actually takes place. At best it acknowledges that we read a post. At worst, it sets up an expectation for acknowledging every single report that comes in and the validity of every piece of information along an extremely long and complicated pipeline for Q/A and debugging. What if it's something to do with Nvidia drivers? What if it's a null bug? What if it's only affecting EU users?
The reason why I responded to this is because it's a significant enough impact that's taken enough hold that I feel the need to respond at this stage in the investigations. As far as understanding the nature of the beast itself, I'm hesitant to respond further until I understand more concepts about the cause and function of the bug. Is it a software issue and inherent to a client build involving these maps? Maybe it's a network issue? Maybe it's related to the spin-up of a new zone on these maps and the spin-up time is impacted somehow. These all take serious testing. The last thing I'd rather do is just "Hey I acknowledge this is an issue!" and then shrug it off and ignore it. If I commit to something like fixing this, I damn well have my teeth in it and the expectation that I'm going to hunt it down to the end of the earth.
An understandable explanation, thanks.
It's good to know it's being looked into, but don't worry, I understand that it could take time or might be something out of the dev teams control. Honestly, I'm happy just knowing they're investigating the issue.
There are several threads about this in the bug forum and none of the devs or community managers says a word. Yet when someone posts a thread about it in the general forum, even though it is against the rules, someone finally takes notice. Discord would be so proud for having things not making sense per usual.
Hate venting like this, but it is rather frustrating. This has been going on since the start of "New Dawn".
There are many other issues that have been repeatedly reported and are still in the game. Some have been around for years now. A favorite of mine?
The T5 C-Store B'Rel can use the T1 B'Rotlh BOP skin but the T5 Fleet version can't. This has repeatedly been reported since it was discovered when the B'Rotlh came out in Summer 2013 with Legacy of Romulus' release. Yet the problem is STILL here. Even better, the new T6 Kor, C-Store and Fleet versions, inherit the SAME issue.
There's also the old problem of the KDF Kar'Fi Carrier that is missing half its textures. It's merely a few spines floating in space. This affects both the player and NPC versions of the ship. This is an old issue and has been reported many times. It's a very glaring issue that reminds you every time you see one of these ships in the game and slaps you across the face, "THIS TRIBBLE IS TRIBBLE UP."
Report it, I have a few times. On my 4th toon waiting to beam in, sitting at 97.something each time. Crashing the game. But for the record happens everyday and most every toon. I have found crashing the game and re-launching it, most the time I beam right in. I start my day and end it at DS9. forum.arcgames.com/startrekonline/discussion/1210139/latency-investigations#latest
Comments
Thanks for the update boss. Much appreciated.
Hate venting like this, but it is rather frustrating. This has been going on since the start of "New Dawn".
Some of the Bug Hunters have brought it up in the registry and have commented on a few of the threads in the Gameplay Bug Reports section, however I'm not going to waste my time answering every single little thread written by someone who can't be bothered to see if its already been posted or not.
The reason why I responded to this is because it's a significant enough impact that's taken enough hold that I feel the need to respond at this stage in the investigations. As far as understanding the nature of the beast itself, I'm hesitant to respond further until I understand more concepts about the cause and function of the bug. Is it a software issue and inherent to a client build involving these maps? Maybe it's a network issue? Maybe it's related to the spin-up of a new zone on these maps and the spin-up time is impacted somehow. These all take serious testing. The last thing I'd rather do is just "Hey I acknowledge this is an issue!" and then shrug it off and ignore it. If I commit to something like fixing this, I damn well have my teeth in it and the expectation that I'm going to hunt it down to the end of the earth.
An understandable explanation, thanks.
It's good to know it's being looked into, but don't worry, I understand that it could take time or might be something out of the dev teams control. Honestly, I'm happy just knowing they're investigating the issue.
Thanks.
There are many other issues that have been repeatedly reported and are still in the game. Some have been around for years now. A favorite of mine?
The T5 C-Store B'Rel can use the T1 B'Rotlh BOP skin but the T5 Fleet version can't. This has repeatedly been reported since it was discovered when the B'Rotlh came out in Summer 2013 with Legacy of Romulus' release. Yet the problem is STILL here. Even better, the new T6 Kor, C-Store and Fleet versions, inherit the SAME issue.
There's also the old problem of the KDF Kar'Fi Carrier that is missing half its textures. It's merely a few spines floating in space. This affects both the player and NPC versions of the ship. This is an old issue and has been reported many times. It's a very glaring issue that reminds you every time you see one of these ships in the game and slaps you across the face, "THIS TRIBBLE IS TRIBBLE UP."
forum.arcgames.com/startrekonline/discussion/1210139/latency-investigations#latest