Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Today
  3. Of course... Oops. Sorry for that Log.txt
  4. Post a complete copy of Log.txt as an attachment.
  5. Hi guys, After quite some time I just wanted to start a flight on version 1.5.2 and whenever I loaded in the sim I never got to see the airplane at all. The camera just spun around and at some point I got the message that the aircraft crashed. So I tried a new installation but that doesn't go through. I get an error as soon as the process reaches "systems/win_x64/systems.xpl Any idea? Thanks
  6. Sorry to hear that. Good luck. I hope you’re into the virtual skies again soon.
  7. Thank you for the info! However i will not able to use the sim for a couple of months at least. Unfortunatly my GPU died today. Thank you and i will keep in mind your help for the next time i will install it again! Jack
  8. Ok, then you should disable whatever blocked that file from being installed and run the CL-650’s installer again. If you’re generally concerned about PC security, reasonably so, run the subsequently installed XPL file through VirusTotal before starting the sim, you’ll find it’s “clean” and safe.
  9. I checked in the folders, but I don't have that file. The only file that I can see is a text file named "Sims". I attached a photo of the directory and the file as well if you need it. syms.txt
  10. The only product I'm aware of that was distributed without an installer is the piagio avanti which is a freeware demo product. Clicking the update notice box should hide it.
  11. Yesterday
  12. Patience, please. There’s another big update coming.
  13. Can you check if this file exists …/X-Plane 11/Aircraft/X-Aviation/CL650/plugins/systems/win_x64/systems.xpl ? I’m guessing your antivirus has blocked the install or loading of this code.
  14. I'd like to request commands for Ground Services -> Refuel -> Refuel Truck Ground Services -> Refuel -> Interior Refuel/Defuel panel So that I can map keyboard shortcuts to these pop-ups. Thanks!
  15. Seems strange, since yesterday was working fine. This part of file log show the errors, i think: 0:01:23.850 I/SND: This aircraft is using FMOD in FULL mode. 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 839 0:01:23.850 E/SOUN: The sound event event:/apu/ext/apu_start_init has an invalid command trigger CL650/anim/apu/start_init 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2129 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/vs_wheel_1 has an invalid command trigger CL650/FCP/vs_pitch_up 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2139 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/vs_wheel_2 has an invalid command trigger CL650/FCP/vs_pitch_down 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2189 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/knob_1 has an invalid command trigger CL650/FCP/crs1_up 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2194 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/knob_2 has an invalid command trigger CL650/FCP/crs1_down 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2249 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/knob_3 has an invalid command trigger CL650/FCP/speed_up 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2254 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/knob_4 has an invalid command trigger CL650/FCP/speed_down 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2329 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/knob_5 has an invalid command trigger CL650/FCP/hdg_up 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2334 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/knob_6 has an invalid command trigger CL650/FCP/hdg_down 0:01:23.850 E/SOUN: snd error in file: Aircraft/X-Aviation/CL650/fmod/CL650.snd line 2369 0:01:23.850 E/SOUN: The sound event event:/switches/fcp/knob_1 has an invalid command trigger CL650/FCP/alt_up It's not all, if you want i attached the log file to this comment. Log.txt
  16. Hello Devs, Any chance for a fix, please?
  17. Any X-Aviation product installer. It is the only way to obtain new version of Gizmo. It is no longer available for public consumption outside of that. You can't.
  18. Ben, it's not that I need an "old version of Gizmo", but in my case, Gizmo64 keeps notifying me with a popup that there is a new version and I need to update. I've been checking your site for a few months now, but on your Gizmo page, there isn't a link to download a new version, or any version of the Gizmo64 plugin. I would like to update mine. I have version 20.07.0120. If there is a new version out there, could you please post a link where I can download it? Every link I find to download it either takes me to Threshold, where this is also no link to download the package, or to your Gizmo page, where there is also no link to download the package anymore. If nothing else, could you at please advise me on how to turn off the popup that keeps telling me to download the new version? It covers other plugin status notifications and I can't figure out a way to move it out of the way. Oh, you had, in another thread, advised me to "rerun my product installer to get the update", but that didn't tell me which product installer you were advising me to rerun. I didn't get an installer with my original download of Gizmo64. It was just a Zip file to unpack and drop in plugins. I did drop in a fresh copy of that from my backup drive, but that didn't make the notification go away. I assume that's because that's the same version I already have. Thanks.
  19. Most likely you don’t have the Gizmo plugin installed or running. Please check your Log.txt.
  20. As the title suggest, when i load the aircraft, is bugged for some reason. All started this morning, and when the load endend, this is what i saw: (see the image attached) I don't know why. I can't use the aircraft, i can't walk inside or around and all of the systems don't work.
  21. Hi Coop, I still have the same problem. I installed the newest NVIDIA driver and your svs.dll file, but it still won't work. The X-Plane 11.55 start-up screen simply disappears briefly after the plane starts loading. Log file attached. Regards, Sjors Log.txt
  22. Additional information. Issue does not appear to be occurring when not connected to VATSIM. Oddly the ground ATIS at KORD is just stating current information golf then cutting out, the cycle then repeats. Not sure if this ATIS error might be related to this crash.
  23. Loading in at KORD with a simple direct route to KIND while logged into the VATSIM network in VR. As soon as I go to Route Menu > Wind Update > SEND the sim CTDs. Log.txt
  24. For some reason when launching the CL650 while in VR mode the flight settings window is very dim like it's out of focus. When you select career mode and confirm the flight the sim crashes to desktop. Log.txt
  25. Last week
  26. I'm not sure on the drivers, unless there is something specific with the current drivers, I'd probably recommend the latest drivers. I'm DMing you a file to test with to see if it fixes the issue.
  27. It is with great joy that I’m announcing the release of XMidiCtrl Version 1.00! I started this project around one year ago. The initial commit was on the 4th May 2021 and I’m honestly rather proud how well it turned out. Since the release of the first version on 1st November 2021 I have received many nice messages from people all around the world. Within the last few months, the plugin evolved even more, thanks to the many suggestions and ideas I received from you. Together we succeeded to enable support of various MIDI devices and not just the Behringer X-Touch Mini. The release of the Hot Start Challenger 650 was another milestone in the young history of XMidiCtrl. Thanks to the great help of Graeme from Reflected Reality Simulations, I was able to offer support for this amazing aircraft from day one. Recently I did some major refactoring and added some ideas I had for a long time. With all the work done and some extensive testing from quite a few people, I’m confident to label the current version as 1.00. I hope this will be a clear sign to new users, that we are talking about a stable and feature complete plugin. Development will not stop here, of course! But all the initial ideas I had are finally implemented. Okay, let’s have a look at the new features: Support for all MIDI message types In order to support all kind of MIDI devices, it was necessary to implement support for all MIDI message types. Initially the plugin was able to send and receive Control Change messages, only. With the new version of can send and receive: Control Change Note on/off Pitch Bend Program Change New logging system I was never happy with the logging system. It was still the initial implementation from the first prototype. I wanted an improved system which shows the user exactly the information she/he needs to see without the need to search an extensive log file. First of all, there are no log levels anymore to choose from in the settings window. You can enable a debug mode if required, but otherwise all warnings and info messages are being logged. There are not many of them anyway and most get raised when loading an aircraft profile. In addition, there is a new tab page in the profile window. It shows you all errors and warnings for the current aircraft profile: When you open the new messages window and change to the MIDI Message tab page, you will see quite a few changes, as well: As you can see, I added some icons instead of text. Most icons provide a tooltip with additional information. This allows you to see all mappings and log messages related a specific MIDI message. However, all messages are still logged to the common log file, if you prefer to monitor the plugin this way. Log entries related to a MIDI message: Mapping used for a MIDI message: Enhanced Mappings I added some additional mapping parameters to allow more advanced mappings. Most notable additions are: Encoders – value_min and value_max Allows you to specify minimum and maximum values for the mapping. Example: { ch = 11, cc = 8, type = "enc", dataref = "AirbusFBW/XPDRPower", modifier_up = 1, modifier_down = -1, value_min = 0, value_max = 4 } Dataref support for Push&Pull So far it was only possible to specify commands for push and pull. With this version you can also modify Datarefs directly. It’s even possible to mix commands and Datarefs, such as have a push command and modify a Dataref for the pull event. Examples: { ch = 11, cc = 9, type = "pnp", dataref_push = "AirbusFBW/BaroStdCapt", values_push = ['0', '1'], dataref_pull = "AirbusFBW/BaroUnitCapt", values_pull = ['0', '1'] } { ch = 11, cc = 9, type = "pnp", command_push = "AirbusFBW/Toggle_BaroStdCapt", dataref_pull = "AirbusFBW/BaroUnitCapt", values_pull = ['0', '1'] } Labels This is one of my most favourite additions. Labels allow you to display display a text when a mapping event takes place. Lets assume you have a mapping to change the transponder mode using a knob on your MIDI device. The mapping would probably look similar to this one: { ch = 11, cc = 8, type = "enc", label = "xpdr", dataref = "AirbusFBW/XPDRPower", modifier_up = 1, modifier_down = -1, value_min = 0, value_max = 4 } That will work rather nicely, but often the transponder mode knob is between the pilot seats. If you want to check the current setting you must look down and that annoyed me. In order to display labels, you have to define the label in the aircraft profile: [xpdr] text = "Transponder Mode:" values = [ { value = "0", text = "STBY" }, { value = "1", text = "ALT RPTG OFF" }, { value = "2", text = "XPNDR" }, { value = "3", text = "TA ONLY" }, { value = "4", text = "TA/RA" } ] In this case I created a new label with the id xpdr. In addition, I specified a text to be displayed each time the mapping gets executed and some labels for the different values. Finally, you have to bind the label to your mapping: { ch = 11, cc = 8, type = "enc", label = "xpdr", dataref = "AirbusFBW/XPDRPower", modifier_up = 1, modifier_down = -1, value_min = 0, value_max = 4 } Whenever you change the transponder mode using the MIDI device, the label for current value will be displayed. If no label value has been defined, the Dataref value will be shown. The new settings dialog allows you to modify the position where the label text will be displayed: Init Mappings This new mapping option allows you to send some MIDI messages to the device just after the aircraft has been loaded. It can be useful when using the Behringer X-Touch Mini to initialise the behaviour or the encoder lights. Example: [[device]] name = "Behringer X-Touch Mini" port_in = 0 port_out = 1 mapping_init = [ # Encoder Lights # 0 = Single # 1 = Pan # 2 = Fan # 3 = Spread # 4 = Trim { ch = 1, cc = 1, velocity = 1 }, { ch = 1, cc = 2, velocity = 2 }, { ch = 1, cc = 3, velocity = 3 }, { ch = 1, cc = 4, velocity = 4 }, { ch = 1, cc = 5, velocity = 4 }, { ch = 1, cc = 6, velocity = 3 }, { ch = 1, cc = 7, velocity = 2 }, { ch = 1, cc = 8, velocity = 1 } ] New Examples The new version comes with some additional example mappings: Updated version for the ToLiss A321 iniBuilds A310 Felis Boeing 747-200 I hope you enjoy the new version as much as I do and please let me know if you have any questions. Thanks, Marco
  1. Load more activity
×
×
  • Create New...