• 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.

Ground Polygon Photoscenery...

Shaun

Shaun

Messages
1,964
Country
unitedkingdom
I have used gpolys for the entire photoscenery, but have run into a problem with the mipmaps...

With mipmaps on, there is a visible black line between the tiles of the scenery.

Without them, the moire effect makes it unusable.

Any recommendations on how to use this method successfully?

:confused:
 
The mipmapping is bringing over pixels from the opposite edge of the texture for blending purposes. That gives you the "edges". The solution is to reduce your texture mapping by a pixel or two along all edges of each ground polygon. This will usually eliminate the edging.
 
****


So, one needs to cut the texture into 1024 sheets for use with this method?

And each sheet is a drawcall?

For a 30cm/pix resolution with 15km^2 coverage, that is about 112 "1024x1024" sheets and drawcalls :confused:
 
It has been discussed in this thread

There are pros and cons. I think the bigger area of ground poly is the benefit of it is less.

Why don't use them together? I usually use photoscenery for large area and use ground poly where you need more detail such as appron, parking lots. It is quite easier to do.
 
Ah yeah cheers! I forgot that it mentioned the inordinate amount of drawcalls and work.

I'm resampling it and doing it the old fashion way!
 
Another question regarding this topic...

Say you have some nice crisp 25cm aerial images for your photoscenery; using them as ground polygons necessitates mipmapping to aviod the dreadful shimmering experienced. But then you loose 4x the resolution? So you now have 1m/pix photoscenery? It looks blurry!
 
Why would you loose resolution adding the mipmaps? The lower resolutions are only used in the distance.
 
But when you convert something to mipmaps the "main surface" is made lower resolution to afford the space for the mipmaps?

All of mine seem to work that way. Textures without mipmaps look much crisper when next to them, but suffer the debilitating shimmering.

The "main surface" has the same texture sheet size, but the pixels are weighted across several by the looks of it.
 
The resolution is the same. But indeed less colours are used as a compression technique for dxt. For each area of 4x4 pixels 4 different colours are used.
 
Hi,

No, the lower mipmaps are added to the file. Mipmapped files are larger than those without mipmaps. I don't believe there is any difference in the main image itself.

What you are seeing is the *effect* of mipmapping in FS, not the result of a lower resolution image.

Hope this helps,
 
You must log in or register to reply here.
Back
Top