I have the livery that I want to use but I would like the sim to use my camera.cfg and my flight_model.cfg file with the livery.
Just coping the files into my livery folder and running MSFSLayout does not seem to work.
Any clues appreciated.
tia
Try copying the camera file into the Microsoft Flight Simulator / SimObjects / Airplanes folder for the plane you want, assuming there is a folder present for it.
Sorry, I just saw that you have a flight_model.cfg file too. The only way I know to make that active is to overlay the one in the plane’s “main” directory (I hope you get what I mean - at least that’s the way it works for me). Obviously you want to make a backup of that file in case something doesn’t work right.
That should work. For example, here is a third party mod for the JF Warrior.
Note the path at the top. Dropping the cameras.cfg file , at the same level as “flight_model.cfg” , should make that camera file override the default one.
I think it used to work but I can’t get it to work on my machine
Do you know the “tree” command? If so, could you run it on your mod folder, and post here?
This is what one looks like for me:
tree z_BS_Baron_fm_mod /F
D:\FLIGHT SIMULATOR\COMMUNITY\Z_BS_BARON_FM_MOD
│ layout.json
│ manifest.json
│
└───SimObjects
└───Airplanes
├───bksq-aircraft-analogbaron
│ │ flight_model.cfg
│ │
│ └───model.base
│ AnalogBaron.xml
│
└───bksq-aircraft-analogbaronturbo
flight_model.cfg
How is this…
C:\USERS\MEHOG\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALCACHE\PACKAGES\COMMUNITY\ZZZ_LONGITUDE_PW
│ layout.json
│ manifest.json
│
└───SimObjects
└───Airplanes
└───PW_Longitude
│ aircraft.cfg
│ cameras.cfg
│ flight_model.cfg
│
├───MODEL.PW
│ model.CFG
│
├───TEXTURE.PW
│ LONGITUDE_AIRFRAME_ENGINE_ALBD.PNG.DDS
│ LONGITUDE_AIRFRAME_ENGINE_ALBD.PNG.DDS.json
│ LONGITUDE_AIRFRAME_FUSELAGE1_ALBD.PNG.DDS
│ LONGITUDE_AIRFRAME_FUSELAGE1_ALBD.PNG.DDS.json
│ LONGITUDE_AIRFRAME_FUSELAGE2_ALBD.PNG.DDS
│ LONGITUDE_AIRFRAME_FUSELAGE2_ALBD.PNG.DDS.json
│ LONGITUDE_AIRFRAME_LIVERY_ALBD.PNG.DDS
│ LONGITUDE_AIRFRAME_LIVERY_ALBD.PNG.DDS.json
│ LONGITUDE_AIRFRAME_UNDERCARRIAGE_ALBD.PNG.DDS
│ LONGITUDE_AIRFRAME_UNDERCARRIAGE_ALBD.PNG.DDS.json
│ LONGITUDE_AIRFRAME_WINGS_ALBD.PNG.DDS
│ LONGITUDE_AIRFRAME_WINGS_ALBD.PNG.DDS.json
│ texture.CFG
│ thumbnail.jpg
│ thumbnail_small.jpg
│
└───TEXTURE.PW-NEW
LONGITUDE_AIRFRAME_ENGINE_ALBD.PNG.dds
LONGITUDE_AIRFRAME_ENGINE_ALBD.PNG.DDS.json
LONGITUDE_AIRFRAME_FUSELAGE1_ALBD.PNG.dds
LONGITUDE_AIRFRAME_FUSELAGE1_ALBD.PNG.DDS.json
LONGITUDE_AIRFRAME_FUSELAGE2_ALBD.PNG.DDS
LONGITUDE_AIRFRAME_FUSELAGE2_ALBD.PNG.DDS.json
LONGITUDE_AIRFRAME_LIVERY_ALBD.PNG.DDS
LONGITUDE_AIRFRAME_LIVERY_ALBD.PNG.DDS.json
LONGITUDE_AIRFRAME_UNDERCARRIAGE_ALBD.PNG.DDS
LONGITUDE_AIRFRAME_UNDERCARRIAGE_ALBD.PNG.DDS.json
LONGITUDE_AIRFRAME_WINGS_ALBD.PNG.dds
LONGITUDE_AIRFRAME_WINGS_ALBD.PNG.DDS.json
texture.CFG
thumbnail.jpg
thumbnail_small.jpg
I’m not expert but I think that looks fine.
In the “aircraft.cfg” do you have the following set?
[VARIATION]
base_container = "..\Asobo_Longitude"
I’d be surprised if this were a bug, that you can create a livery, but it cannot contain a camara config as well.
[VERSION]
major = 1
minor = 0
[VARIATION]
base_container = “…\Asobo_Longitude”
;===================== FLTSIM =====================
[FLTSIM.0]
title = “Cessna Citation Longitude PW” ; Variation name
model = “PW” ; model folder
panel = “” ; panel folder
sound = “” ; sound folder
texture = “PW” ; texture folder
kb_checklists = “” ; Procedures/Checklist sibling file name
kb_reference = “” ; Reference information sibling file name
description = “TT:AIRCRAFT.DESCRIPTION” ; Variation description.
wip_indicator = 2 ; know if the variation is good to go or still WIP : -1=Disabled, 0=Rough, 1=1st Pass, 2=Finished
ui_manufacturer = “Textron” ; e.g. Boeing, Cessna
ui_type = “Citation Longitude” ; e.g. 747-400, 172
ui_variation = “PW” ; e.g. World Air, IFR Panel
ui_typerole = “Twin Engine Jet” ; e.g. Single Engine Prop, Twin Engine Prop, Rotorcraft, etc
ui_createdby = “Asobo Studio” ; e.g. Asobo Studio, Microsoft, FSAddonCompany, etc
ui_thumbnailfile = “” ; app relative path to ThumbNail image file
ui_certified_ceiling = 45000 ; service ceiling / max certified operating altitude (ft)
ui_max_range = 3500 ; max distance the aircraft can fly between take-off and landing in (NM)
ui_autonomy = 7 ; max duration the aircraft can fly between take-off and landing in (Hrs)
ui_fuel_burn_rate = 1800 ; average fuel consumption per hour (lbs/hr) - reminder: fuel density is ~6.7lbs per US gallon
atc_id = “N700-PW” ; tail number
atc_id_enable = 1 ; enable tail number
atc_airline = “” ; airline name
icao_airline = “”
atc_flight_number = “” ; flight number
atc_heavy = 0 ; heavy?
atc_parking_types = “RAMP” ; “ANY” / “RAMP” / “CARGO” / “MIL_CARGO” / “MIL_COMBAT” / “GATE” / “DOCK”
atc_parking_codes = “” ; Comma separated and may be as small as one character each
atc_id_color = “#191154” ; color for the tail number : i.e. “#ffff00ff”
atc_id_font = “” ; font for the tail number
isAirTraffic = 1 ; Is the plane usable for air traffic
isUserSelectable = 1 ; Is the plane selectable by the user
I never thought to ask. In your OP you said it doesn’t work.
Can you elaborate on what doesn’t work?
I assumed that your camera config didn’t work once spawned in with your livery, but is it perhaps more fundamental than that?
is that a forum issue. I see three dots in the base container variable.
1 Like
Better eyes than me! Yes, that should be two i.e. one folder up.
Fixed the 3 dots…still no dice
1 Like
That is correct the camera still is/was the default camera and the weights in the flight_model.cfg are also the default.
I know this used to work…
Does your livery work though? That would tell us whether the addon is being processed at all.
Are you getting your new textures.
1 Like
yes livery works
yes livery works
Talking to other devs, they say no can’t override camera.cfg.
However you could fake out the VFS by setting up your own version of the main aircraft folder.
WARNING — this is dangerous as you will affect the default aircraft and other liveries — WARNING
just create your own SimObjects/airplanes/Asobo_Longitude in the community folder and add the camera.cfg there.
I don’t recommned this for livery distribution, but for your own sim setup.
2 Likes
Before you do the above … dangerous thing.
Try going back to the main menu and rebuild your project there. Changing cameras and sounds need to to close the project and restart the flight.
This is what I have done in the past, or in some cases simply .bak the original file, and replace the default one with my own. Much less effort, and I’m not distributing anything so I don’t care how it gets done. 