Issues with your account? Bug us in the Discord!
JAVA-Java3D rendering design
bobo
(A monkey)
Hope y'all don't mind if I post some ramblings about Java 3D as I learn new items. I think Java is a tool that is overlooked by many, thinking that the performance is too slow (no longer true for most applications/platforms).
I'll post more items as I learn, perhaps giving someone else the incentive to investigate Java and Java 3D.
====== Rendering =======
I've been reading about the rendering methodology. Java 3D separates the virtual world model from the physical world model, so that changing the viewing device does not impact the rest of the applicaton. This means that you can design the virtual world once, then decide later how you want to view it (computer monitor, head mounted display (HMD), multiple displays (such as three projection TVs forming three sides of a cube), etc.). Additionally, changing the movement tracking device (mouse, keyboard, head tracker, or to-be-designed-later) does not affect the application developers design approach.
One interesting (IHMO) trick that this implies is that you can decide if a rendered scene is viewed through a physical world or virtual world window. If physical, then moving the window around on the desktop changes the scene in the virtual world that is visible, but the objects apear to remain in the same place "within the computer".
Additionally, if the window is attached to the virtual world, then resizing the window to be smaller makes all the drawn objects smaller. However, if the window is attached to the physical world, then all the objects are rendered the same size (i.e., use the same amount of pixels), but less of the virtual world is visible.
This would be a nice tie in to the thread that talked about story design and drama engines in the main forum. If the window on the screen is truly treated as physical world window onto a world "within the computer", the affect would be more convincing (again, IMO).
------------------
bobo
<*>
B5:ITF
I'll post more items as I learn, perhaps giving someone else the incentive to investigate Java and Java 3D.
====== Rendering =======
I've been reading about the rendering methodology. Java 3D separates the virtual world model from the physical world model, so that changing the viewing device does not impact the rest of the applicaton. This means that you can design the virtual world once, then decide later how you want to view it (computer monitor, head mounted display (HMD), multiple displays (such as three projection TVs forming three sides of a cube), etc.). Additionally, changing the movement tracking device (mouse, keyboard, head tracker, or to-be-designed-later) does not affect the application developers design approach.
One interesting (IHMO) trick that this implies is that you can decide if a rendered scene is viewed through a physical world or virtual world window. If physical, then moving the window around on the desktop changes the scene in the virtual world that is visible, but the objects apear to remain in the same place "within the computer".
Additionally, if the window is attached to the virtual world, then resizing the window to be smaller makes all the drawn objects smaller. However, if the window is attached to the physical world, then all the objects are rendered the same size (i.e., use the same amount of pixels), but less of the virtual world is visible.
This would be a nice tie in to the thread that talked about story design and drama engines in the main forum. If the window on the screen is truly treated as physical world window onto a world "within the computer", the affect would be more convincing (again, IMO).
------------------
bobo
<*>
B5:ITF
Comments
------------------
[b][url="http://www.minbari.co.uk/log12.2263/"]Required reading[/url][/b]
Never eat anything bigger than your own head.
The Balance provides. The Balance protects.
"Nonono...Is not [i]Great[/i] Machine. Is...[i]Not[/i]-so-Great Machine. It make good snow cone though." - Zathras