So, I got to this formula for multiresthreshold=0:
Fh = 2*arctan(w/r)
Fh - horizontal FOV
w - stage width (size of the embedded flash or, when in fullscreen, the screen resolution)
r - resolution level
After some tests, I can conclude that this formula isn't right :P However, it does fail "predictably". That is, the offset to the real value only seems to depends on the final Fh. So, I just did a function fitting and got values which match very well the tests I made.
The attached table shows the minimum horizontal fov at which krpano will keep a certain resolution level. This depends on the stage resolution, which is displayed on the left. The table contains values for the most commonly used screen resolutions (usage data from a website I have and the first couple of hits on google for "most common screen resolutions" ;).
Using this table, you can predict which resolution level will be seen, and hopefully it will help plan the multiresolution levels better :) I'm also attaching an Excel sheet, where you can add your own resolutions and levels.
By the way, the offset I got before compensating with the fitted function was this. Any thoughts on what this function may be? X is the predicted FOV and Y is the offset to the measured FOV.
I guess Klaus has more info on how multires levels are selected, as well as on how exactly the multiresthreshold parameter affects it. Could we have some insight on this? ;)
Also, is the manual setting of resolution levels in kmakemultires (like mentioned
here ) planned for any time soon? It would be extremely helpful!
Cheers,
Manuel