Hi, Im currently working on improving an A320 Neo model. For test purpose it’s
relying on the current FBW A320 systems to being able to fly. T he
Problem is: When changing values in the flightmodel.cfg e.g. Contact point
position or wingflex scalar, the engines will no longer function. When
started, the the engines will creep up to 3-7%N1 (N2 is well enough above for
Ingnition engaged) but will never run fully or produce thrust.
The APU is still working, and
doesn’t seem to be affected.
Changing back the values doesn’t fix the problem, the only fix is currently
replacing the modified .cfg with the original one. (But it’s not a solution
currently since I need the changes).
This happened once before and was fixed - seems to have become ‘unfixed’
again. I have also noticed that, if using the aircraft editor to adjust the
flightmodel.cfg only , then other .cfg files including the engines show the
timestamp of when the flightmodel was saved.
Hi, Could you send us your aircraft sources before and after modification in
order for us to investigate your issue ? Thank you in advance.
Be careful as the A32NX uses custom engine code (wasm), and is generally not
intended or tested for use with the aircraft editor. I suggest using the Asobo
A320 as your base instead.
This can happen for good reasons and is driven by what’s defined in the
FileDefs_AircraftEditor.xml file in the fs-devmode official package. For
example, you can have legacy parameters that are no longer used in MSFS 2020
and the AircraftEditor will comment them out. Or you can have new parameters
that are considered as mandatory and will be added and set to their default
values. So using a diff tool to compare your engines.cfg before and after
modification can help identify the issue here. Regards, Sylvain
Thank You for your response! I actually found out, that when changing values
in the aircraft editor, the editor will add some additional lines which didn’t
existed in the original .cfg before. Changing values outside of MSFS fixed the
problem and systems will still working correctly.
That’s good to know. Could you tell me which added parameters cause this
problem so we can fix it ?
Resaving the cfg. through the Aircraft Editor changes mostly the format only
(something like: 0.0 becomes 0). But it’s adding a few lines as shown in the
pictures.
When Resaving it only effected
the flight_model, engines an systems.
But as I mention changing the
values outside will fix the problem. I didnt make out any changes in the
systens and engines beside from the reformating.
