Hi. Thank you for this really fast response. I found the problem: As soon as I toggle the overlay image in the background to “invisible” (with the “eye” icon), I am able to select single nodes of my taxiway.

I don’t know why it does not work. The bezier curve must be from an airport entity though, not from some scenery element.

I downloaded WED 1.1r1 and have I problem with it (Windows 7 x64): I am not able to select a line segment of a bezier curve. The documentation says on page 19 (“Markings & Lighting”) that one has to select the node at the beginning of a segment in order to apply markings for this segment. Unfortunately, this does not work for me. I can click and drag the single nodes of the bezier curve, but WED does not display the attributes of the nodes/segments. I always displays the attributes of the whole shape. So I cannot add lighting to just one segment of the shape.

Do you have any hints for me?

Cool, this feature may come in handy

It lets you control which rendering setting your objects appear at. In older builds, ALL custom objects appeared ALL the time (as long as objects were not set to none).

You can now set some of your custom object placements to only appear at higher rendering sttings.

So for example you can add a lot of static planes to an airport, but set some of them to only appear at “insane” objects. Now your package is not a framerate killer because users can “turn down” the complexity.

I think I understand the problem, but I am still not quite sure how you can solve the problem better than us by replacing our UI. If the proble with our UI is that it “breaks immersion” by putting a menu on screen, where in real life can you possibly put any ATC UI (other than voice recognition) that would be that much better. Having ATC on your FMC isn’t realistic either. To me the only complete solution is to fly VATSIM so you can use strictly voice transmissions. (And even then, if you hit a text controller, you are still stuck.)

Hi Ben / Chris,

For us people building full scale cockpits (i.e. see http://www.fransedano.net), it’s completely awkward to use any kind of keyboard, mouse, on screen texts… We are looking to replicate a plane, not a computer! So, the goal is NOT to have the ATC text on screen AND interact with it by some other means (i.e. pushbutton on Yoke). It’s fairly easy to map yoke pushbutton to execute any X-Plane command. But it’s not so easy doing it “blind”. i.e. “readback transmission” is going to be always first option in the menu? Can it be moved? How can I know if the controller got the readback or not?

So, we are asking for some dataref providing us such information. Having a command for every available option (with a dataref telling us if cmd is available or not) would be a solution. Another solution, the one we use for FMCs is to map each of the window lines to a different dataref, so we can read them..

Thanks again for the great work you guys are doing. Just having this conversation and listening to requests makes all the diference 🙂

Hi Fran,

Wait, what are you trying to automate? Is your goal to:
– Provide a way to “do” all of the things you can do in the UI from your cockpit hardware or
– Something else??

Hi Chris,

How can I read list of options available via dataref, then? Without knowing available options, any automation is going to fail. Also, can I use the cmd keys even if ATC window is disabled via dataref? And, moreover, how can I know if entry window is enabled or not? Sure “enter” will enable or disable, but I need to know the current state, otherwise I’ll go out of sync soon.

Thanks!