LWMDraw3 Beta Test

[Guest]

Hi AllAs some of you know I created LWMDraw primarily to place an LWM default type water area into FS2002. The first version only contained a picturebox and textbox for using copy-n-paste routine to a template source file. Then version 2 included coordinate input boxes and etc labels for display plus generated the LWMSource.asm file. Now here's version 3 beta which includes all the above plus VTP method 2 poly's for roads/lines/shorelines and the Extended data point option for both LWM's and VTP's.I'm hoping I can convince several of you to download version 3 and check it out. I not only want to know how the program works for you but I'd also like to know if I was accurate in writing the text help files so that usage is explained well for any users that might think LWMDraw might be helpful to them.Here's the download hyperlink:http://www.flightsimnetwork.com/webads/lwm/LWMDraw3.zipAt this point, and for lack of programming knowledge on my part, I haven't been able to add zoom and scrolling ability for better cursor placement when it comes to clicking exact X and Y cursor coordinates around the edges of the opened image and this causes me to have to edit the ListBoxes manually at times. In time I certainly want to add a zoom and scrolling feature though.I'd much appreciate any comments and suggestionsThanks Super MuchlyKen

[spotlope 0]

This looks fantastic, Ken! I'm going to use it to build a test bit of scenery this weekend, following your tutorials. I'll let you know how it works out, but my initial reaction on reading through the docs is very positive.

[Guest]

Thanks BillI'll be looking forward to any comments and suggestions good and bad.I hope you find it helpful too.Ken

[Guest sapper42]

Gday matewill give it a try this weekend.if i can understand it, anyone can.rgds Jeff

[Guest gorchi]

Hi Ken!I have made a test lake in approx 10 minutes and I must say Your tool is fantastic. And I smell that it can be used also for other things, like drawing cities also... I have found one bug though. I entered N46

[Guest]

Hi GoranThanks for the test. I typed your coordinates as well but came up with 14.11 the first time. I also tried typing the longitude minute two different ways like (9.01) and (09.01) and both times came up with the same result of 14, 11 so I'm not sure what might have happened with that.I was playing around this morning with the bush lake example of combining multiple Areas and may have found a major error on the VTP side of things. I was thinking it may have something to do with some If statements I added but I removed them and the problem continues.For this reason you may want to try generating a separate VTPSource.asm for each Area until I figure out what the heck is going on.For anyone that might give me some help on this. Here's the problem VTPSource and a screenshot showing what happened.Thanks again for the testKen---------------------------------------;----> FS Coordinates: 61 29.43 -149 25.82;----> VTP Method2 road/line/shoreline;----> 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, -148, -150, 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 95VTPWidePoint 5726, 1, 4845, 0VTPWidePointWidth 1VTPWidePoint 5726, 1, 4845, 0VTPWidePointWidth 30VTPWidePoint 5726, 0, 4845, 0VTPWidePoint 5716, 0, 4841, 0VTPWidePoint 5705, 0, 4833, 0VTPWidePoint 5692, 0, 4820, 0VTPWidePoint 5687, 0, 4812, 0VTPWidePoint 5686, 0, 4802, 0VTPWidePoint 5686, 0, 4795, 0VTPWidePoint 5692, 0, 4786, 0VTPWidePoint 5700, 0, 4782, 0VTPWidePoint 5707, 0, 4778, 0VTPWidePoint 5715, 0, 4777, 0VTPWidePoint 5722, 0, 4777, 0VTPWidePoint 5732, 0, 4776, 0VTPWidePoint 5743, 0, 4778, 0VTPWidePoint 5751, 0, 4783, 0VTPWidePoint 5764, 0, 4785, 0VTPWidePoint 5772, 0, 4786, 0VTPWidePoint 5783, 0, 4783, 0VTPWidePoint 5791, 0, 4778, 0VTPWidePoint 5795, 0, 4774, 0VTPWidePoint 5797, 0, 4768, 0VTPWidePoint 5803, 0, 4763, 0VTPWidePoint 5816, 0, 4762, 0VTPWidePoint 5829, 0, 4762, 0VTPWidePoint 5840, 0, 4762, 0VTPWidePoint 5848, 0, 4762, 0VTPWidePoint 5853, 0, 4762, 0VTPWidePoint 5858, 0, 4767, 0VTPWidePoint 5865, 0, 4769, 0VTPWidePoint 5610, 0, 4770, 0VTPWidePoint 5618, 0, 4775, 0VTPWidePoint 5624, 0, 4781, 0VTPWidePoint 5632, 0, 4784, 0VTPWidePoint 5643, 0, 4786, 0VTPWidePoint 5651, 0, 4782, 0VTPWidePoint 5655, 0, 4775, 0VTPWidePoint 5655, 0, 4766, 0VTPWidePoint 5651, 0, 4758, 0VTPWidePoint 5644, 0, 4750, 0VTPWidePoint 5639, 0, 4744, 0VTPWidePoint 5635, 0, 4736, 0VTPWidePoint 5639, 0, 4727, 0VTPWidePoint 5643, 0, 4720, 0VTPWidePoint 5649, 0, 4717, 0VTPWidePoint 5697, 0, 4721, 0VTPWidePoint 5710, 0, 4725, 0VTPWidePoint 5718, 0, 4734, 0VTPWidePoint 5721, 0, 4741, 0VTPWidePoint 5722, 0, 4749, 0VTPWidePoint 5723, 0, 4755, 0VTPWidePoint 5720, 0, 4759, 0VTPWidePoint 5715, 0, 4760, 0VTPWidePoint 5712, 0, 4763, 0VTPWidePoint 5707, 0, 4764, 0VTPWidePoint 5705, 0, 4769, 0VTPWidePoint 5704, 0, 4777, 0VTPWidePoint 5702, 0, 4784, 0VTPWidePoint 5699, 0, 4788, 0VTPWidePoint 5695, 0, 4790, 0VTPWidePoint 5683, 0, 4792, 0VTPWidePoint 5674, 0, 4798, 0VTPWidePoint 5669, 0, 4801, 0VTPWidePoint 5663, 0, 4806, 0VTPWidePoint 5661, 0, 4810, 0VTPWidePoint 5662, 0, 4816, 0VTPWidePoint 5666, 0, 4825, 0VTPWidePoint 5672, 0, 4830, 0VTPWidePoint 5678, 0, 4833, 0VTPWidePoint 5685, 0, 4837, 0VTPWidePoint 5690, 0, 4840, 0VTPWidePoint 5697, 0, 4845, 0VTPWidePoint 5701, 0, 4590, 0VTPWidePoint 5712, 0, 4597, 0VTPWidePoint 5718, 0, 4602, 0VTPWidePoint 5726, 0, 4606, 0VTPWidePoint 5732, 0, 4611, 0VTPWidePoint 5737, 0, 4616, 0VTPWidePoint 5737, 0, 4624, 0VTPWidePoint 5740, 0, 4635, 0VTPWidePoint 5743, 0, 4646, 0VTPWidePoint 5746, 0, 4655, 0VTPWidePoint 5747, 0, 4665, 0VTPWidePoint 5749, 0, 4672, 0VTPWidePoint 5753, 0, 4675, 0VTPWidePoint 5759, 0, 4677, 0VTPWidePoint 5768, 0, 4679, 0VTPWidePoint 5782, 0, 4683, 0VTPWidePoint 5788, 0, 4685, 0VTPWidePoint 5790, 0, 4689, 0VTPWidePoint 5790, 0, 4694, 0VTPWidePoint 5788, 0, 4700, 0VTPWidePoint 5780, 0, 4704, 0VTPWidePoint 5768, 0, 4710, 0VTPWidePoint 5752, 0, 4714, 0VTPWidePoint 5739, 0, 4717, 0VTPWidePoint 5727, 0, 4718, 0VTPWidePoint 5715, 0, 4717, 0VTPWidePoint 5703, 0, 4712, 0VTPWidePoint 5690, 0, 4714, 0VTPWidePoint 5679, 0, 4704, 0VTPWidePoint 5667, 0, 4697, 0VTPWidePoint 5658, 0, 4693, 0VTPWidePoint 5647, 0, 4690, 0VTPWidePoint 5633, 0, 4688, 0VTPWidePoint 5622, 0, 4690, 0VTPWidePoint 5610, 0, 4688, 0VTPWidePoint 5865, 0, 4685, 0VTPWidePoint 5853, 0, 4679, 0VTPWidePoint 5843, 0, 4675, 0VTPWidePoint 5836, 0, 4664, 0VTPWidePoint 5828, 0, 4656, 0VTPWidePoint 5819, 0, 4652, 0VTPWidePoint 5807, 0, 4645, 0VTPWidePoint 5797, 0, 4643, 0VTPWidePoint 5784, 0, 4640, 0VTPWidePoint 5773, 0, 4637, 0VTPWidePoint 5753, 0, 4634, 0VTPWidePoint 5745, 0, 4632, 0VTPWidePoint 5740, 0, 4630, 0VTPWidePoint 5738, 0, 4622, 0VTPWidePoint 5737, 0, 4614, 0VTPWidePoint 5738, 0, 4602, 0VTPWidePoint 5736, 0, 4598, 0VTPWidePoint 5733, 1, 4590, 0VTPWidePointWidth 0datamark_v1 label word;----> End Data Area Information <----;----> Begin Cell_65_81's defination data information <----Cellv_65_81 EQU VTPCellID 0, 65, 81VTPIndexStart label wordVTPIndexHeader 1, VTPIndexData, VTPStartVTPIndexData label wordVTPIndexEntry Cellv_65_81, VTPStart, datamark_v0, datamark_v1;----> End Cell_65_81'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 "1091" ;black sandVTPTextureType 2, 0, 0, 4texturemark_1 label word VTPTextureName "1091" ;black sandVTPTextureType 2, 0, 0, 4texturemark_2 label word VTPTextureName "1091" ;black sandVTPTextureType 2, 0, 0, 4texturemark_3 label word VTPTextureName "1091" ;black sandVTPTextureType 2, 0, 0, 4texturemark_4 label word VTPTextureName "1091" ;black sandVTPTextureType 2, 0, 0, 4texturemark_5 label word VTPTextureName "1091" ;black sandVTPTextureType 2, 0, 0, 4TextureDataEnd label word;----> End Texture Information <----;----> The next line below ENDS this file <----VTPEnd label word-------------------------------------------------------

[Guest]

I just found what I did wrong. I completed going around all 4 LOD 13 Areas but left the coordinates set at Area 6, 2. With that you'll need to move the coordinates to the Area your going to go around.The labels above the image display the X and Y cursor coordinates and it's from those displays that gets printed into the ListBoxes and the Source files upon generation. I certainly get that important change into the help tutorial menu right away.Thanks allKen

[rhumbaflappy 113]

Hi Ken.I don't think there is anything wrong with the code itself. It's going where the points are.But some of the points make a jump ( 100+ ) occasionally:VTPWidePoint 5697, 0, 4845, 0VTPWidePoint 5701, 0, 4590, 0For example, that line goes from 4845 to 4590... a jump vertically of 255 points ( interesting number, yes? ).Your program's code may be using LWM point sets to derive VTP point sets.As we have discussed earlier, they are based differently, as VTPs have a 255x255 grid per LOD13, and LWMs ( mathematically ) have 256x256. So I think your code is seeing a change of LOD13 area, and moving the VTP point up 255 to reflect that change. But VTPm2s don't use an LOD13 in their calculations...just LOD8. What is odd, is that the line then continues normally ( until the next LOD13 area is crossed )? Ideally, you'd use completely different computations to derive the LWM and VTPm2 points. VTPm1's use the same point sets as LWMs.----------I see you spotted it! :-beerchug Dick

[rhumbaflappy 113]

Hi Ken.By now, you have noticed the tapering of the lines that gives them a wormlike appearance.That can be eliminated by overlapping the start and end of the lines.If you examine some of the default MS shorelines, that's how they do it sometimes. So that trick could go into the help file.Another trick is to start the line at it's sharpest bend... because lines taper there anyways... and then it doesn't need an overlap.Dick

[Guest]

Thanks DickI've just uploaded the new file replacing the old one so the download link at the top of this thread is still a good one.I updated the Help file reflecting that it's important to change the coordinates to reflect the LOD 13 Area that's going to be worked on. That'll make the display labels show the correct LOD 8 data point values. I also updated the Quick Start Guide reflecting the overlap HINT you mentioned. Frankly, I had been doing that but forgot to add the helpful hint for it.It's nice to get the responses that I've been getting here. And it's great to get these inconsistancies worked out. I greatly appreciate everyone's help.Thanks AgainKen

[Guest]

Very, very promising program! I downloaded it, read the manuals and gave it a run. Unfortunately no luck. The program always crashes to the desktop with the error message Run-time error '13': Type mismatchwhen my cursor touches the picture area in the middle of the screen! No matter whether a picture is loaded or not, no matter whether coordinates are entered and calculations made or not. My system is an AMD Athlon, Windows XP Pro, Hercules ATI Radeon All-In-Wonder 8500DV, latest drivers, DirectX 8.1. Regional setting is Finland/Sweden but decimal character setting is changed to a point (not a comma as default for this setting).I tried to run it in all possible compatibility modes, and in different screen resolutions, but the problem is 100% reproducable. Any hints on how to solve this?BamceEFHN

[Guest]

Hi BamceDuring development I had twice encountered the dreaded runtime 13 error and on both occasions corrected the problem. I'm certain that Windows XP comes with the vb6 runtime library dll files as well but this is the only thing I can think of at this point that might be causing your problem. You could try reinstalling the vb6 runtime library and see it that helps. And I hope it does but please let me know if you get it working. I'll look around and see if I can reproduce the error.Thanks for your postKen

[Guest]

Here's a download link for the VB6 Runtime Library files. This will be required for Windows 98 and earlier windows versions. If you get runtime errors it might be because your vb runtime library may have gotten corrupted somehow. Please try installing this in that case:http://www.flightsimnetwork.com/webads/dow.../VBRun60sp5.exeI hope it helpsKen

[Guest]

Hi Ken, and thanks for very fast response :-) And thanks for the lib - I actually already downloaded the same file from another site, installed it and rebooted. But - unfortunately the problem persists... BamceEFHN

[Guest]

Well darn BamceI'm uncertain of what is causing the problem but please don't get discouraged because where there is a problem there is also a reason for it. LWMDraw seems to work well on my XP machine and others are getting good results as well but being your getting the error upon entering the cursor into the PictureBox area I'm thinking I'll look into error handling routines for the MouseMove event procedure. Hopefully I'll get it working for ya.Stay CoolKen