HSF
Inconsistent Cameras
Description: There is a critical inconsistency in the zooming mechanism between the active Perspective Camera and the Orthographic Camera. This leads to the Orthographic mode being essentially unusable for standard tasks, such as visualizing the full detector.
🐞 Bug Behavior
When switching to the Orthographic Camera and attempting to zoom out (e.g., to frame the entire detector), the following occurs:
- The Perspective Camera's position is updated as well, resulting in it moving too far back.
- This causes scene elements to disappear, including critical components like tracks.
- Because both cameras share the same position, and the Perspective camera interprets this position differently, zooming out breaks the scene rendering in both modes.
Example
In the attached images, you can clearly see:
- After zooming out in Orthographic mode, the back/mid scene layers vanishes.
- Even before full disappearance, tracks are missing due to the extreme distance of the Perspective camera.
🔄 Expected Behavior
- Orthographic and Perspective cameras should manage zoom/position independently, or
- A mechanism should be added to decouple their zoom levels and field of view/focus behavior.
Hi! I'm really interested in contributing to this repository and becoming a part of the Phoenix project. I'm new to the codebase, but I'm eager to learn and get involved. I'd like to work on this issue—could you please assign it to me if it's still available? It would also be very helpful if you could elaborate a bit more on the problem and guide me on where to begin in the codebase. Thanks in advance for your support!
Hi! Thanks a lot for your interest in contributing to the Phoenix project , it’s always great to see new contributors getting involved!
Just a heads-up: I’ve already submitted a pull request that includes a fix for this issue along with several other related bugs (https://github.com/HSF/phoenix/pull/720) . However, this particular bug is relatively simple and could still be a great exercise for you to get familiar with the codebase.
If you're still up for it, I’d be happy to walk you through how the problem was tackled and point you to the relevant parts of the code. I’ve been working on the project actively for the past couple of months, so I can share some insights that might help you ramp up faster.
Let me know how you'd like to proceed !
Thanks so much for the quick response and for the warm welcome!
I'd definitely love to go through the issue as an exercise and get familiar with the codebase. It would be great if you could walk me through how you approached the fix and point me to the relevant parts of the code. That kind of guidance would really help me ramp up faster and start contributing meaningfully.
Looking forward to learning from you!
