View Issue Details
ID | Project | Category | Date Submitted | Last Update | |
---|---|---|---|---|---|
0018096 | Starward Rogue | Bug - Other | Dec 29, 2015 3:26 pm | Mar 19, 2016 7:40 pm | |
Reporter | Pepisolo | Assigned To | keith.lamothe | ||
Status | resolved | Resolution | fixed | ||
Product Version | 0.207 | ||||
Fixed in Version | 1.018 | ||||
Summary | 0018096: Shot_homing_range applies to bullet pattern...but in a weird way. | ||||
Description | Ever in search of the ability to mix homing and straight shots on a weapon, I tried a couple of bullet patterns, one with the <die> tag, one without. Straight shot with the tag, homers without, expecting that the homing property would only pass on to the homers, but this doesn't quite happen. The homing property does affect the straight shots using the <die> tag, too -- but it does so in an unusual way. Rather than the shots traveling towards a target and then acquiring to home in, instead the shots only home when my mech is within the specified homing range from the target. Let's say I set the homing range to 500, if I stand outside that range and shoot then no homing ever occurs, if I'm within that range it homes. This is in contrast to the expected behaviour which is that the bullet will travel until it hits its homing range and then acquire. If I remove the <die> tag normal behaviour is resumed. | ||||
Tags | No tags attached. | ||||
|
Sorry, lazy programmer here, could you give me xml for a gun that should do what you want but doesn't? I get that the homing range appears to be computed from your location rather than from the shot's location, but it also sounds like in other configurations the homing range appears to be computed from the shot's location. Is that correct? |
|
It's been a while since I posted this report, but just doing a quick test, and setting the SMART Gun up in my test chamber with the problem in the latest revision 2567, it seems like the issue may be that homing is not even supposed to apply to bullets in a bullet pattern? Is this correct, theoretically? If so, then instead, if you use the weapon in my test chamber you should be able to see that if you shoot the weapon at far range (beyond 500), the shot never aqcuires, but if you walk into range and shoot, the shot homes in immediately. So, yeah, most of the time homing seems to work as expected, coming from the shot's location, but in this one instance of homing being applied to a bullet pattern with a <die/> tag it seems to do unexpected things. Hopefully this info helps. |
|
Just a note, I've recently updated the Smart Gun to work properly, so if you need to test this issue you'd need to roll the configuration folder back to revision 2567. If this is awkward to do, I can prepare a weapon as a mod to recreate the oddity. |
|
For 1.018: * Fixed a bug where a system with homing and a bullet pattern would allow the homing to work on the initial firing (it was correctly not trying to home after that; bullet patterns override homing until the pattern expires). Thanks :) Basically you're correct that homing is not supposed to apply to a bullet-pattern shot. The pattern controls movement, so if it was also homing that would get contradictory in a lot of cases. But it was inconsistent that homing would change things in the initial firing in that case, and that's been fixed now. |
Date Modified | Username | Field | Change |
---|---|---|---|
Dec 29, 2015 3:26 pm | Pepisolo | New Issue | |
Jan 20, 2016 5:56 pm | Chris_McElligottPark | Assigned To | => keith.lamothe |
Jan 20, 2016 5:56 pm | Chris_McElligottPark | Status | new => assigned |
Mar 11, 2016 1:13 pm | keith.lamothe | Note Added: 0045395 | |
Mar 11, 2016 1:13 pm | keith.lamothe | Status | assigned => feedback |
Mar 11, 2016 2:50 pm | Pepisolo | Note Added: 0045403 | |
Mar 11, 2016 2:50 pm | Pepisolo | Status | feedback => assigned |
Mar 11, 2016 2:50 pm | Pepisolo | Note Edited: 0045403 | |
Mar 12, 2016 4:50 pm | Pepisolo | Note Added: 0045406 | |
Mar 19, 2016 7:40 pm | keith.lamothe | Note Added: 0045445 | |
Mar 19, 2016 7:40 pm | keith.lamothe | Status | assigned => resolved |
Mar 19, 2016 7:40 pm | keith.lamothe | Fixed in Version | => 1.018 |
Mar 19, 2016 7:40 pm | keith.lamothe | Resolution | open => fixed |