Posts by mastucc

Hi Klauss,
thank you very much for the update and the constant support.

Marco

Hi Klauss,
thanks for your checking and your answer.
Now, let's wait for the new updated version.

Best regards,
Marco

Hi Klauss,
thanks for the new version 1.22.1
The previous problem has been solved..!!!
But I would like to report a strange behavior with combobox.xml, as you can see in the attached image.
With the new version 1.22 / 1.22.1 there are two empty elements, while in the old version 1.21 it work fine.
I investigated the code and discovered that the problem is here:

<action name="hideflag">
	for(set(i,1), i LT 153, inc(i),
		set(hotspot[calc('spot_' + get(i))].alpha, 0.0);			
	);
</action>

Line 1230 in tour2.xml

This action is called by skin_setup_littleplanetintro in vtourskin.xml to make the flags invisible.

Version 1.21 (work fine)

Version 1.22.1 (not work fine - In this example I reduced the number of pano for convenience)

I could not solve the problem.
I would like to ask you if you also experience differences between the versions.
Thanks in advance.
Marco

Thanks Klaus for your prompt response and detailed analysis of the problem.
But also thanks for all the work done in constantly updating the krpano player.

I am "anxiously " waiting for the new version...
Marco

Hi Klaus, congratulations on the new version.
I have to report a problem between version 1.21 and the new version 1.22.
Using exactly the same code, there is a completely different behavior in a conditional code execution (if...).
I take a variable ("mytag") and compare it with the value of another variable passed by an argument. in version 1.22 the "if" condition is not executed, while in version 1.21 it works correctly.
To test the different behavior, click on the two icons on the right to activate or deactivate the colored icons on the map.

        for(set(i,1), i LT 21, inc(i),
            if(hotspot[calc('spot_' + get(i))].mytag == get(var1), 
                switch(hotspot[calc('spot_' + get(i))].visible);
             );
        );

Below I have attached both projects with both versions.
Link Projects:

Version 1.21 (works correctly)
Version 1.22

Please, where is the problem...???

Marco

Thanks very much Klaus!!!
Congratulation

Marco

I have the same problem. In pc it's always flicker

Thanks, Marco

Very interesting discussion.
Is it possible to insert an image in the div block?

For example:

<li>With support for browser-based-scrolling by mouse-wheel, scroll-bars and touch-controls.</li>
<li>Fully integrated into krpano as &lt;layer&gt; container element.</li>
<img src="acb.jpg" alt="test image">

I can't link correctly the image.
Where is my mistake,
Marco

Hi Klaus,
...a Minor Release, but fantastic bugfix for camroll.

I will send you an example.

Thanks, Marco

Quote from klaus.krpano

Good question - I have added now a compensation for the camroll setting when controlling/panning the pano. Will be also there in the next release (1.20.6).

Thanks Klaus for your answer and future update in new realese.
This function is very important in the case of rotation of a dome, for the analysis of figures and frescoes.
Please look at this link --> https://www.marcostucchi.com/Panoramiche/Vi…_CupolaGenerale

Through a slider I want to allow rotation +180 degrees, -180 degrees.
Thanks Marco

hi all, interestng discussion. I also have a flat image (a cartographics map) and when I rotate the image it alters the behavior of the muose inside the view.
My question: is it possible to alter the rotation of the image, but normally functionally keep the muose on the Cartesian axes?
If I rotate the image by +45 or -90 degrees, the behavior of the muose is also altered.
Thanks, Marco

Hi all, hi Klauss,

I often integrate flat images into my projects, but today krpano does not support, oe better ... this works in VR too, but the image will be very very small.
My question: is it possible to exclude a flat image when I use VR mode ... ?
For example, when switching from normal view to VR mode, flat images are not displayed, as long there is not a easy solution a new krpano version.

Thanks a lot, Marco

Quote from Scott Witte

Virtual tour image resolution seems significantly less in Firefox Reality than in the Oculus browser on the Oculus Go. View change while moving your head seems a little more "stuttering" as well -- lower frame rate. Anybody else experience this? Is there some setting either in the browser or in KRPano that could correct these issues? A Google search didn't seem to find any discussion suggesting these are known issues.

I confirm...!!! when I use Firefox.
I have exactly the same problems...!!!

With Oculus browser il work very, very fine.

Marco

http://www.marcostucchi.com/

Hi all,

I have the same problem with this image with version 1.19-pr13.

Marco

Hi Klauss, thanks for your reply.

Marco

Hi Alexey, thanks for your reply.
I also think the problem is in new skin design and VR.
I have read the code in 'vtourskin.xml', but I understand where is the problem... between 1.18.6 version and 1.19-pr8 version.

Now I created un new test, with hotspot elements; previous example used layer elments.
Please see the difference in the attached images and check the link directly with the mobile devide.
The hotspot elements are scaled if you use the 'distorted=true', but not if 'distorted' is set to false.
Test with 1.18.6

-> http://www.marcostucchi.com/temp/testkrpan…18.6/tour2.html

Test with 1.19-pr8

-> http://www.marcostucchi.com/temp/testkrpan…-pr8/tour2.html

After these simple tests I noticed that the new version all elements version does not scale properly.
Does anyone have these same problems with scaling elements.

Thanks, Marco

Hi Klauss,
I have a question about mobilescale setting.
There are the difference between version 1.18.6 and 1.19-pr8.

With krpano 1.18 versione all elements are correctly scaled, but with 1.19-pr8 the elements aren't scaled by default.
In krpano documentation there is:
•By default all krpano content on mobile devices will be scaled by 0.5.
•To disable that scaling, set the mobilescale setting to 1.0.

Obviously, I can you use the property device.mobile="0.5" for all elements in my xml project, but I would like to know why this difference.
Why this new version (1.19-pr8) don't work as previus version (1.18.6)...?

Example with 1.18.6 version:

http://www.marcostucchi.com/temp/testkrpan….18.6/tour.html

Example with 1.19-pr8 version:

http://www.marcostucchi.com/temp/testkrpan…9-pr8/tour.html

With 1.19-pr4 I had already reported a problem with the mobilescale setting.

Thanks and best regards, Marco

Hi Klaus, hi all.
I would like to report a problem with 1.19pr4.
With the version 1.19pr4 the the buttons version does not scale correctly, while with version 1.18.5 - 1.18.6 it work very fine.
I tested this example a sun Galaxy S7 Edge with Firefox and Chrome browers.
Does anyone have the same problem???

Link:

Hi all
But someone uses CB Enabler for Gear VR...???

MArco

Hi Klauss,

Thank you for your reply.

Marco