Version 1.39 Feedback

[jvile]

Jon: I hope you don't mind a few questions.

1. While in approach mode, if I create a new T_WP the dialogue box indicates (with a red exclamation point) that the WP already exists in the region. This is the case for any WP I add...even my name Is this correct? I would think the warning would only show if you are actually duplicating (second time around).

I have seen this before. I normally exit and restart ADE and the exclamation goes away. It seem to get stuck from time to time.

2. Also, is there a way to insert a leg into an approach? I ask because several times I created the wrong leg type and I was required to delete the string of legs and start over.

At one time we could add the leg and then drag it with the mouse up to its correct position. I do not see that working so Jon will have to respond.

3. While in approach mode, when I create new approach legs or make changes to existing legs I'm not always given the opportunity to save my work.

I see the same thing but 'save as' always allows me to save.

4. Why don't the existing VORs show up in Approach mode? One example is KIAD. I can't see (graphically) MRB or CSN.

At some point in time you may have loaded ADE from a saved XML or BGL file. This will cause you to loose certain NAVAIDS since we save those as per the .ade and not always per the GRID

This is good feedback since you are working with a beta version that helps us to find these small issues. I am still looking for the appr altitude issue. That is a very important piece of data that must be found on why it is getting deleted. I had the same problem with WSSS after writing all new approaches for for the additional runway.

 

[scruffyduck]

1. While in approach mode, if I create a new T_WP the dialogue box indicates (with a red exclamation point) that the WP already exists in the region. This is the case for any WP I add...even my name Is this correct? I would think the warning would only show if you are actually duplicating (second time around).

I have not seen this. We will see if we can replicate it

2. Also, is there a way to insert a leg into an approach? I ask because several times I created the wrong leg type and I was required to delete the string of legs and start over.

Add the leg - it will appear of the bottom of the list depending on whether it is an approach, missed approach leg and so on. Select it and use the U key to move it up to the correct position in your list. D will move it down. You cannot move it outside its own group - so for example you can't move a missed approach leg into the approach legs.

3. While in approach mode, when I create new approach legs or make changes to existing legs I'm not always given the opportunity to save my work.

This is a known issue and is on the list

4. Why don't the existing VORs show up in Approach mode? One example is KIAD. I can't see (graphically) MRB or CSN.

As far as I know all existing navaids should show up. Are they in the navaid list?

 

[scruffyduck]

Jim we cross posted. I will treat the terminal waypoint error as confirmed

 

[jvile]

I see that we crossed posted Jon

I forgot about the U and D key even though I have used it.

I have seen the exclamation mark get stuck on adding T_Waypoints but it did not stop me from adding them anyway.

 

[kagazi]

Jim/Jon: Thank you for the explanation regarding the U and D key; this will come in handy as I have some cleaning up to do.

kagazi

 

[Daveo]

First basic airport from scratch worked out very well with new ILS approaches. Did a flawless ILS landing in heavy snow and near zero visibilty. I noticed though the scrolling using the arrow keys in pointer mode seems to hang up once in awhile and instead of scrolling, the program starts running through the menu selection buttons and drop down menus instead. Also happens with the mousewheel. Another thing is holding the middle mouswheel button down to drag the screen around also seems to function intermittenly also. I don't know what I click on to get it back working again. Sometimes I just save the airport and then it works again. Other then that as new as I am to playing around with airports and making mods the new version seems to work very nice.
Where is the donate button??

 

[kagazi]

Jon: In my KIAD project I (manually) attached a beacon (rotating w/glow at night) to the new tower. If I save the xml back to an ade I lose the rotating beacon - the new xml does not contain the "attach" code. My xml does not contain the extensive land class poly work so I need the ade if I plan to revise in the future. At this time I can get around it by simply using the sdk2 compiler to compile the xml w/beacon separately.

I'm wondering if I'm doing something wrong or if ade simply won't support the inclusion of the rotating beacon at this time.

Thanks,
kagazi

 

[scruffyduck]

Jon: In my KIAD project I (manually) attached a beacon (rotating w/glow at night) to the new tower. If I save the xml back to an ade I lose the rotating beacon - the new xml does not contain the "attach" code. My xml does not contain the extensive land class poly work so I need the ade if I plan to revise in the future. At this time I can get around it by simply using the sdk2 compiler to compile the xml w/beacon separately.

I'm wondering if I'm doing something wrong or if ade simply won't support the inclusion of the rotating beacon at this time.

Thanks,
kagazi

Sorry - that is the problem. ADE does not support it so has probably stripped it out. We plan to include beacons and effects in a later version

 

[Daveo]

Im pretty sure I havent botched anything up as I've done this before with previous versions but the progressive taxi doesnt seem to be functioning on a new airport.


**EDIT***
PT works fine on incming AC but not outgoing. I read an old post on this from 2007 and I don't think its an altitude problem as ADE writes the new ALT bgl to the scenery\world\scenery directory. I'll test later with a departing airliner that has an actual parking code and and assigned gate that worked ok on arrival and see if that works. First test was with a Mooney Bravo.

 

[buedi]

Maybe I found a Bug.
When in Approach Mode I added a Missed Approach Leg. I switched the Leg Type from AF to VR. When I change the Value in Rec Fix Type nothing happens. It´s always showing the T_Waypoints. When I switch i.e. to VOR it still shows the T_Waypoints.

BUT:
Add a Missed Approach Leg. When Leg Type is AF change Fix Type to VOR and then switch Leg Type to VR. Then the list still shows the T_Waypoints, but the previously selected VOR is still in the list.


Another one:
I added a Leg Type VR. When compiling the Airport

INTERNAL COMPILER ERROR:  #C2577: 

ERROR:  This LEG is missing some of this required part (000009C1 00000BC1)
        Missing:  Theta, 
INTERNAL COMPILER ERROR:  #C2031: Failed element parse <Leg>
INTERNAL COMPILER ERROR:  #C2032: XML Parse Error!  Element tree follows:

ERROR: <FSData 
ERROR: 	version = 9.0
ERROR: >
ERROR: 	<Airport 
ERROR: 		country = Germany
ERROR: 		state = Bavaria
ERROR: 		city = Allgau
ERROR: 		name = Allgau
ERROR: 		lat = 47.988889105618
ERROR: 		lon = 10.2394446730614
ERROR: 		alt = 629.107M
ERROR: 		magvar = -1
ERROR: 		trafficScalar = 0.7
ERROR: 		airportTestRadius = 5000.0M
ERROR: 		ident = EDJA
ERROR: 	>
ERROR: 		<Approach 
ERROR: 			type = ILS
ERROR: 			runway = 24
ERROR: 			designator = NONE
ERROR: 			suffix = 0
ERROR: 			gpsOverlay = FALSE
ERROR: 			fixType = TERMINAL_WAYPOINT
ERROR: 			fixRegion = LS
ERROR: 			fixIdent = OGROB
ERROR: 			altitude = 1249.68M
ERROR: 			heading = 238.92
ERROR: 			missedAltitude = 1554.48M
ERROR: 		>
ERROR: 			<MissedApproachLegs 
ERROR: 			>
ERROR: 				<Leg 
ERROR: 					type = VR
ERROR: 					recommendedType = VOR
ERROR: 					recommendedRegion = LS
ERROR: 					recommendedIdent = ALD
ERROR: 					magneticCourse = 327
ERROR: 				>
ERROR: 
INTERNAL COMPILER ERROR:  #C2607: Compilation errors detected, compilation failed!


Parse complete!

But in VR there´s no Theta field, so I can´t add any values to it. Is this a Bug or am I doing something wrong?


Kind regards.

 

[jvile]

VR leg is missing Theta and Rho

The VR is also missing the following three attributes that have to be filled in. We are woking to get these attributes to show in the proper leg types.

recommendedType = VOR
recommendedRegion = K6
recommendedIdent = MRB

 

[scruffyduck]

I have that issue on the fix list

 

[spud88]

Greetings!

First of all awesome job on designing ADE. I really do love this editing tool.

I started on a project to add the new 5th runway to KATL (10/28) and ended up creating it from scratch. I went ahead and just added the ILS and let ADE create the approach and when I went to test it, everything worked great for that runway.

I did notice though after letting the simulator play out for about 45 minutes that no aircraft were utilizing the default ILS approaches for the original 4 runways. About half of the volume of traffic should utilize (08L/26R) for landing normally.

I saw that there were several aircraft crawling across the ground miles short of the runway.

I'm guessing this is the same error found above with KIAD where the default approaches are zeroed out.

I also am having a problem with the feature that lets you save generic buildings from one airport to use in another. I'm doing a side project where I'm modifying KMLB and I decided to try this out with the terminal building from KEYW.

After I add the building to KMLB, the program begins to lag heavily and I have to close it out and restart. I'm not sure what is bogging down the program when I do this. I opened up KATL and tried adding the KEYW building and got the same problem.

I've attached my purely fictional KATL file along with the terrain modification done using SBuilderX.

 

[jvile]

I did notice though after letting the simulator play out for about 45 minutes that no aircraft were utilizing the default ILS approaches for the original 4 runways. About half of the volume of traffic should utilize (08L/26R) for landing normally.

You have 2 ILS approach codes for 8L. THe Stock approach and you hand made a second ILS using new T_Waypoints IAF G5YE and FAF AKMWL.

You cannot make a ILS approach when one already exist in the stock database. This confuses the AI Plane Traffic and ATC.

Some of your approach Alt= have become zero but not all of them.

 

[spud88]

Greetings!

Sorry for the slow reply.

I had tried to troubleshoot the problem by overlaying ADE ILS approaches over the default, but that had caused a compiler error. I ended up creating quite a mess with the approaches.I forgot to delete the ADE ILS for that runway.

I'm still having the AI land way short of my runways due to the zeroed approaches. I'm sorry to ask such a dumb question, but I can't figure out for the life of me what I need to edit in ADE to fix this since I'm not very familiar with approaches.

If I can figure out what to edit, I'll pull up the stock KATL and use that as a reference.


Thanks for your time,
Drew

 

[jvile]

Get the SDE utility off Jon's web site.

Use it to open a airport like KATL. In the rightside window go down to the approach code section. Starting with the first approach header which is a

<Approach
type="ILS"
runway="08"
designator="LEFT"
suffix="0"
gpsOverlay="FALSE"
fixType="TERMINAL_WAYPOINT"
fixRegion="K7"
fixIdent="FF08L"
altitude="5000.0F" <<<<<<<<<<<========== you need this altitude
heading="89.8867340087891"
missedAltitude="3500.0F">

Now open your KATL .ade and go into the approach mode.

In the drop down menu Approaches choose open and select the R08L ILS. A tree of legtypes will show in the right window. Select the very top part of the tree which says R08LEFT:ILS and the property window will open. At the bottom of the property window you will see

Appr Alt Feet 5000

if it says 0 then change to 5000.

do all the remaining approach headers the same way.

 

[spud88]

Thanks for the info

 

[spud88]

Jim,

I went back and edited the approaches for KATL and everything works fine now. Thanks again for the help.


I am having another problem though, and I'm not entirely sure its strictly related to 1.39, but I figured I'd post it here anyway.

I've been having trouble adding jetways after I started using 1.39. I edited the stock Colorado Springs Airport (KCOS) and added some jetways and I can't get any of them to display in FSX.

All the other mods I made such as new parking, and some library objects display fine, but its just the darn jetways.

This is my ADE file:

And this is what I see in FSX:

I did some searching through these forums and went back to make sure that all jetways were assigned to the proper parking spot, as well as checked for any duplicates. I also deleted all of the original parking and added it back. After that didn't work I deleted all of the jetways and added them back in with a setting of Dense and changed them all to (Gate A) due to the possibility that FSX still was seeing the original jetways from the stock to no avail.

I'm out of ideas on how to troubleshoot this

In FSX I have my scenery complexity set to extremely dense, and my autogen scenery also set to the same.

Thanks for your time,
Drew

 

[GHD]

Hi Drew,

Using your bgl they show fine on my system:



Do you have your scenery complexity set correctly in FSX?

 

[glottis]

spud88

just have a look and see if you have another bgl file
for the same airport in the add-on scenery/scenery folder as you well may have duplicates