Hard Light Productions Forums

Modding, Mission Design, and Coding => The Modding Workshop => Topic started by: karajorma on September 14, 2003, 11:15:15 am

Title: Truespace bug/problem
Post by: karajorma on September 14, 2003, 11:15:15 am
They say a picture is worth a thousend words so here goes
(http://homepage.ntlworld.com/karajorma/freespace/Misc-Pics/Working-Missile.jpg)

For those that didn't recognise it that's a Rockeye missile. Notice the planes they've used for the fins? Saves a lot of polys doing it that way.

Anyway I'm trying to build a missile in TS. I made the missile body and then made a tail fins out of planes and then used a boolean to join the two together. What I got was this
(http://homepage.ntlworld.com/karajorma/freespace/Misc-Pics/Non-Working-Missile.jpg)

What did I do wrong/How do I get my tail fins to have two sides.
Title: Truespace bug/problem
Post by: StratComm on September 14, 2003, 01:13:49 pm
Ahh, the woes of Truespace.  Your best bet is to make it so that you have a small triangular fin (Small thickness at the bottom, point on top) and then to merge the vertices on the base so that the front and back polygons are reduced to a line.  Truespace calls this vertice welding I think, though in other programs that name has a much different function.  That *should* do the trick.
Title: Truespace bug/problem
Post by: KARMA on September 14, 2003, 01:29:00 pm
it's not truespace prob i think
ts automatically works with double side polys usually, if it doesn't it is probably because of
1 double side/single side option checked (if there is this option)
or
2 geo problem

first prob can be solved by flipping faces
second prob can be fixed by NOT using booleans
DON'T use booleans in this cases, just add verts/edges or use polydraw or connect manually  the verts of two separated objects (after you unify them with boolys but maintaining them separated)
Using booleans it is very possible that the verts are not connected (two non connected verts share the same position and seem one single vert), in this case sometime the internal render of TS goes crazy, and it only partially render the wrong polys
BTW fs2 only support one side faces, so you will need two polys mirrored to make those fins visible from any angle
Title: Truespace bug/problem
Post by: karajorma on September 14, 2003, 03:17:35 pm
Okay. I'll look into that. I had thought of doing the thin poly thing but the problem is that it adds more polys while a flat pane only has 1 (or two if you count both sides as different polys).

 I took a closer look at the Rockeye and it's got some really wierd geo. Edges that aren't connected to anything, points with nothing attached to them. Very weird.
Title: Truespace bug/problem
Post by: magatsu1 on September 14, 2003, 04:09:52 pm
'suppose you get away with  slightly dodgy models when doing missles (v.small, v.fast moving)
Title: Truespace bug/problem
Post by: karajorma on September 14, 2003, 04:12:24 pm
Yeah I know I can but I've made some bombs with the same fins and people will spot the error on a slow moving bomb more easily than on a missile.

Oh While I'm here does anyone have a map for thruster01 etc. I know I can simply just use another texture renamed but I was wondering if anyone had bothered to extract a file from the ani. It makes it easier to visualise what the missile will look like in-game if the texture is a static version of the in-game one.

Plus I keep accidently putting the thruster texture on backards and a proper texture would stop that happening :D
Title: Truespace bug/problem
Post by: WMCoolmon on September 14, 2003, 04:54:23 pm
(http://members.cox.net/~wmcoolmon/thruster01.gif)

Is this what you wanted? It wasn't that hard to get with ANIView...
Title: Truespace bug/problem
Post by: karajorma on September 14, 2003, 04:58:32 pm
Perfect. Thanks for that :) Never thought of just doing a screengrab :D
Title: Truespace bug/problem
Post by: Killfrenzy on September 14, 2003, 05:13:37 pm
Or at least, use aniview's image saving function! :D
Title: Truespace bug/problem
Post by: WMCoolmon on September 14, 2003, 05:19:02 pm
Quote
Originally posted by Killfrenzy
Or at least, use aniview's image saving function! :D


(http://members.cox.net/~wmcoolmon/howto.gif)
Title: Truespace bug/problem
Post by: karajorma on September 14, 2003, 05:51:59 pm
Doh! Need to look more closely at Aniview :D
Title: Truespace bug/problem
Post by: diamondgeezer on September 14, 2003, 11:20:29 pm
Come on kara, even I worked out how to do that. And I suck at this stuff :nod:
Title: Truespace bug/problem
Post by: karajorma on September 15, 2003, 03:41:31 am
I did wonder why no one had asked a similar question before :D

Momentary lapse in thought. Won't happen again :)

As for sucking at this stuff I'm no great modder either. I've just been at this for about 6 months to a year longer than you :D
Title: Truespace bug/problem
Post by: Killfrenzy on September 15, 2003, 07:10:02 am
So what CAN you do? :D:D
Title: Truespace bug/problem
Post by: karajorma on September 15, 2003, 09:36:20 am
In a word, FRED. :D
Title: Truespace bug/problem
Post by: Killfrenzy on September 15, 2003, 12:45:10 pm
Yeesh....
Title: Truespace bug/problem
Post by: magatsu1 on September 15, 2003, 12:47:37 pm
is "FRED" a proper word ? :D


quick moan: why the hell do Caligari make registering "your product" such a pain in the a**e ?
Title: Truespace bug/problem
Post by: magatsu1 on September 15, 2003, 03:44:36 pm
Quote
Originally posted by magatsu1
is "FRED" a proper word ? :D


quick moan: why the hell do Caligari make registering "your product" such a pain in the a**e ?


Ignore the above moan (I'm an Idiot) Sorry Caligari !!:sigh:
Title: Truespace bug/problem
Post by: diamondgeezer on September 16, 2003, 10:03:53 am
No no, Caligari do suck. A bit, at least.