Back to post

Revisions 4


1 years ago
How to obtain the aspect ratio / frustum of a render control?
How to obtain the aspect ratio / frustum of a render control?
Hi, your solution is correct. I wrote some backround information about this topic: [https://github.com/aardvark-platform/aardvark.docs/wiki/client-values](https://github.com/aardvark-platform/aardvark.docs/wiki/client-values) TL;DR: - These values are hidden because they need to be system-intrinsic for fast performance - You can use those values freely **within the scene graph** using `renderControlWithClientValues` (or the according CameraController) - In case you have **only one client with only one renderControl**, you can evacuate view and proj trafo into your model (and subsequently into javascript) using `renderControl'`, which exposes the calculation of those trafos to the outside. Just do the same calculations in your model (in some "hacky" way) .This changes the performance of the system. - **Recommendation:** Can you solve the problem differently? You should rarely ever need the trafos outside of 3d rendering, and if you do, it will probably have massive performance implications. Please ask here if there are any more questions.
Hi, your solution is correct. I wrote a bit about this topic: [https://github.com/aardvark-platform/aardvark.docs/wiki/client-values](https://github.com/aardvark-platform/aardvark.docs/wiki/client-values) TL;DR: - These values are hidden because they need to be system-intrinsic for fast performance - You can use those values freely **within the scene graph** using `renderControlWithClientValues` (or the according CameraController) - In case you have **only one client with only one renderControl**, you can evacuate view and proj trafo into your model (and subsequently into javascript) using `renderControl'`, which exposes the calculation of those trafos to the outside. Just do the same calculations in your model (in some "hacky" way) .This changes the performance of the system. - **Recommendation:** Can you solve the problem differently? You should rarely ever need the trafos outside of 3d rendering, and if you do, it will probably have massive performance implications. Please ask here if there are any more questions.

1 years ago
How to obtain the aspect ratio / frustum of a render control?
How to obtain the aspect ratio / frustum of a render control?
Hi, your solution is correct. I wrote a bit about this topic: [https://github.com/aardvark-platform/aardvark.docs/wiki/client-values](https://github.com/aardvark-platform/aardvark.docs/wiki/client-values) TL;DR: - These values are hidden because they need to be system-intrinsic for fast performance - You can use those values freely **within the scene graph** using `renderControlWithClientValues` (or the according CameraController) - In case you have **only one client with only one renderControl**, you can evacuate view and proj trafo into your model (and subsequently into javascript) using `renderControl'`, which exposes the calculation of those trafos to the outside. Just do the same calculations in your model (in some "hacky" way) .This changes the performance of the system. - **Recommendation:** Can you solve the problem differently? You should rarely ever need the trafos outside of 3d rendering, and if you do, it will probably have massive performance implications. Please ask here if there are any more questions.
Hi, I wrote a bit about this topic: [https://github.com/aardvark-platform/aardvark.docs/wiki/client-values](https://github.com/aardvark-platform/aardvark.docs/wiki/client-values) TL;DR: - These values are hidden because they need to be system-intrinsic for fast performance - You can use those values freely **within the scene graph** using `renderControlWithClientValues` (or the according CameraController) - In case you have **only one client with only one renderControl**, you can evacuate view and proj trafo into your model (and subsequently into javascript) using `renderControl'`, which exposes the calculation of those trafos to the outside. Just do the same calculations in your model (in some "hacky" way) .This changes the performance of the system. - **Recommendation:** Can you solve the problem differently? You should rarely ever need the trafos outside of 3d rendering, and if you do, it will probably have massive performance implications. Please ask here if there are any more questions.

1 years ago
How to obtain the aspect ratio / frustum of a render control?
How to obtain the aspect ratio / frustum of a render control?
Hi, I wrote a bit about this topic: [https://github.com/aardvark-platform/aardvark.docs/wiki/client-values](https://github.com/aardvark-platform/aardvark.docs/wiki/client-values) TL;DR: - These values are hidden because they need to be system-intrinsic for fast performance - You can use those values freely **within the scene graph** using `renderControlWithClientValues` (or the according CameraController) - In case you have **only one client with only one renderControl**, you can evacuate view and proj trafo into your model (and subsequently into javascript) using `renderControl'`, which exposes the calculation of those trafos to the outside. Just do the same calculations in your model (in some "hacky" way) .This changes the performance of the system. - **Recommendation:** Can you solve the problem differently? You should rarely ever need the trafos outside of 3d rendering, and if you do, it will probably have massive performance implications. Please ask here if there are any more questions.
Hi, I wrote a bit about this topic: https://github.com/aardvark-platform/aardvark.docs/wiki/client-values TL;DR: - These values are hidden because they need to be system-intrinsic for fast performance - You can use those values freely **within the scene graph** using `renderControlWithClientValues` (or the according CameraController) - In case you have **only one client with only one renderControl**, you can evacuate view and proj trafo into your model (and subsequently into javascript) using `renderControl'`, which exposes the calculation of those trafos to the outside. Just do the same calculations in your model (in some "hacky" way) .This changes the performance of the system. - **Recommendation:** Can you solve the problem differently? You should rarely ever need the trafos outside of 3d rendering, and if you do, it will probably have massive performance implications. Please ask here if there are any more questions.

1 years ago
Original
How to obtain the aspect ratio / frustum of a render control?
How to obtain the aspect ratio / frustum of a render control?
Hi, I wrote a bit about this topic: https://github.com/aardvark-platform/aardvark.docs/wiki/client-values TL;DR: - These values are hidden because they need to be system-intrinsic for fast performance - You can use those values freely **within the scene graph** using `renderControlWithClientValues` (or the according CameraController) - In case you have **only one client with only one renderControl**, you can evacuate view and proj trafo into your model (and subsequently into javascript) using `renderControl'`, which exposes the calculation of those trafos to the outside. Just do the same calculations in your model (in some "hacky" way) .This changes the performance of the system. - **Recommendation:** Can you solve the problem differently? You should rarely ever need the trafos outside of 3d rendering, and if you do, it will probably have massive performance implications. Please ask here if there are any more questions.
Hi, I wrote a bit about this topic: https://github.com/aardvark-platform/aardvark.docs/wiki/client-values TL;DR: - These values are hidden because they need to be system-intrinsic for fast performance - You can use those values freely **within the scene graph** using `renderControlWithClientValues` (or the according CameraController) - In case you have **only one client with only one renderControl**, you can evacuate view and proj trafo into your model (and subsequently into javascript) using `renderControl'`, which exposes the calculation of those trafos to the outside. Just do the same calculations in your model (in some "hacky" way) .This changes the performance of the system. - **Recommendation:** Can you solve the problem differently? You should rarely ever need the trafos outside of 3d rendering, and if you do, it will probably have massive performance implications. Please ask here if there are any more questions.