[Possible Bug] Saved entry FOV precision

[LedZeppster]

Hello @DPI Wizard,

I think I found a bug with FOV precision when saving/loading a calculator entry. I've reproduced it with a couple of different games. Auto FOV doesn't appear to cause it, but seems related.

 

Apex Legends

When creating a new conversion manually (e.g. not loading a saved entry), the FOV is calculated to be "1.285714" (expected and correct):

 

I saved the above as a new entry, then refreshed the page and loaded it. The FOV is now "1.28571" (incorrect):

 

Re-entering "90" (or just hitting a key like Ctrl) in the Auto FOV box causes the FOV to be recalculated and fixed. 

Maybe it has something to do with the max precision in the Apex config file? The "1.285714" value will stay set unless certain graphics settings are changed ingame, causing it to be truncated (or rounded?) to "1.28571".

 

Here's a second example with Deep Rock Galactic...

Calculated value is correct:

 

Saving and loading the entry truncates the value significantly:

On launch, Deep Rock Galactic changes the entered FOV and sensitivity values slightly (expected engine behavior), but keeps the same level of precision unlike Apex.

 

Did I find a bug or am I misunderstanding something?

Thanks!

[DPI Wizard]

There was a limit to the decimal places when saving, I've increased this now so this should work better.

[LedZeppster]

Working as expected now. Thanks!