- New
- Official Post
I was really hoping at this stage there would be an extensive gui
I'm too but I'm working hard in that direction, many of the new features help with developing editor stuff.
I was really hoping at this stage there would be an extensive gui
I'm too but I'm working hard in that direction, many of the new features help with developing editor stuff.
Bravo Klaus!
Particularly delighted about the Vision OS support. I'm hoping that it will make it possible to use the Apple Simulator to test VR without actually having to have a headset in your hands.
great job Klaus thanks for the same
Thanks a lot. I am going to test it.
Bug: Encryption using custom keys does not work properly. Using a license to encrypt is fine.
Bug: Encryption using custom keys does not work properly. Using a license to encrypt is fine.
Are the custom keys embedded in the viewer?
There is check for this in the make vtour droplet and in the protect tool.
Additionally also always clear the browser cache to make sure that the latest files are getting loaded.
If still not working, please send a non-working example by mail.
Are the custom keys embedded in the viewer?
There is check for this in the make vtour droplet and in the protect tool.
The test revealed some interesting phenomena and found that the problem came from id. When using lowercase letter combinations such as "zlp|123456789" will not work, but "Zlp|123456789" will work.
King, huge update.
But why free this update? You spend all your life and here most of developers will be happy to pay for this big upgrade
For some of us, 1.22 does require a license upgrade (from 1.20)
The test revealed some interesting phenomena and found that the problem came from id. When using lowercase letter combinations such as "zlp|123456789" will not work, but "Zlp|123456789" will work.
Thanks for noticing that!
This is a bug in the viewer, a small 'z' character in the key 'ID' name causes the problem (only the 'z' is the problem, all other characters are fine). There will be soon a fixed version.
Thanks very much Klaus!!!
Congratulation
Marco
Hello:
In the ThreeJS: Dancing Cat (Animations) case, roaming in a room with collision detection function, using 3D software to generate three files: tourmodel.obj, texture.jpg, and texture_preview.jpg. Can this be achieved with just the following code?
include url="%VIEWER%/plugins/depthmap_navigation.xml" />
<image>
<preview url="../depthmap/depthmap-textured/texture_preview.jpg" />
<depthmap url="../depthmap/depthmap-textured/tourmodel.obj" texurl="../depthmap/depthmap-textured/texture.jpg" scale="100" hittest="true" />
</image>
Happy to see the updated release. Does 1.22 bring additional functionality to the Vision Pro?
In the ThreeJS: Dancing Cat (Animations) case, roaming in a room with collision detection function, using 3D software to generate three files: tourmodel.obj, texture.jpg, and texture_preview.jpg. Can this be achieved with just the following code?
Sorry, I don't understand what you mean or want to achieve...
Btw - for better clarity, please create separate threads for the discussions about individual examples or how-to-do questions.
Happy to see the updated release. Does 1.22 bring additional functionality to the Vision Pro?
Yes, the Apple Vision Pro should be working now (although still without explicit hand-tracking support yet):
https://krpano.com/docu/releaseno…krpano122_webvr
https://krpano.com/docu/releaseno…_browsersupport
Report - Backwards compatibility issue
When using <depthmap> to display a 3D object (without a pano), in 1.21 it was possible to position the 3D model using the "center" attribute. Even though this was undocumented (at least, I cannot find it in the online documentation) it allowed to reposition the model in 3D space.
In 1.22, this attribute does not work any more and the models in some of my projects are now complete shifted (to the center).
Example code:
<scene name="motorcycle" autoload="true" thumburl="models/motorcycle/motorcycle_preview.jpg" title="Motorcycle 3D Scan">
<!-- the view start for this scene -->
<view oz="2500" vlookat="10" hlookat="0" tx="0" ty="0" tz="0" fov="120" fovmin="70" fovmax="70"/>
<!-- image holds the targets for the introanimation -->
<image targetoz="500" targetvlookat="12" targethlookat="250">
<depthmap url="models/motorcycle/untitled.obj" hittest="true" rendermode="3dmodel" scale="250" textured="true" waitforload="true" origin="0|0|0" center="-.3,.5,0" axis="+x+y+z"/>
</image>
</scene>
Demo
krpano kri-soft annotations plugin DEMO
Using javascript, it was even possible to control the position:
krpano=document.getElementById("krpanoSWFObject").get("global")
krpano.image.depthmap.center="1,0,0"
would move the object. in 1.22, this does not work any more.
origin="0|0|0" center="-.3,.5,0"
Hi,
'origin' and 'center' are doing the same, but with different coordinates systems.
In version 1.21 the 'center' setting was replaced with the 'origin' settings.
The reason for this change was that 'center' was using an arbitrarily coordinate system, and 'origin' then the krpano coordinate system. To keep compatibility, the 'center' setting was still supported and automatically converted to the 'origin' setting. That means internally both settings are getting mapped to same internal variables.
When the depthmap object gets first parsed, 'center' is evaluated as first and then 'origin' as second.
That means in this case, when both are defined, the 'origin' values will overwrite the 'center' ones.
As solution try either removing the origin setting - or remove the center setting and set origin to center values (mapped using x=z, y=y, z=-x).
Best regards,
Klaus
Thanks for the quick response.
The solution with origin instead of center worked, but not with the original values, but with multiplied with the scale as well.
so original:
becomes x=z*scale, y=y*scale, z=-x*scale:
After this little math trick, the model appears in proper location again.
Also, only using center did not solve it - the same math trick had to be applied... new values:
gave the expected result.
So still, there is some small backwards compatibility thing with center. But in the future, I will ofc refrain from using center and use origin instead...
gr,
Kristof
Don’t have an account yet? Register yourself now and be a part of our community!