-
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.
Can't exclude!
- Thread starter meshman
- Start date
I opened the stock airport, save KOVE as an ADE file and located the pole in question. First, your coordinates were ever so slightly off from that of the stock location. Did you at one point move the pole? Why not simply move or delete it? I was able to both. Maybe I didn't understand the question?
edit: Ok, I see; you're not able to view the pole using ADE. I can't help you there as I'm able to view it. The pole should show up with a sparse scenery setting.
edit: Ok, I see; you're not able to view the pole using ADE. I can't help you there as I'm able to view it. The pole should show up with a sparse scenery setting.
Attachments
Last edited:
- Messages
- 12,244
- Country
Hi Lance,
I don't see a problem, use
Without exclude:
With exclude:
Edit.
Or, as Kagazi said, just delete it in ADE.
I don't see a problem, use
Code:
<?xml version="1.0"?>
<FSData
version = "9.0"
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:noNamespaceSchemaLocation="bglcomp.xsd" >
<ExclusionRectangle
latitudeMinimum = "39.4944808"
latitudeMaximum = "39.4948083"
longitudeMinimum = "-121.6168737"
longitudeMaximum = "-121.6164539"
excludeAllObjects = "TRUE"
/>
</FSData>Without exclude:
With exclude:
Edit.
Or, as Kagazi said, just delete it in ADE.
Last edited:
- Messages
- 34,981
- Country
Yea, I found it, by going back and seeing it placed via the XML. Which then caused me to ask why it didn't display? Going into HYPER-zoom revealed this minute yellow square, as seen in relation to the windsock display.
Wonder if there couldn't be a minimum display size for objects, seeing as some of us can't see that close without pressing our nose against the display...
Just wait, Jon. There will be bifocals in your future...
Another way to highlight it would be to select it from the Scenery Object List.
Varifocals for me
Pyscen
Resource contributor
- Messages
- 3,040
- Country
Another way to highlight it would be to select it from the Scenery Object List.
Varifocals for me
You could also use a position marker also... Varifocals, better then bi-focals?
if so I'll take one!
