Mouse Cursor Off Center?

[Pandur]

Hey guys, i did try to find something about it with google/forums search for 30 minutes but did not find anything.

 

I played SB versions 2.5XX, 3.0XX, 4.0XX so far and now upgraded recently to 4.2XX( and with 4.2 there is something new with the mouse cursor in the gun sights of all tanks and also other sights.

 

In all the older versions when i put the mouse cursor(little black crosshair)in the center of the gun sight/reticle the gun was perfectly still and centered and not moving. Now with 4.2 when i do the same, the gun is moving upwards, so for the mouse the center of the sight is well below the center of the reticle/crosshair.

 

This makes it quiet a bit harder to aim i feel, at least for me so far, since the movement induced by the mouse cursor position is relative to an invisible(!!!?) point on the sight and no longer relative to the center of the reticle/sight. I hope you understand what i try to say.

Since this point is invisible it is quiet a bit more fiddly to match the sights movement to a moving target and also to simply stop the sight moving on a stopped target, since you never know exactly where that point that used to be on the reticle center is located now, it is, well, an invisible point.

 

Now, is that only for me? Is that a bug or is that a deliberate change? As said, last version i play was a 4.0 version and it was not like that and all the old versions it was also not like that... so why did that change?

 

Greetings

[Lumituisku]

Maybe you have some other controller giving inputs?  You could try to center your joystic  Alt + J?   

 

Does this happen on all vehicles or some specific vehicle / weapong system? 

[Ssnake]

I'm not aware of a recent change. Personally, I always wanted the reference center for mouse control to be the reticule of the sight. I respect the programmers' decision to use the center of the screen instead, which often (but not always) coincides. It makes programming less error prone (which is also important) and of course there's fire control systems with a moving crosshair, so what should the reference then be?

Okay, so the screen center it is.

If you want to check across different tanks, activate the option for the "mouse vector". That way you can at least see where the center is that the mouse uses for reference.

 

If you find inconsistencies, please document with screenshot while the mouse vector is drawn. That makes it easier to investigate.

[Pandur]

I do not have a joystick plugged in, i have nothing plugged in with an axis. Only mouse and keyboard is plugged into the PC.

 

Its not that my picture is constantly moving but that i have to put the mouse cursor about ~1cm(measured on the real world screen) below the center of them crosshair/reticle so the gun stops moving up. Left/right is perfectly center but up/down is not.

 

So you say that is not how its supposed to be now? I guess that is good so i can maybe fix it to be just like it used to be.

 

If my explaination is not understandable i can try to illustrate it with a picture or two. And yes, it is absolutely consistently off in every sight i used so far, gunner sights, commander sights/citv.

 

28 minutes ago, Ssnake said:

I'm not aware of a recent change. Personally, I always wanted the reference center for mouse control to be the reticule of the sight. I respect the programmers' decision to use the center of the screen instead, which often (but not always) coincides. It makes programming less error prone (which is also important) and of course there's fire control systems with a moving crosshair, so what should the reference then be?

Okay, so the screen center it is.

If you want to check across different tanks, activate the option for the "mouse vector". That way you can at least see where the center is that the mouse uses for reference.

 

If you find inconsistencies, please document with screenshot while the mouse vector is drawn. That makes it easier to investigate.

 

Ok, mouse vector, i did not know about that, i will try that and make screens as needed.

I dont know how, but something must have changed, either on my PC or the game, since the center was always in the center of the gunner reticule in almost all vehicles in all versions i play before, only now in 4.2 i notice the change first time. I did not play a 4.1 version so i dont know if it is the same in 4.1 as it is now.

[Pandur]

This is how it looks with vector, the white mouse crosshair is invisible on screenshot.

 

On this 2 screens the sight is perfrectly still and not moving, but the mouse is quiet a bit below the marked center of the screen(or reference point). IF i move the mouse up to shorten the vector/move the cursor to the center, the sight will start to move upward.

 

 

Edited August 22, 2021 by Pandur

[Ssnake]

In some vehicles (ASLAV-25 comes to mind) and with some types of binoculars the crosshairs of the reticule never are in the center of the screen (vertically), so that would be an example where it's perfectly normal. Since the "center of the screen" also depends, obviously, on the screen aspect ratio, this could also result in a (horizontal) shift of the center, depending on the realism settings (e.g. Leopard 1 may have additional controls at the side that might offset the view slightly off-center, at least in medium and low realism settings).

And like I mentioned, when you have horizontal shifts of the reticule (as in the ASLAV-25, M1, ...) with moving engagements, the mere expectation of the mouse control's origins aligning with the crosshairs simply cannot be met. But none of these examples seem to be an exact match of your case description.

 

In your screenshots, i'm not entirely sure if your mouse is below the crosshairs, or right in them. If you could move the sight slightly to one side, then it'll become obvious what the origin of the line is and where it ends.

[Pandur]

In the screens you can see the vector? It extends/originates from the center of the reticule(top end of vector) and the mouse is on the bottom end of the vector. In this position the sight is perfectly still. But should´nt it move down?

 

I do have high realism selected and i know the m1a1 sights do jump on laze, that is not the problem here i think. The bottom pic is the m1a2 sep and the top is a cv3040.

 

EDIT: i am in 1920x1080 full screen, as i always was back in older versions.

 

EDIT2: there is another notable change, the mouse cursor always  used to be black and was hard to see in white hot TIS at times... now suddenly in 4.2 i have a white mouse cursor... is this supposed to be like that or could this indicate some other problem? Some sort of hard or software acceleration problem with the mouse or something?

I do have the same mouse since ages, so that did not change but i upgraded to win10 only recently and played all the older versions, where things behaved normaly, in win7.

Edited August 22, 2021 by Pandur

[Ssnake]

I agree, if a mouse vector line is drawn, it should "pull" the view. If it doesn't, then something's not quite right.

This is now bug #9971.

[Pandur]

14 hours ago, Ssnake said:

I agree, if a mouse vector line is drawn, it should "pull" the view. If it doesn't, then something's not quite right.

This is now bug #9971.

 

It should, right? I am glad you say that cause i started wondering if that is supposed to be like that.

 

It seems not many people have this problem, and i also never had this problem in any other version before, so maybe something is off with my mouse (Logitech G3 + set point software) or some setting on my PC.

I take a look how old my set point software is and try update it or something, maybe its not the games fault ... it seems that i am the first one to report this so it has to be very rare.

Edited August 23, 2021 by Pandur

[Ssnake]

Seems like this was introduced in version 4.1 with another bug fix. We're on it.

[Pandur]

Wow nice one, i just came back in here to say that i try a few things on my end, but no luck on my side, i could not make it go away.

I wanted to ask if i can provide anything to help... DxDiag or something from my PC?

 

On short range it is no problem, but it rly throws off my long range gunnery, especially on moving targets, very annoying.

 

Lucky me i have a gunnery rating of 105 and the AI hit well for the most part in single player  (not sure if it is internally hard capped at 100 anyways or if the extra 5 do anything)

Edited August 26, 2021 by Pandur

[Ssnake]

I think we're all set. We can replicate the problem, we "just" have to patch it, test the patch, then release an update.