Roboquest

3 minutes ago, jinglebuns said:

How do I properly adjust the sensitivity? It's only letting me input values in increments of 1.

Are you not able to enter the sensitivity manually with many decimals?

I'm on the demo, let me know if it's different on the full version!

3 hours ago, jinglebuns said:

Nope. It seems like they changed it from the demo.

The release was indeed completely different! Updated it now!

23 minutes ago, PIECEofTOAST said:

Bumping because this listing appears to be incomplete and/or changed recently. There is a scope sensitivity slider in-game that isn't listed on this site. Also the calculations in-game might have changed? I'm not sure. My sensitivity doesn't feel quite right in-game after converting but that might be caused by a different issue

It does seem to be slightly changed indeed, will take a closer look at it tomorrow!

13 hours ago, PIECEofTOAST said:

Bumping because this listing appears to be incomplete and/or changed recently. There is a scope sensitivity slider in-game that isn't listed on this site. Also the calculations in-game might have changed? I'm not sure. My sensitivity doesn't feel quite right in-game after converting but that might be caused by a different issue

Roboquest is updated now. This is new:

• Adjustable FOV
• Sensitivity scale to actual FOV (not configured FOV)
• Scope added

Note that this game still have a lot of issues with report rate, so I would set it to 125 Hz to be sure it isn't negatively accelerated.

3 hours ago, PIECEofTOAST said:

unsure how much of an effect this has, just figured I'd mention it here if you wanted to look into it. 

It's just good news, this means that 1000 Hz polling rate works fine. Calculations stay the same but the sensitivity is more precise.

14 hours ago, The_Fartist said:

the calculator says, that the 360 distance (sensitivity) should be 43.5472cm, but it felt off, so i checked it out by using the kovaaks sensitivity matcher

The calculations are correct, but the sensitivity slider is inaccurate. Instead of dragging it, enter the numbers manually, and it should be spot on. Note that the distance you should enter into the sensitivity matcher is 43.9871 (Horizontal Speed), as this is slightly corrected compared to the base sensitivity due to lack of decimals

3 hours ago, poppe said:

1.0 got released. Seems like they 10x'd the sensitivity range from 1-100 to 1-1000 so you can be more precise.

Also, is vertical speed really supposed to be 100?

I've updated it now, and also re-ordered the calculation so the Horizontal Speed is calculated first. This will increase the range and avoid potential errors.

Vertical Speed should be set to the same as Horizontal if you want them 1:1.