w9nwrwi

Colin, Looks like you might have a good start on a topical collection of aircraft. You might enjoy: http://stampbears.net/thread/2280/aircraft-stamps-world If you decide to persue it, you will find tons of info about all aspects of it on the net. It can become addictive in your search for new material. Chuck

Excellent Jan, Worked as you described, and I thank you AGAIN... Will copy and paste to the .org so others may, like you say, benefit. Chuck

Did not have any luck at the .org to my question so will try here. I want to correct some signage errors which have been showing up in Log.txt, in this case at ESSV, Visby. Wed 1.3 is open, I select apt.dat (within Custom Scenery/Global airports) and then select ESSV within WED. All is good, signs, runway, etc (no hangers, aircraft) go to the hierarchy panel on the right. I make the changes to the signs, run a Validation, and get the all ok. Since we are reminded from the Gateway instructions to also include the DSF for the airport, I select the DSF for ESSV and it is inserted into the WED Hierarchy panel. so far so good. Now I run another Validation and get the "You cannot export airport overlays to the X-plane Gateway if overlay elements are outside airports in the hierarchy" alert. Looking at the Hierarchy panel that makes sense since I now have two major items in the panel, Visby and the next one way below the runways, signs, etc. sits the Earth nav data\ file that I was supposed to send also to the Scenery Gateway. Of course since I have the hierarchy alert it is not going to go. I am doing something wrong, but I sure can not figure it out. Without the DSF I could send in the sign changes but not both (apt & dsf) at the same time. I assume that Gateway needs both at the same time? With both APT data and DSF data in the hierarchy pane panel, how do those of you who have submitted proceed with your inputs? Thanks for any help, Chuck

WED 1.3 is available here: http://developer.x-plane.com/tools/worldeditor/ WED 1.3 Manual is available here: http://developer.x-plane.com/docs/scenery/worldeditor-wed-manual-v1-3/ Chuck

MRD, If you cannot find KPIA at the various X-plane sites you might want to try your hand at WED. http://developer.x-plane.com/tools/worldeditor/ KPIA might be a bit much if your just starting out, might want to try a small one first. Chuck

Very nice John, Just what I was trying to get. Looks good. I appreciate your work and support of your products in such a timely manner.. Always someting to pique our interest. Thanks, Chuck

I might add that in your next post you tell us what your computer specs are. RAM, GPU type and VRAM in it, etc. Will help folks to determine if your system will handle your xplane Rendering settings, and provide a base for folks to help you out. Chuck

Cosmo, I find this one quite usefull: http://www.xflightplan.com/ Chuck

Nils, I have had good luck in the last few weeks using Lizard Tech GeoViewer. Get your airport from the National Map site as a JP2 and GeoViewer will export it to a file as a Geotiff. Few mouse clicks and its done and ready as your overlay. Chuck

Ben, If your still pondering my trouble with the Gizmo you can close it out. Between swapping Gizmo versions around I ended up with nothing working. Did a complete re-download and install on the DC-3 1.4 and all is ok. I will leave it alone. Thanks for your interest in the trouble. Chuck

Ben, tried a reinstall of the new Gizmo and still no joy with the DC-3. Here is a copy of Log.Txt and Gizmolog.txt Log.txt GizmoLog.txt

Windows 7

Ben, I removed the old Gizmo64 and unzipped and installed the new one. The DC-3 (wheel variant) in my case does not now present True Air Speed, no Vertical speed, no 2 minute turn, altitude indicator reads zero on the ground, no engine start switch toggle and Magneto switch will not function. Removed the new Gizmo and reinstalled the old Gizmo and everything works fine. Do not see any other complaints here so maybe I did something wrong. Install of the new Gizmo was just a basic unzip and install in place of the old Gizmo, old gimzo moved out of plugins first of course. I should of copied the log.txt and gizmo.txt when I had the new one installed but it slipped my mind. Chuck

Thanks for the response Cameron, I was not aware of the issue of tuning being view dependent. That sure can run the aggravation factor up and I hope that LR will come up with a fix at some point. Will operate then under those conditons and requirements. Chuck

Hi Angelo, Well I took your "view" advice and it worked, both sides. I found that I must be looking at an angle and not right on it. A frontal shot and it will not work. Well, I will have to accept that, but it is strange. I got the Left Magneto to engage finally, but it took a lot of manipulating. If I remember right it was view sensitive also in some manner, kind of hard to explain when the repeatability is position sensitive or so it seems. Anyway, thanks for your hints, they are appreciated. Chuck