AstonMartinDBS

Geniale Idee, werde heute mal schauen, ob ich sowas zuhause herumliegen habe! Danke für den Tipp! Edit1: Ist zufällig jemand in der Nähe seiner Base und kann mal nachmessen, wie der maximale/ideale Außendurchmesser der Dichtung sein darf? Edit2: Außendurchmesser = 35 mm, habe leider keine passende herumliegen. Die Dichtung im Gardena-Schlauchanschluss hat einen Durchmesser von 30 mm.

Die Scheibe soll dann genau dort rein, wo auf dem o. a. Foto die Pfeile hinzeigen, richtig? Hat jemand eine Ahnung, wie dick diese Gummibeilage im Idealfall sein soll?

I've noticed that issue yesterday flying my Huey. I had to embark a group of 8 soldiers, but only 5 have been boarding.

Removing trees is still randomly bugged. Tried first with medhod 1, but the trees weren't removed; got it to work with method 3 then. But sometimes it works with method 1 as well (after a fresh restart of DCS).805 UH-1H FARP SetupTest.miz

Hm... the ATC feature works as soon as I change the FARP type to standard (with four heli pads). Is this a bug or a feature? :huh:

Is there still no simple trigger condition to check, if an unit has emarked/disembarked?

Good to know. I also missed the WP 0.

Thx for those tutorials! I'm happy about the explainations on the FPAS page! :thumbup:

I did (after TARGET installation). Or should I do that after each windows boot up process? In that case I prefer the other workarounds... ;)

I've now also tried to deactivate the enhanced USB Powermanagement, according to https://forums.eagle.ru/showpost.php?p=3808285&postcount=6. But when I reached the correct registry-entry I was surprised, that this option already was deactivated by default...

The proper re-installation of TARGET following the steps "disconnected my controller, uninstalled Target, Rebooted, reinstalled Target, rebooted, plugged controller" didn't solve the issue for me. Uninstalling the Microsoft store isn't an option for me (several windows core-applications will be updated by the store frequently). Excluding the whole thrustmaster- (c:\program files (x86)\thrustmaster\) and script directories (%appdata%/thrustmaster) from Windows Security didn't help... :( Thanks anyway for your suggestions!

Thx for the hints, I'll first give the correct reinstallation of the TARGET software a try.

I use the same workaround, but it's not a satisfying solution for me. I think that this issue can be fixed by an expert.

According the instructions in the Thread https://forums.eagle.ru/showthread.php?t=210857 I've managed to bind every switch position of my Warthog Throttle. It generally works well with DCS, but there's a little issue in the script which causes the following strange behaviour: When I start the TARGET-script for the first time immediately (within first minute) after the windows-login it works as intended: the virtual device "Thrustmaster Virtual Game Controller (root)" is created and the native "Throttle - HOTAS Warthog" will be removed/hidden (screenshot #2) after a few minutes after windows-login it doesn't work correctly: the virtual device will be generated as well, but the native device is still there (screenshot #3) Any ideas to fix this behaviour? The native "Throttle - HOTAS Warthog" device should be removed, otherwise it would be preferred against the virtual device in DCS and the script would be useless. I've attached my slightly modified script, where I just added the lines for excluding not connected and unneeded devices (TFRP) in comparision of the original script in the referred Thread. But the described behaviour occured in the original script as well. I'm not able to locate the code which removes or hides the native device from the gamecontroller list. targetdx128 20200425.zip

I've set a curve of 32 for the X- & Y-axis and it works fine for me.

Ok, I found the answer myself: //reject (non connected) devices from virtual controller Configure(&HCougar, MODE_EXCLUDED); Configure(&Joystick, MODE_EXCLUDED); Configure(&T16000, MODE_EXCLUDED); Configure(&T16000L, MODE_EXCLUDED); Configure(&LMFD, MODE_EXCLUDED); Configure(&RMFD, MODE_EXCLUDED); Configure(&TWCSThrottle, MODE_EXCLUDED);

Modul: F-16C Optionen/Steuerung/Kategorie "Gasgriff (Throttle)/HOTAS"/Transmit-Schalter - UHV... ...sollte wohl Transmit-Schalter - UHF heißen.

Danke fürs positive Feedback! Über das Zusammenfassen der vier Checklisten in einem einzigen Thread habe ich schon mal nachgedacht. Aber vorerst könnt ihr ja über meine Signatur zur jeweiligen Checkliste switchen.

I've built a mission containing a FARP with a single heli pad, but I can't get working it's ATC. Callsign & frequency are set for the FARP and there is an APC M1025 HMMWV next to the FARP, which should provide the APC capabilities (following the instructions in ). But when I start the misson the COMMs menu shows only "..." instead of the callsign. Neither placing the APC M1025 HMMWV onto the FARP nor removing the Oil- and Gasplatforms from the mission solves this issue (see screenshot). Is this a bug or have I overlooked something? 801 UH-1H FM-Homing-Test.miz

Auch meine Checklisten für den Kaltstart der A-10C Warthog und A-10C II Tank Killer will ich mit euch teilen. Orientiert habe ich mich dabei eng an der Startup-Procedure von Chuck's A-10C Guide (Version vom 09.11.2018 ). Vielleicht kann der eine oder andere von euch damit was anfangen. Verbesserungsvorschläge und/oder fehlende Schritte könnt ihr mir gern melden. In meiner Signatur findet ihr die Links zu meinen anderen Checklisten. Legende: Spalte 2 LK - Linke Konsole LVI - Linke vordere Instrumententafel MVI - Mittlere vordere Instrumententafel RVI - Rechte vordere Instrumententafel RK - Rechte Konsole UFC - Up Front Controller HTS - HOTAS Spalte 3 SW - Switch/Schalter BTN - Button/Taste Spalte 4 R - Rechtsklick L - Linksklick W - Mausrad Verlauf: A-10C Warthog: 23.04.2020: v1.7.3 (Erstveröffentlichung Checkliste A-10C Warthog) 08.11.2020: v1.8.0 (kleinere Anpassungen an die aktuellste Version der A-10C) 08.11.2020: v1.8.1 (kleine optische Korrekturen) 18.11.2020: v1.9.0 (an neues Feature angepasst: Flashlight) A-10C II Tank Killer: 08.11.2020: v1.1.1 (Erstveröffentlichung Checkliste A-10C II Tank Killer) 08.11.2020: v1.1.2 (kleine optische Korrekturen) 18.11.2020: v1.2.0 (an neues Feature angepasst: Flashlight) Download: A-10C Warthog: DCS-A-10C-ColdStartChecklist-de-v190-A4Q1S.pdf A-10C II Tank Killer: DCS-A-10C-II-ColdStartChecklist-de-v120-A4Q1S.pdf Weitere Downloads: F-16C: ALIC Tables for the AGM-88C HARM (.pdf and Kneeboard) F/A-18C: Threat Codes for the AGM-88C HARM (.pdf and Kneeboard)

Many thanks for sharing this script, Grodin! It runs great and makes the bindings for all of the throttle switches in DCS so much easier. I'm so happy that I found this thread. :thumbup: Had the same problem with my TFRP Rudder Pedals and managed to work again with your hint. But how can I eliminate the "USB HID device with hardware id XY cannot be found" messages in the TARGET script window?

What about an additional option in the drop-down-box called "disabled" or "deactivated" to deactivate the desired mode/function? Roger! You're right. That issue belongs only to the last six keys. All others are saved properly. I use simFFB since three days but it happened several (at least 6) times during tweaking the settings. Great! Please let me know when the new version is available! :) Die Frage stellst du besser hier: https://forums.eagle.ru/showthread.php?t=189133

Sehe das genauso. Manchmal glaube ich, ED wirft die Begriffe in den Google-Translator, holt sie von dort 1:1 raus und pflanzt sie dann ohne weitere Prüfung in den DCS ein. Die ganzen Fachbegriffe inkl. Keybindings sollten einfach unverändert bleiben, dann bewegt man sich auch in den englischsprachigen Foren auf einem Level.

Habe ein paar Icons erstellt, die ihr z. B. für eure simFFB-Desktopverknüpfung verwenden könnt. Download: https://forums.eagle.ru/showpost.php?p=4295127&postcount=19 Die Screenshots zeigen die Vorher-Nachher-Situation :smilewink:

I recogniced right now, that this graphical issue only occurs, when the ext position lights are active (independend of the mode flash/steady or dim/bright).