|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
KalOfTheRathi
Black Phoenix Mercenaries
736
|
Posted - 2013.09.20 23:43:00 -
[1] - Quote
DeathwindRising wrote:to clarify, the turret does not disappear at 250m. the tactical info that appears while aiming at a target disappears at 250m, which if i understood its function, means that i am outside my weapons maximum range.
i can see and hit targets with a rail gun at over 550m no problem, so if the enforcer skill was working properly, then the tactical info should be showing me a maximum range of about 287m, which is what im expecting.
am i misunderstanding something? Only that you think it should work as documented.
It does look like you have tested it correctly, personally. Some confusion from the Rail Gun crowd is to be expected. We lose track of everything beyond 300m or so. Although our range still seems to be 599m.
As a last resort you might file a trouble petition with [email protected] including the information you posted here. Please be polite, like you were here, as they are real people. You will get an automated reply and then sometime later they will get back to you. |
KalOfTheRathi
Nec Tributis
748
|
Posted - 2013.09.25 01:14:00 -
[2] - Quote
bear90211 wrote:your not misunderstanding, i think the range might be a carry on thing, try testing a sica on a new char and aim at a turret, if its the same as those then its bugged, but if its less then the enforcer skill carries over to any tank, (max out both to get 20% more range on anything, and 15% dmg extra for missles and blasters on any tank), try that though. Your comment makes me remember some of the Close Beta issues. Some of the information worked, however it was not displayed correctly in the UI. This has been the source behind a constant stream of requests to add more information on all weapons with range being specifically singled out.
The OP tests showed the system is not working correctly. When we had CPU display/modification issues the values worked on the Suit (with its rounding down problems) but the display had trouble letting you know how much CPU a particular weapon actually needed if you had boosted the required skill.
Here the Missile bonus does not work at 250m. Either the Sica should work less effectively or the Maruader Skill should boost the Falchion to Something More Than 249m.
I would however try your suggestion. Build a test alt. Give them enough ISK to buy a Sica with a missile turret. Then repeat the test, without the Falchion. That should clarify the situation. If the Sica is limited to 200m then the Skill is working. If the Sica is exactly the same at 249m yes/250m no then the skill is broken or bugged.
Looking at the Range Document it claims the missile turret is limited to 200m.
It is sticky posted in the Rookie Training forum:
https://forums.dust514.com/default.aspx?g=topics&f=899 |
KalOfTheRathi
Nec Tributis
749
|
Posted - 2013.09.25 11:20:00 -
[3] - Quote
DeathwindRising wrote:the range document shows a max range of 200m for small missile turrets.
it actually shows 250m as the max range (we now know thats incorrect) for large turrets, again, indicating the skill is bugged/broken Reply to the sticky with your information. It can always use the data.
Nnow you can reply to support and inform them that you find the numbers don't add up. Request that they give specific answers regarding how much you should see from your bonus skills. It can be a hassle as they will have to duplicate the problem in their test environment. Or worse, in game. What should happen (in the normal course of events, not in Shanghai or DUST) would be some numbers provided by a Dev (range is X, bonus makes is X*1.1 or such). This might resolve by itself when range information is included in a patch.
Don't forget to show what you got, plus the Calculated differences while asking them to correct your math if necessary. That might produce some actual data.
In the future you might use my cynical solution. Level to 1. Try it. If you like it then skill to lvl 3. Past that I only do it if I need to get to the next level or I have a Huge Surplus of SP. As if. I have AR to lvl 5 because I have collected Officer weapons which require Prof lvl 3. So that got bumped. Several tank skills however provide a poor return on SP investment past lvl 3. Your mileage may vary and you may not be quite as devoted a cynic as I am.
Good Luck.
|
KalOfTheRathi
Nec Tributis
754
|
Posted - 2013.09.26 01:36:00 -
[4] - Quote
I wish I could say I was surprised by the response. I am not.
They will not respond to 99.999% of Bugs in the Technical Support/Bugs Forum. Which induces rage and frustration.
There is no bug tracking system such that someone could be pointed to an existing bug report and say, "Yep, we know about that. it is not fixed and is not on the current schedule to be fixed. Check back later". Many systems do. Many companies do. CCP (Iceland or Shanghai) Do Not. At least not one that is visible to their customers. Somewhat surprising in all actuality.
I would strongly suggest that you quit spending more SP on the Skill until the Vehicle Change Everything And Maybe Fix It Later Patch is added back to the schedule and actually is Released.
Before I got my SP Respec I had many problems with my SP and the Skill Tree. Now I only have made one or two mistakes. Partly because some of the worst documentation problems are known or have been fixed.
Remember, the core game does not work consistently nor correctly. That needs to be fixed yet it has no actual references to any plans on getting any resources allocated to it, much less it actually being something that should be fixed. New things are being added, many things promised have never arrived, the 1.1 patch drove many away and while 1.4 is the best version of Uprising it is still essentially a broken game.
Which means, fixing your skill bonus problem is so low on the to do list that I doubt if one could see it with the original FarSight Sniper Rifle, back when one could see 1.5km.
As Ever, Good Luck. KR |
KalOfTheRathi
Nec Tributis
758
|
Posted - 2013.09.26 12:24:00 -
[5] - Quote
DeathwindRising wrote:Thanks, and it's disappointing that we don't even get an acknowledgement from devs about bugs such as this. What's the point in having a technical support and bugs forum if we don't know if anything is being fixed or worked on?
Well, when you figure it out please post it because it makes no sense to me.
The only thing that has consistently gotten some response (i.e. fixes) have been map feedback. I have posted several and they were fixed. Which left me with unreasonable expectations regarding the rest of these forums.
|
|
|
|