• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

VTP2 Polys - St-Simon-les-Mines Scenery

Messages
26
Country
us-alaska
HugoA,

I don't know how you are laying down your polys, but a number of programs will do. I use FS Architect, but it is payware. Mostly just long habit on my part. A good, simple freeware program is FS Scenery Creator, known mostly as FSSC. Perhaps Arno has a quick and simple system for polygons in general and the VTP2 polys.

Making VTP2 polys using scasm is all I know, so I will confine my remarks to that. I suspect I will be picking up XML techniques soon, just not quite yet. But since you are still using FSDS2 scasm is appropriate.

If you use FS Architect or FSSC you should download my program, polybsetup.zip, from AVSIM. The combination with the shortest learning curve, to just "get it done", would be FSSC and polybsetup.zip.

The first thing to know is that when you make VTP2 polygons, they are just like FS9 scenery and will change with the seasons automatically. That is because they are covered with landclass. That limits your choices, but there are about 142 different landclasses. My program includes a visual catalogue of the landclasses, PolyView, and should be downloaded even if you don't make the polygons that way. There are two programs in the download:

PolyB - will make VTP2 polygons from appropriately labeled scasm source from FS Architect and FSSC. I can't vouch for other programs, but it might work.

PolyView - a stand alone landclass visual catalogue, there is also an integrated version in PolyB.

There is adequate documentation in integrated help files in PolyB to tell you about how to use it. There are a few caveats in using VTP2 polygons, such as limited complexity, but you may not get to that limitation. If you try them and have some problems, then we can go into it further. Arno and rhumbaflappy are the gurus in this realm, I just hacked out a utility.

Hope that helps...

Jim
 
Thanks Jim. I will get the combination FSSC and polybsetup.zip and have a try on it. Never realy used FSSC but I gather it has similarities with Airport wich I am more familiar with. Will let you know of the progress.

HugoA

BTW you can call me by my short name; Hugo :)
 
VTP2 polys can be any named texture set... not just landclass. Read the SDKs.

The only limitation is the approximate 4.8 meter/pixel size.

Dick
 
VTP2 Polys

Dick,

Thanks for the correction, guess I have just focused on my area of interest and forgot the other uses.

Jim
 
Which SDK discusses making the VTP2 polys with XML? also, is there any tool, commercial or otherwise, which assists in making scenery the XML way? What I mean is, I have FSDS3, EZ-Scenerya nd AFCAD2, but the ground texturing/polygons are not entirely handled by these programs - what would round out this toolset well (I'd like all my tools to be XML-oriented and not SCASM oriented).

Thanks,

J
 
ahuimanu said:
Which SDK discusses making the VTP2 polys with XML?

None, as you can not make mesh scenery with XML code.

ahuimanu said:
also, is there any tool, commercial or otherwise, which assists in making scenery the XML way? What I mean is, I have FSDS3, EZ-Scenerya nd AFCAD2, but the ground texturing/polygons are not entirely handled by these programs - what would round out this toolset well (I'd like all my tools to be XML-oriented and not SCASM oriented).

For ground polygons there are two options:

  1. Place them with the mesh code, for example with resample. This has the limitation of maximum 4.8 meters per pixel resolution.
  2. Place them with Fs2002 GMax or SCASM ground polygons. This allows a much higher resolution, but works best on flat areas, around airports for example.

There is just no modern (XML way) that gives us high detail. So if you want to follow the Fs2004 standards, use the mesh techniques, else refer to the old polygons. Just be sure to make use of the floating point commands if you use SCASM, they are so much easier :).
 
Thanks Arno,

So, if I wanted airport polys or other type polys there is no way using FS2004 SDK techniques? I suppose landclass was to have replaced this?

I do notice that some airports do seem to have a grass-type texture under them.

This is the one part of contemporary scenery design that I just don't "get" at all. :confused:
 
ahuimanu said:
So, if I wanted airport polys or other type polys there is no way using FS2004 SDK techniques?

You can, with the XML code, but then you get the same as AFCAD. If you want more control or more complex things, you need to revert to the older commands.

ahuimanu said:
I suppose landclass was to have replaced this?

No, landclass has nothing to do with this. That is a just a way to have textures all over the world on the ground.

ahuimanu said:
I do notice that some airports do seem to have a grass-type texture under them.

All default airports do. That are VTP polygons, making sure the autogen gets excluded properly. And it also looks better of course.
 
Back
Top