One the interface things that always seems to "get" me and requires a few more clicks or changes is the settings in this dialog box. Why does setting the Field of View (Zoom): Min: update the Viewing Parameters / Limits ? I mean I can understand why it might need to if the view was outside...

I'm looking to create a couple set of VRs for clients. r One will show a before and after, I'd like to allow a automatic and/or controlled and blended transition in a full 360 by 180, no cylindrical. The second set will have lots of embedded video thats part of the VR, i.e. as if a TV set was on ins...

If I extract a patch using the $C placeholder variable to include the position information I'm getting two patches output. One has the $C in the file name, the other is correct and has the position information in it. open a EQ file, add a patch, put $C in the file name and click on the extract butto...

Thanks Erik,

Thomas, any input on if this is a feature or .....

Regards,

Robert

Loading a 11,737 by 8592/16 image as Cylindrical, horizontal FOV is 360 (vertical is about 133). Leaving all settings pretty much as default, both QT and Flash output failing. QT produces a 4.5 k mov file, flash is 42.6 K. Cylinder height is set at 2233 in both. This same file works in Pano2QTVR 1.6...

thanks Thomas and Smooth,

Guess I should have search the forum on just "Patch" instead of Patch Tool to avoid a duplicate post, but seems it was worthwhile anyway as slowly but surely we're dragging those placeholders out one "$" at a time.

Regards,

Robert

It would be a wonderful enhancement if the patch tool would record the placement settings(ie. FOV, Pan, Tilt, Roll) for each patch in it's file name by default. The reason I'm asking is this: If you load a VR into Pano2VR, add a patch and forget to save this specific VR and patch as part of a projec...

I think this will do what you need, see the third tutorial on point hotspots, note the relation to ID in the template to Skin-ID in the pano point hotspot and how that is used.

Good Luck,

Robert

Hi Smooth, Thanks for testing, have to figure out why my IE7 has the problem in "regular" screen and FF 3 also seems to fail on autorotation when taken into full screen. And the text above the menu bar is a active "button" that should also take you to full screen. Regards, Robert

thanks for the compliment Dave.

So, are you saying in IE7 the text hotspots are dimmed when you view the VR's NOT in full screen mode?

Regards,

Robert

After a bit of monkey business :) I was able to get the point hotspots working as noted and it's great, really a wonderful feature that has all kinds of potential beyond just simple hotspots. My first simple test is from the link below. http://www.robertharshman.com/JW/333/AVRFS/lr1.html One of the ...

You should look at the point hotspots tutorials, while I'm sure there are probably better ways to accomplish what you are looking for, you could do this via point hotspot templates. Think of the pink 'X" as your highlight image and control the alpha to the degree you need.

regards,

Robert

Hey Thomas, No problem, just a bit confusing but I've worked through that and everything is working now. I have a 5 VR test set with many point hotspots as text that fades in and out. The more I work with this the more I realize just how powerful this simple template can be. Very much looking forwar...

Finally, got a simple test to work! Still not sure why the first test did not work, perhaps: Used a 700megabyte multi layers 16 bit tif file as input EQ, changed to a 250megabyte 16 bit tif single layer. Did NOT make any changes (as in tutorial example) to make a custom controller with a point hotsp...

Hi Wim, Good suggestion, tried it, but on inspecting the demo files it's failed to start. No html included and most surprising only one of the project files has any links or files noted in the defined point hotspots and these are not to other VRs but fully qualified links to wiki pages. Only one of ...