Jump to content
Sign in to follow this  
Badfrank

Problem with multiple Lod Object Placement to Terrain

Recommended Posts

Want to place some additional Objects directly on the Terrain.

Objects with more than one Lod seems here a littlebit problematic...

Cane someone give me here some tips please... :idea:

 

 

Here what i have done with the PT-76 (Renamed it in PT-76s)

 

Entry in PT-76s.ini

 

LOD001]

Filename=PT-76s.lod

Distance=100

 

[LOD002]

Filename=PT-76s_lod002.lod

Distance=250

 

[LOD003]

Filename=PT-76s_lod003.lod

Distance=500

 

[LOD004]

Filename=PT-76s_lod004.lod

Distance=8000

 

[shadow]

CastShadow=TRUE

ShadowCastDist=500

MaxVisibleDistance=500

 

 

Entry in Types.ini

 

[TargetType146]

Name=PT-76s

FullName=PT-76s

ModelName=PT-76s.lod

TargetType=APC

ActiveYear=0

TargetValue=0

UseGroundObject=TRUE

RepairRate=0.555

StartDetectChance=0

StartIdentifiedChance=0

IncreaseDetectChanceKey=0

MaxVisibleDist=8000.0

DestroyedEffect=MediumFire

SecondaryEffect=SmallRocketGroundExplosion

SecondaryChance=100

Edited by Badfrank

Share this post


Link to post
Share on other sites

First, the very first entry is truncated (missing a [ ).

 

Second, you haven't specified the particular issue you are having.

 

FC

Share this post


Link to post
Share on other sites

Okay.

 

First, under the ModelName= parameter in the Types.ini, just use the name of the primary ini ( PT-76s ). I don't think you need to specify the lod.

 

Second, within the PT-76s.ini, comment out the other entries, and start with the primary LOD file out to the max distance. In other words, instead of:

 

[LOD001]

Filename=PT-76s.lod

Distance=100

 

[LOD002]

Filename=PT-76s_lod002.lod

Distance=250

 

[LOD003]

Filename=PT-76s_lod003.lod

Distance=500

 

[LOD004]

Filename=PT-76s_lod004.lod

Distance=8000

 

You do this:

 

[LOD001]

Filename=PT-76s.lod

Distance=8000

//Distance=100

 

//[LOD002]

//Filename=PT-76s_lod002.lod

//Distance=250

 

//[LOD003]

//Filename=PT-76s_lod003.lod

//Distance=500

 

//[LOD004]

//Filename=PT-76s_lod004.lod

//Distance=8000

 

Check that LOD. If it works, then try:

 

[LOD001]

Filename=PT-76s_lod002.lod

Distance=8000

//Filename=PT-76s.lod

//Distance=100

 

//[LOD002]

//Filename=PT-76s_lod002.lod

//Distance=250

 

//[LOD003]

//Filename=PT-76s_lod003.lod

//Distance=500

 

//[LOD004]

//Filename=PT-76s_lod004.lod

//Distance=8000

 

Do this for each LOD. If each one shows up, then troubleshoot with 2 lods at a time. Remember, NONE of the LODs will show up at all, if the hierarchy is different between any of them...hierarchys if changed can only be changed from the 'tips' to the 'roots' of the tree.

 

FC

Share this post


Link to post
Share on other sites

For the definition in terrain_types.ini:

 

add this right after this line:

UseGroundObject=TRUE

GroundObjectType=PT-76s (The folder name of the object inside groundobjects)

 

You don't need the ModelName variable here. It reads that info from PT-76s.ini.

Edited by pureblue

Share this post


Link to post
Share on other sites

For the definition in terrain_types.ini:

 

add this right after this line:

UseGroundObject=TRUE

GroundObjectType=PT-76s (The folder name of the object inside groundobjects)

 

You don't need the ModelName variable here. It reads that info from PT-76s.ini.

 

I know that that is a Way.

But i want to place it directly to the Terrain and not as Groundobject.

Share this post


Link to post
Share on other sites

Well if you mean you want it to be a Terrain Object instead of a Ground Object (you can add both of these types directly to the terrain)

 

Have it as:

ModelName=PT-76s

UseGroundObject=FALSE

 

AND

 

Copy the LOD & Corresponding bmp textures to the terrain folder.

Also copy over your ini file from the first message.

 

IF you do it this way, it will just sit there and not fire at anything. It won't have the necessary info from _data.ini.

Edited by pureblue

Share this post


Link to post
Share on other sites

Yup, as PB outline above, you turn a GroundObject into a TerrainObject (this was one of the ways it was done pre-06 patch levels.

 

Be advised, however, of doing it that way -- having all those 'terrainobject vehicles' will dramatically increase loading times and may tend to decrease framerates. Using the "UseGroundObject=TRUE" line is the prefered method, as this will allow them to spawn and despawn as the player aircraft passes the 50km ring to/from them. (which is actually kinda cool to watch -- they just "pop" out out -or into- existence like Scotty beamed them down)

 

If you're running into trouble placing GOs, use that mission I posted in the KB's Terrain section, just edit as I've outlined. Puts you right over the selected target area, and makes things vERY easy to place locate

 

(I think that was the question in your PM that I totally forgot to reply to...sorry!!!!)

 

wrench

kevin stein

Share this post


Link to post
Share on other sites

Get all the Stuff to work.

 

The Problem where some wrong entrys in the Types.ini...

 

UseGroundObject=TRUE

 

 

Thanks Guys!

:drinks:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..