Jump to content
Sign in to follow this  
rhumbaflappy

Somemore LWM Questions . . .

Recommended Posts

Hi all. I have pretty much figured out LWM for what I am trying to do, but I am stuck on one thing. I have made a poly of new trees, and they show up very nicely. The problem I am having now is that when you go to winter season, the ground around the trees turns to snow, but the new tree poly doesn't. Is there anything I can do to the ASM file before feeding it to the BGLC to make the new groundwork turn to snow? Here is the VTP for the forest if it helps. Thanks for any assistance. :)Don; Eagle1 By: Moser; ; FS Coordinates: Lat: 61 31.56 Long: -145 57.01; VTP Method2 Polygon; The next two files MUST be included within the same directory as; BGLC.exe when this file is assembled (compiled).;include TDFHeaders.incinclude TDFMacros.inc;;----> Begin Header Section <---- BGLHeader 62, 60, -144, -146, TerrainHeaderStart, VTPHeader;VTPHeader label word VTPFileHeader 256, VTPIndexStart, TextureStart, VTPEnd;----> End Header Section <----;;----> Start File Data <----VTPStart label word;;----> Begin Cell 72, 80 and Area 20, 31 Data Point Information <----datamark_v0 label word; VTPDataArea 1, 1, 0, 0 VTPLayer 30, 0 VTPNumTexturesInLayer 1, 0 VTPTextureId 4, 0 VTPPolyCount 1, 0; VTPPolyMethod2 21, 0, 0;VTPPointXY2 9309, 12058VTPPointXY2 9324, 12062VTPPointXY2 9342, 12071VTPPointXY2 9356, 12069VTPPointXY2 9365, 12061VTPPointXY2 9386, 12089VTPPointXY2 9380, 12114VTPPointXY2 9361, 12123VTPPointXY2 9348, 12143VTPPointXY2 9336, 12154VTPPointXY2 9324, 12164VTPPointXY2 9316, 12165VTPPointXY2 9317, 12155VTPPointXY2 9328, 12147VTPPointXY2 9327, 12129VTPPointXY2 9316, 12127VTPPointXY2 9313, 12110VTPPointXY2 9320, 12093VTPPointXY2 9312, 12081VTPPointXY2 9309, 12069VTPPointXY2 9309, 12058;datamark_v1 label word;----> End Cell 72, 80 and Area 20, 31 Data Point Information <----;;----> Begin Cell_72_80's defination data information 80;VTPIndexStart label word VTPIndexHeader 1, VTPIndexData, VTPStartVTPIndexData label word VTPIndexEntry Cellv_72_80, VTPStart, datamark_v0, datamark_v1;----> End Cell_72_80's defination data information <----;;----> Begin Texture Information <----TextureStart label word VTPTextureListHeader 5, TextureIndexStart, TextureDataStart, TextureDataEnd;TextureIndexStart label word VTPTextureListEntry TextureDataStart, texturemark_0, texturemark_1 VTPTextureListEntry TextureDataStart, texturemark_1, texturemark_2 VTPTextureListEntry TextureDataStart, texturemark_2, texturemark_3 VTPTextureListEntry TextureDataStart, texturemark_3, texturemark_4 VTPTextureListEntry TextureDataStart, texturemark_4, texturemark_5;TextureDataStart label wordtexturemark_0 label word VTPTextureName "22" ;Cool Conifer Forest VTPTextureType 1, 0, 0, 4texturemark_1 label word VTPTextureName "22" ;Cool Conifer Forest VTPTextureType 1, 0, 0, 4texturemark_2 label word VTPTextureName "22" ;Cool Conifer Forest VTPTextureType 1, 0, 0, 4texturemark_3 label word VTPTextureName "22" ;Cool Conifer Forest VTPTextureType 1, 0, 0, 4texturemark_4 label word VTPTextureName "22" ;Cool Conifer Forest VTPTextureType 1, 0, 0, 4texturemark_5 label wordTextureDataEnd label word;----> End Texture Information <----;;----> The next line below ENDS this file <----VTPEnd label word

Share this post


Link to post
Share on other sites

Hi Don.I just had a post about a technique I borrowed from Holger, that might work for you:TextureDataStart label wordtexturemark_0 label wordVTPTextureName "22" ;Cool Conifer ForestVTPTextureType 1, 0, 0, 4texturemark_1 label wordVTPTextureName "22" ;Cool Conifer ForestVTPTextureType 1, 0, 0, 4texturemark_2 label wordVTPTextureName "22" ;Cool Conifer ForestVTPTextureType 1, 0, 0, 4texturemark_3 label wordVTPTextureName "22" ;Cool Conifer ForestVTPTextureType 1, 0, 0, 4texturemark_4 label wordVTPTextureName "253" ;Cool Conifer ForestVTPTextureType 1, 0, 0, 4texturemark_5 label wordTextureDataEnd label wordThis changes your texture to non-seasonal CUSTOM. Your VTP2 poly lies within a single LOD13 Area... so it has one CUSTOM name. You can place CUSTOM autogen without placing a texture, as Holger found.So if you make the above change, then add 000302100032322an.agn to the SceneryWorldtexture folder, with the default autogen. The autogen trees will show over the existing landclass texture. I'll attach a zip file of the autogen... it could be renamed for other CUSTOM LOD13 areas needing trees, then activated by VTP2 polygons.Tcalc2004 gave me the CUSTOM name... the names can be found in Ground2K4 as well. I made the AGN file with Annotator.http://forums.avsim.net/user_files/62574.jpgDick

Share this post


Link to post
Share on other sites

Thanks Dick, I appreciate the help. It used to be so much easier! LOL! Don

Share this post


Link to post
Share on other sites

I hear ya, Don!The only other solutions would be to alter the default textures that make up "22", or to use Gerrish's trees. Gerrish's trees won't hug the mesh like the autogen... so the use of CUSTOM without providing the texture might be the best solution. The worst of that is the odd long names, and the idea that a large area might need 100's of tiny AGN files!For small areas this is a good trick, for larger areas landclass is the way to go.I wouldn't worry about placing the autogen into "SceneryWorldtexture" as that is where autogen belong, unless part of a photoreal scenery. Unused AGN files shouldn't hurt anything.Dick

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  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...