If this is affecting other controllers I'll update the title accordingly.
Yes, I also have the error with the joystick from WINWING.
But since I always have to synchronise the levers with the TCA quadrant anyway (move completely once), this does not bother me with the joysticks.
With my configuration, it almost always happens when connecting controllers that usually 1 switch "jams", usually it is a switch in connection with view. Therefore, as my pre-start-routine, I move all switches.
It doesn't turn into "stop block" now, but it doesn't play my sound
No STOP-Cube is good.
Now you still have to add the lines of code for the call (event). I suggest looking in the Flugzeug.TMD to see how it is solved there with other calls.
I think you have the sounds in the wrong section, because they belong here:
<[pointer_list_tmsound][SoundObjects][]
>I like the STOP cube - especially if it doesn't get in my way when testing.
Speaking of testing, this could be something:
My current programming is hidden behind this flap:😆😎
Behind the flap is the REFUEL PANEL, with which each of the 8 tanks can be filled in an exemplary manner.
We also enable, deviating from the model, fast fueling and defuling at the bottom, so that each tank can be set to the individually desired fill level.
But it is time to be careful, because the fuel consumption by the engines is also simulated. If there is too little fuel, it can then come to the cold6dark state in the air.
To avoid this, air refuelling is planned.
My current programming is hidden behind this flap:😆😎
... Avoid using USB hubs as well...
Moin Jan,
on my MacBook, external controllers with USB C connecter only work if I connect them via a USB-C to USB-A hub.
Great that it already works.
I remember that at first I also had difficulty assigning reverse appropriately. I then reset the TCA quadrant and assigned reverse first and then throttle. However, the assignment can also be made in the gc-main.mcf via the keyboard.
I've been using Thrustmaster's various TCA products on my Macs since they've been around. And regardless of the product and the Mac, it always works plug%Play.
I just remembered that I initially had a Mac with a USC A-port. When switching to my Mac with USB C port, the controllers did not work with a USB C-USB-C cable, but only with the USB C-USB A cable plus USB A to USB C adaptor. Try it out if it's because of it.
I noticed you have MacBook Pro with Thursmaster, is there any driver you installed? For some reason, my stick does not work, AeroFly does not see anything. I even tried a 3rd party app and the OS does not see anything.
No, I don't have a driver, to my knowledge there is no driver for the Mac either. I just plug in all my controllers and they work.
I have now taken a closer look at the data on the A320 in the controls.tmd and in the subdirectory "base" in the system.tmd. With a closer look at your wish, I don't think it makes sense to change anything about these two files.
Therefore, I also looked at my gc-map.mcf on my Mac:
(1) SECTION [list_tmchannelmap][Channels][]
For me, the ThrustLevers are already separated by the menu Settings in the FS 4 into the two axes "X" and "Reverse 1" or "y" and "Reverse 2":
<[tmchannelmap][element][225]
<[string8u][FunctionID][TwinJetThrottle1]>
<[string8u][InputID][X]>
<[uint64][DeviceUniqueID][1234567890]>
<[string8u][DeviceIDString][TCA Q-Eng 1&2]>
<[bool][IsDigital][false]>
<[bool][IsValue][false]>
<[float64][Sign][1]>
<[float64][Direction][0]>
>
<[tmchannelmap][element][227]
<[string8u][FunctionID][TwinJetThrustReverse1]>
<[string8u][InputID][Reverse 1]>
<[uint64][DeviceUniqueID][1234567890]>
<[string8u][DeviceIDString][TCA Q-Eng 1&2]>
<[bool][IsDigital][false]>
<[bool][IsValue][false]>
<[float64][Sign][1]>
<[float64][Direction][0]>
>So nothing can be changed here.
(2) SECTION [list_tmdevicesetting][Settings][]
A possible change could take place here:
<[tmdevicesetting][element][4]
<[uint64][DeviceID][67568719]>
<[string8u][DeviceName][TCA Q-Eng 1&2]>
<[string8u][DeviceType][Throttle]>
<[string8u][DeviceMode][]>
<[bool][Enabled][true]>
<[bool][GamePad][false]>
<[float64][Sensitivity][0.5]>
<[float64][DeadZone][0]>
<[int32][Priority][0]>
<[list_tmdevicecalibration][Calibration][]
>
>I use the controller PFT-PUMA to fly helicopters and it has a fine adjustment in the Calibration line:
<[tmdevicesetting][element][2]
<[uint64][DeviceID][0987654321]>
<[string8u][DeviceName][PFT-PUMA]>
<[string8u][DeviceType][Joystick]>
<[string8u][DeviceMode][]>
<[bool][Enabled][true]>
<[bool][GamePad][false]>
<[float64][Sensitivity][0.5]>
<[float64][DeadZone][0]>
<[int32][Priority][0]>
<[list_tmdevicecalibration][Calibration][]
<[tmdevicecalibration][element][0]
<[string8][InputID][X]>
<[float64][Zero][-0.015]>
<[float64][Min][-0.1]>
<[float64][Max][0.045]>
>
<[tmdevicecalibration][element][1]
<[string8][InputID][Y]>
<[float64][Zero][0.002]>
<[float64][Min][-0.062]>
<[float64][Max][0.066]>
>
<[tmdevicecalibration][element][2]
<[string8][InputID][Z]>
<[float64][Zero][-0.129]>
<[float64][Min][-0.25]>
<[float64][Max][-0.08]>
>
<[tmdevicecalibration][element][3]
<[string8][InputID][Rx]>
<[float64][Zero][-0.215]>
<[float64][Min][-0.32]>
<[float64][Max][-0.11]>
>
<[tmdevicecalibration][element][4]
<[string8][InputID][Ry]>
<[float64][Zero][-0.248]>
<[float64][Min][-0.45]>
<[float64][Max][-0.046]>
>
<[tmdevicecalibration][element][5]
<[string8][InputID][Rz]>
<[float64][Zero][-0.08]>
<[float64][Min][-0.28]>
<[float64][Max][0.12]>
>
<[tmdevicecalibration][element][6]
<[string8][InputID][Slider 0]>
<[float64][Zero][-0.0425]>
<[float64][Min][-0.12]>
<[float64][Max][0.035]>
>
<[tmdevicecalibration][element][7]
<[string8][InputID][Dial]>
<[float64][Zero][-0.0575]>
<[float64][Min][-0.14]>
<[float64][Max][0.025]>
>
>
>I think a comparable calibration is possible with the TCA quadrant.
With the PFT-PUMA I proceeded in such a way that I always looked at the individual movements in the SETTINGS/CONTROLS menu and changed them until it fit me.
I'm not sure, but it seems to me the Airbus throttle positions are related to the TCA virtual buttons.
I would love to have the option to config the positions as well, as I have customized detents on my TCA.
Which axles should be adapted for which aircraft?
I would not split the throttle range in the gc-map.mcf, so that the throttle-lever universal remains operational for all aircraft types.
Instead, I would create a subfolder for the affected aircraft in my own user directory and enter the deviating data between the external controller and the aircraft TMD there. I'm doing this for the C130.
What kind of splitting would you like to have on which plane?
Until the end of this year there is still Flight-sim.org. there are for many areas of high-resolution IMAGES:
There are also other helicopters there:
Correct. The starter switch can only be pushed down on mobile.
I can both pull the starter switch on my iPad in version FS Global 1.05.09.11 (20251022) (finger on the starter and pull outwards) and press.
ApfelFlieger is it possible to get your list again, this time with the additional airport names? I could start to add the codes to ourairports.com, to improve the map.
Here are the airfields with 6-digit airfield codes.
Of course - right now I'm just less on the computer due to school holidays.
Before I turn to the large sehgment of propulsion and buoyancy, one more look at my work in recent days and weeks:
All internal doors (cockpit-cargo compartment) and outer doors (crew entrance, paratroop doors left and right, ramp and ramp door) now work on "our" C130 as with the model:
This means that the loading master can now also act in addition to the two pilots and the flight engineer (e.g. by flying the C130 via the co-pilot function).
Here comes my wish for IPACS:
it would be nice to be able to go through the plane in flight and thus, for example, to be able to take on the role of the loading master. And thought very far into the future you could perhaps also jump out of the C130 (but from my point of view would really be "only" a gimmick).
The topic of "mobile camera" has often been mentioned here, in the C130 and also in the UH-60 we would even have concrete aviation uses for this.
After the review comes now an outlook:
As part of my propulsion optimisation, I will also continue to adapt the fuel system. Steve alias larrylynx has already done a very big preliminary work here, in which he has programmed an exemplary consumption. He has also already created the modules for refuelling on the ground and in the air, which must now be brought to life. I'm curious to see how far we'll get along with it.
