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

0.45 Changing Patterns

Messages
221
Country
denmark
So here's the first observation ;-)

Trying to change the Primary and secondary Pattern.

Default is as you now LEFT.

You Can't changes it to NOT_SET, that be what it is. Trying to do so changes the value to RIGHT (Isn't there a both value here...?)

You can change the Primary to RIGHT, and keep the Secondary to LEFT, so far so good. You can the continue and change the Secondary to RIGHT as well... still good.

Now, if you want to change the Secondary back to LEFT....you can not. No matter what you change it continues to stay at RIGHT.

You can still change the Primary though.

I haven't tried changing the values in SDE, but that wouldn't be a problem I guess, as it is merely an advanced but manual XML-editor so everything goes here ;-)

EDIT: Just tried the SDE... same thing here.... so I guess I must revert to old Notepad.... ;-) Happy coding.
 
Last edited:
Dan

Are you trying to change it for any particular reason?

I am just wondering why the importance of making it something other then the default.

Not sure why Jon has a NOT_SET since patterns are always either LEFT (default) or RIGHT but not BOTH
 
Last edited:
Thanks Dan I will look at that - sounds like a problem with the Engine itself
 
Nope, I'm just testing the application....

I guess the pattern is the route the aircraft takes when leaving the runway either because of a go-around or a take-off. Correct me if I'm wrong.

While EKCH has two parallel runways, I thought it would be appropriate to have the, say, 22R to leave to the right, and 22L to leave to the left, same the other direction (04L/R), but as you see I had to take a trip over SDE to Notepad back to SDE and then back to ADE again....

Btw. while compiling/saving the file in ADE there seem to have sneaked in a space-character in the file name

My file is name EKCH_AFX_ ADE.bgl where it should say EKCH_AFX_ADE.bgl

Just in front of ADE and after AFX_ ... a bit difficult to show a space..... :-)
 
Last edited:
Btw. while compiling/saving the file in ADE there seem to have sneaked in a space-character in the file name

Hi Dan - thanks - that has been reported but I have failed to fix it so far :o


EDIT

Fixed for 0.46
 
Last edited:
If we are talking about the pattern then this is the landing pattern and is always left or right handed :) (At least as a lowly private VFR pilot understands things :) ) It stops the guys in the circuit bumping into each other :D
 
The name space was reported but must have got past Jon this time around.


I guess the pattern is the route the aircraft takes when leaving the runway either because of a go-around or a take-off. Correct me if I'm wrong.

There are many parts of a airport that do nothing for the User Aircraft. There are also parts that FS uses for just the AI Planes. Then there are parts that the FS uses for both type planes.

User Aircraft turn based on what you want to do. If the pattern is Left then you the User makes that decision and not a set of instructions in a compiled bgl.

User Plane and AI Planes on a VFR/IFR FP will be told by ATC which way to turn on departure. Normally in the direction of the great circle route of the FP.

Missed Approach or Go Around for both User and AI when on a FP is based on a degree heading of the IAF based on the approach coding and nothing about the runway properties.

Not much left for the Pattern LEFT/RIGHT that you are trying to change except!!

A AI Plane on a VFR FP written to do Touch and Go's (TNG). So if you write FP's using the FP compiler in the FSX SDK, the pattern is the control instructions on which way you want the AI Plane to fly TNG patterns (LEFT or RIGHT) and nothing in between such as BOTH or NOT_SET.

Also when a VFR is flying TNG turning in the direction of what Pattern is set the AI Plane also uses the Pattern Altitude that is also nesting in the same records.

If a AI Plane is on a FP both VFR/IFR then the altitude in the FP is compiled. However, if a TNG is written regardless of the altitude used in the FP the AI Plane flys what is written in the instruction code of the bgl.

There are very few people that write FP's using the FSX FP compiler and fewer people writting TNG FP's.

For the User of ADE, if something has no importance because it requires more knowledge in other areas (writing TNG FP's) then why not just stay with a default value that FSX uses.

IF you ever get to the point where you start writing TNG FP's for a airport then the LEFT/RIGHT Pattern, altitude will become important based on the airport traffic pattern set by the FAA.
 
I moved the discussion on flight plans to another thread - hopefully I got them all :)
 
Back
Top