Where to find the *.ini file.....?
Does anyone know where I can find the *.ini file to edit the below?
'0' is the default value and is compatible with the Honeycomb hardware. Changing that manually to '1' (make sure the aircraft isn't loaded at the time) will provide compatibility with the TCA hardware.
Do I have to uninstall the old version first to install the update?
Or can I just install over the old version?
The location of the ini file depends on whether you are using the MS Store or Steam version.
With my MS Store installation it's here:
@martyn the newest version 0.1.2 does NOT contain the lines [HARDWARE]
THR_LATCH=0 in the INI file. Is the file JF_146? because all that is containted there are these lines:
I have uninstalled and reinstalled the 146 twice today and checked the file that says version to confirm I have the 0.1.2 installed. I am using steam version.
Yeah, I don't see the lines "[HARDWARE]" either...maybe you need to add them?
With that said, what does this actually do for your hardware? I own both the Bravo and Airbus TCA throttles, and I'm currently using the TCA with no line for hardware in my .ini. Seems to be working fine right now after I turned the reverse detents off on my TCA throttle.
@Martyn Can you add some clarity here on what this actually configures?
@foxtrot-ostrich Based on the version number shown there, that is the INI file found in the aircraft package folder and not the one in the 'work' folder. The Steam version should be found in C:\Users[username]\AppData\Roaming\Microsoft Flight Simulator\Packages\justflight-aircraft-146\work\
'0' is the default value and is compatible with the Honeycomb throttle levers. Changing that manually to '1' (make sure the aircraft isn't loaded at the time) will provide compatibility with the TCA throttle levers.
It was added due to the two types of throttle lever having opposite behaviour for the SET ENGINE 1/2/3/4 FUEL VALVE control assignments, causing engines to shutdown. If you don't have that issue then I'd ignore this.
@foxtrot-ostrich That's just how the read/write folder structure exists in MSFS, but you can ignore the version in the aircraft package folder and just make any edits to the version in the 'work' folder, as that's the version that the aircraft will use.