missing contrary evidence Radar cursor speed too slow

[Terzi]

Hello,

I setup my TDC cursor axis to have no deadzones in hardware and DCS settings. On the FCR I get zero deadzone (as intended) where I can move the cursor with excellent slow rates precision. But in Maverick WPN page there is a hidden deadzone that you can never get rid of. You need to move it up to some point (let's say 5%), and only after that point, maverick screen will move with 6% input rate. You can never move it with e.g 2% control.

If the cursor graphs would be visible just like Right Ctrl + Enter I could show it. Please try yourself and if you cannot generate, I will try to make a video. Thanks!

[_SteelFalcon_]

This. It‘s been this way for way too long already. FCR slew is significantly slower than any other mfd cursor. It‘y be nice if the speeds were the same across all sensors

Edited May 23, 2023 by _SteelFalcon_

[AZDane]

The Radar cursor speed is too slow compared to the real deal. Is there a way to speed it up?

I don’t have any curves and my radar cursor switch on my WW Throttle is correctly calibrated. 
Wonder if there is any option to  increase the speed. 

[Furiz]

43 minutes ago, AZDane said:

The Radar cursor speed is too slow compared to the real deal.

Can you show us the real deal?

[AZDane]

8 minutes ago, Furiz said:

Can you show us the real deal?

Don’t have access anymore, but it’s significantly slower. Doesn’t really matter when you are moving the cursor around the screen, but when you quickly want to change between A6 & A3 it’s annoying. 

[Furiz]

I can agree it's annoying when switching A6 to A3 etc, but don't have any reference for now. I'll try to dig in some vids but they need specifics...

[AZDane]

Old radar, but it shows how quickly you can move the cursor in the airplane:

https://youtu.be/Aq5HXTGUHGI?t=320

Look 5:20 and 5:48

Edited May 26, 2023 by AZDane

[Oceandar]

I don't know about the real thing but I like cursor speed of Viper more than Hornet after ED tuned it more faster.

[AZDane]

36 minutes ago, Oceandar said:

I don't know about the real thing but I like cursor speed of Viper more than Hornet after ED tuned it more faster.

It’s just too slow when you use it to switch screens. I think the real cursor might follow a curve. You need to be able to switch screens really quick while retaining the ability to do precise cursor work. 

[Gungho]

I agree along with the poor energy retention of the viper. The cursor being so slow at max deflection of the slew axis gets me killed in bvr engagements.

[ACME_WIdgets]

Just use a curve with "+" setting/number and it will get much faster around center.

[AZDane]

2 hours ago, ACME_WIdgets said:

Just use a curve with "+" setting/number and it will get much faster around center.

Its the max speed thats the problem. Not the speed around center. To flip quickly between A3/A6 you use max deflection. Same with changing range.

[_SteelFalcon_]

And it‘s a lot slower on the fcr compared to HSD and HAD currently at max deflection. Shouldn‘t they behave the same in that regard across all displays and pages?

Edited May 31, 2023 by _SteelFalcon_

[darkman222]

And its faster slewing Maverick seeker heads around, makes it really a challenge not to overshoot with the crosshair, while the speed on the TGP is slower.

Dont know if this inconsistency in speed is realistic or not. But its impossible to assign an input curve to the mini stick / radar cursor that is convenient for all sensors.

[falcon_120]

The real aircraft has what you'd call in windows mouse acceleration, basically is sense pressure so can be extremely fast when needed or extremely precise if force applied is subtle.

In this video you can kind of see how the tdc accelarates in certain moments.

 

 

[darkman222]

Very interesting. So wait, what youre saying is that the radar cursor mini stick is force sensing like the F16 side stick too? Which means it does not move, or just little as the side stick?

Are you a pilot or F16 maintainer and share some more insight?

[VarZat]

I believe the ministick is indeed force-sensing. I think the early pre MLU ones was full travel though

[Geraki]

20 hours ago, VarZat said:

I believe the ministick is indeed force-sensing. I think the early pre MLU ones was full travel though

Hi the F-16 throttle microstick in reality is not force sensing , it is move in X/Y/Z  axes , but i think in the lua you can edit the values of cursor movement to make it move quicker.

[_SteelFalcon_]

This should be a special option slider instead of having to set curves for it or editing lua files.

also the cursor speed should be the same across all displays, which it currently clearly is not

[Terzi]

Just a reminder. Any comments on this from officials?

[Terzi]

This needs a contrary evidence? How? Should I jump in a real F-16 (I wish I could) and make a video? This is about usability. Please test this: Try moving the Maverick WPN cursor by tiny amounts. You will understand the problem for sure.

[falcon_120]

This needs a contrary evidence? How? Should I jump in a real F-16 (I wish I could) and make a video? This is about usability. Please test this: Try moving the Maverick WPN cursor by tiny amounts. You will understand the problem for sure.

there already a video above showing the speed of the TDC, now it is indeed a bit too slow, or at least is not possible to bump it quick enough.

Enviado desde mi ELE-L29 mediante Tapatalk

[Terzi]

I think my original point was not clear. I was not complaining about FCR cursor speed. The problem I described above is: Maverick WPN page has some hidden deadzone and you can have hard time doing minor adjustments. (Was the topic title somehow changed?)

[AZDane]

20 hours ago, Terzi said:

I think my original point was not clear. I was not complaining about FCR cursor speed. The problem I described above is: Maverick WPN page has some hidden deadzone and you can have hard time doing minor adjustments. (Was the topic title somehow changed?)

No. Title has always been:

Radar cursor speed too slow

[Terzi]

Okay the title is fine. How about the hidden deadzone in maverick WPN page that I mentioned in the 1st post? Is it going to be fixed or needs evidence? Has ED even looked at it?