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

FS2004 Question on "Remove Stock Data" tool

danfoster

danfoster

Messages
359
Country
unitedkingdom
Hi,

How does this work when I only tick the "Scenery Objects" box?

Is it like "Load Stock Data", except that it only creates the excludes, but doesn't go on to add the scenery into the file as well?

If I load an afcad or afx produced bgl into ADE, can I use "Remove Stock Data" even if I haven't previously used "Load Stock Data"? What would I be "adding" to my project file if I did that?

Cheers,

Dan
 
In answer to my own question: No.

So when and how does the "remove" function work? Is it only for use when working with a stock airfield? If I've loaded stock data into a project started from a bgl or xml file, then edited some of that stock data, what get's removed when I use the "remove" function? Do the micro-excludes get removed?

Long story short, is there anywhere that I can find an explanation of this function?

Cheers,

Dan
 
danfoster said:
In answer to my own question: No.

So when and how does the "remove" function work? Is it only for use when working with a stock airfield? If I've loaded stock data into a project started from a bgl or xml file, then edited some of that stock data, what get's removed when I use the "remove" function? Do the micro-excludes get removed?

Long story short, is there anywhere that I can find an explanation of this function?

Cheers,

Dan
Click to expand...

Micro Excludes do not get removed

Remove stock data is based on what is checked. Example if you select Comms all the comms are removed except for the airport you are working on.

If you select scenery then we remove the scenery objects from the airport you are working on.

Selecting Navaids is a little misleading. We are removing certain Navaids (Waypoints) from the ADE screen in approach mode so they do not display but FS still falls back onto the root navaids (Waypoints).
 
So it's not really a "remove stock data" tool, but more of a "remove all data" tool?

If I check "remove scenery", you're saying it will remove all the scenery from the file, yes? Is that including non-stock buildings that I added myself, and also the stock buildings that I have edited and changed?
 
danfoster said:
So it's not really a "remove stock data" tool, but more of a "remove all data" tool?

If I check "remove scenery", you're saying it will remove all the scenery from the file, yes? Is that including non-stock buildings that I added myself, and also the stock buildings that I have edited and changed?
Click to expand...

Dan

As far as non-stock and stock buildings you have added I do not know the outcome. I have not used that feature (remove stock data) except to test that it works with a loaded stock airport.

When Jon returns on June 1st we can pick his brain on just what it will do with scenery that does not load as part of the stock airport loading process.
 
Interesting. We included to remove stock data function to reverse the effects of loading stock data. The whole area of stock data is fraught with problems since ADE has to try and work out whether an object is truly stock or not. It may or may not do a very good job of removing ( or not duplicating) stock objects at the moment.
 
I guess that begs a question then: If you don't want stock data in the first place, why load it? And then why need to remove it again?

Who actually uses the "remove" tool, and does it work as they hoped?

I don't really understand the purpose of the tool. I think it would be of greater usefulness to have a tool that just created the micro-excludes (like with "load stock data, but without the actual scenery objects), thereby ensuring all default stock data was excluded ("removed"). This would be useful for when creating an afcad for a a new scenery.
 
Last edited:
It is about stock data being loaded into ADE and not about whether stock data shows up in FS or not. However I take your point that it needs some extra thought
 
[FSX]
I'm trying to add an approach. I didn't like my first attempt so deleted it.
The approach was deleted but when I tried to delete the waypoints I'd added (the four in line) ADE tells me that they are stock data. No way! or they weren't twenty minutes ago.

Also the NDB is listed as stock, again, no way.

Anybody any idea why ADE thinks these are stock data?
 

Attachments

  • SP32-20100619-150509.jpg
    SP32-20100619-150509.jpg
    5.6 KB · Views: 483
chris said:
[FSX]
I'm trying to add an approach. I didn't like my first attempt so deleted it.
The approach was deleted but when I tried to delete the waypoints I'd added (the four in line) ADE tells me that they are stock data. No way! or they weren't twenty minutes ago.

Also the NDB is listed as stock, again, no way.

Anybody any idea why ADE thinks these are stock data?
Click to expand...

So these are Waypoints you added?
 
Yes, I added the waypoints and the NDB.
You can't see them in the attachment but they are MON28, WP28, MON10 & MON28.
 
chris said:
Yes, I added the waypoints and the NDB.
You can't see them in the attachment but they are MON28, WP28, MON10 & MON28.
Click to expand...

OK then can you zip up and email me the .ad2 project file so I can take a look. Email to jon AT scruffyduck.co.uk
 
Jon - the same issue in this thread http://www.fsdeveloper.com/forum/showthread.php?t=20356 The OP added the ILS feather to Rwy 36 and ADE 1.47.7 shows it as being stock. I checked the stock airport and there's no ILS feather for 36. I've also observed this myself at two airports and used the tool you provided to make the correction. I suspect this happens when we work from our bgl file at some point in the process.

Is there a way for ADE to check the FSX database against what gets added to prevent this issue as well as Navaid/waypoint duplication in the airspace of the airport? The concern I have is when I update the STAR/DP Navaid/waypoints to bring the airport up-to-date.

If I don't see the Navaid/waypoint while viewing in approach mode does this mean that it doesn't actually exist in FSX? Or is it possible that it exists but is outside of the viewing area of the approach mode? If the latter, is there a way for ADE to check against the FSX stock database to prevent a duplication?
 
Jon - the same issue in this thread http://www.fsdeveloper.com/forum/showthread.php?t=20356 The OP added the ILS feather to Rwy 36 and ADE 1.47.7 shows it as being stock. I checked the stock airport and there's no ILS feather for 36. I've also observed this myself at two airports and used the tool you provided to make the correction. I suspect this happens when we work from our bgl file at some point in the process.

Is there a way for ADE to check the FSX database against what gets added to prevent this issue as well as Navaid/waypoint duplication in the airspace of the airport? The concern I have is when I update the STAR/DP Navaid/waypoints to bring the airport up-to-date
Click to expand...
.

ADE has a list of all navaids and waypoints in the fixes database.It could therefore make a 'live check' on these -perhaps via the fault finder. We do have a big issue with navaids especially in FSX since we cannot move them without a risk of duplication. Perhaps you could add an entry to the issue tracker for me to look at 'live checking' of fixes against the database to check for stock.

If I don't see the Navaid/waypoint while viewing in approach mode does this mean that it doesn't actually exist in FSX? Or is it possible that it exists but is outside of the viewing area of the approach mode? If the latter, is there a way for ADE to check against the FSX stock database to prevent a duplication?
Click to expand...

ADE loads fixes up to 60nm from the airport reference point. Over that distance the fixes will be in the database but are not in the ADE project file. Again if you are suggesting that we run a check on fixes being added by the user in case they are already in stock then that could be done.
 
Again if you are suggesting that we run a check on fixes being added by the user in case they are already in stock then that could be done.
Click to expand...

This would be a big help as many of the STAR/DP waypoints are beyond 60nm.

I will see about adding the request to the tracker. Thanks.
 
Darn, I followed the link and there I was.

I hope this is helpful: Before whats in my recent thread, I tried to import stock approaches. It crashed, I got more back than just stock approaches. Buildings came back as well.

I solved this by making the stock airport a bgl, and imported the stock data from the bgl (which is an ADE option). Then I got only what I asked for, the approaches. All well, works fine.

Straight from memory, correct me if I am wrong.

Cheers,
:stirthepo
 
You must log in or register to reply here.
Back
Top