Currently the way the cursor behaves when using a hat or buttons to move it is it accelerates from zero to full speed. IMHO, this makes it feel sluggish and unresponsive.
If its starting speed was 1/4 or 1/2 of full speed instead, it would give immediate feedback, while still being slow enough to enable small movements.
When I run F4RADAR from 2D as indicated, the PPTs and the lines aren’t displayed. Bullseye is displayed on the right location.
When I go into 3D, the bullseye, PPTs and lines get pushed to the lower left corner of the map.
About AWACS:
Before 4.35 (maybe 4.34? I’m not entirely sure), AWACS wouldn’t stop screaming if you passed above a pair of enemy cargo helicopters. After 4.35, AWACS will not warn you about incoming threats on its own. Though you can clearly hear it warning other flights in your package.
Related to the previous point, I wish AWACS would also warn about new incoming threats (fighters moving towards me at high speed) when already engaged.
AWACS seems to have no memory. It it loses a previously ID’ed group, it will forget their ID.
About wingmen:
Before 4.36.3, wingmen would attack a single vehicle in a group or structure in a complex if you ordered them to “attack target”(W/E/R-1), and they would attack all vehicles or structures if ordered to “attack targets” with an S (W/E/R-8, currently 9). Now in 4.36.3, they always attack all vehicles or structures, no matter what order you give them.
Before 4.36.3, wingmen would release weapons immediately upon receiving the order to attack a target if they were in range, without leaving formation. Now they fly all over the place until they find a firing position they like.
Finally, I wish wingmen would warn about immediate threats they detect and give some information about what targets they want to attack when requesting permission to engage.
When controling the SOI cursor with the keyboard or joystick buttons (not an analog control), there’s suposed to be an “acceleration” or speed ramp-up.
However, this “acceleration” is missing when making a cursor movement in one axis (up/down), and then attempting to move it in another axis (left/right). The acceleration is present when making movements on the same axis (moving the cursor up and down or left and right repeatedly).
@jayb Those options are for controlling the behavior of an analog joystick axis used to control the cursor, for cases of physical ministicks on joysticks not working quite right.
Unfortunately for our case, it doesn’t affect “digital” cursor controls.
@RingoSurf I’m pretty sure all the cursors are affected, but the TGP is where it’s most noticeable.
@airtex2019 I don’t think the problem can be well represented in a video clip.
Also, the AA FCR feels like the least affected cursor.
To replicate, bring up the TGP. Using SimCursorLeft and Right, move the view left and right. You should notice the view accelerates from zero to full speed.
Then, press SimCursorUp or Down. You should feel like the view starts moving almost or at full speed right from the beginning. But if you continue moving the view alternating between SimCursorUp and Down, you should feel the same acceleration as when moving it left and right
@airtex2019 I am using SimCursorUp/Down, releasing it, then using SimCursorLeft/Right. Never using the diagonal directions.
Edit: To clarify even further, the problem also appears when using SimCursorUp/Down after having used SimCursorLeft/Right.
When controling the SOI cursor with the keyboard or joystick buttons (not an analog control), there’s suposed to be an “acceleration” or speed ramp-up.
However, this “acceleration” is missing when making a cursor movement in one axis (up/down), and then attempting to move it in another axis (left/right). The acceleration is present when making movements on the same axis (moving the cursor up and down or left and right repeatedly).
@danaos75 more than a month later…
That looked promising, but sadly it only affects the behavior of the cursor when controlled by an analog axis.
@danaos75 said in Sluggish cursor when using hat or buttons:
@Huesudo maybe this will help https://forum.falcon-bms.com/post/363021
That looks interesting. I’ll give it a try! 
p.s. I also have to see why I’m not getting email notifications about post replies. 
@danaos75 indeed you can change the cursor speed in the config, but that’s the final full speed. I’d like to change the initial speed.
Currently the way the cursor behaves when using a hat or buttons to move it is it accelerates from zero to full speed. IMHO, this makes it feel sluggish and unresponsive.
If its starting speed was 1/4 or 1/2 of full speed instead, it would give immediate feedback, while still being slow enough to enable small movements.
@spectrclaw said in My thoughts on the current state of AI wingmen and AWACS:
Also I’m wondering if they still have the Archer Inbound callout from the AI wingman. Maybe they can implement different warnings for AI in the future.
They still do sometimes. I’m not sure what are the conditions for them to give the warning.