Palworld Mouse Aim Conversion Issues

[Razoroth]

I have followed every bit of information available here to correctly convert and set the settings in Palworld. Values show correctly in game after using the HEX editor to set them up, but despite all that, the camera and aim settings in game just don't "feel" correct. It feels much much slower than the game(s) I'm converting from (Mainly overwatch 2). My aim settings across all fps titles so far are identical, but for some reason just aren't right in Palworld.

I've already disabled mouse smoothing in the input.ini config file, used hex editor to change mouse setting, went as far as to set aim sens to 2 (Read somewhere to set this to 2 for 1:1 ads/hip aim) but I just can't get it to feel right.

Is it just Palworld at this point? Or are the calculations being used on here incorrect? I know this is a newly added game, so it's still early. Just losing my mind here trying to swap between this game and Overwatch/The Finals because once I leave this game and start up those, my aim on those feel way faster and it's screwing my aim up completely due to muscle memory not being the same.

Advice? (Other than just use controller for Palworld, already considering that for now)

[DPI Wizard]

Is the 360 distance correct? If so it's just a matter of first person and third person feeling different.

[Razoroth]

In the calculator it says the discrepancy is 0% but I can load up both games and even go into a custom match on overwatch forced into third person and there's a huge difference in camera turn speed. I don't have to move it much in OW to turn the camera but moving the same amount in Palworld take me picking my mouse up and repositioning it twice to go the same distance when turning...

[DPI Wizard]

This sounds very much like negative acceleration due to mouse smoothing. Is there any difference with 125 Hz polling rate vs 1000 Hz?

[Razoroth]

No difference. As I said before Mouse Smoothing is disabled via the config file. I tried setting 125hz polling rate anyways to test and it's the same feeling with both 125 and 1000.

I turned the mouse aim setting up from the recommended .71*** to just a flat 2 in game and the camera speed gets faster like expected. I feel like it's something with the calculator at this point. The conversion doesn't feel correct.

[Razoroth]

So I did some more testing, and although it is recommended to edit the config and .sav files to set the settings, the calculations are drastically different between config and in-game calculations.

OW2 --> Palworld ::::: In-Game --> In-Game

Spoiler

 Overwatch 2 - Hipfire  (In-Game)

Sensitivity 1: Sensitivity 11.00%

360° Distance: 6.1983 inches

Config FOV: Field of View 103

 

 Palworld - Look (In-Game)

Sensitivity 1: Mouse Sensitivity 1.4

360° Distance: 6.1231 inches

Max discrepancy: -1.2146% (-0.0753 inches)

Config FOV: Field of View 90

OW2 --> Palworld ::::: In-Game --> Config

Spoiler

 Overwatch 2 - Hipfire (In-Game)

Sensitivity 1: Sensitivity 11.00%

360° Distance: 6.1983 inches

Config FOV: Field of View 103

 

 Palworld - Look (Config)

Sensitivity 1: MouseSensitivity d01d413f (0.754361)

360° Distance: 6.1983 inches

Max discrepancy: 0% (0 inches)

Config FOV: FOV 90

Exact same settings for both calculations, with only the In-Game or Config file setting for Palworld changed to compare results. While I don't expect EXACT same numbers between the two ways of changing the settings, one calculating .71 and the other 1.4 is a large difference, and going by the In-Game settings suggested feels closer to how it should. I'm guessing since the In-Game calculation is 2x the config file setting, that there may be a missing or incorrect part of the calculation taking place. (I'm not a math expert or coding expert by any means, idk how all this works, hence why I'm here for my settings in the first place lol. Just my observation on the two numbers produced)

I feel that the recommendation to set settings via the config file over the In-Game settings should be changed for now as it is not producing correct results, at least for my situation.

Changing the FOV with a hex editor should only be suggested if going above 90 since that's the only way it can be set higher right now.

Hope this info helps someone else in my situation!

Edited January 27 by Razoroth

[DPI Wizard]

I see the issue now, you have entered 90 as the FOV for config file. This is effectively an FOV of 165, not 90 since it's a multiplier. Switch the FOV type to Hdeg Res if you want to enter the actual FOV directly, then check the output for the Config FOV which is the FOV you should configure in the config file.

This should solve the issue