MoppleTheWhale42

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.

Looks like the problem was caused by birds as the number of birds was not set to 0 in the missions and therefore the individual settings of the DCS installations defined the number of birds. Thank you for all your comments!

Since all pilots have set the number of birds to 0, the problem has not occurred. I'll wait a few more weeks, not that it was just a coincidence, but it looks like it was the angry birds.

razo+r, thank you for looking into this issue. Yes, birds are enabled in my setting, and I think I get your point. It looks like birds are not forced off in the mission and this is why bird strikes can happen. To answer your other questions: The only failures that happen are engine flameouts. The problem occurs in different missions. I will make sure that the next missions we fly will have birds forced to 0 and hope that this solves the problem.

Please find attached the trk-File, which contains the mission. Pig-1-1 suffered from two engine failures. I had to put the trk-file into an archive, otherwise it would have execeeded the 50 MB file size limit. Bambini_Caucasus_Standard_v4-20231013-203656.zip

I have smokewinders on the outer pylons, turn on master-arm, go into AA-mode and select the smokewinders. Then I press the weapon release trigger, but nothing happens. Since I usually look for the error with me, I asked the other squadron members to test the smokewinder. Nobody could activate the smokewinders, so I assume it is a bug.

Thanks for your hints. Fuel flow is set to NORM. Fuel pumps are running. If it would happen to the same player all the time, I would assume an individual error. However, it appears to happen randomly, it appears at a random time and the affected player also seems to be "selected" randomly.

For several months now, random engine failures have been occurring repeatedly on the A-10C II. Without any external cause, one engine is on fire. This can be the left or right engine. If you are unlucky, even both within one mission. It does not always happen to the same A-10 within the mission. Birds are turned off in the missions, as is the random failure of system components (I checked this in the mission file). There is no strafing either. So I don't see any reason why one engine keeps going up in flames. Are there any other reasons for the engine failure listed above?

Hi, I'm using a 32:9 monitor and unfortunately all the objects at the edge of the screen are extremely distorted and stretched out. The two screenshots show an A-10 standing next to me on the runway, once when I look directly at the A-10, so that the A-10 is in the middle of the screen. The other image, shows the same A-10, but this time it is at the edge of the screen and is extremely elongated. Are there any settings to prevent this distortion? I don't have this problem in other games.

The setting is named "TGP switch ON/OFF"

What do you mean by "missile step"? What shall the Mav do?

Hi, to my understanding, the AGM-65H has no INS. Thus, in forced correlate mode, it uses its CCD for aiming. If this is true, why does the AGM-65H work reliably in forced correlate mode in complete darkness? Is this a bug, or is my understanding how the AGM-65H identifies its target in forced corelate mode wrong? Kind regards Mopple