Guys,Did anyone play around with the autogen transmition lines? I'm trying to use them without luck.Object is supposed to be vtp,1211 on layer 4Regards,Jay

Hi Jay,I've no problems placing them, though I use a higher layer (which shouldn't matter). The towers are ~600m (1800ft) apart and not always esay to see. Also, your autogen density slider has to be at least at Normal to see the power poles.Do you not see anything or does the clearcut beneath show up?Cheers, Holger

Holger,The clearcut does show but the poles don't show up. What layer and width do you use?Jay

Hi Jay,I'm using layer 20 and widths ranging from 40 to 80, depending on the size of the corridor in the real world.If the cuts show your VTP2 line the code itself is correct and it's only a matter of missing the autogen display. There was a tweak for improving frame rates that removes the vector-associated autogen and other items (factories, restaurants, etc.). Perhaps you've got that one active?Cheers, Holger

Holger,My default.xml and terrain.cfg are untouched. I'm gonna try your settings to see what happens.Regards,Jay

Holger,What software are you using to create the transmition lines? I'm using autoasm. I tried layer 20 and it didn't work.You can see the path but not the towershttp://forums.avsim.net/user_files/89656.jpgJay

Hi Jay,I'm using Ground2K4 but the software wouldn't make a difference.It looks to me as if your autogen density setting is pretty low; try setting it to maximum for a test and see whether the towers show up.Cheers, Holger

Holger,I put the autogen slider to the max...http://forums.avsim.net/user_files/89685.jpgI don't get it...Jay

Hi Jay, I haven't used this line type before so I tried it. I have even less success than you! Sometimes part of the lines show with a snow texture or the line doesn't show at all. I tried several different line widths and layer values. Here's a sample asm generated by AutoAsm. This small vertical line doesn't show up at all. The layer value is 10. Can anyone see what's wrong with it? For this feature to work does it need an updated version of bglc or Dick's include files? Best regards, Chris*********************************************include TDFHeaders.incinclude TDFMacros.incBGLHeader 17, 13, 47, 43, TerrainHeaderStart, VTPHeaderVTPHeader label wordVTPFileHeader 256, VTPIndexStart, TextureStart, VTPEndVTPStart label worddatamark_v0 label wordVTPDataArea 1, 1, 0, 0VTPLayer 10, 0VTPNumTexturesInLayer 1, 0VTPTextureId 0, 0VTPPolyCount 1, 0 VTPPolyMethod2 31, 1, 0VTPPolyMethod2Ex 35VTPWidePoint 11971, 1, 5664, 0VTPWidePointWidth 1VTPWidePoint 11972, 1, 5665, 0VTPWidePointWidth 50VTPWidePoint 11971, 1, 5680, 0VTPWidePointWidth 50VTPWidePoint 11971, 0, 5696, 0VTPWidePoint 11971, 0, 5713, 0VTPWidePoint 11971, 0, 5729, 0VTPWidePoint 11971, 0, 5745, 0VTPWidePoint 11971, 0, 5762, 0VTPWidePoint 11971, 0, 5778, 0VTPWidePoint 11971, 0, 5794, 0VTPWidePoint 11971, 0, 5810, 0VTPWidePoint 11971, 0, 5827, 0VTPWidePoint 11971, 0, 5843, 0VTPWidePoint 11971, 0, 5859, 0VTPWidePoint 11971, 0, 5877, 0VTPWidePoint 11971, 0, 5893, 0VTPWidePoint 11971, 0, 5909, 0VTPWidePoint 11971, 0, 5925, 0VTPWidePoint 11971, 0, 5942, 0VTPWidePoint 11971, 0, 5958, 0VTPWidePoint 11971, 0, 5974, 0VTPWidePoint 11971, 0, 5991, 0VTPWidePoint 11971, 0, 6007, 0VTPWidePoint 11971, 0, 6023, 0VTPWidePoint 11971, 0, 6039, 0VTPWidePoint 11971, 0, 6056, 0VTPWidePoint 11971, 0, 6072, 0VTPWidePoint 11971, 0, 6088, 0VTPWidePoint 11971, 0, 6105, 0VTPWidePoint 11971, 0, 6122, 0VTPWidePoint 11971, 0, 6138, 0VTPWidePoint 11971, 0, 6154, 0VTPWidePoint 11971, 0, 6171, 0VTPWidePoint 11971, 0, 6187, 0VTPWidePoint 11971, 0, 6203, 0VTPWidePoint 11971, 0, 6220, 0VTPWidePoint 11971, 0, 6236, 0VTPWidePoint 11971, 0, 6252, 0VTPWidePoint 11971, 0, 6268, 0VTPWidePoint 11971, 0, 6285, 0VTPWidePoint 11971, 0, 6301, 0VTPWidePoint 11971, 0, 6317, 0VTPWidePoint 11971, 0, 6334, 0VTPWidePoint 11971, 0, 6350, 0VTPWidePoint 11971, 0, 6366, 0VTPWidePoint 11971, 0, 6383, 0VTPWidePoint 11971, 0, 6400, 0VTPWidePoint 11971, 0, 6416, 0VTPWidePoint 11971, 0, 6432, 0VTPWidePoint 11971, 0, 6449, 0VTPWidePoint 11971, 0, 6465, 0VTPWidePoint 11971, 0, 6481, 0VTPWidePoint 11971, 0, 6498, 0VTPWidePoint 11971, 0, 6514, 0VTPWidePoint 11971, 0, 6530, 0VTPWidePoint 11971, 0, 6546, 0VTPWidePoint 11971, 0, 6563, 0VTPWidePoint 11971, 0, 6579, 0VTPWidePoint 11971, 0, 6595, 0VTPWidePoint 11971, 0, 6612, 0VTPWidePoint 11971, 0, 6628, 0VTPWidePoint 11971, 0, 6645, 0VTPWidePoint 11971, 0, 6661, 0VTPWidePoint 11971, 0, 6678, 0VTPWidePoint 11971, 0, 6693, 0VTPWidePoint 11971, 1, 6694, 0VTPWidePointWidth 0datamark_v1 label wordCellv_479_213 EQU VTPCellID 0, 479, 213VTPIndexStart label wordVTPIndexHeader 1, VTPIndexData, VTPStartVTPIndexData label wordVTPIndexEntry Cellv_479_213, VTPStart, datamark_v0, datamark_v1TextureStart label wordVTPTextureListHeader 1, TextureIndexStart, TextureDataStart, TextureDataEndTextureIndexStart label wordVTPTextureListEntry TextureDataStart, texturemark_0, texturemark_1TextureDataStart label wordtexturemark_0 label wordVTPTextureName "1211"VTPTextureType 2, 0, 0, 4texturemark_1 label wordTextureDataEnd label wordVTPEnd label word

Howdy Chris,The "VTPTextureType 2, 0, 0, 4" looks a bit odd. According to the terrain.cfg, "1211" should be set to "3, 4, 1, 1", as in:[Texture.1211] // utilityType=3Size=4ExcludeAutogen=1MaskClassMap=1VectorAutogen=0Textures=utilitymask.bmpRenderToTexture=0It's a shot in the dark but maybe try those values instead.Whether one sees the "cut" or not depends on the underlying landclass and also the presence of Joachim's CTD fix .bmp files.Cheers, Holger

>Howdy Chris,>>The "VTPTextureType 2, 0, 0, 4" looks a bit odd. According to>the terrain.cfg, "1211" should be set to "3, 4, 1, 1", as in:Hello Holger,I think that the second parameter refers to "no effect" and the third is allways 0. So may be VTPTextureType 3, 0, 0, 4 is better. Still, if you set "VTPTextureType 2, 0, 0, 4", I do not know if FS takes the type of texture as 2 or 3 (3 from the terrain.cfg).Regards, Luis

Hi all,Oops! I confused the Vector Texture Format from the terrain.cfg with the VTP2 Texture Type Format. Mea culpa - Luis is correct.The first value is the type of texture, which should be "3" for the utility corridors, according to the SDK, but "utilitymask.bmp" actually looks like Type 1 or 2 (four rows instead of eight).The second value assigns effect/no effect, as Luis states.The third value needs to be zero.The fourth gives the meters per pixel of the source texture, usually "4".However, none of this really pertains to the presence of autogen, which is determined in the terrain.cfg and the default autogen files. In fact, any of the power lines I draw with G2K4 show "VTPTextureType 0, 0, 0, 0" in the raw asm code yet the display works perfectly fine for me. BTW, my G2K4 directory contains BGLC.exe dated 6/4/02 and the inc files from 12/17/03 Cheers, Holger http://forums.avsim.net/user_files/89830.jpg

Hi all.Here's a decompilation from LWMViewer:

VTPTexStart	label word	VTPTextureListHeader	1,VTPTexListStart, VTPTexNameStart, VTPTexNameEndVTPTexListStart	label word	VTPTextureListEntry	VTPTexNameStart, VTPTexName0, VTPTexName1VTPTexNameStart	label wordVTPTexName0	label word	VTPTextureName	"1211"	VTPTextureType	2, 0, 0, 4VTPTexName1	label wordVTPTexNameEnd	label wordVTPDataStart	label word; Start of cell 192 x 127 dataCELLSTART_000000	label wordCellID_000000	EQU VTPCellID 0, 192, 127	VTPDataArea	1, _Method2_, 0, 31	VTPLayer	4, 0	VTPNumTexturesInLayer	1, 0	VTPTextureId	0, 0	VTPPolyCount	2, 0	VTPPolyMethod2	7, _IsLine_, 0; Cell 20 x 32, offset 128,117	VTPWidePoint	9308, _UseWidth_, 12357, 6		VTPWidePointWidth	30		VTPChildPoint	-7, 0, 0, 0		VTPChildPoint	-2, 0, -112, 0		VTPChildPoint	0, 0, -1, 0		VTPChildPoint	-1, 0, -1, 0		VTPChildPoint	0, 0, -1, 0		VTPChildPoint	0, 0, -1, _UseWidth_			VTPWidePointWidth	0

I learn 3 things here:VTPTextureType 2, 0, 0, 4....... is correct.The data structure uses the VTPChildPoint structure we worked out here at AVSIM, and has a "hook" at each end, as is usual for FS9 line types.The width is 30, and the line terminates with a width of 0. Edgar Knobloch, Christian Fumey and I have assumed the line structure and "hook" is needed to control the VTP2 autogen. The terminal width of 0 might also be needed to control the autogen.Dick

Thanks Guys!Seems that VTPChildPoint is the key or "hook". Is there any docs available that describe it?Jay

Hi Jay.Ground2K4 uses ChildPoints as it's default, in the latest version, and uses a "hook" to define the start and end of the line. The ASM code would need to be tweaked to add the terminating 0 width.The search function of the forum:hook childpoint( and mark "AND" ) would find the documentation here in the forum. Edgar wrote a childpoint converter to produce that structure from the traditional code ( chptconv.zip ):http://library.avsim.net/esearch.php?CatID...04sd&DLID=43105=====================I still don't see why your code cannot produce the autogen, however. Our research into ChildPoints and hooks helped to control the placement of vector autogen, but it still displayed for us without their use. Can you include the ASM code as a text attachment, so we can try it?Dick