sedenion

Use the force Package Editor : Tools > Package Editor...

Nop, new software, new standards... OpenModMan is more advanced. I suggest you to talk to you squadron about migrating from OvGME to OpenModMan. It embed a repository file editor (Tools > Repository Editor).

I do not have Youtube video as you request, but I can explain how the Advanced AP logic behav, since I have coded it. It may be suitable or not depending the available commands (and their behavior) for the aircraft. Maybe you simply cannot use this Advanced AP properly because available bindable commands and their behavior are not suitable.

Okay, for this, download and install the latest TARGET Software version (3.0.20) https://support.thrustmaster.com/en/product/hotaswarthog-en/

What are (all) available commands related to autopilot for each modules ?

Well, I uploaded a new 1.6 version with usual virtual Keyboard+Mouse creation.

Well, I released new version, available for download with some little changes and fix: v1.6 (2021-11-26) - Add support to exclude Airbus Edition devices. - Add options to change LEDs intensity and disable Throttle backlight. - Fix wrong mapping for EACOFF. - Fix virtual keyboard and mouse not created as usual.

You right, it's an error. The mapping for EACOFF should be DX60... Notice this error occure only if you disable the LED assignment for EAC switch.

The goal of my mapping script is to create a virtual device with only DX buttons, in this context there is no need for virtual mouse or keyboard. You are free to adapt and customize it as your needs. Also notice that the "DX++ module" (wich is a very small piece of code) is not copyrighted, you can freely take it, embed it in your own mapping script...

Yes I saw this, but this is really a weak workaround... I hope ED will implements some filtering for vector strokes.

Guys, you did a really good job, however I have a little bemol to signal, but I don't know if you can do anything: The SVG render really miss some anti-aliasing. With SSAA it's ok, but SSAA is too slow for me, so I prefer to use MSAA, and with MSAA, the SVG render is very aliased.

Ok, I think you were actually more responding to GrapeFruiT...

I understood absolutely nothing...

I think you should create a new topic in the Thrustmaster section, because your request have very little to do with the purpose of this current one.

At last, I will no longer need to update my mod ! Good job guys.

Indeed, as far as I know this is not specific to this script, TARGET or even warthog, but how input data are gathered through Windows HID API. In short, unless you change device state (button or axis) no data is received and programs have no ability to "poll" device state nor query 'last device data'. Programs have to implement some workaround on their own, and this is unperfect.

Also remember that once the script is runing, it is like you have a new device plugged to your computer, DCS detects a totaly new device (the virtual Combined Device) whith its own controls / buttons assignations. In the same time, the usual two Warthog device disapear (they are temporarly disabled by TARGET). This mean that you must verify the DCS commands setup and assigned buttons/axes while the script is running, because this is only at this moment that the "virtual Combined Device" is detected by DCS. Once you stop the script, the Combined Device disapear (like if you unpluged) and the two Warthog physical devices come back, with their own specific commands setup.

I have to add... Instead of the script, I think you better investigate first in the DCS side to determine what command is triggered to act to the F18 trim/elevators. It must be a command or axis command somewhere, in any section that you don't spot, and is triggered by something. Once you found that, then we could determins how the script may influence this.

The script cannot compile with the two first lines you "disabled" unless you also "disable" the lines 167, 168, 194 and 195... The two other lines (the include directives) have pratically no effect since there is no mapping, included files are simply placeholder with a function that return 0. Anyway, with "disabled" lines as you show in your screenshots, the script cannot run, and the output should show you a runtime error.

POV Positions = Buttons. Except in some low level software aspect relative to HID spec, this is the same thing. The hardware maping (meaning, as it is recognized natively by HID interface, without script, withou virtual device) of the Warthog Stick (F18 or F16) is that H1 IS the POV HAT, and my script simply replicate this hardware configuration. Your problem cannot come from there, forgots this. No, I not member of any squadron. Ask somebody have the F/A-18C module and Warthog to try my script, and ask him if it has the same problem. But I think not, I think there is something specific in your setup that cause that.

This is simply technically impossible. This mean there is something you missed, something you have not spotted that create an input. An axis, another device... I don't know, but the TARGET software itself cannot interact directly with DCS (or any other software) in such manner, it simply can't. I don't have the F/A-18C module. Reshader have nothing to do with that, you can exclude this theory. I cannot investigate... I don't have your setup, I don't have F/A-18C module, I have no access to your computer... The only thing I can tell, is that if something happen in DCS, this is triggered by an input, either a button, an axis, or emulated keyboard or mouse, that trigger a command which act on trim, so you have to discover what command, and what input. Computers are not magical, they are logical, so, be logical. So, proceed by elimination, try and check... First, to avoid any driver or software bug, uninstall then reinstall Warthog drivers and TARGET software with latest versions, also verify you flashed your devices with the latest firmware...

The profile itself is not the problem, it is more probably related to drivers, softwares or USB ports. Uninstall all TARGET software and drivers related to TM Warthog Download latest TM Warthog drivers and TARGET software : https://support.thrustmaster.com/en/product/hotaswarthogflightstick-en/ Package drivers - Hotas Warthog - 2018_TMHW_1 + Firmware T.A.R.G.E.T - Software v3.0.20.826 Install TM Warthog drivers Install TARGET Software Update throtthle and stick firmware following this procedure : https://ts.thrustmaster.com/download/accessories/pc/hotas/manual/HOTAS_Warthog/HWarthog_Firmware_Update.pdf Try again. If the problem occure again, please copy-past here the content of the script output log that appear when you run the script.

I don't know what happen exactly, but I am pretty sure this has nothing to do with the script... This appear to be a pure hardware problem, like a bad electrical contact in the HAT switch that cause "false" and unwanted button press...

Did you mean that once the situmalation is started, the F18's elevators continuously trim even if you press no button ? And did you mean that this happen even if you don't have defined any input to the Trims commands in DCS controls options ? If yes, to me this is technically impossible. Please confirm I well understood you or correct. I don't know what you mean by "clear" in this context, sorry. Wich buttons you talk about ? Physical button on the Warthog ? The commands in DCS's controls options ? What is "same result", what "result" are you talking about. Please clarify: You cleared what, where, in what context ? Please, BE THE MOST PRECISE possible. I am sorry to say that, but since i don't realy understand what is the problem, I don't know... From what I understood at this stage, things looks like more of devil's possession of your Joystick than any logical or technical problem...

Be indulgent, I had hard time to found proper terms to name such abstract concepts... Terminology is confusing but principle is pretty simple. Create a Software Context nammed "DCS World" where you want Within this Software Contexte, create a Target Location named "Main" with destination folder that point to DCS World's installation folder. Put the mods to install into the "Library" folder of the previously created Target Location subfolder