yakiniku

If understanding TWS and datalink makes me a hipster, I guess the USAF is the biggest hipster club on Earth.

I couldn’t understand it from the manual, so this thread was very helpful. I’m wondering whether the fact that you can’t tell without performing this operation is actually the real aircraft’s specification.

Thanks for your reply. The HSD appears a bit jittery compared to the other displays. It seems even harder to read when the Pixel Density is low. I had set this option to 1.0 in the DCS options and increased the Foveate Resolution to 180% in the QuadViews Companion App. Due to a recent DCS update issue, some of my settings were reset, and with QuadView turned off, the HSD had become extremely difficult to see. The issue has been resolved for now. Thank you very much.

I’m using a Meta Quest 3, and only the information displayed on the HSD is very difficult to see. All the other displays and instruments are clear enough, but the HSD data becomes very blurry even with slight head movements, making it hard to read. Does anyone know a solution for this?

Deleting the MissionEditor folder solved the issue. Thank you.

After reverting DCS to version 2.9.19.13478, both keyboard and joystick inputs returned to normal. And after updating to the new version again, it stopped accepting inputs. It seems there is indeed some kind of bug in the new version.

The control settings have not been deleted. On this screen, it does not even respond to key inputs. Naturally, both the keyboard and joystick work fine outside of DCS.

After the update, I cannot use any keyboard or joystick inputs at all. I noticed this on the controls settings screen. Also, when pressing several keys on the controls settings screen, the display turns completely black and becomes unreadable. In addition, when I press the OK button to return to the main screen, the display also turns completely black. ログ.zip

I am using the HOTAS X56, but this throttle does not have an Afterburner Detent Release Switch. So, I made one myself using 3D printing. I have completed a prototype, but I am not sure if the detent position is correct. Currently, based on the axis tuning panel, the position is set to In=30 and Out=30. What are the positions for products like the Thrustmaster HOTAS Warthog? Thank you in advance!

I understand that it's not a bug. Thank you.

Doesn't the TMS input work as follows? TMS UP -> BORE TMS DOWN -> 20(HUD Scan) TMS DOWN -> 60(Vertical Scan) TMS DOWN -> 20(HUD Scan) TMS DOWN -> 60(Vertical Scan) The manual states "TMS Down: 10° × 60° (Vertical Scan)," but it's very strange that it initially switches to HUD SCAN.

In the F-16C ACM mode, isn't it a bug that the HUD scan and Vertical Scan toggle each time the Target Management Switch is pressed backward? The manual provides the following explanation on page 348. • TMS Up: Boresight (BORE) Sub-mode • TMS Down: 10° × 60° (Vertical Scan) • TMS Right: 30° × 20° (HUD Scan) • TMS Left: No function

In the F-16C ACM mode, isn't it a bug that the HUD scan and Vertical Scan toggle each time the Target Management Switch is pressed backward?

Plugging it into a different USB port and then calibrating fixed the issue.

Hello. There is an issue with the rudder control input for the F-15C. Please take a look at the attached image. The mechanical rudder position is centered, but in the F-15C settings screen, the detected position is to the left. When I switch to the F/A-18C in this state, it shows the correct centered position. Do you know why this phenomenon occurs with the F-15C? null

This tool is convenient. It took some time, but I was able to set it up. Thank you. I see, I just needed to select OFF. I hadn't looked closely at the settings screen. Thank you.

Hello. I'm a beginner who just started. I'm setting up the X56 controller for the FA-18. I want to assign the speed brake control to the switch (ON/OFF) on the throttle. I found the following script through ChatGPT. -- F/A-18C Speed Brake Control Script -- JOY_BTN33 control for speed brake local speedBrakeCommand = { down = 3013, -- Replace with your specific command for speed brake down (extend) up = 3014 -- Replace with your specific command for speed brake up (retract) } function update() local brakeSwitchState = get_digital_input(33) -- JOY_BTN33 if brakeSwitchState == 1 then -- Speed brake down (extend) command_once(speedBrakeCommand.down) else -- Speed brake up (retract) command_once(speedBrakeCommand.up) end end However, since the information on ChatGPT is outdated, I don't know how to apply the script to the latest version of DCS. How can I apply the script, and is the content of the script correct? Thank you for your help.