Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: IPAndrews on January 22, 2008, 02:01:40 am
-
Please can someone tell me. Is there a flag or registry entry to turn on the wireframe target view by default?
-
That would be no then. :)
-
Isn't there a key press to do it?
-
Can I program the TBP installer to automatically press the key every time the game is started up? :)
-
Nah but if a key press does exist it mean I'd only have to do the easy work to add the feature. :D
-
There is a key-combo for it, but there was also supposed to be an option somewhere to enable it by default. I can't remember what that option is, or if it ever even got into CVS, but the plan was to add it (to hud_gauges.tbl, but I don't see anything about it in the commit logs).
-
Ok thanks for looking. :yes:
-
There is a key-combo for it, but there was also supposed to be an option somewhere to enable it by default. I can't remember what that option is, or if it ever even got into CVS, but the plan was to add it (to hud_gauges.tbl, but I don't see anything about it in the commit logs).
There isn't one. I've just added one though.
EDIT:
http://www.freespacefaq.com/Misc-Downloads/Builds/Wirefram_Targetbox_Test.7z
And here's where it goes in hud_gauges.tbl
$Max Escort Ships: 5
$Length Unit Multiplier: 1
$Wireframe Targetbox: 1
#Custom Gauges
0 = standard, 1 = wireframe, 2 = textured wireframe (whatever that is). There's not really much point in using 0 as that's what the game defaults to anyway.
If that works for you IP I'll rebuild the BtRL builds for you with it in.
-
Crap, now I remember: it wasn't supposed to go into hud_gauges.tbl but be species/ship specific instead. I was going to set it up so that it would be set on a per-species basis for default, but it could also be set on a per-ship basis. I think that the per-ship version was also going to prevent the user from changing to another view, basically forcing it to be just wireframe. There is probably a conversation or two around here which goes over that stuff.
But if the hud_gauges version is good enough for you then it's fine with me too. :)
-
The way it's currently set up you can either have it on or off and that's about it. If it ever went over to being per ship or per species it would still make sense to keep a version in hud_gauges as a master switch anyway.
I can't imagine the TBP team would want to go through every species they have adding it if they simply want all of them in wireframe.:)
-
i wouldnt mind being able to draw wire frames (individual mesh or full scene) from scripting for use in rtt and custom huds. then you could have that starfury wireframe display :D
-
I know this is an old thread.. just asking... does this still work? I just tested it.. the key-combo still works but this hud_gauges.tbl entry doesn't..
This would be very nice to have in 3.6.10 if it isn't too much to ask to be re-included..
-
Key combo works, but doesn't carry over from the mission you're on. Personally I'd like to see it as part of the HUD settings, just like the gauge color (HUD config) or support rearm time (Launcher flag) rather than mucking about with tables. Seriously, why would you ever want some ships to be solid and some wireframe, instead of a global setting?
-
Well it was in hud_gauges.tbl. That was a global setting for all ships, it was just a possibility to pre-set a different default. Right now you always have to switch to wireframe via key combo. With the table entry you could set wireframe as default. I didn't mean a per-ship setting :)
-
And I think Taylor _might_ have been talking about the ship/species you're flying, not what's being targeted. But I might be wrong.
-
Although only tangentially related, here is Mantis 1889 (http://scp.indiegames.us/mantis/view.php?id=1889) and the patch (http://scp.indiegames.us/mantis/file_download.php?file_id=1244&type=bug) I proposed for the wireframe target view (now deferred until after 3.6.10 is out and the code freeze lifted).
-
I'll have to see if I still have the changes I made to enable this to work If I don't it's probably easy to re-code them.
-
I'll have to see if I still have the changes I made to enable this to work If I don't it's probably easy to re-code them.
Saga would appreciate it :) A recent dicussion seems to have the result that we'd like to use wireframe by default :)
-
Probably could be put to use for a "targeting computer view" ala death star trench run.
-
Done. While I was in there I improved it over the previous version.
As before, here's where it goes in hud_gauges.tbl
$Max Escort Ships: 5
$Length Unit Multiplier: 1
$Wireframe Targetbox: 1
$Lock Wireframe Mode: YES
#Custom Gauges
0 = standard, 1 = wireframe, 2 = textured wireframe.
Lock Wireframe mode diables the SHIFT+ALT+Q keypress, locking the player into whatever mode you selected (or the default if you never added one).
EDIT : Here (http://www.freespacefaq.com/Misc-Downloads/Builds/Wireframe_Fixes.7z)'s the build
WARNING - This build is not multiplayer compatible with 3.6.10 RC1. It may be compatible with RC2 when that is released though.
-
Lock Wireframe mode diables the SHIFT+ALT+Q keypress, locking the player into whatever mode you selected (or the default if you never added one).
Thanks! I was going to ask about possibility to lock the setting next. ;)
-
I forgot to mention. The new builtin message is also in that build but it's been toned down to a 1 in 10 chance that a message will be sent for every kill.
-
Cool stuff karajorma, thanks =)