Sign in to follow this  
Old_As_Dirt

A funny thing happened in WED

Recommended Posts

Actually, it was not funny.  It nearly caused me to tear out my hair and I don't have much.  

 

Using the default runway/taxi area in my home airport, I built my own airport using the default tools (no OSM) and everything seemed great.

 

Upon landing and turning off onto the first ramp (off 34 KROA if anyone is interested) I stayed in the middle of the ramp and very shortly after entering the main pad, the aircraft hit a wall - invisible.  

 

The only changes I had made was taxi lines so I removed them and, on the first landing after that, thought that had fixed the problem, but the next landing proved I hadn't.  Nothing there, but a crash.  I found that if I hugged the left side of the ramp, it wouldn't do it.

 

After hours of trying to figure it out, I found that one of the points in the line drawn on the side of the pad (taxiway) was one of those with a arrow-dot-arrow (don't know what you call them).  I highlighted it and removed it and the problem went away.  Seems there should be a separate command to install (or not) these trouble-makers. 

 

I hope this might help someone if they have a similar problem with WED.  I don't know enough about the program to know why these things just randomly show up, but this one was a default one in the program and it really caused a problem.  I'm sure there are many others around the X-Plane world causing similar problems for my friends.

 

John

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi John,

 

You not alone, many months ago same thing happened to me. Very strange feeling, taxing along and all of sudden a crash and smoke. Also took me some time to figure it out.

the arrow-dot-arrow you mentioned is a node to initiate a Bezier (sic?) curve if memory serves correctly.

 

I guess one should investigate the mantis bug reporter for WED and see if its been reported, or if it even is a bug or maybe a stupid move on our part.

 

Chuck

Share this post


Link to post
Share on other sites

 

 


r if it even is a bug or maybe a stupid move on our part.

 

In my case, stupid probably applies!   :unsure:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this