> > > Hi Captains! The team continues to investigate an issue where some players may be stuck on a loading screen. We appreciate your continued patience! < < <
Jolan tru Captain!
Welcome to Legacy of Romulus!
If you have purchased a Legacy or Starter Pack, please see this thread for instructions on how to claim your items in-game. (Please see the yellow text in the linked thread for instructions on creating a Reman.) (Not seeing your pack in-game? Please see the lime-green text in the linked thread above for information.)
If you have additional questions about the Legacy or Starter pack, please read this FAQ.
Thanks SO MUCH for all your support, and we'll see you in-game!
- The Star Trek Online Team
***Resolved Issues***
"Login failed for unknown reason" error
Missing additional character slot for current/ lapsed Gold Members
Slow patching in the launcher
A bug that involved Romulan Liberated Borg captains and their skills once they chose an ally
Support this thread. This problem has existed for way too long.
Quote:
Originally Posted by Archived Post
Problem:
When using Fire at Will the hit rate of the beams drops to the hit rate level of a common turret. The hit rate does not noticeably improve with [Acc] modifiers on the weapons.
I suspect that FAW either ignores [Acc] modifiers or uses a wrong magnitude (e.g. +1% bonus accuracy instead of +10%).
Some sample data (22,7% bonus accuracy vs 54,3% bonus defense):
Turret (common): 79% hit rate
Turret [Acc]x2: 91%
Beam array (common) with FAW2: 75%
Beam array [Acc]x2 with FAW2: 76%
This was a short test (~12min, ~470 shots per weapon), so there is some room for error, but it is already obvious that the [Acc] modifier is not being applied correctly.
How to reproduce:
1) Equip beam arrays and turrets with the same accuracy modifier.
2) Enable the combat log.
3) Shoot at a target with a fixed defense value (that is higher than your bonus accuracy) and use FAW. Keep doing this for a long time to gather useful data.
4) Look at the combat log and calculate the hit rates for beams with FAW and turrets.
5) Repeat steps 1-4 with different accuracy modifiers.
(To make it easier, you can also equip weapons of different energy types with different [Acc] modifiers, so you can test them simultaneously and still have useable combat log data since it distinguishes between different energy types (at least for FAW2).)
Expected Behaviour:
FAW hit rates with a given bonus accuracy level are equal to hit rates with other weapons with the same bonus accuracy.
These test results are from April of 2012 and should be credited to Hilbert (Mancom)
Last edited by brandonfl; 01-12-2013 at 12:20 PM.
Reason: added in quote since the other was a zombie
Is Cryptic really that afraid of people knowing that this bug has existed for 9 months?
Why shoot down "zombies" if not a single entry in that thread is outdated? Every single bit of information in that thread is still valid. Nothing has changed.
Maybe we need a community-run bug tracker for this game to avoid these attempts of revising history.
This makes the engineer class a bit useless in PVP...... Please fix FAW.
aka naz1911
"No, there is no real problem with P2W in STO. Obviously, if you fight against someone with an equal level of skill in the game, better equipment will give you an edge. But usually, it is the skill level that determines the outcome, not the P2W." - Sprinkles
by the sounds of it, it can basically never miss, or have no accuracy bonus at all. they cant get it to work in between that. a beam with 95% accuracy in pvp will only have about 75% accuracy when FAW is used right now. even if it was hitting well it still wouldn't be a very good ability at dealing damage in a group, all the shots are spread out everywhere. i'd rather have a single target FAW if they do anything to it.
by the sounds of it, it can basically never miss, or have no accuracy bonus at all. they cant get it to work in between that. a beam with 95% accuracy in pvp will only have about 75% accuracy when FAW is used right now. even if it was hitting well it still wouldn't be a very good ability at dealing damage in a group, all the shots are spread out everywhere. i'd rather have a single target FAW if they do anything to it.
Is Cryptic really that afraid of people knowing that this bug has existed for 9 months?
Why shoot down "zombies" if not a single entry in that thread is outdated? Every single bit of information in that thread is still valid. Nothing has changed.
Maybe we need a community-run bug tracker for this game to avoid these attempts of revising history.
It's not about it being a bug, or it still having accurate information, it's a blanket forum rule about any thread in these forums (except stickies) established well before my time here. I agree with it because most threads necroed are way out of date, and if they are not, how do we (mods) know for sure it actually is still accurate for sure? If it's been over 30 days with no replies, regardless of the topic, restart a new one and quote the OP (as Brandon did above, with my edit of putting the quote in).
I don't know if it's a bug or not, so a systems dev would need to look into it. Can anyone confirm that CSV *is* affected by ACC?
Cheers,
Brandon =/\=
--------------------
Brandon "BranFlakes" Felczer | Community Manager
Follow us on Twitter: @trekonlinegame | "Like" us on Facebook
Follow me on Twitter: @PWE_BranFlakes If you wish to speak to someone on the community team, file a "Forums and Website" support ticket here.
how do we (mods) know for sure it actually is still accurate for sure?
If I just repost exactly the same information in a new thread, that changes nothing about the information that others will see (other than hiding that this is a longstanding bug with zero response from Cryptic) or about how capable you are of judging its correctness.
How does that help you more than me saying "yes, everything I said the the first post is still valid"?
I get it. It's a rule and it's easier to mindlessly apply it everytime than only when it makes sense. But in this case it hides valuable information. The fact that a bug is not new is important, because it gives you an indication of when the issue was introduced into the code base.
Quote:
Originally Posted by pwebranflakes
Can anyone confirm that CSV *is* affected by ACC?
Yes, CSV does take [Acc] modifiers into account. There are some quirks with CSV's accuracy too, but nothing major. It's certainly much closer to what it should be than FAW which simply ignores the modifiers.
(Fun fact: not only does FAW ignore [Acc] modifiers, it also uses the cannon accuracy formula instead of the one for beams.)