|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001165||FSSCP||OpenGL||public||2006-12-03 13:51||2012-01-09 13:06|
|Target Version||Fixed in Version||3.6.9|
|Summary||0001165: Tertiary thrusters do not work on capital ships|
|Description||What the title says.|
Specifying tertiary thrusters in the ships.tbl has no effect ingame:
$Thruster01 Radius factor: 1.2
$Thruster02 Radius factor: 1.2
$Thruster03 Radius factor: 1.9
This entry works on fighters without any problems.
We are using DDS thrusters. Now that I think of it: only the long engine trail will be rendered (It is the secondary thruster unless I am much mistaken) if using TGA thrusters.
|Tags||No tags attached.|
|See if it's fixed in: http://icculus.org/~taylor/fso/willrobinson/hoopla.rar|
what's this rubbish anyway?
Warning: Use of deprecated subsystem syntax. Please use the $Flags: field for subsystem flags.
At least one of the following tags was used on ship TCS CV-50 Wellington, subsystem ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌhstuff03a:
[This filename points to the location of a file on the computer that built this executable]
parse_shiptbl() ship_init() game_init() game_main() WinMain() WinMainCRTStartup() kernel32.dll 7c816f9f()
|and a small nitpick: why are secondary thrusters fading away depending on the angle|
take a look at this. Is this intended? Can't see why it should, but...
I mean, how should thruster flame be visible from one angle and not from another?
The subsystem syntax was changed by WMC in the untable branch, and Goober just added that to the stable branch (3.6.9) to try and keep things compatible. I'm debating whether to change it from a Warning to just a quiet debug log thing though, since it is rather annoying. Both the old and new options work still. What it basically means is that instead of using +untargetable and/or one of the others, you replace them with something like: $Flags: ( "untargetable" "carry no damage" )
As far as fading away, I'm not really sure. That's still Bobboau's original code so he would be the one to ask about it.
from what I gathered Wanderer changed that to avoid clipping issues. The result is that I am forced to reduce the trail length by factor two to keep this less noticeable, i.e. I add
$Thruster01 Length factor: 0.5
which oddly enough scales the length of Thruster02.
Personally I see no reason for this fading, because the clipping issue is related to primary/tertiary thrusters. The secondary thruster has little effect if placed properly.
fs2open: fs2_open_3_6_9 r3789
Timestamp: 2006-12-07 13:21:25
|unbreak the breakage that I broke when I tried to fix breakage that wasn't broken the second time but initialy broke instead
(yeah, this one confused me ;)) (Mantis bug 0001165)
|mod - /branches/fs2_open_3_6_9/fs2_open/code/model/modelinterp.cpp|
|2006-12-03 13:51||Tolwyn||New Issue|
|2006-12-03 13:51||Tolwyn||Status||new => assigned|
|2006-12-03 13:51||Tolwyn||Assigned To||=> taylor|
|2006-12-06 03:40||taylor||Note Added: 0007247|
|2006-12-06 06:15||Tolwyn||Note Added: 0007259|
|2006-12-06 06:21||Tolwyn||Note Added: 0007260|
|2006-12-06 06:28||Tolwyn||Note Added: 0007261|
|2006-12-06 12:00||Tolwyn||File Added: thrusters.jpg|
|2006-12-06 12:01||Tolwyn||Note Added: 0007262|
|2006-12-06 14:13||taylor||Note Added: 0007263|
|2006-12-06 15:10||Tolwyn||Note Added: 0007264|
|2006-12-07 15:46||taylor||Status||assigned => resolved|
|2006-12-07 15:46||taylor||Fixed in Version||=> 3.6.9|
|2006-12-07 15:46||taylor||Resolution||open => fixed|
|2006-12-07 15:46||taylor||Note Added: 0007276|
|2012-01-05 17:55||taylor||Changeset attached||=> Import 2012-01-05 17:52:05 fs2_open_3_6_9 r3789|
|2012-01-09 13:06||taylor||Changeset attached||=> fs2open_websvn fs2_open_3_6_9 r3789|