Forums » Suggestions
AA off = Tracking missiles dumbfire
So gems, swarms, firefly, etc, all dumbfire when you turn AA off.
It doesn't make a lot of sense that you have to untarget if you want to dumbfire them.
It doesn't make a lot of sense that you have to untarget if you want to dumbfire them.
Yeah lets do this. Dumb-firing is one of those things that generally sucks, but it has its uses where it's really the only thing you can do, in those cases you end up using the targetnone command and doing it anyway.
Be nice to streamline this.
Be nice to streamline this.
this makes sense, disable your targeting computer, everything fires manual
+1
+1
Use the Force Luke.
+1 TBH it makes perfect sense to "that you have to untarget if you want to dumbfire them" There homing after all, and not related to your ships computer.
That said, I think if VO were real file there would be a dumbfire button on the flight stick/cockpit wall/implant/meditation ritual etc. etc. and this does give a good way to do it that doesn't result in having to bind yet another button to something.
This could be done via plugin.
That said, I think if VO were real file there would be a dumbfire button on the flight stick/cockpit wall/implant/meditation ritual etc. etc. and this does give a good way to do it that doesn't result in having to bind yet another button to something.
This could be done via plugin.
+1
Someone told me that there already is a plugin to temp untarget so you can dumbfire missiles but it's tricky to set up.
As for linking the homing feature of missiles being linked to the ship's targeting computer not being realistic. The missiles are already communicating to the targeting computer in order to get their target so whether or not they home should be a targeting computer issue anyway.
Someone told me that there already is a plugin to temp untarget so you can dumbfire missiles but it's tricky to set up.
As for linking the homing feature of missiles being linked to the ship's targeting computer not being realistic. The missiles are already communicating to the targeting computer in order to get their target so whether or not they home should be a targeting computer issue anyway.
+1 This is a great idea!
"This could be done via plugin."
Let me say this for the last time.
Making Plugins to solve an issue does not solve the issue for everyone, in fact it reaches very few people.
It's like saying, why should the developers redesign the station UI, or the HUD? We can just do it via a plugin. I never ever want to see this used as a solution.
/rage
Let me say this for the last time.
Making Plugins to solve an issue does not solve the issue for everyone, in fact it reaches very few people.
It's like saying, why should the developers redesign the station UI, or the HUD? We can just do it via a plugin. I never ever want to see this used as a solution.
/rage
+1
+1
+1
+a lot
+1
+1
@Kierky - Two reasons
1. The likely hood of this getting implemented is horridly small. It was decided that it is intuitive for homing missiles to home even with AA off. Now you want to go counter to that. Think of how "complicated" it would be to turn on a/a for a gem then turn it off to get your AAP working again and then back on to shoot another gem then back off....... It adds complexity to a fight that not everyone wants. Not to mention that I would guess you want your homing missiles to home no matter what far more frequently then you want to dumb fire them.
2. The plugin interface is quite extensive. As you said you could totally redo the PDA and many aspects of the game. I would be willing to bet that anyone "advanced" enough to when to dumb fire a missile can handle installing a plugin. That would allow you to get your *feature* with out making the devs do it.
But this is the standard plugin argument. There are benefits to both. I don't think your feature is likely to be implemented in the core interface. But I like the idea, and plugin seems a good fit.
1. The likely hood of this getting implemented is horridly small. It was decided that it is intuitive for homing missiles to home even with AA off. Now you want to go counter to that. Think of how "complicated" it would be to turn on a/a for a gem then turn it off to get your AAP working again and then back on to shoot another gem then back off....... It adds complexity to a fight that not everyone wants. Not to mention that I would guess you want your homing missiles to home no matter what far more frequently then you want to dumb fire them.
2. The plugin interface is quite extensive. As you said you could totally redo the PDA and many aspects of the game. I would be willing to bet that anyone "advanced" enough to when to dumb fire a missile can handle installing a plugin. That would allow you to get your *feature* with out making the devs do it.
But this is the standard plugin argument. There are benefits to both. I don't think your feature is likely to be implemented in the core interface. But I like the idea, and plugin seems a good fit.
1. How do you know what was decided? The game's behavior now might just be a consequence of how it was implemented.
2. Yes you can do it with a plugin, there's already a plugin that does this. The problem is, the plugin untargets your enemy, just like you would have to manually, which makes the lead indicator and bounding box disappear. Both of which are useful in determining where to aim.
I'd actually prefer a toggle that turns off missile locking independently from blaster autoaim.
2. Yes you can do it with a plugin, there's already a plugin that does this. The problem is, the plugin untargets your enemy, just like you would have to manually, which makes the lead indicator and bounding box disappear. Both of which are useful in determining where to aim.
I'd actually prefer a toggle that turns off missile locking independently from blaster autoaim.
coteyr, there is this awesome invention that was recently developed. It's called the checkbox. You should look into it. They're particularly useful in configuration windows.
@Pizzasgood - Bah checkboxes are overrated, and rarely implemented. Even in VO.
@abortretryfail - It was decided either passively or actively. Just because someone didn't actively decide not to do something doesn't mean that they didn't passively decide. We make these decisions all the time.
@abortretryfail - It was decided either passively or actively. Just because someone didn't actively decide not to do something doesn't mean that they didn't passively decide. We make these decisions all the time.
Okay, by that logic just delete the suggestions forum, because they decided to make the game exactly how it is right now and any suggestion for change is futile.
+1 Kierky