You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -290,12 +290,13 @@ Translate [screen boundaries](#screen-coordinates) (corners) to world coordinate
290
290
*```bounds``` (vector4) Screen bounds (x = left, y = top, z = right, w = bottom)
291
291
292
292
293
-
### camera.world_to_screen(camera_id, world)
294
-
Translate world coordinates to [screen coordinates](#screen-coordinates), based on the view and projection of the camera. This is useful when manually culling game objects and you need to determine if a world coordinate will be visible or not.
Translate world coordinates to [screen coordinates](#screen-coordinates), based on the view and projection of the camera, optionally taking into account an adjust mode. This is useful when manually culling game objects and you need to determine if a world coordinate will be visible or not. It can also be used to position gui nodes on top of game objects.
295
295
296
296
**PARAMETER**
297
297
*```camera_id``` (hash|url)
298
298
*```world``` (vector3) World coordinates to convert
299
+
*```adjust_mode``` (number) One of gui.ADJUST_FIT, gui.ADJUST_ZOOM and gui.ADJUST_STRETCH, or nil to not take into account the adjust mode.
0 commit comments