Jump to content

Recommended Posts

Posted

Hi!

 

I'm playing with hi-poly ground objects replacements lately. The problem is obvious high CPU/GPU usage:

 

 

 

To solve it I created three levels of detail for ranges of 7000, 500 and 100 meters. But the problem stated in topic's title is as follow -only the closest LOD shows up.

 

Here's example from new shelterB.ini :

 

[LOD001]

Filename=ShelterB.lod

Distance=100

 

[LOD002]

Filename=ShelterB_med.lod

Distance=500

 

[LOD003]

Filename=ShelterB_low.lod

Distance=6000

 

 

[shadow]

CastShadow=FALSE

ShadowLOD=

ShadowType=0

ShadowCastDist=0

MaxVisibleDistance=0

 

ONLY the [LOD001] shows up at the given 100 meters range. Is it that the ground objects don't support lods or am I messing things up? Shadow works, but thrown away as most people dont use it.

 

Have been digging through Knowledge Base with no luck on the matter.

 

Any ideas?

Posted

Yeah, but mine are those that are placed in terrain folder... In given terrain _TYPES.INI these have variable "use ground object=FALSE" -that means they are not ground objects in the sense sim threats them? Been trying make them GO with no luck.

Posted

Do they need to use a seperate ini (sorta like drop tanks for weapons pak?)

 

Even though listed in the types, perhaps having a seperate ini would be worth experimenting?

 

Wrench

kevin stein

Posted (edited)

Yes, they do have separate ini. I tried placing them in corresponding folders in Ground Objects foler (ex. Hangar2, ShelterA etc.) and set them in "battle of britain_types.ini" to

 

use ground object=TRUE

 

But that gives nothing. Even the nearest lod is gone. Here's all for ShelterB, to be used as GO:

 

[GroundObjectData]

ObjectFullName=Aircraft Shelter

ObjectDataFile=SHELTERB_DATA.ini

 

[LOD001]

Filename=ShelterB.lod

Distance=200

 

[LOD002]

Filename=ShelterB_med.lod

Distance=1000

 

[LOD003]

Filename=ShelterB_low.lod

Distance=7000

 

[shadow]

CastShadow=FALSE

ShadowLOD=

ShadowType=0

ShadowCastDist=0

MaxVisibleDistance=0

 

and ShelterB_Data.ini:

 

[MissionData]

NationName=RAF

ServiceStartYear=1900

ServiceEndYear=1950

GroundObjectRole=HANGAR -matches TargetType= entry in _types.ini, also tried settings static_aaa and EW_RADAR

Availability=COMMON

Exported=TRUE

ExportStartYear=1932

ExportAvailability=COMMON

 

[GroundObjectData]

DamagedModel=

DestroyedModel=SHELTERB_destroyed.LOD

DestroyedEffect=VehicleFireEffect

Edited by CA_Stary
Posted
perhaps its a hierachy prob.... GOs can use sub-lods without prob... most stock GOs do.

CA_Stary, did you check the heirarchy like MJ suggested? Maybe you could post the OUT files from ShelterB.lod and ShelterB_med.lod just to verify that.

Posted (edited)

That hangar looks fantastic!! :good:

 

I think that perhaps your naming convention is incorrect... Perhaps ***_001.LOD, ***_002.LOD etc... might be worth looking at other files to see examples....

 

ML

Edited by Major Lee
Posted (edited)

OK, changed the naming convention as ML suggested, with no positive effect. Then it must be my lower LOD models related error, as stock Thirdwire terrain objects have lods -any airfield for example.

 

Anyway thanks again for all the help

 

EDIT:

 

PROBLEM SOLVED, LODS ARE WORKING!

 

I changed the LOD2 and LOD3 to simple cubes, and they do work -simply my mesh problems as I wrote.

Edited by CA_Stary

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

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..