[DaBrain]

There has been a great feature... and nobody, except for Omniscaper really seemed to use it.
Now a small bug got fixed and it became the most easiest feature to use ever!

What is "detail box"?

Detail boxes are an addition to the lod system. They are really useful for large ships where large areas lack detail, and you can't create more detail, cause the lod0 has a high polycount already.
It's also useful for small ships. For details that are only notice able on close-ups. Like cockpits or semi-complete interiors.

Detail boxes determine the visibilty of subobjects.

How can I set them up?

Setting up a detail box is a really simple. You can do this in 3ds MAX, in PCS and possibly truespace.

In MAX you add this to the user defined properties:
$detail_box: 1
$box_min: -1500,-1500,-1500
$box_max: 1500,1500,1500

(Those values determine the size of the virtual box. In meters.=

In PCS you can do the same. Just add this to the 'properties' in 'SubObjects'.

And you're done! (No, ... really!)


10 minute example:

This is a really crappy model ... and it's set up pretty crappy too.
I hope you still get the idea.

Each cube has 80k polygons(!)



Looks like they're part of the background, eh?


They are not.





Short clip: Download (12MB x264 codec)

[Vengence]

Sooo... when you get closer to the borg cubes (lol) they get greebled?

[DaBrain]

Yeah. I turned down the model quality slider in the options to make the effect more visible. (Which made plopping-up worse.)

The model options acutally have an effect on the detail box size. So low-end user can decide to see less details and get more fps.

In a properly done version, the bigger plates should appear first, and then the smaller details.

[taylor]

In MAX you add this to the user defined properties:
$detail_box: 1
$box_min: -1500,-1500,-1500
$box_max: 1500,1500,1500

A quick addition to this, the $detail_box option has two settings.  A value of "1" means that you have to be inside of the $box_min and $box_max to see the detail.  A value of "-1" means that you have to be outside of that box to see the detail.

I'm not the model guru, so I'm not totally sure all of the uses for this, but one application might be to have a very detailed subobject using this:

$detail_box: 1
$box_min: -1500,-1500,-1500
$box_max: 1500,1500,1500

and then a low detailed suboject using this:

$detail_box: -1
$box_min: -1500,-1500,-1500
$box_max: 1500,1500,1500

The subobjects would be positioned directly on top of each other, and so when you are inside of the specified box you will only set the detailed version, and when you are outside of the box you only see the lower detailed version.

This should allow for a much more intricate LODing of models rather than just dropping from LOD0 to LOD1 to LOD2.

[At]

I'm not the model guru, so I'm not totally sure all of the uses for this, but one application might be to have a very detailed subobject using this:

Maybe something like in FEAR, though more on a subobject level.  One of the Multiplayer models in FEAR has that gasmask cylinder thinger on the end of the helmet.  In LOD0 (The model drawn for the camera sitting inside it), though, the little cylinder is missing.  I'm not actually sure why you'd want to do that here, but who knows.

Still, detail boxes = yum.  I'll have to consider them in future meshes...

[Taristin]

I'm not the model guru, so I'm not totally sure all of the uses for this, but one application might be to have a very detailed subobject using this:

Maybe something like in FEAR, though more on a subobject level.  One of the Multiplayer models in FEAR has that gasmask cylinder thinger on the end of the helmet.  In LOD0 (The model drawn for the camera sitting inside it), though, the little cylinder is missing.  I'm not actually sure why you'd want to do that here, but who knows.

Still, detail boxes = yum.  I'll have to consider them in future meshes...

In this case it'd be that 1 would be a highly detailed hangar bay, and -1 would be a lesser detailed version. That way when inside, you see everything, but when you leave it, it cuts the detail.

[RavenTS]

Woah, nice thing such a detail box. Thinking of manned ships, where you can see people in it walk by the windows or explosions/fire behind the glass...   

[Gregster2k]

Detail boxes are really the only way to go IMO when it comes to TRULY detailing things.

[Scooby_Doo]

Do detail boxes count as subsystems?

[DaBrain]

No, but you probably could use them as subsystems.

[taylor]

And in truth, if the model design works with this, you could have a LOD0, debris, and just use detail boxes to fill in all the rest of the detail.  I'd be pretty interested in seeing what someone can do with something like that.  Technically speaking it should be possible to make a highly detailed model that way, using only LOD0, and have it perform as well as, or better than, a normally LODed model, all while being far more detailed.

Do detail boxes count as subsystems?

Nope.  They are just part of subobjects and don't count against anything, other than the little bit of extra time needed to calculate your position relative to the box.

[Flipside]

Hmmmm... I might well sticky this, we are getting a lot of tutorials these days though, and there are quite a lot of Stickies. I'm hoping to do a texturing tutorial to supplement some of Scooby's work soon as well....

Might be an idea for something like a read only Forum for tutorials if we get enough of them?

[Scooby_Doo]

A heads up Flipside, I'd like to another one one my newer texturing style.  The better looking gritier one.  I don't really care if no-one reads it, but it'll give me a reminder for myself when I forget something

[Bobboau]

detail boxes allow recursive detail LODing
this means that a child object of a detail boxed subobject won't be evaluated unless it's parent has passed, so detail that 'belongs' to an object should be made a child of that object.

detail boxes have nothin to do with subsystems in any way, they do not talk to each other, they do not write to each other, they look the other way when they walk past each other in the store, giveing an object that is a subsystem a detail box will not effect it's subsystem status, and makeing a detail boxed subobject a subsystem will not effect it's detail box status.

the box nature of this system has advantages over the radius based LOD system in that you can specify a regon of visability, so if you have detail that is only visable from one side of a ship, you can set up a box that is only on that side of the ship.

if you can avoid drawing two models all the time it would be better to do so, for instance, give a relitively low poly version of the main hull that has a very low detail hanger bay modeled into it, set this model to render when outside it's box, make another version that has a hole were the hanger should be, given a detail box (exactly the same dimentions as the first one) that you should only draw when inside it. in a seperate model (as a child) have a higher poly version of the hanger set it to have a smaller detail box set to only draw while outside the box, as a sibling to this make a highest poly version of the hanger that draws only when inside the box. and as children to the highest poly hanger you can add fighter models and cranes and all sorts of delicious greeble.

keep in mind that detail boxes are in the subobject's frame of reference, so any rotateing submodels will have rotateing detail boxes (this can be worked around by makeing them children of polyless  subobjects with a detail box).
and you can give any sort of animated subobjects (this includes turrets and rotateing subobjects) or groups thereof a detail box.

a shperical equivilant of the detail box, may be available at some point in the near future.

as you can see you can go into rediculus levels of detail with your detail management. have fun

[castor]

Wow! Sounds like a damn powerful feature this one
I know s**t about modding, but can't skip this without throwing a few 

[IPAndrews]

I would use this for Babylon 5 if it had LODs at all . I like the idea of these "Use the features!" threads though. I only discovered the "same turret cooldown" weapons flag yesterday and that's proven extremely useful.

[Flipside]

Agreed, there is a hell of a lot of features available to make Freespace look utterly incredible, in fact, they are coming so thick and fast that they either pass by un-noticed or people simply don't have the time to go back and include these features on their campaign models.

I'm wondering if some kind of central database of Tutorials as they are created would make the features easier to access for people who are just starting out with the modding thing, and make a useful reference point for the more experienced ones.

If I had the Webspace, I'd host them myself to be honest, but Pipex' main weakness is the lousy 50Meg I got given

[karajorma]

This sort of thing should be indexed (and also preferably copied) onto the wiki anyway

[Flipside]

Agreed. I've certainly come across Tutorials for modding other games that provide a 404 error because the user long since gave up modding themselves, and therefore have removed the files from their server. I suppose that's my main concern, to keep stuff somewhere where it'll still be available even if the author decides to leave the community or loses access to their server or whatever

[Scooby_Doo]

Agreed. I've certainly come across Tutorials for modding other games that provide a 404 error because the user long since gave up modding themselves, and therefore have removed the files from their server. I suppose that's my main concern, to keep stuff somewhere where it'll still be available even if the author decides to leave the community or loses access to their server or whatever

In total agreement