Forums » Bugs
Leadoff marker for l-port weapons
As per Incarnate's request, I'm posting what happened to me this afternoon.
During an hive skirmish run, I found myself sent off to an ion storm roid field to fight the rust buckets. I had a Territorial Defender with an Axia Accelerated Positron and Mega Positron.
I went back to the nearest base in Latos, and mounted a storm extender. After this, my mposi shown the behavior I'm reporting here.
Basically, the leadoff yellow reticle stopped "working right": it's present onscreen, but always glued on the target (ship, roid, cargo), instead of, well, leading off where I should fire.
At first I thought the auto-target had been accidentally disabled, or not working anymore for the mposi. However, after deeper tests (see below), the autotarget feature DOES work. It's just the display of the leadoff marker that's kind of stuck.
Trying to replicate the behavior, I conducted some tests. In all the tests, the weapons were on DIFFERENT groups:
TD + mposi alone = reticle not working
TD + any s-port WEAPON + mposi = reticle works
TD + storm + mposi = doesn't work
Rag + mposi = doesn't work
Rag + adv gatling turret = doesn't work
Rag + mposi + agt = doesn't work
Rag + agt + mposi = doesn't work (so doesn't depend on weapon order/group)
Rag + gov plasma + mposi and/or agt = works
Rag + storm extender + mposi and/or agt = doesn't work
It seems that for the l-port leadoff marker to work, it needs an s-port weapon present on the ship.
People in guild chat were asked to confirm the behavior, and they confirmed. At least one in channel 100 said mposi worked fine for him, but I don't know if he tried it alone, or with another s-port weapon mounted.
It's not a catastrophic problem, once you know how to work around it. But sure it's annoying.
During an hive skirmish run, I found myself sent off to an ion storm roid field to fight the rust buckets. I had a Territorial Defender with an Axia Accelerated Positron and Mega Positron.
I went back to the nearest base in Latos, and mounted a storm extender. After this, my mposi shown the behavior I'm reporting here.
Basically, the leadoff yellow reticle stopped "working right": it's present onscreen, but always glued on the target (ship, roid, cargo), instead of, well, leading off where I should fire.
At first I thought the auto-target had been accidentally disabled, or not working anymore for the mposi. However, after deeper tests (see below), the autotarget feature DOES work. It's just the display of the leadoff marker that's kind of stuck.
Trying to replicate the behavior, I conducted some tests. In all the tests, the weapons were on DIFFERENT groups:
TD + mposi alone = reticle not working
TD + any s-port WEAPON + mposi = reticle works
TD + storm + mposi = doesn't work
Rag + mposi = doesn't work
Rag + adv gatling turret = doesn't work
Rag + mposi + agt = doesn't work
Rag + agt + mposi = doesn't work (so doesn't depend on weapon order/group)
Rag + gov plasma + mposi and/or agt = works
Rag + storm extender + mposi and/or agt = doesn't work
It seems that for the l-port leadoff marker to work, it needs an s-port weapon present on the ship.
People in guild chat were asked to confirm the behavior, and they confirmed. At least one in channel 100 said mposi worked fine for him, but I don't know if he tried it alone, or with another s-port weapon mounted.
It's not a catastrophic problem, once you know how to work around it. But sure it's annoying.
Is the L-port weapon bound to Secondary fire?
The aiming reticle leads the target for ONLY the primary weapon group. If you've grouped your weapons right, you shouldn't have this problem, but if you put something that doesn't fire straight at a forward velocity (scanner, mining beam, most missiles, mines) in the primary weapon group, the aiming reticle will cease to function and will remain locked on your target.
The aiming reticle leads the target for ONLY the primary weapon group. If you've grouped your weapons right, you shouldn't have this problem, but if you put something that doesn't fire straight at a forward velocity (scanner, mining beam, most missiles, mines) in the primary weapon group, the aiming reticle will cease to function and will remain locked on your target.
Also, if you have two or more weapons in your primary fire group, the one listed first on the grouping interface is the one whose autoaim is used--so if you have a neut and a gauss on that group, and the neut is listed first, you'll only see the targeting reticle of the neut. (and vice versa.)
The answers explain it all.
In all my tests, the L-port weaponry were either in the secondary or in the tertiary group.
I was not aware that the leadoff reticle is linked only for the first weapon listed in the primary group. It seems very limiting to me, but at least from a bug point of view, this is not a bug at all. :)
Can be locked, I guess.
In all my tests, the L-port weaponry were either in the secondary or in the tertiary group.
I was not aware that the leadoff reticle is linked only for the first weapon listed in the primary group. It seems very limiting to me, but at least from a bug point of view, this is not a bug at all. :)
Can be locked, I guess.
Very well handled, Cunjo and MSKanaka.
[locked]
[locked]