[ARSPR]

While digging about FS1 hud, (see this post), I've noticed that $Reticle Style: FS1 from fsport-reticle-hdg.tbl in fsport3_1_1.vp is undocumented in Hud_gauges.tbl wiki help

Although its usage and meaning is pretty obvious, I think you should update the wiki with an explanation about what this entry exactly does and its position in the table. I don't mind doing myself, but I have no knowledge about it.

(Also I don't know which is the opposite setting to $Reticle Style: FS1, in case I wanted to undo it ($Reticle Style: Default?, $Reticle Style: FS2?, $Reticle Style: Original?, ...). Or even if it has other possible values)



OTOH I just want to check if I understand the difference of XMT and non-XMT tables.

+ XMT table means that every $Named entry does not override the tbl one. It just modify the tbl one. In this situation just modified subentries are needed.
+ non-XMT table means that every $Named entry does override the tbl one. So the modder needs to type the full subentries that $Named entry needs in order to work.

[Woolie Wool]

Seconding this motion, and it would also be really nice if the feature could be implemented under #Ship Main Gauges instead of globally so I could assign it to individual ships.

Also, if anyone could translate the original FS2 HUD into a Main Gauges set for hud_gauges.tbl, that would be really great.

[blowfish]

Just looked at the code.  It's either FS1 or FS2.

[ARSPR]

Thank you, Blowfish.

Could you provide more info or update wiki? I mean:

• Its position in the table
• What it exactly changes. (Ie, it does not load neither 2_lock1.ani (hi-res) nor lock1.ani (low-res) but 2_lock1_fs1.ani, or whatever, and so on)

I repeat, I don't mind updating the wiki myself but I don't know what this setting exactly does. I can just guess...

  Also a little bump... Could someone check if I understand XMT vs non-XMT? Thank you in advance.

[blowfish]

TBH I could look up where it is pretty easily, but figuring out what, specifically, it does would require a lot more time and effort...

[Zacam]

$Reticle Style: added to Misc list.

I don't fully know the difference between XMT vs non-XMT, but I do know that for mflash.tbm to work, it can only add new information. If it contains no changes to the default TBL entries. Changes to the main tbl entries requires a tbl.

Ergo why the MediaVP's have a TBL in MV_Effects, but a TBM in MV_Advanced. The one in Effects makes changes to the hard-coded values while the one in Advanced adds the additional muzzle flash effect.

In summary: XMT can Modify and/or Extend. Non-XMT can Replace or Extend. Replacement usually has to occur via TBL though.