MoppleTheWhale42

Hi, I wonder whether there is a way to generate "events" via DCS LUA scripts, which show up in tacview. Let's assume my LUA scripts come to a certain decision, such as "raid of blue" starts. Is there any way how I can generate an associated event, which shows up in the tacview flight log? Of course I could create an object, which shows up, but I would appreciate to create a log with a text, which I can define from within a LUA script.

Das Senden von Tastaturkommandos mittels Streamdeck funktioniert bei mir problemlos. Schau mal hier: https://docs.barraider.com/faqs/supermacro/getting-started/

Eduardo, thank you very much!

Hi, I am trying to set the main mode of ARC210 (A-10CII) via clickable action. The master knob has device id 55 and 3043. My problem is, that whenever I call performClickableAction the knob does not rotate into the next clockwise or counter clockwise position, but rotates left or right to the very left, resp. very right position. What am I doing wrong? How can I programmatically set the knob into a specific position respectively mode? thank you Mopple

Good point. We faced the issue on the Syria and the Caucasus map.

After the issue with Reshade, and I am not sure whether the problem was caused by Reshade, or by some other Mods, I have re-installed DCS again. Plain Vanilla DCS. I created a mission, where I fly in an A-10CII and drop a GUB-12. While the GBU is falling, I change my role to JTAC, lase the target and the bomb hits as expected. This mission ran on my PC, started out of the mission editor. The success made me think that the problem is solved. But during our last training (which ran on a server of our squadron), where I acted as a JTAC, no A-10CII could spot my LASER, no GBU-12 did hit the marked targets. Therefore, I think that gcask gave an important hint: "As stated above the issue does not occur if the human JTAC is also the host (players will fail to see the laser from a second human JTAC though)". This is in line with my experience.

The bug re-appeared after installing Reshade. Guess I have to install DCS again...

I have uninstalled and re-installed combined arms. Problem persists. I now have uninstalled and re-installed DCS and the problem is gone. Thus, something with my installation was broken, what could neither be fixed by repair, nor by reinstallation of combined arms. Thank you all for your support. Special thanks to razo+r for spending his time to look into the track files.

That's weird. Yes, I did.

As requested, I have removed all mods and have reproduced the problem. Please find the track file attached. CA-Misplaced-IR-Pointer.trk

Looks like the position of the smoke is in line with the position of the IR marker. But also for the IR marker, I expect that it points to the center of the cross-hair.

When I act as a JTAC and look through the binocular, I expect that smoke appears at the middle of the cross-hair (there is no wind in the mission) and that smoke does not stay forever. However, smoke appears to the left of the cross-hair center (see screenshot) and smoke seems to stay forever. At least for 2 hours. Is my expectation wrong, or is this a bug?

I have the same issue. Laser from me as JTAC cannot be spotted by planes (A-10, F-14) and GBUs also seem not to spot my LASER marking as they miss the target.

Hi, to my understanding the difference between FROM TO and TO TO waypoints is the information I get in the CDU Nav/Attributes page: In case of TO TO the CDU provides the course between the two waypoints (not the course between the current location of the airplane and the next waypoint). So far, so good. But, what is the practical use of TO TO waypoints? I cannot figure out when to use TO TO waypoints. Thank you & kind reagrds Mopple

Smokewinders are working again. Ticket can be closed.