Jump to content

VirtualCPT

Members
  • Posts

    87
  • Joined

  • Last visited

Posts posted by VirtualCPT

  1. Hi Brad,

    I'm sorry for the late reply. Has been a rather busy week for me.

    Looking at your Log.txt it seems that the plugin was loaded correctly. Unfortunately, I cannot read the XMIdiCtrl_Log.txt - it shows some Chinese characters, only.

    The most important thing is to configure your Loupedeck in order to send and receive MIDI messages. I don't own a Loupedeck and cannot really help, but others in this forum have been successful and there is even a little tutorial available.

    The profiles should be placed in the folder .\Output\preferences\XMidiCtrl\Profiles - then you have all profiles in a single place. That's much better than placing them directly in the aircraft folder.

    Each profile has a section called [[device]] which includes the two parameters port_in and port_out. You have to enter here the correct ports for your device.

    Have a look at the documentation, please. I tried to explain how the creation of profiles works:
    https://mauer.github.io/xmidictrl/#/create_profile

    A screenshot of your MIDI Devices screen of XMidiCtrl would be useful, too.

    Thanks,
    Marco

     

  2. Hello Jeff,

    It's difficult to say what wrong without an log on debug level. It could be that your Midi Fighter Twister is sending range messages instead of relative messages. You can try that very easily by just adding the mode parameter to your mapping.

    It would look like this:

    { ch = 1, cc = 0, type = "enc", mode = "range", dataref = "sim/cockpit2/controls/elevator_trim", modifier_up = 0.0125, modifier_down = -0.0125, value_min = -1, value_max = 1, value_wrap = true }

     

    When you commands instead of a dataref no negative values are required at all. You just have to define command_up and command_down. A correct mapping would be:

    { ch = 11, cc = 1, type = "enc", command_up = "sim/instruments/barometer_up", command_down = "sim/instruments/barometer_down" }

     

    Please enable the debug mode in the settings, turn the knob a couple of times up and down and send me the XMidiCtrl_log.txt, please. Then I can see what kind of messages your device is sending. I'm pretty sure that are using the range mode.

    Have a nice day,
    Marco

  3. Hi,

    I believe the X-Touch Editor software is not available on Linux und macOS. You can use the X-Touch with the default settings, as well. Instead of Control Change messages it will send Note messages. You basically have to adjust the aircraft profiles, but otherwise it will be working fine even without the editor software.

    (I'm a Linux user)

  4. Dear all,

    I just created an aircraft profile for the Mitsubishi MU-2 to use this wonderful plane with the XMidiCtrl plugin:

    This was quite an interesting profile to create, as the Mitsubishi has two GPS devices installed. All GPS related buttons are on layer B of the X-Touch Mini. On the first button row you will find a button labelled GPS 1/2. If the button is not illuminated, all buttons are mapped to GPS 1, otherwise they are mapped to GPS 2. During my test flights I rarely used GPS 2 as it is linked to the instruments on the Copilot side. Using GPS 1 was more then sufficient.

    The autopilot buttons are all on layer A and illuminated. That's quite useful to quickly check which mode is currently active. Luckily the developer of the plane provided datarefs for each button light.

    rn_image_picker_lib_temp_68691623-d2df-40e8-a3ae-a5c44a463a7f.thumb.jpg.af92ace09ea4807ee21271768110cd84.jpg

    Please let me know if there are any problems or errors.

    Thanks,
    Marco

  5. Hi @KirkR,

    Many thanks for the kind words. I'm very happy that you like my plugin - I like it as well and cannot imagine X-Plane without using the midi devices. You have a very nice setup, would love to have those G1000 screens :-)

    I was looking at the MSFS SDK, but that really a very different world. Such a tool needs to be developed as a standalone application rather than a plugin. It would be a complete rewrite and would require a lot of work. There is a very nice and cheap tool called Axis and Ohs which supports the X-Touch. I'm using that for MSFS and I'm rather happy with it.

    Hope that help,
    Marco

     

  6. 18 hours ago, Ben Russell said:

    I downloaded v1.04

    It contains a "fat plugin" binary with both x86_64 and arm64 segments present.

    There is definitely a glitch with the signed status of the file.

    It claims it is unsigned yet attempting to sign it with my own Apple Dev cert fails.

     

    I was able to get the plugin working by extracting the arm64 portion of the plugin and renaming some files.

    cd ~/X-Plane 12/Resources/plugins/XMidiCtrl/mac_x64
    
    mv XMidiCtrl.xpl fat.xpl
    
    lipo fat.xpl -extract arm64 -output XMidiCtrl.xpl 

    After extraction X-Plane 12 starts without error and XMidiCtrl was present.

     

    The lipo tool might not be available if you don't have Xcode installed...

    Hi Ben,

    Many thanks for taking the time to check my plugin. I don't own a Mac and cannot test the macOS version of the plugin. So far I cross compiled the macOS version on Ubuntu Linux. However, I recently started to use GitActions instead which allows me to compile directly on macOS.

    Do you have any idea how I can fix this problem?

    Signing the plugin isn't an option, as I don't have an Apple Developer Subscription :-(

    Thanks,
    Marco

×
×
  • Create New...