Sign in to follow this  
Guest

LWMdraw3:I can't get shorelines,what am i doing wrong?

Recommended Posts

First,thanks to Ken for this wonderful job.I can see effects ,surf or no surf,but i can't get any differents shore,sand...The width is set to 10 or 20 and the layer to (default) 8. What is wrong?Daniel

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi DanielIf you copy-n-past the text of your VTPSource.asm file here maybe I or someone will see your problem but I'm uncertain at this point how to give you a hand.ThanksKen

Share this post


Link to post
Share on other sites

Thank you for this quick answer.This the text of the vtpsource.asminclude TDFHeaders.incinclude TDFMacros.inc;----> Begin Header Section <----BGLHeader 45, 43, 7, 5, TerrainHeaderStart, VTPHeaderVTPHeader label word VTPFileHeader 256, VTPIndexStart, TextureStart, VTPEnd;----> End Header Section <----;----> Start File Data <----VTPStart label worddatamark_v0 label word;----> Begin Data Area Information <----VTPDataArea 1, 1, 0, 0VTPLayer 8, 0VTPNumTexturesInLayer 1, 0VTPTextureId 4, 0VTPPolyCount 1, 0VTPPolyMethod2 31, 1, 0VTPPolyMethod2Ex 28VTPWidePoint 4499, 1, 5229, 0VTPWidePointWidth 1VTPWidePoint 4499, 1, 5229, 0VTPWidePointWidth 15VTPWidePoint 4499, 0, 5229, 0VTPWidePoint 4494, 0, 5230, 0VTPWidePoint 4491, 0, 5229, 0VTPWidePoint 4483, 0, 5227, 0VTPWidePoint 4479, 0, 5226, 0VTPWidePoint 4474, 0, 5226, 0VTPWidePoint 4469, 0, 5226, 0VTPWidePoint 4464, 0, 5226, 0VTPWidePoint 4460, 0, 5223, 0VTPWidePoint 4455, 0, 5223, 0VTPWidePoint 4452, 0, 5221, 0VTPWidePoint 4446, 0, 5220, 0VTPWidePoint 4442, 0, 5219, 0VTPWidePoint 4440, 0, 5215, 0VTPWidePoint 4436, 0, 5211, 0VTPWidePoint 4432, 0, 5205, 0VTPWidePoint 4430, 0, 5202, 0VTPWidePoint 4428, 0, 5198, 0VTPWidePoint 4428, 0, 5189, 0VTPWidePoint 4425, 0, 5184, 0VTPWidePoint 4420, 0, 5172, 0VTPWidePoint 4418, 0, 5170, 0VTPWidePoint 4416, 0, 5167, 0VTPWidePoint 4416, 0, 5164, 0VTPWidePoint 4415, 0, 5160, 0VTPWidePoint 4418, 0, 5159, 0VTPWidePoint 4423, 0, 5159, 0VTPWidePoint 4429, 0, 5159, 0VTPWidePoint 4432, 0, 5160, 0VTPWidePoint 4441, 0, 5157, 0VTPWidePoint 4444, 0, 5160, 0VTPWidePoint 4448, 0, 5162, 0VTPWidePoint 4456, 0, 5167, 0VTPWidePoint 4460, 0, 5171, 0VTPWidePoint 4467, 0, 5173, 0VTPWidePoint 4474, 0, 5173, 0VTPWidePoint 4479, 0, 5175, 0VTPWidePoint 4487, 0, 5179, 0VTPWidePoint 4497, 0, 5181, 0VTPWidePoint 4498, 0, 5183, 0VTPWidePoint 4501, 0, 5185, 0VTPWidePoint 4503, 0, 5188, 0VTPWidePoint 4505, 0, 5191, 0VTPWidePoint 4507, 0, 5192, 0VTPWidePoint 4508, 0, 5195, 0VTPWidePoint 4512, 0, 5201, 0VTPWidePoint 4515, 0, 5203, 0VTPWidePoint 4515, 0, 5205, 0VTPWidePoint 4518, 0, 5210, 0VTPWidePoint 4519, 0, 5210, 0VTPWidePoint 4520, 0, 5217, 0VTPWidePoint 4521, 0, 5220, 0VTPWidePoint 4521, 0, 5220, 0VTPWidePoint 4517, 0, 5224, 0VTPWidePoint 4516, 0, 5226, 0VTPWidePoint 4511, 0, 5227, 0VTPWidePoint 4509, 1, 5227, 0VTPWidePointWidth 0datamark_v1 label word;----> End Data Area Information <----;----> Begin Cell_397_129's defination data information <----Cellv_397_129 EQU VTPCellID 0, 397, 129VTPIndexStart label wordVTPIndexHeader 1, VTPIndexData, VTPStartVTPIndexData label wordVTPIndexEntry Cellv_397_129, VTPStart, datamark_v0, datamark_v1;----> End Cell_397_129's defination data information <----;----> Begin Texture Information <----TextureStart label wordVTPTextureListHeader 5, TextureIndexStart, TextureDataStart, TextureDataEndTextureIndexStart 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_5TextureDataStart label wordtexturemark_0 label word VTPTextureName "1062" ;white sandVTPTextureType 2, 0, 0, 4texturemark_1 label word VTPTextureName "1062" ;white sandVTPTextureType 2, 0, 0, 4texturemark_2 label word VTPTextureName "1062" ;white sandVTPTextureType 2, 0, 0, 4texturemark_3 label word VTPTextureName "1062" ;white sandVTPTextureType 2, 0, 0, 4texturemark_4 label word VTPTextureName "1062" ;white sandVTPTextureType 2, 0, 0, 4texturemark_5 label word VTPTextureName "1062" ;white sandVTPTextureType 2, 0, 0, 4TextureDataEnd label word;----> End Texture Information <----;----> The next line below ENDS this file <----VTPEnd label wordDaniel

Share this post


Link to post
Share on other sites

Hi again DanielI counted the number of data point lines three times to make sure of the count and with that found only 57 line/points BUT this says there are 59 line/points:VTPPolyMethod2 31, 1, 0VTPPolyMethod2Ex 2831+28 = 59With that try editing the VTPSource to show:VTPPolyMethod2 31, 1, 0VTPPolyMethod2Ex 26and then try and reassemble and see what happens.Hope this helps yaKen

Share this post


Link to post
Share on other sites

Hi again DanielI counted the number of data point lines three times to make sure of the count and with that found only 57 line/points BUT this says there are 59 line/points:VTPPolyMethod2 31, 1, 0VTPPolyMethod2Ex 2831+28 = 59With that try editing the VTPSource to show:VTPPolyMethod2 31, 1, 0VTPPolyMethod2Ex 26and then try and reassemble and see what happens.Hope this helps yaKen

Share this post


Link to post
Share on other sites

Hi again KenI've made the change you suggested.I got a window return.I manually added two line/points with the same result.After testing more and more,i realised that when i generate the files at differents Lat/Long,the shoreline stays at the first generation place,and the water is changing.That must explain why i could not see the shore.Perhaps I've not understood your whole help file (sorry for my bad English).Another thing,it seems that 10 or 20 width is not enough,50 is better.Thank you one more time.Daniel

Share this post


Link to post
Share on other sites

Hi DanielAfter you calculate the FS coordinates the Cell and Area labels, (bottom left of window), displays the bounds for the data points you click on within the image. You should not be having this problem if your working within a single Area, (LOD 13), but if your working within multiple Areas it's important to re-adjust the coordinates and press Calculate again so those label displays show the correct Area your working with. The VTP data points are calculated from those display labels within the program code so if you don't re-adjust the coordinates those data points will not be the correct values. I'm working on the next version and have replaced those labels with textboxes so that the user can simply type the Area bounds they wish without having to re-adjust coordinates along with some other added features.I hope it's working for you ok now.Ken

Share this post


Link to post
Share on other sites

Ok KenJust another (surely evident)question:To work with correct scale,the 256 X 256 image must represent 1228.8 m X 1228.8 m (one area's size) where i am living (very close to 45 N).Another one:in the text .asm files,no altitude is written;where is it coded?That's all.Thank you again.Daniel

Share this post


Link to post
Share on other sites

According to the SDK, the Areas avarage 1.2 kms in size but they are determined by decimal degree distance and the cos factor of latitude degrees. And only the LWM determines the altitude.LaterKen

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