Posts by bitbyter

Is there any chance that someone in this thread knows whether it's possible / how to update old Panotour 2.514 with latest krpano engine? If not, what's the best replacement for Panotour using krpano engine?

Thx, Scott

Thanks Mische, that helped! Slowly getting the hang of it! Cheers, Scott

Sorry to bug you again Mische, but I've followed your video example with another model and still can't figure out why "Make Export Ready" button rotates the model on its side (and therefore distorts my new skin). I've made a short video to show that there are no outstanding translations on model, cam, or cam handle but clicking the button results in weird translation. Is there anything else I need to do to get ready for export?

https://youtu.be/qLgS3r0QwdA
Cheers, Scott

Hi, I recently added some sliders to the depthmap_helper.xml file provided by Klaus. Values for prealign X,Y,Z and ox,oy,oz can be changed interactively and work well. However I also tried to add similar controls to investigate the depthmap "center" values but I can't get the model to refresh regardless of using updateobject(true,true), updatescreen(), or invalidatescreen() functions.
I even tried adding a "brute force" test button to change the values and force refresh multiple ways but can't seem to get any joy :(
Anyone know how to force the model to refresh with the new values? Attached is updated depthmap_helper.xml

Cheers, Scott

Quote from Mische

Yes, preparing for krpano works only with well placed PanoCams:

• Delete the UV material
• Add a new PanoCam
• Apply the new Pano material to the model
• Move and rotate the Pano_HANDLE until the panorama fits to the model

Screencast

OMG, exactly what I needed - would never have figured that out on my own so thank you for providing the video! I've followed it and getting much better results. Have just purchased an additional version of PanoCamAdder+ ;)

<<<<EDIT - have moved my question about refreshing the model to its own post in Depthmap Support >>>

Thanks again Mische! Cheers, Scott
** can anyone explain why oy and oz axes seem to be transposed? In my model, oy changes height and oz changes front/back values

Hi Mische, Thank You for checking it and providing the video tutorial (and on a Saturday!) It's extremely helpful to see the techniques you use to build a room from nothing. Since I'm not very familiar with Blender, I was hoping to be able to use the pre-modeled rooms as I have a number of them already provided to me (in OBJ format) and I don't want to recreate all from scratch. Your tutorial gave me a couple clues which have proved extremely useful :
1) the model I provided had a 90 degree rotation which had not been "applied"

2) I had the room origin set to the center of the model, not on XY plane
I'm assuming one or both of these points were important as I've been able to export a model which *almost* fits. After hacking around with tour.xml values for "prealign" and "center" in the depthmap definition, it's really close.

I believe the actual problem is where I've placed the panocam - if it's not in the exact same place as the actual real world cam, then the exported model won't match the original pan file. Do you have any tricks for how to determine/place the panocam to match real world?
Thanks again! Scott

Quote from Mische

Hi Scott!

I will take a look. Can you please send the equirectangular panorama, too?
Easiest way to pack it into the blend-file:
Go to 'File/ External Date/ Pack All Into .blend'

Best regards!

Sorry for delay (no email alert setup) and Thank You so much for taking a look! I've repackaged .blend with external resources and I've included the full resolution source pano in a new zip here: https://we.tl/t-OD2xsnJo0i
Looking forward to your insight!
Cheers, Scott

Hi, I spent all day yesterday trying to export a simple model from Blender using PanoCamAdder+ The model is a single room/pano with doors on three walls and no hotspots. It looks fine in Blender but when I export for krPano, the doors appear as black rectangles that are too small and also seem to be raised above the floor. I've gone through all tutorials / videos and have ensured krpano settings are "autolevel=prealign" as per above post. I've hit the virtual wall!
Any chance you could look at my blender room (<1MB) and resulting tour to see what I'm missing? WeTransfer link: https://we.tl/t-m8R6OhhJor
Any advice appreciated! Thx, Scott

Quote from klaus.krpano

Quoted from "bitbyter"
Unfortunately I've identified a repeatable problem with the new {projectname}.js file that gets generated. Within any planar image which is taller than it is wide, the hotspots seem to be scaled incorrectly so that they are all "shrunken" towards the middle of the image. This does not happen for landscape oriented planars nor full equirectangulars.

Do you have an example?
Are these yellow areas polygonal hotspots?

But maybe this is the reason - in version 1.20 partial panos are supported now, in older versions such panos were falling back to flat panos - and the hotspot coordinates between these pano-types can be different. But I had to admit I don't know yet how Panotour handles this case.

Hi Klaus - apologies for huge delay after you took the time to respond ...Covid didn't get me, but it sure as hell beat up my business! This issue just came up again and I've updated to latest krPano but problem still remains. I created a screen capture video to demonstrate exact reproduction and conclude that it doesn't have anything to do with Panotour since the only file to change in this demo is the {projectname}.js file.

Here is a link to the demo video: https://drive.google.com/file/d/1iDOTrH…iew?usp=sharing
Thanks for your attention and support! Cheers, Scott

First of all, thank you Klaus for creating the update package for Panotour Pro -fantastic new support for Oculus Go!

Unfortunately I've identified a repeatable problem with the new {projectname}.js file that gets generated. Within any planar image which is taller than it is wide, the hotspots seem to be scaled incorrectly so that they are all "shrunken" towards the middle of the image. This does not happen for landscape oriented planars nor full equirectangulars.
The easiest way to see this behavior is to create a simple project with one landscape and one portrait planar image. Draw a polygonal hotspot to cover the entire image for each (make sure the fill is semi-transparent so you can see it when built). Build the project and run ... the landscape image will display with the hot area covering entire image as expected. The portrait version will show the hotspot at about 80% of the size of its background image. This is repeatable with point spots as well.

Here's the clincher - when I build this exact same project with a Panotour that does not have the 1.20 update applied, the results are as expected (with hot areas fully covering their images). Additionally, if I simply substitute the "example.js" file from the old build into the new build and reload, then the hot areas are also as expected (this just assures that there's not anything else in the updated Panotour build process that may be leading to incorrect results - different .XML files, etc).

I haven't attempted to repeat this using just krpano and assembling panos manually but I'd be happy to provide the source and resulting build files for this experiment if anyone is interested.

Cheers, Scott
************ EDIT - ADDITIONAL INFO ****************
Previously I had not used the krPano Tools to simply update a {project}.js file - I have just done so and confirmed that the problem is consistent with above description when updating a project using this tool. I've also done a couple screen caps to illustrate as attached.