• Welcome to SC4 Devotion Forum Archives.
 

News:

The SC4 Devotion Forums are no longer active, but remain online in an archived, read-only "museum" state.  It is not possible for regular members to post or use the private messaging system, and no technical support will be provided for any issues pertaining to the forums in their current state.  Attachments (those that still work) are accessible without login.

The LEX has been replaced with SC4Evermore (SC4E), and SC4E maintains an active Discord server.  For traditional forums, we recommend Simtropolis.

Main Menu

all Model fsh files are in the sc4model file howver model appears red/untext....

Started by mightygoose, August 27, 2008, 04:26:28 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

mightygoose



i have followed the export procedure to the letter 3 times now and i still have the same problem...

if anyone can fix it, PM me, they are welcome to edit the model file because im at my wits end with bat4max... 11 months and only two successful exports... both drafts...

Edit: fix to see the pic ~wouanagaine~
NAM + CAM + RAM + SAM, that's how I roll....

wouanagaine

This may happen in Reader, did you check in game as the code between Reader and SC4 is different in regard to texture handling

And stupid question but did you have all the up to date bat scripts ?

New Horizons Productions
Berethor ♦ beskhu3epnm ♦ blade2k5 ♦ dmscopio ♦ dedgren ♦ emilin ♦ Ennedi ♦ Heblem ♦ jplumbley
M4346 ♦ moganite ♦ Papab2000 ♦ Shadow Assassin ♦ Tarkus ♦ wouanagaine
Divide wouanagaine by zero and you will in fact get one...one bad-ass that is - Alek King of SC4

callagrafx

The normal cause for this is the texture ID being screwed.  Export the LODs again, import into a clean GMAX file and then save with a new name.  Export the LODs from BAT to get the new IID.  Re-open Max to a blank scene and merge the old scene into this new one. Save this file.  Set up the render engine and export again.
The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it

mightygoose

Wou, i have the latest version available as far as i know, i dont think chris adams has released his uograded version yet,

lee, i'll try that when i get back from work, however i have made a fresh set of LODs each time ive rendered.... although i havent tried merging the scene into a fresh one.

will get back to you later
NAM + CAM + RAM + SAM, that's how I roll....

Diggis

OK, I took a look.  Firstly, you need to visit the Maxis site and get the BAT script fix.  GMAX is using sequential Instance IDs not Group ID's.  It looks like you have previously rendered this with a different model file.  MAX tends to hold the IID's of the first render, meaning where you had a F in your model IID, BAT put a C. Changing the C to an F for all the FSH file fixed it.

I would get the update and rerender the LODs. The merge the 3DS model into a new scene and rerender.  Should work fine.  And hopefully Chris's new scripts will fix this issue in the future.

mightygoose

hahaha i got it, the last thing i rendered was a transit model so i have the alternative building mill script in there...
NAM + CAM + RAM + SAM, that's how I roll....


mightygoose

NAM + CAM + RAM + SAM, that's how I roll....

Chrisadams3997

QuoteThis may happen in Reader

hehe, actually... the reader will show it as just fine, until you get in game and find out it's not ::).  But the Pim-X on the other hand catches it :thumbsup:, as you see here.

It's actually very distinct from the problem the Maxis 'model names' script update fixes, as that fixed fsh texture IID conflicts with Maxis textures.  But as Cal and Shaun pointed out, there's an error in Max4Bat's scripts where it'll hold over IID's or some such.  I know the general vicinity of code that causes that particular bug, but it's a lot like Shaun's description of your LOD, bloody complex.  fixing it there could potentially be a  :angrymore: kinda thing.

But I've found a more roundabout(no pun intended, I swear $%Grinno$%) fix that seems to work so far, so hopefully it'll soon be a thing of the past.  In the mean time, Cal's fix should do the trick.

Diggis

Quote from: mightygoose on August 28, 2008, 07:30:01 AM
It wont fit in an avenue roundabout otherwise.....

K, I seem to be missing something here, but I don't see how the LOD will effect the roundabout.  The LOD shouldn't hide anything as long as part of the model isn't in the way.  Seeing as your model is pretty solid it would only hide the bits it's supposed to hide.

Chrisadams3997

Does part of it go underground?  That'd be the only reason in the case of this model (best as I can see) that would require a complex LOD.  Otherwise, like Diggis said, the alpha will take care of it.

mightygoose

yeah part of the model is underground... sorry i should have made that clear...
NAM + CAM + RAM + SAM, that's how I roll....

Diggis

Soory, I still don't see it.  I've just taken a look at the model file, and can see nothing that would hide anything should you use a square LOD.  The underground portion of your model isn't enough to warrant it.

mightygoose

NAM + CAM + RAM + SAM, that's how I roll....

Diggis

Ahh, got it now.  It's the concrete down the side that is causing the issues?  Trick to get round that is to stop the outside of the concrete at Z=0 and then for this inside of the area use 1 sided textures so that they don't show up when you render them.  Might work, although might get the floor showing up, but may be worth a try.

callagrafx

When I rendered Glenni's roundabouts, and modelled the CAM statue, I used a cylindrical LOD with no render issues...not sure why they're such a problem in this case
The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it

Diggis

Oh, the issue wasn't the LODs at all, I just made the comment that they were high poly LODs.  The issue was the model names script.

mightygoose

NAM + CAM + RAM + SAM, that's how I roll....