View Issue Details

IDProjectCategoryView StatusLast Update
0002187FSSCPgameplaypublic2010-09-27 12:02
ReporterDarth Geek Assigned ToWanderer  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.6.12 RC2 
Summary0002187: Lead indicator displays in the wrong place, depending on where the target is on the screen.
DescriptionProblem's in the title.

Say you're targeting a cargo container or sentry gun. The lead indicator should naturally be in the exact center of the target, since it isn't moving.

With this bug, if you're facing the center of the container, then this is the case- the lead indicator is right on top of it. But if you pivot to, say the left, the lead indicator will move to the right a bit.

This becomes a bit of a problem since I'm modding some ships with autoaim, and autoaim fires at the lead indicator.

Upon inspection, it appears that this is yet another FOV issue. Setting FOV to 0.5 resolves the issue (I didn't try to find out where it starts occurring).
Additional InformationFS rendering in general over a certain FOV appears, upon consideration, to suck monkey balls.
TagsNo tags attached.

Activities

Darth Geek

2010-04-21 02:54

reporter   ~0011899

OK, my mistake, this has nothing to do with FOV. It has to do with velocity, it seems- say you target a cargo container that's off to the side and move forward. The lead indicator will appear to move opposite your direction (This would technically be accurate, since it would be depicting relative speeds, but unfortunately it still causes autoaim to be inaccurate).

Wanderer

2010-05-29 12:31

developer   ~0012018

Are you using additive velocity (ship velocity is added to weapon velocity)?

Wanderer

2010-06-11 08:55

developer   ~0012057

It does seem however that code did not take properly account the firing ships velocity if the additive weapon velocity was enabled. It was sort of partially utilized but not to the full extent

Wanderer

2010-06-12 21:00

developer   ~0012062

Try post r6203 builds to see if the problem has been fixed

Wanderer

2010-09-27 12:02

developer   ~0012370

Assuming the problem was fixed

Issue History

Date Modified Username Field Change
2010-04-21 02:13 Darth Geek New Issue
2010-04-21 02:54 Darth Geek Note Added: 0011899
2010-05-29 12:31 Wanderer Note Added: 0012018
2010-06-11 08:55 Wanderer Note Added: 0012057
2010-06-12 20:58 Wanderer Status new => assigned
2010-06-12 21:00 Wanderer Note Added: 0012062
2010-06-12 21:00 Wanderer Status assigned => feedback
2010-09-27 12:02 Wanderer Note Added: 0012370
2010-09-27 12:02 Wanderer Status feedback => resolved
2010-09-27 12:02 Wanderer Resolution open => fixed
2010-09-27 12:02 Wanderer Assigned To => Wanderer