I've got two cabin configurations for a CRK that both have the same number of seats in Y and C class. One configuration is the pre-patch version. I'd like to delete the old pre-patch configuration but I can't do it without first allocating the new configuration to all the aircraft that are using the old configuration.
How can I find out which aircraft is using the old configuration?
You can just click the "tick" box for the aircraft you want to reconfigurate it. If your configuration for the aircraft remains unchanged, then you don't have to worry about "reconfiguration" as it doesn't spend any penny or dollar in your balance. It will change to the new configuration without any reduction (only in the case that you have same configuration for both previous & latest patch).
If there is any increase or change in the configuration, the money will be deducted (if cost increases) or refunded (if cost decreases) to your balance.
And once that is done what Peter-MTA suggested then you wait for 3 days and then you can delete the old Config so you hav no truble anymore ;)
ok, that works but it seems a kind of clunky way of doing things. Why not have the name of the CC displayed as a column item on the fleet management page? In fact, why not make it a sortable column, then you could get all the CCs with the same name grouped together.
I do this with fleets, splitting them up into: Aircraft Type -> Central Location -> Seat Configuration. Makes it really simple to find specific aircraft.
We should have a sorting feature...
Find Aircraft by Type, seat config, etc.
Some things you just have to do yourself.
There is a "sorting" feature for fleet type.
Where?
And is it certain what you said, if you try to apply same seat config (number and type of seats) on the plane that already has that config, it will not charge you?
Where?
And is it certain what you said, if you try to apply same seat config (number and type of seats) on the plane that already has that config, it will not charge you?
Absolutely.
Absolutely.
Well, be careful with that: It won't charge you only if the config that is being replaced is an old config, i.e. pre-patch. If you replace a post-patch config it will charge you, even if it's replaced by an identical config. Or at least that's how I understood it.
Well, be careful with that: It won't charge you only if the config that is being replaced is an old config, i.e. pre-patch. If you replace a post-patch config it will charge you, even if it's replaced by an identical config. Or at least that's how I understood it.
I would like to know definitive answer about replacing "new new" config with the same "new new" one ... a player in this thread http://community.airlinesim.aero/topic/6289-new-cabin-configurations/ reports he was charged indeed, when accidentally replacing the "new new" config with "new new" one .
So let's just put this uncertainty to rest. I will create a dummy airline and change same config and see what happens.
You'll be charged twice. If you replace a valid cabin configuration with another valid cabin configuration, you'll be charged, plain and simple.
OK, so here are the findings:
Imagine that each and every configuration ever created under your airline receives a Configuration ID.
If you apply the very same configuration (same Configuration ID), you are NOT charged.
However, if you create the same configuration (same number of seats, spacing, etc.) but as a different Configuration ID, you WILL be charged.
CHANGE CONFIG ---> SAME CONFIG ID? ---> YES ---> DO NOT CHARGE
|
\|/
NO
|
\|/
CHARGE
P.S. That's why it's good to put a note for each AC like Config ID ... because you now can rename configs, just add your "internal" config designator to config name, and add that internal config designator to aircraft notes. I know it's difficult to do for all those already flying aircraft, but for each config you put on a plane form now onwards, write it down somewhere ...
Some things you just have to do yourself.
I thought that was what we have computers for.... :lol: :lol: :lol:
I would like to know definitive answer about replacing "new new" config with the same "new new" one ... a player in this thread http://community.airlinesim.aero/topic/6289-new-cabin-configurations/ reports he was charged indeed, when accidentally replacing the "new new" config with "new new" one .
So let's just put this uncertainty to rest. I will create a dummy airline and change same config and see what happens.
I tried it yesterday and it seems to be true for "new" "new" configs. No idea about "almost new" "new" or "almost the same amost new" "new".
We should have a sorting feature...
Find Aircraft by Type, seat config, etc.
or just imagine you could write your own sql code.. select aircraft from fleet were aircraft.cabinconfiguration ="ABC" order by aircraft.registration, aircraft.age;
or how about sql update fleet set aircraft.cabinconfiguration = "XYZ" where aircraft.type = "B738" and aircraft.cabinconfiguration = "ABC" ; delete * from cabinconfigurations where name = "ABC"; - thereby reducing hours of work to two SQL statements.
I just got these message today with the words "Please remove all your old seating configurations and change them to new ones by 2014-03-31"
Does anyone know what happens if you don't do the update in time?
P.S. That's why it's good to put a note for each AC like Config ID ... because you now can rename configs, just add your "internal" config designator to config name, and add that internal config designator to aircraft notes. I know it's difficult to do for all those already flying aircraft, but for each config you put on a plane form now onwards, write it down somewhere ...
I thought that's what we have computers for.. it sounds like it would be a great job creation scheme for a real airline, have people typing stuff in on computer screens and then writing down what they typed in on bits of paper so they can type it in somewhere else and then file the bits of paper, duuhh...