Comments on: Giving X-Plane More Info About Aircraft

By: Tyler Young

Tyler Young — Mon, 22 Jun 2015 19:12:27 +0000

In reply to paolozamp. This will be present in the next beta. :)

By: Tyler Young

Tyler Young — Mon, 22 Jun 2015 17:00:21 +0000

In reply to Andrew Cook.

Hi Andrew!

We’re aware of this issue, and we’re looking into it now. Should be fixed in the next beta. 🙂

Edit: Doh! Looks like you already filed a bug report. Sorry for the duplicate response from me!

By: Ben Supnik

Ben Supnik — Wed, 17 Jun 2015 14:20:51 +0000

In reply to Chris R.. My view is that the current "match the file system" rule is extremely unfriendly; better would be to find the matching plane by meta-data, or even by file signature.

By: Chris R.

Chris R. — Tue, 16 Jun 2015 23:43:18 +0000

I am wondering if the file arrangement would have any effect on Multi-User flights. Right now, we have to have the same aircraft doubled and labeled differently but exactly the same as each other machine for this to work. So if 3 of us typically fly together, we all three would need an exact copy of the aircraft in the same fourfold/directory structure. This is killing drive space and right now we need to remain with custom folder structure to make sure we have the same as each other. If this sounds confusing, it is but I can try to make it clearer.

By: Ben Supnik

Ben Supnik — Tue, 16 Jun 2015 13:46:40 +0000

In reply to Peter Meininger.

Remember though, liveries are supposed to be aesthetic – it’s not a general purpose ACF templating system and they’re not supposed to mess with systems or performance!

By: Peter Meininger

Peter Meininger — Tue, 16 Jun 2015 00:11:55 +0000

In reply to Ben Supnik.

I think I remember that RFC + the initial discussion which file types commonly encountered in an aircraft folder are suitable for a livery folder. It sometimes does feel like 6 million years.

What about a text file with a few lines like:
P acf/_callsign speedbird P acf/_tailnum G-ABCD

I could imagine a few other useful airline specific overrides as well 🙂

cheers
peter

By: Ben Supnik

Ben Supnik — Mon, 15 Jun 2015 21:22:42 +0000

In reply to Peter Meininger.

Hi Peter,

There’s an RFC for that from about 6 million years ago…I think the idea was to have an .ini file that let liveries over-ride key meta-data items. It wouldn’t be hard to do this for any of the key-value pairs that drive the aircraft meta-data screen.

By: Peter Meininger

Peter Meininger — Mon, 15 Jun 2015 19:21:54 +0000

In reply to elios.

It would also be nice if tail-number and callsign could be customised for every aircraft livery option. The current format which supports only one tail-number and callsign per acf file requires users to modify the aircraft file (possibly messing it up) or duplicating the whole aircraft folder which defeats the liveries sub-folders.
It might be the perfect time to think about a solution to that issue while you’re at it. 🙂

cheers
peter

By: paolozamp

paolozamp — Mon, 15 Jun 2015 07:49:54 +0000

I belive that is necessary a flag for Ultra Light aircrafts…….

By: elios

elios — Mon, 15 Jun 2015 06:32:51 +0000

a way to change tail numbers in the sim would be nice for VATSIM and Pilotedge