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

Suggestions for Future Versions 2010

Status
Not open for further replies.
Yes, thank you.
One should really go through each option/menu at least once before doing an unnecessary post... Sorry for this...

Greetz,
Wim

No problem :) Section 8.5 of the English Manual deals with Helper Shapes.
 
I would like the ability to edit a helper shape. Usually, when you add a helper shape, you have to delete it then make another one to get the size right.
 
I would like the ability to edit a helper shape. Usually, when you add a helper shape, you have to delete it then make another one to get the size right.

You can re-size them - check the manual ;)
 
Hi Jon
Thanks to you guys for a wonderful piece of software.:D
Suggestion for ADE: Pilot controlled runway lighting at some smaller airports.
Keep up the great work.
 
Hi Jon
Thanks to you guys for a wonderful piece of software.:D
Suggestion for ADE: Pilot controlled runway lighting at some smaller airports.
Keep up the great work.

If I knew how it is done then perhaps I could look at it :o
 
I would like to suggest:

The ability to change the selected-object type, by clicking on the menu bar tool icons. What I mean is, if you have a node already selected, you can click on the "create hold-short node" button, and it will change the type of the selected node (to a hold-short node, in this example). Or if you already have a link selected, you can click on the "create apron path" button, and it will change the link to an apron path (with the possibility of doing the same with runway paths too).

This means that if you are tackling a lot of repetitive editing (ie. you install an ai package, which puts a load of afcads onto your system, but then you discover the afcads are a bit shoddy and need some further work) you don't have to keep double clicking everything, then waiting while the properties menu opens, before setting the new object type, and then finally clicking "ok". All of those clicks and pauses while waiting for menus to open would be replaced by just one direct click on a tool-bar icon. For me personally, it would turn a 5 minute job into a 1 minute job - that's got to be a good thing :D

Cheers,

Dan
 
A "data flush", if I can call it that, would be good.

At the moment, if I open a bgl, add stock buildings and then compile, then open another bgl, adding stock buildings to this new project file causes ADE to lock up. I have to close ADE then reopen it everytime I want to work on a different project.

If I could just somehow flush the system resources being used for the current project in preparation for opening a new project, I might keep my sanity a little more intact :D

A further problem here is that when ADE is locked up, it seems to block Windows Task Manager from starting.
 
A "data flush", if I can call it that, would be good.

At the moment, if I open a bgl, add stock buildings and then compile, then open another bgl, adding stock buildings to this new project file causes ADE to lock up. I have to close ADE then reopen it everytime I want to work on a different project.

If I could just somehow flush the system resources being used for the current project in preparation for opening a new project, I might keep my sanity a little more intact :D

A further problem here is that when ADE is locked up, it seems to block Windows Task Manager from starting.



This is a memory problem and we are looking at it again!
 
I would like to suggest:

The ability to change the selected-object type, by clicking on the menu bar tool icons. What I mean is, if you have a node already selected, you can click on the "create hold-short node" button, and it will change the type of the selected node (to a hold-short node, in this example). Or if you already have a link selected, you can click on the "create apron path" button, and it will change the link to an apron path (with the possibility of doing the same with runway paths too).

This means that if you are tackling a lot of repetitive editing (ie. you install an ai package, which puts a load of afcads onto your system, but then you discover the afcads are a bit shoddy and need some further work) you don't have to keep double clicking everything, then waiting while the properties menu opens, before setting the new object type, and then finally clicking "ok". All of those clicks and pauses while waiting for menus to open would be replaced by just one direct click on a tool-bar icon. For me personally, it would turn a 5 minute job into a 1 minute job - that's got to be a good thing :D

Cheers,

Dan

Well we are re-designing the user interface pretty much from scratch so I can look at this. What I will say is that the new property grid method for modifying objects is a lot faster than the old property dialog - probably still 2 clicks though...
 
Hi to all
Suggestion for ADE: Pilot controlled runway lighting at some smaller airports.
If I knew how it is done then perhaps I could look at it :o
I'm not a programmer, I'm just a curious guy who loves FS and now starts to be marveled with all the programs that have been created to improve the experience of FS.
So I was thinking in this case of controlled runway lighting if the same principal of "moving hangar doors" can be used.
We dial a specific frequency in NAV2 and when within a certain range the doors open. I presume this "range" is made with a trigger, so maybe using a trigger (along the landing path) associated with a NAV2 frequency and some sort of code to light up the runway lights.
Since I'm a noob, I think of it like this:
NAV2 frequency set. Aircraft inside trigger. 2 conditions set, runway lights ON :D
(I know it's not simple as that, but it's the way I see it )

It's just a tought, like I say, I'm not a programmer

Regards
 
I have a feeling someone has already mentioned this but I will ask anyways:

Is it possible to have ADE download ground tiles directly from an online server so the runways and taxiways are exactly where they are in real life, rather than having to match the runway up with a screenshot from Google Earth?

Just a thought...
 
I have a feeling someone has already mentioned this but I will ask anyways:

Is it possible to have ADE download ground tiles directly from an online server so the runways and taxiways are exactly where they are in real life, rather than having to match the runway up with a screenshot from Google Earth?

Just a thought...

Hi Michael

Yes that is on the development list :)
 
Stock Data

Something for the list.

I'd like the capability to update the data files for the stock airports. For example, If I modify a nearby airport or add waypoints in the general area I'd like to be able to import those during a stock data import.

Also I'd like to be able to load non-terminal waypoints and navaids farther out then 60 mi for approach designing.

Thanks. Looks like you have a very big to do list as it is!
 
I'd like the capability to update the data files for the stock airports. For example, If I modify a nearby airport or add waypoints in the general area I'd like to be able to import those during a stock data import.

Do you mean modifying the stock navaid data itself?

Also I'd like to be able to load non-terminal waypoints and navaids farther out then 60 mi for approach designing.

60 was picked as a reasonable limit. We could extend it. We need to be aware of the compromise between distance and the amount of data needed along with the size of files and ADE performance though.
 
Lat/Lon in the Waypoint List

Dear Jon I have now 2 Weeks (90 Hours) worked with the new EDDP Layout.
Specially with the Approaches and I´m not yet finished. :eek:
I have add ISEC, moving, delete some and so on,
but the longest work was the LAT/LON Information for the changed Waypoints to put in a List that I want to use with FSNavigator.

Can you add the Coordinates into the Waypoint List, it is enough place there.

Thank you, you are my Hero.
 
Last edited:
Dear Jon I have now 2 Weeks (90 Hours) worked with the new EDDP Layout.
Specially with the Approaches and I´m not yet finished. :eek:
I have add ISEC, moving, delete some and so on,
but the longest work was the LAT/LON Information for the changed Waypoints to put in a List that I want to use with FSNavigator.

Can you add the Coordinates into the Waypoint List, the is enough place there.

Thank you, you are my Hero.

Yes I can - I have put it on my list of things to do in the next version ;)
 
Do you mean modifying the stock navaid data itself?



60 was picked as a reasonable limit. We could extend it. We need to be aware of the compromise between distance and the amount of data needed along with the size of files and ADE performance though.

Could this be presented as a "user choice"?

In some parts of the world one only needs navaids & wpts upto 60 miles away, and the area may already be full of them - so no need to fill the project file with extra data from further away navaids & wpts.

But in the more empty parts of the world, it would be very useful to have the choice of being able to load data from a greater range if need be - and this wouldn't create too much extra size in the project file, due to the scarcity of navaids & wpts in these regions.

Just a thought: I've managed OK so far without this ability...

EDIT: An additional thought - Whether you include the above idea or not in ADE, I think the 60 mile radius is a good default value. Anything greater than this should need to be selected by the user to deal with "special cases". Otherwise you will get novices running into trouble, writing transitions with initial fixes that are behind the user aircraft by the time ATC offer them transition options for their approach.
 
Last edited:
Otherwise you will get novices running into trouble, writing transitions with initial fixes that are behind the user aircraft by the time ATC offer them transition options for their approach.


Exactly :) I will look at adding an option for range of fixes to include. I need to look at the overhead in performance of saving and loading fixes into the project against reading them in from the database when the file is loaded. If the difference is limited then it might be better all round to just display them when the project loads and not save them in the file at all (they are for display only after all)
 
Status
Not open for further replies.
Back
Top