Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: diamondgeezer on February 21, 2003, 10:53:17 pm
-
This may well have been thunk of already, but whatever.
Nameplates! Big ships, and probably just Terrans ones such as the Deimos, Hecate and Orion (natch), could have their object name appear as a nameplate. I'd guess the squadron badge code could be pinched, and pcxs of the various Bank Gothic charatcers would be displayed in a certain area on the model, spelling out its name. Ideally, you'd tick a box in FRED if you want the name displyed, thus a ship would be flagged if the model could display a name, causing said check box to appear :nod:
-
already added to FRED...in the next version you can change individual textures on the ships...
-
Excellent :drevil:
-
Originally posted by Analazon
already added to FRED
In what way?
This would REALLY help me!
And how do you specify nameplate locations?
-
Originally posted by Killfrenzy
In what way?
This would REALLY help me!
And how do you specify nameplate locations?
I don't have anything to do with the code, but the original idea that I have been working from in my modeling is that there is a specific texture that is replaced for custom nameplates. The Orion (Bastion and Galatea anyway) already support this, as does the Nike corvette (custom) and my Hyperion cruiser. For default, there would be a copy of the base hull texture with a different name applied in a specific section of the ship. Download the Hyperion from my sig and look at textures in Modview, that should give you an idea of how to impliment it in models.
-
Voila...
http://www.hard-light.net/forums/index.php/topic,12764.0.html
-
Will it be in 3.5?
-
:nod:
Although, unfortunately, there's no FRED way to put the texture replacement stuff in. You'll have to add it once you finish FREDding the mission. I'm not sure of the best way to implement it.
-
Er... okay, I appreciate I'm pushing a bit here, but what I was really hoping for was something like this: FS2 has access to various pcx files or characters on coloured backgrounds. So, each letter of the alpahabet would be drawn in white Bank Gothic on a blue background (for Orions) and that dark grey/green (for the Deimos), etc. Then, when the mission designer enters the object's name and ticks a box marked 'nameplate', the game will take the correct pcx files and string them together to make an instant nameplate. Each capital ship would have a base set of skins, with an area of the model defined for nameplates.
The advantage is that a new nameplate pcx wouldn't be needed for each ship. If I wanted a namplate with the current system I'd have to badger an artist each and every time, and they'd get fed up eventually.
Limiting factors include the size available for nameplates (thus the GTD Supercallafragalisticexpealladocious is out ofthe question), the range of characaters that have been produced (But then who'd want $, # and ! in their ship names?). And, of course, wheter it could actually be done or not.
Sorry if I'm being a bit cheeky with my request here, but hey - I like to keep you guys on your toes :)
-
Originally posted by diamondgeezer
GTD Supercallafragalisticexpealladocious
Surely you mean the:
GTD Supercalifragilisticexpialidocious? :D:D:D
:nervous:
*Hides*
-
I think that this would run in to the same problem as damage decals, a tremendous amount of work (for the programmer and processor) required for little productive gain. Plus, if you just defined an area there are al kinds of things to be taken into consideration for such a system, including scaling of the letters and centering, neither of which would be easy to impliment. If someone actually working on the code sees a way, then ignore me, but from a simplicity standpoint you're not looking at an easy add.
As for making custom nameplates, that's the one bit of texture work that I actually can do. It really isn't that hard, especially if you have a base example saved in a layered format so all you have to do is change the lettering. Microsoft PictureIt actually does a good job if you remember to reduce the image size when you are done.
-
Originally posted by diamondgeezer
...
Umm, this would be rather hard to implement. You'd have to create a new graphics texture on the fly by copying text onto a duplicate of an existing one.
Just take the texture you want and type words on it, using any paint program. Then use the texture replace method.
-
Well, I tried :)
:D
-
What DG is saying, though, wouldn't require any graphics tools at all. Even the lowliest Fredder could do it :p And you wouldn't need to keep a dozen almost-identical models floating around for each different ship (e.g., the Galatae and Bastion models in FS1)
The tricky part would be deciding where to put it on the ship, and telling the renderer about it. Actually rendering the text onto an existing map isn't too tough, and it could be done at model load time (part of the mission load process). The ship would then have a different skin, but it would only be in memory, and not need to be saved onto disk.
-
Penguin, read the thread I linked to. The most complicated Paint program you'll ever need with my method is Microsoft Paint, and you don't need any complicated modelling programs at all. All you need to do is put three little lines at the end of your mission file, and you're all set.
EDIT: Has anyone (besides DG) read the thread I linked to? :rolleyes: There's already a very simple source code feature that allows you to juggle textures on any ship you want. What diamondgeezer wants is text generation on the fly, while the mission is loading. This would be too much trouble to implement in the source code, but with only minimal effort you can edit an existing texture in any paint program and have basically the same effect.
-
I just read the thread you linked to :o You still need a paint program, but otherwise, I retract my original post.
Nice addition, Goober5000, I wasn't aware of it. Sorry, I'm still getting my toes back in the water here...
-
That's okay. It's weird rejoining a project when you've been out of the loop for a while. :)
This is just a helpful reminder to everyone to read carefully. ;)
-
We're all guilty of skimming :)
-
So, if I get you correctly, then I would be able to remove three of my four Orion tbl entries, and use FRED to change the nameplate texture on the side to which ever one I want. Right?
still half asleep, bad night
-
yes,
and if someone could merge fred back in I could probly add an interface
-
Yup. :)
Bobboau, what do you mean "merge FRED back in"? All you have to do is CVS the fred2_open module and you can write whatever code you need.
-
it doesn't compile
some weird lib is missing, nafxcwd.lib
have no idea were this is or were this is or what this is, but I am sure it is becase the two are totaly separate projects and as such the fred files are seporated from the code files, so I want fred to be included in the FSO project like 'code' is, thus I won't have go through all sorts of crap to get it compileing
-
You need the "code" project from fs2_open copied to the fred2_open directory. That probably will fix it.
-
isn't there a way to have them share the code project so I don't have to keep updateing
there is no nafxcwd.lib
-
That error IIRC is a project file configuration screwup. (The file listed is, I think, part of MFC.) Go into the project settings and change "Use MFC in a Shared DLL" to "Not Using MFC", hit OK, then go back in and change it back. That ought to fix it. (I originally had that problem myself.)
Edit: For more info on just what that file is, check out afx.h in the Microsoft include files. (It is part of MFC.)