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

Objects visible from only some aircraft

Messages
8
Country
unitedstates
Hi All,

First off, let me say that I am a novice FSX scenery maker, so I’m bound to say something stupid. My forum searches lead me to believe this may have something to do with LOD's.

I’m trying to construct some WWII scenery using scenery objects from various sources. I’ve imported and exported scenery objects using the very nice ModelconverterX acquired from this site. I’m hoping that it is just my inexperience with this tool and scenery construction in general that causes my dilemma.

Edit: I told you I would say something stupid. The Problem is resolution e dependent. NOT aircraft dependent. The lower resolution allows the objects to be viewable.

Problem:
Some scenery objects placed on my airfield only show up when viewed from certain aircraft and/or display resolutions.

Example:
I’ve place a collection of oil drums (taken from a library of Truk Lagoon objects). These oil drums are visible when viewed from a JU-52 (the one by Oliver Fischer). I can see them from all views and at multiple resolutions on multiple monitors.
The same exact fuel drums can NOT be seen on my primary monitor (30” 2560 x 1600) when viewed from the Touch the Sky Simulations Hawker Hurricane IID. However, the oil drums ARE visible from my secondary screen (24” 1920 x 1080).

The same anomaly occurs with multiple but not all scenery objects.

Any suggestions on a remedy or debugging methodology to find root cause would be very welcome.

Pertinent System specs:
Windows 7 64Bit
FSX Gold w/Acceleration
ATI Radeon HD 7870 GHz Edition 2GB
Primary Monitor 30" 2560 x 1600
Secondary Monitor 24" 1920 x 1080
Graphics system = DX9
Intel i7 4770K
16 GB RAM
 
Last edited:
UPDATE:SOLVED!

This is a very strange anomolie, which I am at a loss to explain.

I noticed that when I place a tall object (Water Tower) that the bulk of the oject was below the terrain on the primary monitor (2560x1600x32).
Scenery_Anomolie_main_mon.jpg


On the secondary monitor (1024x768x32), the scenery displayed correctly.

Scenery_Anomolie_secondary_mon.jpg


Changing the resolution on the primary monitor to 1024x768x32 had no effect, the scenery displayed the same.

Since an elevation difference seemed to be occuring, I deactivated all addon scenery/mesh. No difference.

A single parameter was the cause of this anomolie and I would not have suspected it as root cause. Only a systematic process of elimination yeilded the solution.

Anyone want to venture a guess?
 
Hello:

AFAIK, most folks here at FSDeveloper are so busy with their own projects that they might not be inclined to appreciate a 'survey' much less a friendly challenge to "guess" how someone solved their development problem, so IIUC the anticipated protocol to be used by participants in these forums is simply a concise explanation of how to do something and/or how a problem is /was solved. ;)

But, personally, I like seeing folks think things through to solve problems, and I especially appreciate it when they share their insights with others here; so to be a good sport, I'll take a "guess". :)

The differing "Zoom" and/or "ChaseDistance" levels, and/or use of different WideViewAspect=True versus WideViewAspect=False parameters apparent in the separate views from IIUC both inside and outside the cockpit are all unlikely to be the basis for the water tower position relative to local ground level, especially if only the FS 'default' terrain mesh (and the same airport background flatten polygon) was used for each of the above screenshots.


IIUC, your reference to a "Parameter" might be inferring that 2 or more different placement files may have been used to place the water tower scenery library object in question, each BGL using different 'parameter' values for:

altitudeIsAGL=TRUE (aka "AGL") versus altitudeIsAGL=FALSE (aka "MSL") ...in your BGLComp scenery object placement XML code.


Or are you actually inferring here that a display resolution setting (in pixels) for your separate computer monitors set in the AMD Catalyst driver external to FSX itself (or set in the "active" FSX.Cfg) ...is the basis for the water tower scenery library object position relative to local ground level as rendered at run time in FSX ? :scratchch

GaryGB
 
Last edited:
Hi Gary,

I just wanted to stimulate a little thinking with my "guess" proposal.;) , however I guess developing scenery is thought stimulating enough.

I said this was a strange one. It must be related to the ATI Catalyst graphics driver. I never would have thought it would manifest in an "altitude" sort of way. I still am struggling to figure this one out.

In the bgl every thing is set to altitudeIsAGL=TRUE.

What corrected the problem was after starting a flight, I went to options->settings-display and toggled the filtering from Bi-linear to Tri-linear. Voila, the objects displayed at the proper altitude! It didn't matter if I started with Bi or Tri-Linear filtering, the objects were still at a lower altitude than set. I only had to toggle it after a flight was started. I am one rev behind the latest release of the Catalyst. I think I'll try the newest to see if this bug occurs in that rev.

Terry
 
Hi Terry:

I appreciate your good intentions in soliciting some interaction on an unusual FS development troubleshooting scenario.

I also especially appreciate the additional clarification and heads up on this, as I too am a user of AMD /ATI video cards, and welcome seeing this type of feedback regarding any anomalies which may occur with FS scenery display using recent Catalyst driver versions.

As I always run FS in either Tri-Linear or Anisotropic filtering mode, I might not otherwise have had occasion to detect this display anomaly.

However I do recall that on my computers immediately after a new installation of FS, within the FS GUI, filtering is by default set to Bi-Linear; although I personally thereafter keep it set it in Tri-Linear or Anisotropic filtering mode, other FS users may not be aware of the potential visual enhancements achievable by doing this ...and could therefore be at risk for seeing such anomalies as you have described above by continuing to use Bi-Linear filtering.


Thanks for caring enough to post about this, and it is good to have you here with us in the FSDeveloper forums ! :)

GaryGB
 
Last edited:
Back
Top