BATTLEZONE COMMUNITY FORUMS

Battlezone I & II Download, Gaming & Development
It is currently May 28th, 2017, 11:55 pm

All times are UTC - 6 hours




Post new topic Reply to topic  [ 22 posts ]  Go to page Previous  1, 2
Author Message
PostPosted: November 4th, 2016, 4:58 am 
User avatar
Moderator
Offline

Joined: November 28th, 2010, 4:03 am
Posts: 1965
Location: Stafford, UK
Just send him the XSI.

_________________
Image
The Battlezone Wiki needs your help!


Top
 Profile  
 
PostPosted: November 5th, 2016, 1:07 am 
User avatar
Moderator
Offline

Joined: May 26th, 2009, 1:51 pm
Posts: 806
Ded10c wrote:
Just send him the XSI.


As far as I'm concerned the issue is resolved to my satisfaction bro. :-bd

_________________
BZII Modeling tutorials for model making igits like you?


Top
 Profile  
 
PostPosted: November 5th, 2016, 6:06 pm 
User avatar
Moderator
Offline

Joined: March 13th, 2005, 3:54 pm
Posts: 572
Location: dallas tx
It's a bad practice to "fix" something, by abandoning it and doing something different. You shouldn't just give up on it. :)

Also I am genuinely curious about what your exporter is doing wrong to the XSI.

_________________
Image
*****General BlackDragon*****


Top
 Profile  
 
PostPosted: November 6th, 2016, 1:16 am 
User avatar
Moderator
Offline

Joined: May 26th, 2009, 1:51 pm
Posts: 806
General BlackDragon wrote:
It's a bad practice to "fix" something, by abandoning it and doing something different. You shouldn't just give up on it. :)

Also I am genuinely curious about what your exporter is doing wrong to the XSI.


I have no idea, but Truespace's x exporter is screwing up the terrain_h part. Tell you what; when I have time I'll upload the terrain_h model part on my modeling forum so you amuse yourself GBD. Personally, I think it's a waste of both our' time, but I guess I'll let you decide that for your self. ~x(

_________________
BZII Modeling tutorials for model making igits like you?


Top
 Profile  
 
PostPosted: November 8th, 2016, 4:35 pm 
User avatar
Moderator
Offline

Joined: March 13th, 2005, 3:54 pm
Posts: 572
Location: dallas tx
Found and fixed in about 5 seconds. As per my reply there:

As I thought, you just need to fix the name in notepad.

Open the .x or .xsi in notepad.

Change:
Code:
Frame terrain__h__-0 {
     FrameTransformMatrix {
  1.000000,0.000000,0.000000,0.000000,
  0.000000,1.000000,0.000000,0.000000,
  0.000000,0.000000,1.000000,0.000000,
  0.000000,0.000000,0.000000,1.000000;;
   }
  Mesh terrain__h__Mesh {


to:
Code:
Frame terrain__h {
     FrameTransformMatrix {
  1.000000,0.000000,0.000000,0.000000,
  0.000000,1.000000,0.000000,0.000000,
  0.000000,0.000000,1.000000,0.000000,
  0.000000,0.000000,0.000000,1.000000;;
   }
  Mesh terrain__h {
     4;


It may be best to remove any ending "__-0" and "__Mesh" from all pieces. Or bug someone to fix their exporter.

_________________
Image
*****General BlackDragon*****


Top
 Profile  
 
PostPosted: November 8th, 2016, 7:17 pm 
User avatar
Moderator
Offline

Joined: May 26th, 2009, 1:51 pm
Posts: 806
General BlackDragon wrote:
Found and fixed in about 5 seconds. As per my reply there:

As I thought, you just need to fix the name in notepad.

Open the .x or .xsi in notepad.

Change:
Code:
Frame terrain__h__-0 {
     FrameTransformMatrix {
  1.000000,0.000000,0.000000,0.000000,
  0.000000,1.000000,0.000000,0.000000,
  0.000000,0.000000,1.000000,0.000000,
  0.000000,0.000000,0.000000,1.000000;;
   }
  Mesh terrain__h__Mesh {


to:
Code:
Frame terrain__h {
     FrameTransformMatrix {
  1.000000,0.000000,0.000000,0.000000,
  0.000000,1.000000,0.000000,0.000000,
  0.000000,0.000000,1.000000,0.000000,
  0.000000,0.000000,0.000000,1.000000;;
   }
  Mesh terrain__h {
     4;


It may be best to remove any ending "__-0" and "__Mesh" from all pieces. Or bug someone to fix their exporter.


Interesting, sounds easy enough to fix, but it sounds like more work then it may be worth especially if I have to reedit the file every time I make changes; which I do quite frequently.
No such luck of getting the exporter redone as Truespace is pretty much obsolete now, although, there is another X exporter that doesn't require me adding double spaces. Perhaps for building types I could try using it instead of the default X exporter. Thx, GBD. Edgrr. :-bd

FYI: 3d Exploration, is also part of the problem as it actually writes out the XSI file itself; maybe that's why it isn't recommended by some BZ2 model makers. I've had good results on most of my models including those with animation in them using 3d Exploration.

PS: I've pretty much burned out on BZ2, but I still pittle around a bit making models and props with Truespace as it fits my style perfectly and is easy enough to use for BZ2 modeling. Edgrr.

_________________
BZII Modeling tutorials for model making igits like you?


Top
 Profile  
 
PostPosted: November 9th, 2016, 10:27 am 
User avatar
Moderator
Offline

Joined: November 28th, 2010, 4:03 am
Posts: 1965
Location: Stafford, UK
3Dex is recommended for BZ2 model makers - quite highly, in fact. It's one of the only pieces of software from roughly the same period (and that thus supports the same version of .XSI) that is both still around and still functional. A full copy of DeepExploration - a companion suite - is something several of us have been trying to track down for quite some time, and if it showed up would be about as valuable as a period copy of Softimage|XSI.

_________________
Image
The Battlezone Wiki needs your help!


Top
 Profile  
 
PostPosted: November 9th, 2016, 4:43 pm 
User avatar
Moderator
Offline

Joined: May 26th, 2009, 1:51 pm
Posts: 806
Ded10c wrote:
3Dex is recommended for BZ2 model makers - quite highly, in fact. It's one of the only pieces of software from roughly the same period (and that thus supports the same version of .XSI) that is both still around and still functional. A full copy of DeepExploration - a companion suite - is something several of us have been trying to track down for quite some time, and if it showed up would be about as valuable as a period copy of Softimage|XSI.


Actually, as I recall someone posted that 3DEX had some issues with it conforming to the specific XSI format that BZ2 uses. I've been using it for years without issue, but apparently it has problems with how it writes out the XSI file; apparently with part names like terrain__h, collision__hc, etc.

The terrain__h just lines the model up in the map editor itself. It apparently isn't required to make the model fully functional, i.e., logging on to the terminal or enabling collisions; they work just fine w/o it bro.

I made some I76 building props w/o it and collisions work just fine. BZ2 is a bit of hack to begin with. If you peeps haven't figured it out by now then consider yourself informed. =))

_________________
BZII Modeling tutorials for model making igits like you?


Top
 Profile  
 
PostPosted: November 9th, 2016, 5:53 pm 
User avatar
Moderator
Offline

Joined: March 13th, 2005, 3:54 pm
Posts: 572
Location: dallas tx
The name was incorrect in the .x format. Which means truespace is the one that incorrectly named it on export. Check the full piece names in Truespace?

3DE doesn't mutilate names, it may however cutoff names.

terrain__h is only needed if you want to replace the terrain, which is required if you want collision to go under ground (i.e. ISDF Comm Bunker, Scion Recycler, Scion Gun Spire, Tunnel Entrance) Otherwise any collision under ground is inaccessible because you can't phase through terrain.

_________________
Image
*****General BlackDragon*****


Top
 Profile  
 
PostPosted: November 10th, 2016, 9:26 am 
User avatar
Moderator
Offline

Joined: May 26th, 2009, 1:51 pm
Posts: 806
General BlackDragon wrote:
The name was incorrect in the .x format. Which means truespace is the one that incorrectly named it on export. Check the full piece names in Truespace?

3DE doesn't mutilate names, it may however cutoff names.

terrain__h is only needed if you want to replace the terrain, which is required if you want collision to go under ground (i.e. ISDF Comm Bunker, Scion Recycler, Scion Gun Spire, Tunnel Entrance) Otherwise any collision under ground is inaccessible because you can't phase through terrain.


Your telling me again what I originally told you GBD that the X exporter was the problem to begin with. I tried the other X exporter and it doesn't work either for the terrain__h part. If 3DEX cuts off the part name then that pretty much is mutilation wouldn't ya think?

That said, you also identified what I need to do to fix the problem. As I said the issue has been resolved to my satisfaction. ^#(^

_________________
BZII Modeling tutorials for model making igits like you?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 22 posts ]  Go to page Previous  1, 2

All times are UTC - 6 hours


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  


PLEASE SUPPORT US BY MAKING A DONATION TO BZ2MAPS.US!

ALL DONATIONS WILL GO DIRECTLY TOWARD HOSTING AND SUPPORT COSTS OF BZ2MAPS.US ~ THANK YOU!

Powered by phpBB® Forum Software © phpBB Group
Copyright © 2011 BZ2MAPS.US