You are not logged in.

limitview problem

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 1,063

Location: Denmark

Occupation: Photographer

  • Send private message

1

Tuesday, June 12th 2012, 8:10pm

limitview problem

I want to set the limitview for my first scene like this.
limitview ="range" hlookatmin="-90" hlookatmax="90" vlookatmin="75" vlookatmax="-68"

on all the other scenes I just want to set it for making possible to look over the zenith like this
limitview="range" vlookatmin="90" vlookatmax="-100"

However it turns out that the first scene limits affects all scenes . Also if I remove the limitview="range" vlookatmin="90" vlookatmax="-100" from those scenes.

This does not make sense at all.

Hans

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 1,063

Location: Denmark

Occupation: Photographer

  • Send private message

2

Tuesday, June 12th 2012, 8:50pm

Even more weird is that if I remove the hlookatmin="-90" hlookatmax="90" from the first scene the other scenes does work as they should do with the different vlookatmax="-100"

Hans

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 1,063

Location: Denmark

Occupation: Photographer

  • Send private message

3

Tuesday, June 12th 2012, 9:01pm

Ok I found out. It seems you have to set the hlookatmin,max to 180 on all the scenes which you do not want to limit.

The documentaion says this; I think that is misleading.
Notes to "range", "fullrange" and "offrange":
when the "hlookatmin", "hlookatmax", "vlookatmin", "vlookatmax" values were not set, they will be automatically calculated from the size of the pano image.

Hans

image360

Intermediate

Posts: 215

Location: Austin, TX and Chicago, IL

Occupation: Photographer

  • Send private message

4

Wednesday, June 13th 2012, 5:51am

Documentation NOt matching results?

Hans, I'm not sure sure about your findings, but the whole view limiting verses the documentation does seem to be off in some way. I've been doing a very large series of limited views (almost 50 sets) and have had to use on a few sets values greater than +-180 which according to the current documentation is wrong, but it works.

Klaus provided some quick support with a useful graphic here. But has yet to respond to me why numbers greater than -+180 seem to work.

http://krpano.com/forum/wbb/index.php?pa…95c1984607e85cc

Regards,

Robert

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 1,063

Location: Denmark

Occupation: Photographer

  • Send private message

5

Wednesday, June 13th 2012, 11:09am

As you can see from above the problem is that if you use the full limitview settings like this on the first scene.
limitview ="range" hlookatmin="-90" hlookatmax="90" vlookatmin="75" vlookatmax="-68"

it will be inherited to all scenes with both hlookat and vlookat even if you use this in the next scenes.
limitview="range" vlookatmin="90" vlookatmax="-100"

the changed vlookatmin="90" vlookatmax="-100" is simply ignored.

That does not make sense.

Hans

klaus.krpano

Administrator

Posts: 13,499

  • Send private message

6

Thursday, June 14th 2012, 11:05am

Hi,

were you using the KEEPVIEW flag?
and is your question regarding to the Flash Viewer or the HTML5 Viewer or both?
and which krpano version?

best regards,
Klaus

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 1,063

Location: Denmark

Occupation: Photographer

  • Send private message

7

Thursday, June 14th 2012, 2:46pm

Quoted from "klaus.krpano"

is your question regarding to the Flash Viewer or the HTML5 Viewer or both?


Latest version but I checked one from last year and it was the same.
I never got as far as checking the HTML5 version. I got it working by using all the settings in all scenes so I did not check that.

No Keep view.

Hans

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 1,063

Location: Denmark

Occupation: Photographer

  • Send private message

8

Thursday, June 14th 2012, 3:05pm

I made an extra xml to test it.
http://virtualdenmark.dk/dnm/audienssale…ama/limits.html

As you can see the initial pano has both horizontal and vertical limits.
If you load number 2 everything works. It has has also horizontal and vertical limits but with different values and the horizontal is set to + - 180

But if you load No 3 pano first you can see that the limits are the same as the initial pano even if I have these settings in the scene.
<view hlookat="0" vlookat="0" fovtype="MFOV" fov="90" maxpixelzoom="1.0" fovmin="60" fovmax="120" limitview="range" vlookatmin="90" vlookatmax="-100" />

Hans

HansNyb

Professional

  • "HansNyb" started this thread

Posts: 1,063

Location: Denmark

Occupation: Photographer

  • Send private message

9

Thursday, June 14th 2012, 3:57pm

Tested it on my iPad and it looks like the problem is only for flash.

Both No 2 and 3 works the same.

Hans

klaus.krpano

Administrator

Posts: 13,499

  • Send private message

10

Friday, June 15th 2012, 11:11am

Hi,

thanks!

Right, it's a bug/issue in the Flash viewer - when using the MERGE flag, the new viewing limits will be merged with the older ones, that means the old limits kept set when they were not overwritten in the new pano.

But I agree that the viewing limits should be always reset, even with MERGE flag - each pano should define it's own viewing limits.

In the next release the viewing limits will be always set back to default when loading a new pano.
The 1.0.8.15 HTML5 viewer already works that way.

As workaround for the current version always all limiting values (hlookatmin,hlookatmax, vlookatmin, vlookatmax) for each pano. Either set hlookatmin=-180 hlookatmax=+180 or hlookatmin=NaN hlookatmax=NaN to disable the horizontal limitation.

Best regards,
Klaus

Similar threads