ADE 1.35 crash

[scott967]

I loaded a default airport. Added 3 taxiways and two new designators. The last taxiway added causes a crash. If I select it and rmb to edit, I get the following error:
InvalidArgument=Value of '51' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex

If I attempt to open the list -> taxi link, I get the following error:
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

If I attempt to open the list -> taxi designators I get the following error:
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

I can select the taxiway and rmb the xml, which is:
<TaxiwayPath
type="TAXI"
start="362"
end="363"
width="30.0M"
weightLimit="0"
drawSurface="FALSE"
drawDetail="FALSE"
surface="ASPHALT"
name="51"
/>

I attempted a compile with this error:
ScruffyDuck Scenery Design Engine Compiling
Using UNKNOWN BglComp....


Parsing document: F:\Flight Sim\Scenery\Project data\FSX rksi\RKSI_ADE_SWS.xml

INTERNAL COMPILER ERROR: #C2592: Did not find TAXI_NAME #51 needed in path #562 at airport RKSI.


Parse complete!

so I looked at the generated xml and found this for the new taxi designators:

<TaxiName
index="49"
name="N"/>
<TaxiName
index="50"
name="M"/>

So it appears the first designator I added, N was properly assigned as name=49, but somehow for the second one, M, it was given name=51 instead of 50 which I imagine caused the crashes.

scott s.
.

 

[GHD]

Hmm, I added three taxiways to RKSI and designated two of them as Mike and November without a problem. Did you do anything else?



George

 

[scruffyduck]

Can you attach the log please Scott? This is the second or third report recently of problems with the taxi name index. I am beginning to suspect that some recent code is causing an intermittent problem. The log might help also if we can get a reproducible bug.

 

[scott967]

I looked in the log, and it doesn't appear that creating new taxi designations is captured at all. Here is my sequence of events:

load default airport rksi
add image file
add runway 16/34
add taxi points 358/359
add runway link 16 358 > 359
add measurement line
add ILS IRKN rwy 34
Note: this was not captured --
-- add taxi designation N
-- add taxi designation M
add taxi point 360/361
add taxi link 360 > 361 (this one is desig N)
add taxi point 362/363
add taxi link 352>363 (this one should be desig M (M was showing in the list box) but had no desig when hover over)

I should note that while drawing the taxiway, I was using the arrow key to pan the window while holding down the lmb. I don't know if that would make a difference.

I just did the following:
deleted the taxi link and points that caused the problems. Now, I can list the taxi designators 000 - 050 as expected. Any attempt to create a new taxi link with designator M in the taxiway name window caused a repeat of the problem: the new taxiway is getting assigned number 51, not 50. I then selected the "blank" taxiway indicator in the taxiway name window, and this time I was able to create a correct taxiway. I could edit it to change designator to M, and that worked OK. Any attempt to create a taxiway with desig M in the window results in the same problem.

I next did another "add taxi name" for U. This showed in the taxi designator list as index 051 as expected. Now if I select "M"" in the taxiname window, and create a taxi link, it is created OK, but with design U, not M as it should. In fact, it doesn't matter what I select in that taxiname window, all new taxiways are given desig U. I think something is messed up in my ADE file. I will probably have to import from the xml to recover from this.

scott s.
.

 

[scruffyduck]

Where did you add the new designator Scott? from the main window or from the List View?

 

[scott967]

I used the window in the toolbar. I started over from scratch, and had some other problems, so uninstalled and did a clean install of 1.20 and then 1.35. Instead of using the toolbar window, I used the list and then added about 25 new designations. It still seems like if I select a designation from the toolbar window it won't use it properly
(indexing problem), and if I use the last (highest index number) designation, 1.35 will create a next-higher index number and attempt to assign that. Once one of these gets in my ade file the file is corrupt and I can't fix it. I found I can work around by creating taxiways without trying to set the proper designation, and then editing the taxiway property sheet once the taxiway segment is complete to select the proper designation as long as I don't attempt to use the last designation. So far that seems to be working (no errors in ADE and it will compile).

scott s.
.

 

[scruffyduck]

Thanks Scott. I will spend some time looking at this problem. As far as I know we have not changed the code related to taxiway designators since the first release so it must relate to some collateral code. So far we haven't managed to replicate it. If you do get an attempt to use an index higher than the last one in the name list then adding a new designator seems to be a work-around.

 

[scott967]

OK. This problem is 100% repeatable for me. I do this:

1. Open a stock airport, xml airport, or bgl airport (doesn't matter). For example, KACK (selected at random).

2. In the toolbar "Taxiway name" window, open the drop down list and select the last taxiway name (not the runway links which are shown at the very bottom. For KACK, this happens to be the SECOND "F" It appears MS defined two different names, both "F". One is 6 and the second is 7 This is inmaterial to the problem though). So "F" should appear in the window.

3. Select the taxi link tool and create a taxiway by click and drag.

4. Select the pointer tool. Hover over the just-created taxiway, and the yellow pop-up box will show:
Designator:

5. Select the taxiway. RMB to get the context menu and click the "Show XML" menu item. The xml is:
<TaxiwayPath
type="TAXI"
start="56"
end="57"
width="30.0M"
weightLimit="0"
drawSurface="FALSE"
drawDetail="FALSE"
surface="ASPHALT"
name="8"
/>

Name 8 does not exist in the airport (7 is the highest defined taxi designator).

Any attempt to do anything with this taxiway except delete will crash ADE.

6. Instead of selecting the last taxi name in the window, if I select any other taxi name the taxiway will created, but the designation (and xml) will be for the next numerically higher taxi name, not the one showing in the taxi name window.

scott s.
.

 

[scruffyduck]

Thanks Scott - I can confirm that is repeatable. I will have a dig into what is going on.

 

[scruffyduck]

I have found the problem and it will be fixed in the next update. In the meantime the workaround is to create taxi links with no designator showing in the drop down box and then adding the designator later