Hi,

that's totally impossible!

That limitation is not from krpano, that's basic math and 3d/2d space .

Best regards,
Klaus

Quoted from "virgil"

Not quick work around?

No, not workarounds, that's a fundamental limitation!

I don't know how to explain it understandable with words, but I have tried explaining the basics here with a simple illustration - look at the different colors:

Hello there,

I am trying to do something similar to this, although I do understand the mathematical limitations, so I only need to know when hotspots are outside of the FOV but still in the projection plane, hence "close" to being displayed.

Although I think there's another problem... I am doing what the original poster was:

spheretoscreen(get(hotspot[trackinghtsp_1].ath), get(hotspot[trackinghtsp_1].atv), hotspotPosX, hotspotPosY);

and the values for hotspotPosX and hotspotPosY always refer to the same spot on the FOV: the center of the video. I move the camera around, and the values accomodate to show that point, not the hostpots ath and atv...

I am tracing as well the hostpots values before using spheretoscreen and they do change without moving the camera, so they are correct...

I'm just starting to learn the ropes, so hopefully I didn't just get the syntax wrong!

Am I doing something wrong? Any ideas?

Ah, got it, it was a matter of sending variables without the "get" method... so this worked:

spheretoscreen(hotspot[trackinghtsp_1].ath, hotspot[trackinghtsp_1].atv, hotspotPosX, hotspotPosY);

THANKS!!! the get or not to get.. the problem is always there!!!