ADE9X feedback

[scruffyduck]

That's been an on going trend here also... sounds like a memory leak of some kind? Not sure if the correct word usage,... but nothing really hurts the project that I can tell. Its like its going through the Alt-tab function of Windows, and sometimes ending up other then ADE.

Are we reporting a bug here chaps??

 

[GHD]

Are we reporting a bug here chaps??

I have learned to live with it

I just keep an eye on the windows task bar.

 

[Gazer75]

Are we reporting a bug here chaps??

I guess you could say that.
Sometimes hitting ok after editing an object ADE will all of a sudden not be the active window.

 

[Pyscen]

Are we reporting a bug here chaps??

I guess you can call it that... usually happens with me while saving or compiling... not sure what could be done about it anyways.

 

[scruffyduck]

I guess you can call it that... usually happens with me while saving or compiling... not sure what could be done about it anyways.

Well I will add it to the list - I can probably brute force the ADE main window to the top after a child window is closed

 

[Gazer75]

Issue with breaking off edge and center lines

Have a problem getting the edge and center taxi lines to stop where I want to.
This used to be possible to do in AFCAD by setting a node in the middle of a path and turn off lines of the line behind that should not have lines.

First picture show what I was expecting to see in FS. The lines ending at apron start. Next shows the node that I made to stop the lines, and finally the result in FS.

It doesn't matter where I put the node, the edge and center line always go all the way to the "T" node.

Only way to stop this taxiway from having lines is to remove node and disable lines on the whole segment to the X-way about 150ft to the right of the pictures.

 

[Gazer75]

Error report

Closed FS while ADE9X was connected and got the following:

Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

at System.Collections.CollectionBase.System.Collections.IList.get_Item(Int32 index)
at UMD.HCIL.Piccolo.Util.PNodeList.get_Item(Int32 index) in C:\Users\Owner\Documents\Visual Studio 2008\Piccolo.NET\Source\Piccolo\Util\PNodeList.cs:line 154
at UMD.HCIL.Piccolo.PNode.RemoveChild(Int32 index) in C:\Users\Owner\Documents\Visual Studio 2008\Piccolo.NET\Source\Piccolo\PNode.cs:line 3945
at UMD.HCIL.Piccolo.PNode.RemoveChild(PNode child) in C:\Users\Owner\Documents\Visual Studio 2008\Piccolo.NET\Source\Piccolo\PNode.cs:line 3932
at ScruffyDuck.AirportDesignEditor.MainForm.disconnectFromFS()
at ScruffyDuck.AirportDesignEditor.MainForm.connectTimer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

[scruffyduck]

Thanks we have seen this before but it never happens when I try to replicate it. I have added it to the bug tracker and we will see if we can track it down

 

[Gazer75]

Which post did you reply to? The taxi lines or the error?

 

[jvile]

Have a problem getting the edge and center taxi lines to stop where I want to.
This used to be possible to do in AFCAD by setting a node in the middle of a path and turn off lines of the line behind that should not have lines.

First picture show what I was expecting to see in FS. The lines ending at apron start. Next shows the node that I made to stop the lines, and finally the result in FS.

It doesn't matter where I put the node, the edge and center line always go all the way to the "T" node.

Only way to stop this taxiway from having lines is to remove node and disable lines on the whole segment to the X-way about 150ft to the right of the pictures.

FSX does not draw the same as FS9. There are many post here that address this issue and how to use blocking nodes to stop line and light draw at intersections.

 

[scruffyduck]

Which post did you reply to? The taxi lines or the error?

The error.....

 

[Gazer75]

FSX does not draw the same as FS9. There are many post here that address this issue and how to use blocking nodes to stop line and light draw at intersections.

In FS9 mode here btw. Don't have FSX.

Can't say search turned up anything useful...

I don't know what to say Jim, its been hit and miss with ADE. Sometimes it works, but most of the time it don't. I've had segments that didn't change no matter how many nodes I put in between. Only way was like I said to remove line from the T intersection to the next T completely.

 

[scruffyduck]

In FS9 mode here btw. Don't have FSX.

Can't say search turned up anything useful...

I don't know what to say Jim, its been hit and miss with ADE. Sometimes it works, but most of the time it don't. I've had segments that didn't change no matter how many nodes I put in between. Only way was like I said to remove line from the T intersection to the next T completely.

I don't think that ADE behaves any differently than AFCAD. I assume this is a problem of display in FS? is it that ADE does not draw the links/markings etc as well or accurately as AFCAD does?

 

[Gazer75]

The problem is that for some reason FS9 will not stop displaying edge and center lines on taxiway segments that don't have them defined.
If you wanted to stop either one on a taxiway between two intersections, using AFCAD, you used a node and disabled what you wanted on one of the segments created.
This doesn't work most of the time anymore.
Even surface selection is sometimes impossible to set for each segment. Often only work between a T or X intersection only, and not by using nodes to make segments and selecting surface type between each node.

 

[scruffyduck]

The problem is that for some reason FS9 will not stop displaying edge and center lines on taxiway segments that don't have them defined.
If you wanted to stop either one on a taxiway between two intersections, using AFCAD, you used a node and disabled what you wanted on one of the segments created.
This doesn't work most of the time anymore.
Even surface selection is sometimes impossible to set for each segment. Often only work between a T or X intersection only, and not by using nodes to make segments and selecting surface type between each node.

One of the differences between ADE and AFCAD is that AFCAD uses its own compiler while ADE uses the standard Microsoft one - you might think that BglComp should do it all right but that is not always true.

I'm not the best person when it comes to the practicalities of design however if we can pin the problem down to the way ADE works then we will, of course, work on fixing it

 

[Gazer75]

Pardon the big picture...
The centerline show where I would put the taxiway.
Yellow line show where edge line would follow if nothing was done.
Blue where I want M4 left side line to stop, and same with right side line on M3.
No matter where I put a node, or any number of nodes, on M3 and 4 between twy M and apron twy, the edge line will go all the way as shown by yellow line.

 

[FlyingMasterChef]

Since you are using 9, this should be very simple.

Start afcad, create the taxi system, check in fs9 and see if it is correct.

Start ADE9X, create the taxi system, check in fs9 and see if it is correct.


IF you get a difference, send both sets of files to Jim and/or Jon and maybe they can figure out what is going on that is different.

- Greg

 

[saiarcot895]

In ADE9X, if you have full logging enabled, then it takes about 9 minutes to load an airport like KORD, versus a few seconds if you don't have logging enabled.

 

[scruffyduck]

In ADE9X, if you have full logging enabled, then it takes about 9 minutes to load an airport like KORD, versus a few seconds if you don't have logging enabled.

Absolutely correct. There is no reason what so ever to have full logging enabled unless we ask you to do it as part of tracking down a problem. In fact in ADE9X you should have Application Logging Unchecked in General Options unless we ask you to do otherwise. At this level ADE still logs your settings and any errors that occur. This is usually enough for us to pin-point a problem. Full logging will log every miniscule action ADE takes so you are making thousands of writes to your disk which is why it takes so long

 

[tgibson]

Hi,

The short answer to your question is that you need to add extra nodes to the taxiway along the bottom and turn off the edge line on those short segments too. FS extends the lines *from both directions* for quite a distance, and that is what you are seeing - the edge lines from the bottom taxiway extending up along the vertical taxiways.

While AFCAD does show this problem, ADE does not. It does not extend the drawing of the edge lines up the sides of the vertical taxiways, as it probably should.

I tried adding these extra nodes and it does work, but I saw some visual anomalies. So I took the advice above and checked out ADE9 vs AFCAD.

Here is the arrangement in AFCAD:

All looks OK. I left the edge lines on the bottom taxiway outside of the curves to show something later.

Here it is in FS9:

Almost all correct, except for a few things. There is a "jump" in the line along the bottom edge line, for some reason. The outside segment's edge lines are not at the edge of the taxiway, but about 10 feet in from that. And the top edge lines are not showing for the outside segments of the bottom taxiway.

Now we'll do it in ADE9:

As you can see, it looks the same as AFCAD, basically.

Now let's see what it displays in FS9:

Well, we have a different problem (sort of) than in AFCAD. The bottom edge line of center part of the bottom taxiway doesn't have that "jump" in it, so that's good. And the top edge lines are showing for the outside segments, also good. But the left side of the horizontal taxiways have all edge lines placed about 10 ft from where they should be (all taxiways are 100 ft wide).

So there are still some drawing errors in ADE9, and there are problems translating that into FS9 for both programs.

Hope this helps,