Author Topic: Truespace 1 & 2:solution to naming trouble.  (Read 1619 times)

0 Members and 1 Guest are viewing this topic.

Offline DTP

  • ImPortant Coder
  • 28
    • http://www.c4-group.dk
Truespace 1 & 2:solution to naming trouble.
I finally figured out how to bypass the problem found in Truespace1 and 2 in respect of the name trouble I have been having.

The problem was that when you named an object or group “Detail 1”, it got renamed to “detail,1” and “turret01” to “turret,1”.

This was of course not something the TO POF Converters could understand.

3DE export was a fail cause it did not export hierarchy information. Instead it linked all previous objects to the first object as Childs, meaning I had make new groups in TS1 and 2,

But I still need 3DE to export into COB since TS 1 & 2 cannot understand the 3ds UV mapping of today.:doh:

So I sort of hacked it into the cob file. Here is what u do.
I named my LOD group and Turrets “detailaa”, and “turretoa” and “turretob”

What I did was that I opened the COB file in an Text editor such as Ultra edit, Searched for “Detailaa” and overwrote “aa” with “ 1”. Did the same thing with the turrets only I replaced “oa” with 01 and “ob” with “02”. You can even reload you model into Truespace1 & 2. However, if your object original was named detail,1, before you “hacked” the cob file, then I found that TS1 & 2 will not reload the model. So make sure your names do not contain commas, just in case that it interfers with the converting.

This sort of hacking is of course something you must do when you model is all finished shiny and ready to be exported. As it is a one way deal. If you did not link it correctly before you started "hacking" you will have to "hack" it all over again.

I think Wordpad can do the job to, but I do not know that.

Well hopes this help all you Truespace 1 and 2 users.

Note I already once before, 7 days ago thought of this sort of way to deal with the problem, but for some reason I discarded it.
VBB member; reg aug 1999; total posts 600.
War is a lion, on whos back you fall, never to get up.
Think big. Invade Space.

 

Offline CP5670

  • Dr. Evil
  • Global Moderator
  • 212
Truespace 1 & 2:solution to naming trouble.
Cool, that works.:) When all else fails, use brute force on the file!:D I actually used to do this for texturing ships (using the same editor, lol) back in the old days when PCS/MV/FSMM2 did not exist, but it looks like it works for other things too.
« Last Edit: February 28, 2002, 11:43:38 pm by 296 »

 
Truespace 1 & 2:solution to naming trouble.
Hmmm, do you really need hex editing these days? The only thing where ",1"-stuff interfered was in the old days with cob2fs2 along with lods. It didn't understand what "detail,1" meant, it should've been "detail1". I used a similar method back then, but now we've got PCS that makes all objects that have "detail" in their name to be lods. Of course if you don't use PCS it's useful....but why wouldn't you? It's superior in every way.

 

Offline HotSnoJ

  • Knossos Online!
  • 29
    • http://josherickson.org
Help can you guys (gals) tell me what all the detail stuff names are (ie the ship detail level names and other sub-objects)?
« Last Edit: March 01, 2002, 04:03:38 am by 516 »
I have big plans, now if only I could see them through.

LiberCapacitas duo quiasemper
------------------------------
Nav buoy - They mark things

 

Offline aldo_14

  • Gunnery Control
  • 213
Truespace 1 & 2:solution to naming trouble.
Quote
Originally posted by Eternal One
Hmmm, do you really need hex editing these days? The only thing where ",1"-stuff interfered was in the old days with cob2fs2 along with lods. It didn't understand what "detail,1" meant, it should've been "detail1". I used a similar method back then, but now we've got PCS that makes all objects that have "detail" in their name to be lods. Of course if you don't use PCS it's useful....but why wouldn't you? It's superior in every way.


Not really, actually.... the latest build seems to autosmooths every model, so I still have to use cob2fs2 for 'blocky' models.

 
Truespace 1 & 2:solution to naming trouble.
Quote
Originally posted by aldo_14


Not really, actually.... the latest build seems to autosmooths every model, so I still have to use cob2fs2 for 'blocky' models.


The latest one has smoothing controls. You make the polygon faceted or smooth from ts shading controls, and PCS outputs it as faceted. If you make the polygon shading to be auto-faceted, PCS outputs the polygon as smoothed. I don't know why Kazan hasn't properly documented this, he's probably still on building the thing or something.

 

Offline aldo_14

  • Gunnery Control
  • 213
Truespace 1 & 2:solution to naming trouble.
Quote
Originally posted by Eternal One


The latest one has smoothing controls. You make the polygon faceted or smooth from ts shading controls, and PCS outputs it as faceted. If you make the polygon shading to be auto-faceted, PCS outputs the polygon as smoothed. I don't know why Kazan hasn't properly documented this, he's probably still on building the thing or something.


Hmm... i'll check again....  could be that i DL-ed an older version somehow.

  
Truespace 1 & 2:solution to naming trouble.
actually as an update on this issue pcs doesnt seem to conform to these rules for the subobjects (only the main body of the model) et1 informs me you sometimes have to reapply the uv ...for some unknown reason if your "updating" a model.  from what ive seen pcs messes up the smoothing/faceted on all the sub objects still, kazan still thinks im talking out of my ass...anyone remember him vigorusly denying smoothing was possible ? ;) so when he calms down and realising this is actually true he might get around to correcting the issue
The Babylon Project 2D Art / Texturing / Model Setup / Experimentation and Implementation

NEWBIE'S GUIDE TO THE VBB:

Enable Beam-free-all.