Cursor radar
-
@mppzgz what version of Vjoy and windows 10 do you have?
-
@TheSilkMan Edición
Windows 10 Pro Versión 21H2 Instalado el 20/11/2020 Compilación del sistema operativo 19044.2364 Experiencia Windows Feature Experience Pack 120.2212.4190.0
-
This post is deleted! -
@Tumbler31 said in Cursor radar:
If the diagonal movements are not mapped, you cannot move diagionally anymore (eg with shift-arrow keys) or get weird results as shown in the clip above.
It seems to come from a refactor with some unintended side effects. Sadly there’s to work around available, but it is on the list for U1
@Tumbler31 Thx.
Do you have any idea how long before the release of the update?
-
@Maveric said in Cursor radar:
@Tumbler31 said in Cursor radar:
If the diagonal movements are not mapped, you cannot move diagionally anymore (eg with shift-arrow keys) or get weird results as shown in the clip above.
It seems to come from a refactor with some unintended side effects. Sadly there’s to work around available, but it is on the list for U1
@Tumbler31 Thx.
Do you have any idea how long before the release of the update?
-
Same problem for me with the cursor of my X52 Pro, having erratics movements.
In 4.36 it was working fine with axis three bands.
Hoping it will be corrected soon ! -
I have a problem with radar cursor even on keyboard with default mapping:
in settings Shift + up/down/left/right show that binding are correct, in cockpit it has no any reaction - cursor ignore it and stays in center no matter what
Saw same complains thing in youtube comments under some video about bms 4.37, so i’m not alone in with it in some degree, but yet can’t find more suitable thread on forum than that one, assuming the same new callbacks kind nature.
-
-
@Dronny just to verify … if you have an analog axis mapped to x/y cursor, the keyboard/button/hat callbacks won’t work
-
@Dronny said in Cursor radar:
in settings Shift + up/down/left/right show that binding are correct, in cockpit it has no any reaction - cursor ignore it and stays in center no matter what
You are not in SP mode by any chance ?
-
@jayb said in Cursor radar:
You are not in SP mode by any chance ?
Nope, same behaviors on any type of soi.
@airtex2019 said in Cursor radar:
if you have an analog axis mapped to x/y cursor, the keyboard/button/hat callbacks won’t work
Have no axis mapped on them as far as i know (none available for that even if i wanted so), yes. And even if controller stays selected as keyboard only, also.
-
@AlehandroGTI Yes, I have the exact same problem in 4.37 using the Logitech X52 Pro model. I have both 4.36 and 4.37 installed on my machine. The Logitech X52 mini-stick (on the throttle) responds as programmed in 4.36 however when I launch 4.37 the mini-stick controller produces this same skittish control result shown in Alehandro’s video (rendering this control pretty much useless) - which is a big deal as we use it to control the Radar curser and I can’t come up with somethig else to do this (aside fro the keyboard). Nice work on 4.37 BTW - Not really complaining, however until I find a solution to this issue I have to stick with 4.36.- Thanks for logging this issue @AlehandroGTI
-
Can sby check if it has been fixed on U1?
-
There is still an issue with it.
For the ministick I’m using the key buttons, together with the logitech X52 software.
For example:
- If I press button up and right cursor moves diagonal to the right.
- If I keep the up button pressed and release the right botton cursor stops. When I press right botton again (still up button pressed) curosr moves to the right
- same with other directions
Cursor should move like in 4.36:
- If I press button up and right cursor moves diagonal to the right.
- If I keep the up button pressed and release the right botton cursor moves up. When I press right botton again (still up button pressed) curosr moves diagonal to the right
-
Don’t think it will get fixed anytime soon as it is not really a common problem, only us X52 users
-
@gabrielwong1991 and keyboard users
-
TM Cougar. Same deal
-
@gabrielwong1991
A solution would be to use the mini-stick as an axis. I have an X52 and it works without an issue. The downside is that you have to “give up” on another axis and I don’t know if that’s what’s preventing you and the others from using it.Personally, I’d take a smooth, analog radar cursor over the twist axis (rudder).
-
issue spotted, should be fixed in a next release
-
It got better since U1, but cursor movement is still weird at times.