-
-
- +
trackis one motion of a moving object. You can add several tracks. More details below. eventis one motion of a moving object. You can add several events. More details below.starttimeis the time when this particular cinematic event starts on the timeline. Specify the start time in seconds since the beginning of the cinematic.
@@ -85,64 +85,56 @@ stateManager.attach(cinematic);
- +
- -
- Create a MotionTrack based on the MotionPath.+
- Create a MotionEvent based on the MotionPath.
-
- Configure your MotionTrack (see below).+
- Configure your MotionEvent (see below).
-
- Add the MotionTrack to a Cinematic.+
- Add the MotionEvent to a Cinematic.
- +
thingNodeis the Spatial to be moved. audioPathis the path to an audio file as String, e.g. "Sounds/mySound.wav".
-- +
endPositionis the target location as Vector3f. isStreamtoggles between streaming and buffering. Set to true to stream long audio file, set to false to play short buffered sounds.
-- +
durationis the time that it should take from start to end point. durationis the time that it should take to play.loopModecan be LoopMode.Loop, LoopMode.DontLoop, LoopMode.Cycle.- -
thingNodeis the Spatial to be rotated.
- - -
endRotationis the target rotation in Quaternion format.
- - -
durationis the time that it should take from start to target rotation.
- - -
loopModecan be LoopMode.Loop, LoopMode.DontLoop, LoopMode.Cycle.
- - -
thingNodeis the Spatial to be resized.
- - +
endScaleis the target Scale in Vector3f format. screenis the name of the Nifty GUI screen to load, as String.
-- +
durationis the time that it should take from start to target scale. durationis the time that it should take to play.loopModecan be LoopMode.Loop, LoopMode.DontLoop, LoopMode.Cycle.- +
audioPathis the path to an audio file as String, e.g. "Sounds/mySound.wav". thingNodeis the Spatial whose animation you want to play.
-- +
isStreamtoggles between streaming and buffering. Set to true to stream long audio file, set to false to play short buffered sounds. animationNamethe name of the animation stored in the animated model that you want to trigger, as a String.durationis the time that it should take to play.
@@ -316,65 +281,40 @@ Details of the constructor:
- -
screenis the name of the Nifty GUI screen to load, as String.
- - -
durationis the time that it should take to play.
- - -
loopModecan be LoopMode.Loop, LoopMode.DontLoop, LoopMode.Cycle.
- - -
thingNodeis the Spatial whose animation you want to play.
- - -
animationNamethe name of the animation stored in the animated model that you want to trigger, as a String.
- - -
durationis the time that it should take to play.
- - -
loopModecan be LoopMode.Loop, LoopMode.DontLoop, LoopMode.Cycle.
- - Full code sample:@@ -13,43 +17,68 @@ In this tutorial, we (re)create a very simple rectangular mesh, and we have a lo
- The indices 0,1,2,3 stand for the four vertices that you specified for the quad in+
vertices[]. - The 2,0,1 triangle starts at top left, continues bottom left, and ends at bottom right.
- The 1,3,2 triangle start at bottom right, continues top right, and ends at top left.@@ -94,18 +139,28 @@ Next we turn the unrelated coordinates into triangles ??? We define the order in | \ | 0--1\1 +
+ +If the shape is more complex, it has more triangles, and therefor also more vertices/indices. Just continue expanding the list by adding groups of three indices for each triangle. (For example a three-triangle "house" shape has 5 vertices/indices and you'd specify three groups:
+ +int [] indexes = { 2,0,1, 1,3,2, 2,3,4 };.) ++
If you get the order wrong (clockwise) for some of the triangles, then these triangles face backwards. If the Spatial's material uses the default+ +FaceCullMode.Back(see "face culling"), the broken triangles appear as holes in the rendered mesh. You need to identify and fix them in your code. + - Using
com.jme3.util.BufferUtils, we create three buffers for the three types of information we have:-
-
- vertex positions,+
- vertex coordinates,
- texture coordinates,
@@ -113,11 +168,11 @@ The Mesh data is stored in a buffer.
- - We assign the data to the appropriate type of buffer inside the mesh object. The three buffer types are taken from an enum in+
com.jme3.scene.VertexBuffer.Type. - We assign the data to the appropriate type of buffer inside the
Meshobject. The three buffer types (Position,TextCoord,Index) are taken from an enum incom.jme3.scene.VertexBuffer.Type.
- - The third parameter describes the number of components of the values. Vertex postions are 3 float values, texture coordinates are 2 float values, and the indices are 3 ints representing 3 vertices in a triangle.+
- The integer parameter describes the number of components of the values. Vertex postions are 3 float values, texture coordinates are 2 float values, and the indices are 3 ints representing 3 vertices in a triangle.
-
- In order for jMonkey to correctly show the mesh in the scene, it needs to know the bounds of our new mesh. This can easily be achieved by calling the updateBound() method on it.+
- To render the mesh in the scene, we need to pre-calculate the bounding volume of our new mesh: Call the
updateBound()method on it. - Call+
updateBounds()on the mesh object, and then
+ - call+
updateModelBound()on the Geometry object containing the mesh.
+ - If you have a very simple scene, you can just deactivate backface culling for this one mesh's material.+
-mat.getAdditionalRenderState().setFaceCullMode(FaceCullMode.Off); - If you have a very simple scene, you can simply deactivate backface culling for this one mesh's material.
mat.getAdditionalRenderState().setFaceCullMode(FaceCullMode.Off);
+
- - The recommended solution is to specify each triangle twice, the second time with the opposite order of vertices. The second, reversed triangle is a second frontface that replaces the culled backface.+
-int[] indexes = { 2,0,1, 1,3,2, 2,3,1, 1,0,2 }; - Another solution for truly double-sided meshes is to specify each triangle twice, the second time with the opposite order of vertices. The second (reversed) triangle is a second frontface that covers up the culled backface.
int[] indexes = { 2,0,1, 1,3,2, 2,3,1, 1,0,2 };+ - ??? dust, smoke
Tracks (CinematicEvents)
+ +Events(CinematicEvents)
-Just like a movie script consists of lines with instructions to the actors, each Cinematic consists of a series of tracks. +Just like a movie script consists of lines with instructions to the actors, each Cinematic consists of a series of events.
-Here is the list of available CinematicEvents that you use as tracks. Each track remote-controls scene objects in a different way: +Here is the list of available CinematicEvents that you use as events. Each track remote-controls scene objects in a different way:
| Tracks (CinematicEvents) | Description | +Events(CinematicEvents) | Description |
|---|---|---|---|
| MotionTrack | Use a MotionTrack to move a Spatial non-linearly over time. A MotionTrack is based on a list of waypoints in a MotionPath. The curve goes through each waypoint, and you can adjust the tension of the curve to modify the roundedness of the path. This is the motion interpolation you are going to use in most cases. | +MotionEvent | Use a MotionEvent to move a Spatial non-linearly over time. A MotionEvent is based on a list of waypoints in a MotionPath. The curve goes through each waypoint, and you can adjust the tension of the curve to modify the roundedness of the path. This is the motion interpolation you are going to use in most cases. |
| PositionTrack | Use a PositionTrack to move a Spatial linearly over time. This linear interpolation results in straight motion segments between the way points. Use this to make the remote-controlled objects zig-zag from one way point to the other in a straight line. | +SoundEvent | Use a SoundEvent to play a sound at a given time for the given duration. |
| RotationTrack | Use a RotationTrack to change the rotation of a Spatial over time. It spins the Spatial to the given angle in the given amount of time by linearly interpolating the rotation. | +GuiEvent | Displays a Nifty GUI at a given time for the given duration. Use it to display subtitles or HUD elements. Bind the Nifty GUI XML to the cinematic using cinematic.bindUi("path/to/nifty/file.xml"); |
| ScaleTrack | Use a ScaleTrack to change the size of a Spatial over time. It resizes the Spatial in the given amount of time by linearly interpolating the scale. | -||
| SoundTrack | Use a SoundTrack to play a sound at a given time for the given duration. | -||
| GuiTrack | Displays a Nifty GUI at a given time for the given duration. Use it to display subtitles or HUD elements. Bind the Nifty GUI XML to the cinematic using cinematic.bindUi("path/to/nifty/file.xml"); |
- ||
| AnimationTrack | Use this to start playing a model animation at a given time (a character walking animation for example) | +AnimationEvent | Use this to start playing a model animation at a given time (a character walking animation for example) |
-The jMonkey team can add more types of tracks, just ask in the forum. +Of course one can make is own event implementation, by extending the AbstractCinematicEvent. +
MotionTrack
+ +MotionEvent
-A MotionTrack moves a Spatial along a complex path. +A MotionEvent moves a Spatial along a complex path.
-MotionTrack track = new MotionTrack(thingNode, path);+
MotionEvent events= new MotionEvent (thingNode, path);
Details of the constructor: @@ -156,158 +148,131 @@ Details of the constructor:
-To create a MotionTrack, do the following: +To create a MotionEvent, do the following:
-
-
| MotionTrack configuration method | Usage | +MotionEvent configuration method | Usage |
|---|---|---|---|
| track.setLoopMode(LoopMode.Loop) | Sets whether the animation along this path should loop (LoopMode.Loop) or play only once (LoopMode.DontLoop). | +event.setLoopMode(LoopMode.Loop) | Sets whether the animation along this path should loop (LoopMode.Loop) or play only once (LoopMode.DontLoop). |
| track.setDirectionType(MotionTrack.Direction.None) | Sets the direction behavior type of the controled node. Direction.None deactivates this feature. You can choose from the following options: LookAt, Path, PathAndRotation, Rotation. | +event.setDirectionType(MotionEvent.Direction.None) | Sets the direction behavior type of the controlled node. Direction.None deactivates this feature. You can choose from the following options: LookAt, Path, PathAndRotation, Rotation. |
| track.setDirectionType(MotionTrack.Direction.LookAt) | The spatial turns (rotates) to keep facing a certain point while moving. Specify the point with the setLookAt() method. |
+ event.setDirectionType(MotionEvent.Direction.LookAt) | The spatial turns (rotates) to keep facing a certain point while moving. Specify the point with the setLookAt() method. |
| track.setDirectionType(MotionTrack.Direction.Path) | The spatial always faces in the direction of the path while moving. | +event.setDirectionType(MotionEvent.Direction.Path) | The spatial always faces in the direction of the path while moving. |
| track.setDirectionType(MotionTrack.Direction.PathAndRotation) | The spatial faces the direction of the path, plus an added rotation. Use together with the setRotation() method. |
+ event.setDirectionType(MotionEvent.Direction.PathAndRotation) | The spatial faces the direction of the path, plus an added rotation. Use together with the setRotation() method. |
| track.setDirectionType(MotionTrack.Direction.Rotation) | The spatial spins (rotates) while moving. You describe the spin by a custom quaternion. Use together with the setRotation() method. |
+ event.setDirectionType(MotionEvent.Direction.Rotation) | The spatial spins (rotates) while moving. You describe the spin by a custom quaternion. Use together with the setRotation() method. |
| track.setLookAt(teapot.getWorldTranslation(), Vector3f.UNIT_Y) | The spatial always faces towards this location. Use together with MotionTrack.Direction.LookAt. |
+ event.setLookAt(teapot.getWorldTranslation(), Vector3f.UNIT_Y) | The spatial always faces towards this location. Use together with MotionEvent.Direction.LookAt. |
| track.setRotation(quaternion) | Sets the rotation. Use together with MotionTrack.Direction.Rotation or MotionTrack.Direction.PathAndRotation. |
+ event.setRotation(quaternion) | Sets the rotation. Use together with MotionEvent.Direction.Rotation or MotionEvent.Direction.PathAndRotation. |
-Tip: Most likely you remote-control more than one object in your scene. Give the tracks and paths useful names such as dragon_track, dragon_path, hero_track, hero_path, etc.
+Tip: Most likely you remote-control more than one object in your scene. Give the events and paths useful names such as dragonEvent, dragonPath, heroEvent, heroPath, etc.
PositionTrack
+ +SoundEvent
-A PositionTrack moves a Spatial in a straight line from its current position to the end position. +A SoundEventplays a sound as part of the cinematic.
-PositionTrack track = new PositionTrack( - thingNode, endPosition, duration, loopMode);+
SoundEvent( audioPath, isStream, duration, loopMode )
+ Details of the constructor:
-
-
- -The start location is always the current location of the Spatial. -
-RotationTrack
+ +GuiEvent
-A RotationTrack remote-controls the rotation of a spatial. +A GuiEventshows or hide a NiftyGUI as part of a cinematic.
-RotationTrack thingRotationControl = new RotationTrack( - thingNode, endRotation, duration, loopMode);+
GuiEvent( screen, duration, loopMode )
-Details of the constructor: -
--
-
ScaleTrack
-+You must use this together with bindUI() to specify the Nifty GUI XML file that you want to load: -A ScaleTrack remote-controls whether a spatial grows or shrinks.
-ScaleTrack thingScaleControl = new ScaleTrack( - thingNode, endScale, duration, loopMode);+
cinematic.bindUi("Interface/subtitle.xml");
Details of the constructor:
-
-
SoundTrack
+ +AnimationEvent
-A SoundTrack plays a sound as part of the cinematic. +An AnimationEvent triggers an animation as part of a cinematic.
-SoundTrack( audioPath, isStream, duration, loopMode )+
AnimationEvent( thingNode, animationName, duration, loopMode )
Details of the constructor:
-
-
GuiTrack
+ +Camera Management
-A GuiTrack shows or hide a NiftyGUI as part of a cinematic. - +There is a built in system for camera switching in Cinematics. It based on CameraNode, and the cinematic just enable the given CameraNode control at a given time.
-GuiTrack( screen, duration, loopMode )
+First you have to bind a camera to the cinematic with a unique name. You'll be provided with a CameraNode -You must use this together with bindUI() to specify the Nifty GUI XML file that you want to load: - -
-cinematic.bindUi("Interface/subtitle.xml");
-
--Details of the constructor:
--
-
AnimationTrack
- CameraNode camNode = cinematic.bindCamera("topView", cam);
-An AnimationTrack triggers an animation as part of a cinematic. +then you can do whatever you want with this camera node : place it so that you have a the camera angle you'd like, attach it to a motion event to have some camera scrolling, attach control of your own that give it whatever behavior you'd like. +In the above example, I want it to be a top view of the scene looking at the world origin.
-AnimationTrack( thingNode, animationName, duration, loopMode )+
//set its position + camNode.setLocalTranslation(new Vector3f(0, 50, 0)); + // set it to look at the world origin + camNode.lookAt(Vector3F.ZERO, Vector3f.UNIT_Y);
+Then i just have to schedule its activation in the cinematic. I want it to get activated 3 seconds after the start of the cinematic so I just have to do -Details of the constructor:
--
-
cinematic.activateCamera(3,???topView???);
Customizations
Code Sample
Bounding Volumes
Usage
Mesh and Scene Graph Collision
Collidables are meshes and scene graph objects
Intersection
Learn the details of how to implement Mouse Picking here.
-+
TODO: @@ -237,5 +237,5 @@ TODO:
-The possibilities are endless. 
+The possibilities are endless.
Use the Mesh class to create custom shapes that go beyond Quad, Box, Cylinder, and Sphere, even procedural shapes are possible. Thank you to KayTrance for providing the sample code!
-In this tutorial, we (re)create a very simple rectangular mesh, and we have a look at different ways of coloring it. A flat rectangle may not look useful because it's exactly the same as a
com.jme3.scene.shape.Quad. We choose this simple example in order to show you how to build any shape out of triangles ??? without the distractions of more complex shapes.
+
+Note: In this tutorial, we (re)create a very simple rectangular mesh (a quad), and we have a look at different ways of coloring it. Coding a custom quad may not be very useful because it's exactly the same as the built-in com.jme3.scene.shape.Quad. We chose a simple quad to teach you how to build any shape out of triangles, without the distractions of more complex shapes.
+
Polygon Meshes
-Polygon meshes are made up of triangles. The corners of the triangles are vertices. So, when ever you create a new shape, you break it down into triangles. -Let's look at a cube. A cube is made up of 6 rectangles. Each rectangle can be broken down into two triangles. This means you need 12 triangles to create a cube mesh. You also need to know the 8 corner coordinates (vertices). The trick is that you have to specify the vertices in a certain order: Each triangle separately, counter-clockwise. -Sounds worse than it is ??? here is an example: +Polygon meshes are made up of triangles. The corners of the triangles are called vertices. When ever you create any new shape, you break it down into triangles. +
+ ++Example: Let's look at a cube. A cube is made up of 6 rectangles. Each rectangle can be broken down into two triangles. This means you need 12 triangles to describe a cube mesh. Therefor you must provide the coordinates of the triangles' 8 corners (called vertices). +
+ ++The important thing is that you have to specify the vertices of each triangle in the right order: Each triangle separately, counter-clockwise. +
+ ++Sounds harder than it is ??? let's create a simple custom mesh, a quad.
Creating a Quad Mesh
-Okay, we want to create a Quad. A quad has four vertices, and is made up of two triangles.
-The base class for creating meshes is com.jme3.scene.Mesh.
+In this tutorial we want to create a 3x3 Quad. The quad has four vertices, and is made up of two triangles. In our example, we decide that the bottom left corner is at 0/0/0 and the top right is at 3/3/0.
Mesh mesh = new Mesh();+
0,3,0--3,3,0 +| \ | +| \ | +| \ | +| \ | +| \| +0,0,0--3,0,0+ +
The Mesh Object
+
-If you create your own Mesh-based class, replace mesh by this in the following examples:
+The base class for creating meshes is com.jme3.scene.Mesh.
public class MyMesh extends Mesh { }
+Mesh mesh = new Mesh();+ +
+Tip: If you create your own Mesh-based class (public class MyMesh extends Mesh { }), replace the variable mesh by this in the following examples.
+
Vertices
+ +Vertex Coordinates
-To define your own shape, determine its vertex positions in space. Store them in an array using com.jme3.math.Vector3f. For a Quad, we need four vertices: Bottom left, bottom right, top left, top right. We name the array vertices[].
+
+To define your own shape, determine the shape's vertex coordinates in 3D space. Store the list of corner positions in an com.jme3.math.Vector3f array. For a Quad, we need four vertices: Bottom left, bottom right, top left, top right. We name the array vertices[].
Vector3f [] vertices = new Vector3f[4]; @@ -59,12 +88,12 @@ vertices[2] = new Vector3f(0,3,0); vertices[3] = new Vector3f(3,3,0);
Texture Coordinates
-Next, define the Quad's 2D texture coordinates for each vertex, in the same order: Bottom left, bottom right, top left, top right. We name this array texCoord[]
+Next, we define the Quad's 2D texture coordinates for each vertex, in the same order as the vertices: Bottom left, bottom right, top left, top right. We name this Vector2f array texCoord[]
Vector2f[] texCoord = new Vector2f[4]; @@ -73,17 +102,33 @@ texCoord[1] = new Vector2f(1,0); texCoord[2] = new Vector2f(0,1); texCoord[3] = new Vector2f(1,1);+
+ +This syntax means, when you apply a texture to this mesh, the texture will fill the quad from corner to corner at 100% percent size. Especially when you stitch together a larger mesh, you use this to tell the renderer whether, and how exactly, you want to cover the whole mesh. E.g. if you use .5f or 2f as texture coordinates instead of 1f, textures will be stretched or shrunk accordingly. +
+Connecting the Dots
-Next we turn the unrelated coordinates into triangles ??? We define the order in which the mesh is constructed. Think of these indexes as coming in groups of three. Each group of indexes describes one triangle. Note that you must specify the vertices counter-clockwise! +Next we turn these unrelated coordinates into triangles: We define the order in which each triangle is constructed. Think of these indexes as coming in groups of three. Each group of indexes describes one triangle. If the corners are identical, you can (and should!) reuse an index for several triangles. +
+ ++Remember that you must specify the vertices counter-clockwise.
int [] indexes = { 2,0,1, 1,3,2 };
+
++ +This syntax means: +
-
+
Setting the Mesh Buffer
-The Mesh data is stored in a buffer. +You store the Mesh data in a buffer.
mesh.setBuffer(Type.Position, 3, BufferUtils.createFloatBuffer(vertices)); @@ -128,20 +183,20 @@ mesh.updateBound();
Our Mesh is ready! Now we want to see it. -
Using the Mesh in a Scene
-We create a com.jme3.scene.Geometry, apply a simple color material to it, and attach it to the rootNode to make it appear in the scene.
+We create a com.jme3.scene.Geometry from our mesh, apply a simple color material to it, and attach it to the rootNode to make it appear in the scene.
Geometry geo = new Geometry("OurMesh", mesh);
-Material mat = new Material(assetManager, "Common/MatDefs/Misc/Unshaded.j3md");
+Geometry geo = new Geometry("OurMesh", mesh); // using our custom mesh object
+Material mat = new Material(assetManager,
+ "Common/MatDefs/Misc/Unshaded.j3md");
mat.setColor("Color", ColorRGBA.Blue);
geo.setMaterial(mat);
rootNode.attachChild(geo);
@@ -149,43 +204,50 @@ rootNode.attachChild(geo);
Ta-daa! -
Dynamic Meshes
-If modifying a mesh dynamically in a way which would change the model's bounds then you need to call updateModelBound() on the Geometry object containing the mesh after calling updateBounds() on the mesh object. There is a warning on updateModelBounds about not usually needing to use it but that can be ignored in this special case. + +If you are modifying a mesh dynamically in a way which changes the model's bounds, you need to update it: +
+-
+
+The updateModelBounds() method warns you about not usually needing to use it, but that can be ignored in this special case.
Optional Mesh Features
There are more vertex buffers in a Mesh than the three shown above. For an overview, see also mesh. -
Example: Vertex Colors
-Vertex coloring is a simple way of coloring meshes. Instead of just assigning one solid color, each vertex (corner) has a color assigned. The faces between the vertices are then colored with a gradient. You can use the same mesh mesh object that you defined above.
-
+Vertex coloring is a simple way of coloring meshes. Instead of just assigning one solid color, each vertex (corner) has a color assigned. The faces between the vertices are then colored with a gradient. For this demo, you can use the same mesh mesh object that you defined above.
Geometry geo = new Geometry ("ColoredMesh", mesh);
+Geometry geo = new Geometry ("ColoredMesh", mesh); // using the custom mesh
Material matVC = new Material(assetManager, "Common/MatDefs/Misc/Unshaded.j3md");
matVC.setBoolean("VertexColor", true);
-
You create a float array color buffer:
-
@@ -209,10 +271,11 @@ You create a float array color buffer:
-Loop over the colorArray buffer to quickly set some RGBA value for each vertex. As usual, RGBA color values range from 0.0f to 1.0f. Note that the color values in this example are arbitrarily chosen. It's just a quick loop to give every vertex a different RGBA value (a purplish gray, purple, a greenish gray, green, see screenshot), without writing too much code. For your own mesh, you'd assign meaningful values for the color buffer depending on which color you want your mesh to have. +Loop over the colorArray buffer to quickly set some RGBA value for each vertex. As usual, RGBA color values range from 0.0f to 1.0f. Note that the color values in this example are arbitrarily chosen. It's just a quick loop to give every vertex a different RGBA value (a purplish gray, purple, a greenish gray, green, see screenshot), without writing too much code. For your own mesh, you'd assign meaningful values for the color buffer depending on which color you want your mesh to have.
-for(int i = 0; i < 4; i++){
+// note: the red and green values are arbitray in this example
+for(int i = 0; i < 4; i++){
// Red value (is increased by .2 on each next vertex here)
colorArray[colorIndex++]= 0.1f+(.2f*i);
// Green value (is reduced by .2 on each next vertex)
@@ -224,7 +287,6 @@ Loop over the colorArray buffer to quickly set some RGBA value for each vertex.
}
-
Next, set the color buffer. An RGBA color value contains four float components, thus the parameter 4.
@@ -233,36 +295,38 @@ geo.setMaterial(matVC);
-Now you see a gradient color extending from each vertex. - +When you run this code, you see a gradient color extending from each vertex.
Example: Shaded Mesh with Normals
+ +Example: Using Meshes With Lighting.j3md
-The examples used the mesh together with the Unshaded.j3md material. If you want to use the Mesh with a Phong illuminated material (such as Lighting.j3md), the mesh needs to include information about its normals. (The Normals encode in which direction a mesh polygon is facing, which is important for calculating light and shadow.)
+The previous examples used the mesh together with the Unshaded.j3md material. If you want to use the mesh with a Phong illuminated material (such as Lighting.j3md), the mesh must include information about its Normals. (Normal Vectors encode in which direction a mesh polygon is facing, which is important for calculating light and shadow!)
float[] normals = new float[12];
normals = new float[]{0,0,1, 0,0,1, 0,0,1, 0,0,1};
mesh.setBuffer(Type.Normal, 3, BufferUtils.createFloatBuffer(normals));
+You need to specify as many normals as the polygon has vertices. For a flat quad, the four normals point in the same direction. In this case, the direction is the Z unit vector (0,0,1), this means our quad is facing the camera. +
-You need as many normals as the polygon has vertices. For a flat quad, they point all in the same direction. In this case, the direction is the Z unit vector (Vector3f.UNIT_Z), this means the quad is facing the camera. ++If the mesh is more complex or rounded, calculate cross products of neighbouring vertices to identify normal vectors!
Example: Point Mode
-Alternatively, you can show the vertices as colored points instead of coloring the faces. +Additionally to coloring the faces as just described, you can hide the faces and show only the vertices as colored corner points.
Geometry coloredMesh = new Geometry ("ColoredMesh", cMesh);
...
@@ -277,39 +341,46 @@ rootNode.attachChild(geo);
-This will result in a 10 px dot being rendered for each of the four vertices. The dot has the vertex color you specified above. The Quad's faces are not rendered at all. This can be used for a special debugging or editing mode. +This will result in a 10 px dot being rendered for each of the four vertices. The dot has the vertex color you specified above. The Quad's faces are not rendered at all in this mode. You can use this to visualize a special debugging or editing mode in your game.
Debugging Tip: Culling
-By default, jME3 optimizes a mesh by culling (not drawing) its backfaces. It determines which side the front or backface of a mesh is by the order of the vertices: The frontface is the one where the vertices are specified counter-clockwise. +By default, jME3 optimizes a mesh by "backface culling", this means not drawing the inside. It determines the side of a triangle by the order of the vertices: The frontface is the face where the vertices are specified counter-clockwise.
-This means for you that your custom mesh is invisible when seen from "behind" or from the inside. This may not be a problem, often this is even intended because it's faster. The player will not look at the inside of most things anyway. For example, if your custom mesh is a closed polyhedron, or a flat wallpaper-like object, then rendering the backfaces (the inside of the pillar, the back of the painting, etc) would indeed be a waste of resources. +This means for you that, by default, your custom mesh is invisible when seen from "behind" or from the inside. This may not be a problem, typically this is even intended, because it's faster. The player will not look at the inside of most things anyway. For example, if your custom mesh is a closed polyhedron, or a flat wallpaper-like object, then rendering the backfaces (the inside of the pillar, the back of the painting, etc) would indeed be a waste of resources.
-In case however that your usecase requires the backfaces to be visible, you have two options: +In case however that your usecase requires the backfaces be visible, you have two options:
-
-
+See also: -See also: Spatial ??? contains more info about how to debug custom meshes (that do not render as expected) by changing the default culling behaviour.
++
See also: @@ -318,4 +318,4 @@ See also: -
\ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/elephant-pointlights.png b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/elephant-pointlights.png index 5803ec7b0..7edbb1b61 100644 Binary files a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/elephant-pointlights.png and b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/elephant-pointlights.png differ diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/endless_terraingrid.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/endless_terraingrid.html index 60c93a6c7..f3ea78305 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/endless_terraingrid.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/endless_terraingrid.html @@ -63,12 +63,13 @@ HeightMapGrid adds the possibility of loading terrain tiles on demand instead of
+
After playing around with the terrain in jME3, soon comes the requirement of having larger explorable lands. Increasing the size of one TerrainQuad leads to more memory usage, while it will still be easy to reach the worlds boundaries. That???s why TerrainGrid was designed. It extends the TerraindQuad class and uses 4 HeightMaps (dark blue) as the four sub-quad. This means that a terrain of size 513 will use tiles of 257. Also an LRUCache is built into the terrain package, so surrounding tiles (green) can be pre-cached on a different thread, lowering the loading time. The quads are updated as the camera approaches the boundary of the light blue section.
Rationale
Usage
-
@@ -111,5 +112,5 @@ Further information about terrain and TerrainQuad can be found in the wiki at:
fade.setDuration().
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/headless_server.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/headless_server.html
index 74d8031e5..13a786a0c 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/headless_server.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/headless_server.html
@@ -92,4 +92,4 @@ Okay, so you can now start your game in a headless 'server mode', wher
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/hinges_and_joints.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/hinges_and_joints.html
index 2991944e8..27c50a87e 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/hinges_and_joints.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/hinges_and_joints.html
@@ -232,4 +232,4 @@ When you disable the motor, the chained nodes are exposed to gravity again:
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/house-directionallight.png b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/house-directionallight.png
index 3cd00edf6..c4ad7a757 100644
Binary files a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/house-directionallight.png and b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/house-directionallight.png differ
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/hud.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/hud.html
index 2a4025a0b..3188e3421 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/hud.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/hud.html
@@ -217,4 +217,4 @@ For HUDs, you basically follow the same instructions as for creating a normal
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/input_handling.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/input_handling.html
index 6068ef1ce..3414c7f1b 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/input_handling.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/input_handling.html
@@ -385,4 +385,4 @@ The abstraction of separating triggers and mappings has the advantage that you c
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/j3m_material_files.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/j3m_material_files.html
index 1568064d4..df5dd38fb 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/j3m_material_files.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/j3m_material_files.html
@@ -359,4 +359,4 @@ The PNG file is in the same
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/jme3_shaders.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/jme3_shaders.html
index 620a71d4b..f301a852e 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/jme3_shaders.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/jme3_shaders.html
@@ -234,7 +234,7 @@ JME3 uses some global uniforms for lighting :
-these uniforms are passed to the shader without having to declare them in the j3md file, but you have to specify in the technique definition " LightMode MultiPass" see lighting.j3md for more information.
+These uniforms are passed to the shader without having to declare them in the j3md file, but you have to specify in the technique definition " LightMode MultiPass" see lighting.j3md for more information.
@@ -464,4 +464,4 @@ Those attributes are deprecated since GLSL 1.3 (opengl 3), hence JME3 global uni
-
-Obviously, this does apply to AmbientLights which have no position. +Obviously, this does not apply to AmbientLights, which have no position.
- +Simple Lighting
BasicShadowRenderer
Parallel-Split Shadow Map
+ +DirectionalLightShadowRenderer
++ +Full sample code +
+-
+
- +
+
DirectionalLight sun = new DirectionalLight(); + sun.setColor(ColorRGBA.White); + sun.setDirection(cam.getDirection()); + rootNode.addLight(sun); + + /* Drop shadows */ + final int SHADOWMAP_SIZE=1024; + DirectionalLightShadowRenderer dlsr = new DirectionalLightShadowRenderer(assetManager, SHADOWMAP_SIZE, 3); + dlsr.setLight(sun); + viewPort.addProcessor(dlsr); + + DirectionalLightShadowFilter dlsf = new DirectionalLightShadowFilter(assetManager, SHADOWMAP_SIZE, 3); + dlsf.setLight(sun); + dlsf.setEnabled(true); + FilterPostProcessor fpp = new FilterPostProcessor(assetManager); + fpp.addFilter(dlsf); + viewPort.addProcessor(fpp);+ +
Parallel-Split Shadow Map (deprecated)
@@ -344,7 +375,7 @@ As said above, it's more efficient to specify individual shadow behaviour f terrain.setShadowMode(ShadowMode.Receive);
Screen Space Ambient Occlusion
-Important: Using third-person view requires you to deactivate the default flyCam (first-person view). This means that you have to configure your own navigation (key inputs and analogListener) that make your player character walk. For moving a physical player character, use player.setWalkDirection(), for a non-pysical character you can use player.move().
+Important: Using third-person view requires you to deactivate the default flyCam (first-person view). This means that you have to configure your own navigation (key inputs and analogListener) that make your player character walk. For moving a physical player character, use player.setWalkDirection(), for a non-physical character you can use player.move().
Code Samples
Camera Node
Code sample: @@ -87,7 +87,7 @@ The camera's transformation is copied over the spatial's transformatio - +
Chase Camera
Code sample: @@ -148,7 +148,7 @@ new KeyTrigger(KeyInput.KEY_SPACE))
Which to Choose?
-See also: Hello Terrain
- setFloat("Texture1Scale",1f);
- setTexture("Texture2", assetManager.loadTexture("")); (green)
- setFloat("Texture2Scale",1f);
-setTexture("Texture3", assetManager.loadTexture("")); (blue)
- setFloat("Texture3Scale",1f);
+See also: Hello Terrain
+ setFloat("Tex1Scale",1f);
+ setTexture("Tex2", assetManager.loadTexture("")); (green)
+ setFloat("Tex2Scale",1f);
+setTexture("Tex3", assetManager.loadTexture("")); (blue)
+ setFloat("Tex3Scale",1f);
setTexture("Alpha", assetManager.loadTexture(""));
setBoolean("PointSprite",true);
Phong Illuminated
setBoolean("WardIso",true);4)
| Special Illuminated Material Definitions | Usage | Material Parameters |
|---|
Other: Test and Debug
| Common/MatDefs/Misc/ShowNormals.j3md | A color gradient calculated from the model's surface normals. You can use this built-in material to debug the generation of normals in meshes, to preview models that have no material and no lights, or as fall-back default material. This built-in material has no parameters. |
RenderStates
Transparency
| getAdditionalRenderState().setBlendMode(BlendMode.PremultAlpha); | Pre-multiplied alpha blending. E.g. if the color of the object has already been multiplied by its alpha, this is used instead of "Alpha" blend mode. | For use with Premult Alpha textures. |
If the DiffuseMap has an alpha channel, use: @@ -332,7 +332,7 @@ Later, put the Geometry (not the Material!) in the appropriate render queue
Culling
| getAdditionalRenderState().setFaceCullMode(FaceCullMode.FrontAndBack) | Culls both backfaces and frontfaces. | Use this as an efficient way to make an object temporarily invisible, while keeping all its other in-game properties (such as node attachment, collision shapes, interactions, etc) active. |
Miscellaneous
| getAdditionalRenderState().setPolyOffset(); | Enable polygon offset. | Use this when you have meshes that have triangles really close to each over (e.g. ), it will shift the depth values to prevent . |
Related Links @@ -389,7 +389,7 @@ Later, put the Geometry (not the Material!) in the appropriate render queue
-
-
- Meshes are made up of triangles.+
-getTriangleCount(???)andgetTriangle(???) - Meshes are made up of triangles:
getTriangleCount(???)andgetTriangle(???)
- - Each mesh has a unique ID+
-getId() - Each mesh has a unique ID:
getId() - Meshes have transformations: Location (local translation), rotation, scale.
-
- Meshes have a bounding volume. jME3 can detect intersections (that is, non-physical collisions) between meshes, or between meshes and 2D elements such as rays.+
-collideWith(). - Meshes have a bounding volume. jME3 can detect intersections (that is, non-physical collisions) between meshes, or between meshes and 2D elements such as rays:
collideWith(). - Meshes are locked with
setStatic()and unlocked withsetDynamic().-
@@ -31,25 +28,35 @@ All visible game elements in a scene, whether it is a Model or a Shape, are made
-You can use default Shapes as meshes; load 3D models (i.e. meshes created in external applications); or create free-form custom meshes programmatically. +You have several options when creating Geometries from meshes:
+-
+
- Use built-in Shapes as meshes;+
+
- Load 3D models (that is, meshes created in external applications); or+
+
- Create free-form custom meshes programmatically.+
+
Vertex Buffer
The VertexBuffer contains a particular type of geometry data used by Meshes. Every VertexBuffer set on a Mesh is sent as an attribute to the vertex shader to be processed. -
+ +Mesh Vertex Buffers
+| Vertex Buffer Type | Description | @@ -97,18 +104,23 @@ The VertexBuffer contains a particular type of geometry data used by Meshes. EveType.BoneIndex | Bone indices, used with animation |
|---|
| Mesh method | Description | ||
|---|---|---|---|
| setLineWidth(1) | +setLineWidth(1) | the thickness of the line if using Mode.Lines | |
| setPointSize(4.0f) | +setPointSize(4.0f) | the thickness of the point when using Mode.Points | |
| setBound(boundingVolume) | +setBound(boundingVolume) | if you need to specifiy a custom optimized bounding volume | |
| setStatic() | Locks the mesh so you cannot modify it anymore, thus optimizing its data (faster). | @@ -117,27 +129,32 @@ The VertexBuffer contains a particular type of geometry data used by Meshes. EvesetDynamic() | Unlocks the mesh so you can modified it, but this will un-optimize the data (slower). |
| setMode(Mesh.Mode.Points) | Used to set mesh modes, see below | +setMode(Mesh.Mode.Points) | Used to set mesh rendering modes, see below. |
| getId() | +getId() | returns the Mesh ID | |
| getTriangle(int,tri) | +getTriangle(int,tri) | returns data of triangle number int into variable tri |
|
| scaleTextureCoordinates(Vector2f) | +scaleTextureCoordinates(Vector2f) | How the texture will be stretched over the whole mesh. |
| Mesh Mode | Description | ||
|---|---|---|---|
| Mesh.Mode.Points | Show only corner points | +Mesh.Mode.Points | Show only corner points (vertices) of mesh |
| Mesh.Mode.Lines | Show lines | +Mesh.Mode.Lines | Show lines (edges) of mesh |
| Mesh.Mode.LineLoop | ? | @@ -158,7 +175,17 @@ The VertexBuffer contains a particular type of geometry data used by Meshes. EveMesh.Mode.Hybrid | ? |
Level of Detail
+
+
+Optionally, custom meshes can have a LOD (level of detail optimization) that renders more or less detail, depending on the distance of the mesh from the camera. You have to specify several vertex buffers, one for each level of detail you want (very far away with few details, close up with all details, and something in the middle). Use setLodLevels(VertexBuffer[] lodLevels).
+
pick target input mapping implements an action that d
-Note: Picking with a visible pouse pointer implies that your application can no longer use the default flyCam where the MouseAxisTrigger rotates the camera. You have to deactivate the flyCam mappings and provide custom mappings. Either different inputs rotate the camera, or the camera is fixed. +Note: Picking with a visible mouse pointer implies that your application can no longer use the default flyCam where the MouseAxisTrigger rotates the camera. You have to deactivate the flyCam mappings and provide custom mappings. Either different inputs rotate the camera, or the camera is fixed.
-
@@ -147,4 +147,4 @@ The following example rotates Spatials named "Red Box" or "Blue B
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/multiple_camera_views.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/multiple_camera_views.html
index 363a81b6f..080c2aeaf 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/multiple_camera_views.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/multiple_camera_views.html
@@ -230,4 +230,4 @@ You have full control to determine which Nodes the camera can see! It can see th
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/multithreading.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/multithreading.html
index 1b083c6f7..efb29180f 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/multithreading.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/multithreading.html
@@ -6,26 +6,25 @@
jME3 is similar to Swing in that for speed and efficiency all changes to the world must be made in a single update thread. This is happening automatically if using Controls and AppSates update metod or simpleUpdate however whenever you pass work to another thread you need to hand the results back to the main jME3 thread before making any changes to the scene graph.
-
public void rotateGeography(final Geography goe, final Quaternian rot) {
- mainApp.enqueue(new Callable<Spatial>() {
-
- public Spatial call() throws Exception {
- return geo.rotate(rot);
- }
-
- });
- }
+public void rotateGeometry(final Geometry geo, final Quaternion rot) {
+ mainApp.enqueue(new Callable<Spatial>() {
+ public Spatial call() throws Exception {
+ return geo.rotate(rot);
+ }
+ });
+}
-Note that this example does not fetch the returned value by calling get() on the Future object returned from enqueue(). This means that the example method rotateGeography() will return immediately and will not wait for the rotation to be processed before continuing.
+Note that this example does not fetch the returned value by calling get() on the Future object returned from enqueue(). This means that the example method rotateGeometry() will return immediately and will not wait for the rotation to be processed before continuing.
If the processing thread needs to wait or needs the return value then get() or the other methods in the returned Future object such as isDone() can be used.
+
Multithreading Optimization
Java Multithreading
Multithreading in jME3
Executor
Control Class Fields
Control Update() Method
The Callable
Conclusion
+
Learn more from the NiftyGUI page: @@ -346,4 +346,4 @@ Learn more from the NiftyGUI page: -
\ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/nifty_gui_xml_layout.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/nifty_gui_xml_layout.html index 87cd6cb5a..5450391f5 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/nifty_gui_xml_layout.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/nifty_gui_xml_layout.html @@ -293,8 +293,12 @@ The font used is jME3's default font "Interface/Fonts/Default.fnt" Before you can use any control, you must load a Control Definition first. Add the following two lines before your screen definitions: -<useControls filename="nifty-default-controls.xml" /> - <useStyles filename="nifty-default-styles.xml" />+
<useStyles filename="nifty-default-styles.xml" /> + <useControls filename="nifty-default-controls.xml" />+ +
+Note that the useStyles tag must be the first child of the nifty tag, otherwise you will see an error in design view. +
@@ -347,7 +351,7 @@ Nifty additionally offers many customizable controls such as check boxes, text f - +Intermediate Result
Next Steps
All non-mesh CollisionShapes can be used for dynamic, kinematic, as well as static Spatials. (Code samples see below) @@ -200,7 +254,7 @@ All non-mesh CollisionShapes can be used for dynamic, kinematic, as well as stat Limitations: Requires heightmap data. Collisions between two mesh-accurate shapes cannot be detected, only non-mesh shapes can collide with this shape.
On a CollisionShape, you can apply a few properties
@@ -214,7 +268,7 @@ On a CollisionShape, you can apply a few properties
new Vector3f(1f,2f,1f)
The mesh-accurate shapes can use a CollisionShapeFactory as constructor (code samples see below). @@ -231,7 +285,7 @@ The mesh-accurate shapes can use a CollisionShapeFactory as constructor (code sa
- +CollisionShape Code Samples
-
@@ -262,7 +316,7 @@ The mesh-accurate shapes can use a CollisionShapeFactory as constructor (code sa
Create PhysicsControl
| Special PhysicsControls | Usage | Examples | Special Control used for collapsing, flailing, or falling characters | Falling persons, animals, robots, "Rag dolls" |
|---|
Click the links for details on the special PhysicsControls. This article is about RigidBodyControl.
- +PhysicsControls Code Samples
Add PhysicsControl to Spatial
Add PhysicsControl to PhysicsSpace
Changing the Scale of a PhysicsControl
PhysicsSpace Code Samples
Specify Physical Properties
On a RigidBodyControl, you can apply the following physical forces: @@ -520,9 +574,9 @@ On a RigidBodyControl, you can apply the following physical forces: (See detailed explanation below.) - + - +
Kinematic vs Dynamic vs Static
setKinematic(false);
When Do I Use Kinematic Objects?
@@ -595,7 +649,7 @@ setKinematic(false); - +Forces: Moving Dynamic Objects
setApplyPhysicsLocal(true) for an object to make it move relatively to its local physics space. You would do that if you need a physics space that moves with a node (e.g. a spaceship with artificial gravity surrounded by zero-g space). By default, it's set to false, and all movement is relative to the world.
@@ -681,7 +735,7 @@ removeCollideWithGroup(COLLISION_GROUP_01)Best Practices
-
@@ -717,8 +771,8 @@ removeCollideWithGroup(COLLISION_GROUP_01)
AudioNode waves = new AudioNode(assetManager, "Sound/Environment/Ocean Waves.ogg", false); +See also: audio. -AudioNode waves = new AudioNode(assetManager, "Sounds/Environment/Ocean Waves.ogg", false); waves.setLooping(true); audioRenderer.playSource(waves);@@ -278,7 +278,7 @@ audioRenderer.playSource(waves);
+
See also: @@ -292,4 +292,4 @@ See also: -
\ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/ragdoll.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/ragdoll.html index c9d85febc..9908a0312 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/ragdoll.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/ragdoll.html @@ -214,4 +214,4 @@ If you experience weird behaviour in a ragdoll ??? such as exploding into pieces - \ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/read_graphic_card_capabilites.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/read_graphic_card_capabilites.html index 75115007e..1dedb032c 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/read_graphic_card_capabilites.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/read_graphic_card_capabilites.html @@ -69,4 +69,4 @@ VertexTextureFetch, FloatTexture, TextureCompressionLATC] - \ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/remote-controlling_the_camera.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/remote-controlling_the_camera.html index 9275d7dd6..0c9af2669 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/remote-controlling_the_camera.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/remote-controlling_the_camera.html @@ -56,4 +56,4 @@ If desired, attach the camNode to a MotionTrack to let it travel along waypoints - \ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/save_and_load.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/save_and_load.html index e2f012c9c..fbb87dd4f 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/save_and_load.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/advanced/save_and_load.html @@ -167,7 +167,7 @@ To make a custom class savable:-
-Cloned spatials share the same mesh, while each cloned spatial can have its own local transformation (translation, rotation, and scale) in the scene. This means you only use clone() on spatials whose meshes never change. The most common use case for cloning is when you use several Spatials that are based on the same Shapes.
+Cloned spatials share the same mesh, while each cloned spatial can have its own local transformation (translation, rotation, and scale) in the scene. This means you only use clone() on spatials whose meshes never change. The most common use case for cloning is when you use several Spatials that are based on the same Shapes (e.g. trees, crates).
-The second use case is: When you load a model using loadModel() from the AssetManager, you may get a clone()ed object. In particular:
+The second use case is: When you load a model using loadModel() from the AssetManager, you may automatically get a clone()ed object. In particular:
-
-
- If the model is not animated (it has no+
AnimControl), you get a clone. All clones share one mesh object. (Uses less memory) - If the model is not animated (it has no
AnimControl), jME loads a clone. All clones share one mesh object in order to use less memory.
- - If the model is animated (it has a+
AnimControl), thenloadModel()duplicates the mesh for each loaded instance. (Uses more memory) - If the model is animated (it has a
AnimControl), thenloadModel()duplicates the mesh for each loaded instance. (Uses more memory, but can animate.)
+
Usually there is no need to manually use any of the clone() methods on models. Using the Asset Manager's loadModel() method will automatically do the right thing for your models.
clone() methods
-
+
How to Add Fields and Methods to a Spatial
-This first example adds an integer field named health to the Spatial player_node, and initializes it to 100.
+This first example adds an integer field named health to the Spatial playerNode, and initializes it to 100.
player_node.setUserData("health", 100);
+playerNode.setUserData("health", 100);
The second example adds a set of custom accessor methods to the player object. You create a custom PlayerControl() class and you add this control to the Spatial:
-player_node.addControl(new PlayerControl());+
playerNode.addControl(new PlayerControl());
In your PlayerControl() class, you define custom methods that set and get your user data in the spatial object. For example, the control could add accessors that set and get the player's health:
@@ -148,11 +149,11 @@ public void setHealth(int h) {
}
-Elsewhere in your code, you can access this data wherever you have access to the Spatial player_node.
+Elsewhere in your code, you can access this data wherever you have access to the Spatial playerNode.
health = player_node.getControl(PlayerControl.class).getHealth(); +health = playerNode.getControl(PlayerControl.class).getHealth(); ... -player_node.getControl(PlayerControl.class).setHealth(99);+playerNode.getControl(PlayerControl.class).setHealth(99);
- You can add as many data objects (of String, Boolean, Integer, Float, Array types) to a Spatial as you want. Just make sure to label them with unique case-sensitive strings (
health,Inventory,equipment, etc).
@@ -171,7 +172,7 @@ This is how you list all data keys that are already defined for one Spatial:
}
How to Access a Named Sub-Mesh
house is the loaded model. The s
Geometry submesh = (Geometry) houseScene.getChild("door 12");
What is Culling?
-Face culling refers to not drawing certain polygons of a mesh. The "inside" of the mesh (the so called backface) is never visible to the player, and as an optimization, game engines skip calculating backfaces by default. You may want to deactivate Face Culling while debugging custom meshes, so you can see them in case you turned them inside-out by accident. +Face culling means not drawing certain polygons of a mesh. Face culling behaviour is a property of the material. +
+ +
+Usage: The "inside" of a mesh (the so called backface) is typically never visible to the player, and as an optimization, the Back mode skips calculating all backfaces by default. Activating the Off or Front modes can be useful when you are debugging custom meshes and try to identify accidental inside-out faces.
-You can switch the com.jme3.material.RenderState.FaceCullMode to +You can switch the com.jme3.material.RenderState.FaceCullMode to either:
-
-
- +
FaceCullMode.Back(default) ??? only the frontsides of a mesh are drawn. This is the normal behaviour. FaceCullMode.Back(default) ??? Only the frontsides of a mesh are drawn. Backface culling is the default behaviour.
-- +
FaceCullMode.Front??? only the backsides of meshes are drawn. The mesh will probably turn invisible. Useful if you are debugging a hand-made mesh and try to identify accidental inside-out faces. FaceCullMode.Front??? Only the backsides of a mesh are drawn. A mesh with frontface culling will most likely be invisible. Used for debugging "inside-out" custom meshes.
-- +
FaceCullMode.FrontAndBack??? The mesh becomes invisible. FaceCullMode.FrontAndBack??? Use this to make a mesh temporarily invisible.FaceCullMode.Off??? Every side of the mesh is drawn. Looks normal, but slows down large scenes.
@@ -255,7 +260,7 @@ Example:
spatial.setCullHint(CullHint.Never); // always drawn
See also
-
@@ -273,5 +278,5 @@ Example:
Understanding the Code
The Terrain Code
The Collision Detection Code
Combining the Two
-
-
- The CollisionShapeFactory creates the CollisionShape+
terrainShapefor theterrainnode. - You create a static (zero-mass) RigidBodyControl.
-
- Out of the-
terrainShape, you create a static (zero-mass) RigidBodyControllandscape.
- - Add the+
landscapecontrol to theterrainto make it physical. - Add the control to the
terrainto make it physical.
/** 6. Add physics: */ - CollisionShape terrainShape = - CollisionShapeFactory.createMeshShape((Node) terrain); - landscape = new RigidBodyControl(terrainShape, 0); - terrain.addControl(landscape);+ terrain.addControl(new RigidBodyControl(0));
You attach the terrain and the first-person player to the rootNode, and to the physics space, to make them appear in the game world.
@@ -290,7 +282,7 @@ You attach the terrain and the first-person player to
bulletAppState.getPhysicsSpace().add(player);
Conclusion
You should spawn high up in the area and fall down to the map, giving you a few seconds to survey the area. Then walk around and see how you like the lay of the land.
-+
See also: @@ -320,5 +312,5 @@ See also:
For best practices on how to use setWalkDirection(), see the Navigation Inputs example below.
Walking Character Demo
Code Skeleton
public class WalkingCharacterDemo extends SimpleApplication
@@ -132,7 +137,7 @@ For best practices on how to use setWalkDirection(), see the Naviga
public void onAnimChange(AnimControl control, AnimChannel channel, String animName) { }
Overview
Activate Physics
private BulletAppState bulletAppState;
@@ -175,7 +180,7 @@ public void simpleInitApp() {
}
Initialize the Scene
Create the Animated Character
Set Up AnimControl and AnimChannels
Add ChaseCam / CameraNode
private ChaseCamera chaseCam;
@@ -302,7 +307,7 @@ public void simpleInitApp() {
...
Handle Navigation
+
Optionally, download
@@ -207,6 +212,11 @@ Activating the nbandroid plugin in the jMonkeyEngine .* + +Notes
@@ -229,7 +239,7 @@ Activating the nbandroid plugin in the jMonkeyEngine +Android Considerations
Using Android specific functions
More Info
Animation Controler and Channel
+Animation Controller and Channel
@@ -177,7 +177,7 @@ In your case, where you want animations to chain for the whole skeleton, you jus
Responding to Animation Events
implements AnimEventListener to the class declaration. This int
}
Trigger Animations After User Input
Exercises
Conclusion
+
See also: @@ -357,5 +357,5 @@ See also:
+
See also: @@ -498,4 +498,4 @@ Let's add some action to the scene and continue with the - \ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_audio.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_audio.html index eeefda9e0..e3dc9130b 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_audio.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_audio.html @@ -7,7 +7,7 @@ Previous: Hello Te
-This tutorial explains how to add 3D sound to a game, and how make sounds play together with events, such as clicking. You learn how to use an Audio Listener and Audio Nodes. You also make use of an Action Listener and a MouseButtonTrigger from the previous Hello Input tutorial to make a mouse click trigger a gun shot sound. +This tutorial explains how to add 3D sound to a game, and how to make sounds play together with events, such as clicking. You learn how to use an Audio Listener and Audio Nodes. You also make use of an Action Listener and a MouseButtonTrigger from the previous Hello Input tutorial to make a mouse click trigger a gun shot sound.
@@ -17,7 +17,7 @@ This tutorial explains how to add 3D sound to a game, and how make sounds play t
- +Sample Code
package jme3test.helloworld; @@ -110,13 +110,13 @@ When you run the sample, you should see a blue cube. You should hear a nature-li
Understanding the Code Sample
-In the initSimpleApp() method, you create a simple blue cube geometry called player and attach it to the scene ??? this just arbitrary sample content, so you see something when running the audio sample.
+In the initSimpleApp() method, you create a simple blue cube geometry called player and attach it to the scene ??? this is just arbitrary sample content, so you see something when running the audio sample.
@@ -124,7 +124,7 @@ Let's have a closer look at initAudio() to learn how to use
AudioNodes
Triggering Sound
Ambient or Situational?
play().playIns
Buffered or Streaming?
Play() or PlayInstance()?
| The same sound cannot play twice at the same time. | The same sounds can play multiple times and overlap. |
Your Ear in the Scene
Global, Directional, Positional?
-It makes equally sense to make the gunshot positional, and let the ambient sound come from every direction. How do you decide which type of 3D sound to use from case to case? +It makes equal sense to make the gunshot positional, and let the ambient sound come from every direction. How do you decide which type of 3D sound to use from case to case?
- In a game with moving enemies you may want to make the gun shot or footsteps positional sounds. In these cases you must move the AudioNode to the location of the enemy before@@ -356,7 +356,7 @@ In short, you must choose in every situation whether it makes sense for a sound
playInstance()ing it. This way a player with stereo speakers hears from which direction the enemy is coming.
Conclusion
+
@@ -391,5 +391,5 @@ See also:
-Run the sample. You should see a town square with houses and a monument. Use the WASD keys and the mouse to navigate around with a first-person perspective. Run forward and jump by pressing W and Space. Note how you step over the sidewalk, and up the steps to the monument. You can walk in the alleys between the houses, but the walls are solid. Don't walk over the edge of the world!
+Run the sample. You should see a town square with houses and a monument. Use the WASD keys and the mouse to navigate around with a first-person perspective. Run forward and jump by pressing W and Space. Note how you step over the sidewalk, and up the steps to the monument. You can walk in the alleys between the houses, but the walls are solid. Don't walk over the edge of the world!
-Previously in the onAction() method, you have collected the info in which direction the user wants to go in terms of "forward" or "left". In the update loop, you repatedly poll the current rotation of the camera. You calculate the actual vectors to which "forward" or "left" corresponds in the coordinate system.
+Previously in the onAction() method, you have collected the info in which direction the user wants to go in terms of "forward" or "left". In the update loop, you repeatedly poll the current rotation of the camera. You calculate the actual vectors to which "forward" or "left" corresponds in the coordinate system.
@@ -494,7 +494,7 @@ This is how the walking is triggered:
- +Conclusion
+
@@ -535,5 +535,5 @@ Related info:
test-data.jar. You can
-Copy them into you assets/Effects directory to use them.
+Copy them into your assets/Effects directory to use them.
Creating Custom Textures
assets
Emitter Parameters
setGravity() You can find details about effect parameters here. @@ -336,7 +336,7 @@ Add and modify one parameter at a time, and try different values until you get t
- +Exercise
Conclusion
+
-In order to see the total time that a key has been pressed for then the incoming value can be accumulated. The analogue listener may also need to be combined with an action listener so that you are notified when they key is released. +In order to see the total time that a key has been pressed for then the incoming value can be accumulated. The analogue listener may also need to be combined with an action listener so that you are notified when the key is released.
- Example: Navigational events (e.g. Left, Right, Rotate, Run, Strafe), situations where you interact continuously.@@ -325,7 +325,7 @@ Mappings registered to the ActionListener are digital either-or } - +
Table of Triggers
@@ -361,14 +361,14 @@ You can find the list of input constants in the files- +src/core/com/jme3/in KeyTrigger(KeyInput.KEY_LEFT), KeyTrigger(KeyInput.KEY_RIGHT)Tip: If you don't recall an input constant during development, you benefit from an IDE's code completion functionality: Place the caret after e.g.
- +KeyInput.|and trigger code completion to select possible input identifiers.Exercises
- +-
@@ -396,7 +396,7 @@ inputManager.addMapping("Pause", new KeyTrigger(usersPauseKey
Conclusion
@@ -418,5 +418,5 @@ Now you can already write a little interactive game! But wouldn't it be coo- - \ No newline at end of file + + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_main_event_loop.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_main_event_loop.html index f552e1591..348012f9f 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_main_event_loop.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_main_event_loop.html @@ -89,7 +89,7 @@ Now have a closer look at thesimpleUpdate()method ??? this is the-A rotating object is just a simple example. In the update loop, you typically have many tests and trigger various game actions. This is were you update score and health points, check for collisions, make enemies calculate their next move, roll the dice whether a trap has been set off, play random ambient sounds, and much more. +A rotating object is just a simple example. In the update loop, you typically have many tests and trigger various game actions. This is where you update score and health points, check for collisions, make enemies calculate their next move, roll the dice whether a trap has been set off, play random ambient sounds, and much more.
-
@@ -108,7 +108,7 @@ A rotating object is just a simple example. In the update loop, you typically ha
Init - Update - Render
@@ -155,7 +155,7 @@ Keep this in mind for later when your application grows.- +Exercises
@@ -189,7 +189,7 @@ Look back at the Hell- +Conclusion
@@ -201,7 +201,7 @@ Now you are listening to the update loop, "the heart beat" of the game- - \ No newline at end of file + + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_material.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_material.html index e685fbabe..127db9b2c 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_material.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_material.html @@ -417,7 +417,7 @@ You have also learned that a material can be stored in a .j3m file. The file ref Now that you know how to load models and how to assign good-looking materials to them, let's have a look at how to animate models in the next chapter, Hello Animation. -The next thing the game needs is some interaction! Continue learning how to respond to user input.
-
+
See also: @@ -221,5 +221,5 @@ See also:
+
See also @@ -431,7 +431,7 @@ See also
- (PDF)
-
- +
- You create a RigidBodyControl floor_phy for floor_geo.
-
-
- floor_phy has a mass of 0f+
- floor_phy has a mass of 0f
- You add floor_phy to floor_geo.
@@ -650,4 +650,4 @@ You have learned how to activate the jBullet PhysicsSpace in an application by a
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_picking.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_picking.html
index 186660d47..b0090df45 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_picking.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_picking.html
@@ -506,7 +506,7 @@ Use your imagination from here:
Now, wouldn't it be nice if those targets and the floor were solid objects and you could walk around between them? Let's continue to learn about Collision Detection.
-
- Escolha Arquivo (File)???Novo Projeto (New Project)??? do menu principal.+
- Choose File???New Project??? from the main menu.
-
- No assistente de Novo Projeto, selecione o modelo JME3???Jogo B??sico (Basic Game). Clique em prosseguir (Next).+
- In the New Project wizard, select the template JME3???Basic Game. Click Next.
-
-
- Especifique um nome de projeto, e.g. "HelloWorldTutorial"+
- Specify a project name, e.g. "HelloWorldTutorial"
-
- Especifique um caminho para armazenar seu novo projeto, e.g. um diret??rio projetosjMonkey no seu diret??rio de usu??rio.+
- Specify a path where to store your new project, e.g. a
jMonkeyProjectsdirectory in your home directory.
- - Clique em terminar (Finish).+
- Click Finish.
- D?? um clique com o bot??o direito no n?? pacotes de c??digo-fonte (Source Packages) de seu projeto.+
- Right-click the Source Packages node of your project.
-
- Escolha Novo (New)??? ???Classe Java (Java Class) para criar um novo arquivo.+
- Choose New??????Java Class to create a new file.
-
- Digite o nome da classe:+
HelloJME3 - Enter the class name:
HelloJME3
- - Digite o nome do pacote:+
jme3test.helloworld. - Enter the package name:
jme3test.helloworld.
- - Clique em Finalizar (Finish).+
- Click Finish.
- Voc?? deveria ver uma janela simples exibindo um cubo 3D.+
- You should see a simple window displaying a 3D cube.
-
- Pressione as teclas WASD keys e mova para navegar ao redor.+
- Press the WASD keys and move the mouse to navigate around.
-
- Olhe no texto do FPS e na informa????o de contagem de objeto na esquerda-fundo. Voc?? usar?? esta informa????o durante o desenvolvimento, e voc?? remover?? ela para a libera????o. (Para ler os n??meros corretamente, considere que as 14 linhas de texto contam como 14 objetos com 914 v??rtices.)+
- Look at the FPS text and object count information in the bottom left. You will use this information during development, and you will remove it for the release. (To read the numbers correctly, consider that the 14 lines of text counts as 14 objects with 914 vertices.)
-
- Pressione Escape (Esc) para fechar a aplica????o.+
- Press Escape to close the application.
- Load the heightmap.
-
+
See also: @@ -534,4 +534,4 @@ See also: -
\ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_simpleapplication.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_simpleapplication.html index 8420d279b..3e18d7e6c 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_simpleapplication.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_simpleapplication.html @@ -13,85 +13,85 @@ Next: Hello Node-Nesta s??rie de tutoriais, n??s assumimos que voc?? usa o SDK da jMonkeyEngine. Como um desenvolvedor Java intermedi??rio ou avan??ado, voc?? rapidamente ver?? que, em geral, voc?? pode desenvolver c??digo da jMonkeyEngine em qualquer ambiente de desenvolvimento integrado (NetBeans IDE, Eclipse, IntelliJ) ou mesmo da linha de comando. +In this tutorial series, we assume that you use the jMonkeyEngine SDK. As an intermediate or advanced Java developer, you will quickly see that, in general, you can develop jMonkeyEngine code in any integrated development environment (NetBeans IDE, Eclipse, IntelliJ) or even from the command line.
-OK, Vamos nos aprontar para criar nossa primeira aplica????o jMonkeyEngine3. +OK, let's get ready to create our first jMonkeyEngine3 application.
- -Crie um Projeto
+ +Create a Project
- - \ No newline at end of file + + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_terrain.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_terrain.html index ea536d372..bc24b63cd 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_terrain.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/beginner/hello_terrain.html @@ -226,14 +226,14 @@ It requires an image from a JME Texture.-Na SDK da jMonkeyEngine: +In the jMonkeyEngine SDK:
-
-
-Se voc?? tem perguntas, leia mais sobre Cria????o de Projeto aqui. +If you have questions, read more about Project Creation here.
-
N??s recomendamos atravessar os passos voc?? mesmo, como descrito nos tutoriais. Alternativamente, voc?? pode criar um projeto baseado no modelo JmeTests no SDK da jMonkeyEngine. Isto criar?? um projeto que j?? cont??m as amostras jme3test.helloworld (e muitas outras). Por exemplo, voc?? pode usar o projeto JmeTests para verificar se voc?? tem a solu????o certa. +- -We recommend to go through the steps yourself, as described in the tutorials. Alternatively, you can create a project based on the JmeTests template in the jMonkeyEngine SDK. It will create a project that already contains thejme3test.helloworldsamples (and many others). For example, you can use the JmeTests project to verify whether you got the solution right.Escreva uma aplica????o de amostra
+ +Write a SimpleApplication
- --Para este tutorial, voc?? deseja criar um pacote jme3test.helloworld no seu projeto, e criar um arquivo
HelloJME3.javanele. +For this tutorial, you want to create ajme3test.helloworldpackage in your project, and create a fileHelloJME3.javain it.-No SDK da jMonkeyEngine: +In the jMonkeyEngine SDK:
-
-
-O SDK cria o arquivo HelloJME3.java para voc??. +The SDK creates the file HelloJME3.java for you.
C??digo de Amostra
+ +Sample Code
- --Substitua os conte??dos do arquivo HelloJME3.java com o seguinte c??digo: +Replace the contents of the HelloJME3.java file with the following code:
package jme3test.helloworld; @@ -125,48 +125,48 @@ public class HelloJME3 extends SimpleApplication { }-D?? um clique com o bot??o direito na classe HelloJME3 class e escolha Executar (Run). Se um di??logo de configura????es da jME3 aparecer, confirme as configura????es padr??o. +Right-click the HelloJME3 class and choose Run. If a jME3 settings dialog pops up, confirm the default settings.
-
-
-Parab??ns! Agora camos decobrir como isso funciona! +Congratulations! Now let's find out how it works!
Compreendendo o c??digo
+ +Understanding the Code
- --O c??digo acima tem inicializado a cena, e iniciado a aplica????o. +The code above has initialized the scene, and started the application.
Inicie a SimpleApplication
+ +Start the SimpleApplication
- +-Olhe na primeira linha. A classe HelloJME3.java estende
com.jme3.app.SimpleApplication. +Look at the first line. The HelloJME3.java class extendscom.jme3.app.SimpleApplication.public class HelloJME3 extends SimpleApplication { // your code... }-Todo jogo JME3 ?? uma inst??ncia de com.jme3.app.SimpleApplication. A classe SimpleApplication gerencia seu grafo de cena 3D e automaticamente desenha ele para a tela ??? isto ??, em breve, o que uma engine de jogo faz para voc??! +Every JME3 game is an instance of
com.jme3.app.SimpleApplication. The SimpleApplication class manages your 3D scene graph and automatically draws it to the screen ??? that is, in short, what a game engine does for you!@@ -188,7 +188,7 @@ This code opens your application window. Let's learn how you put something
Understanding the Terminology
- +- +@@ -211,14 +211,14 @@ This code opens your application window. Let's learn how you put something
You want the cube to appear in the center. I create the Box at the origin = at Vector3f.ZERO.If you are unfamiliar with the vocabulary, read more about the Scene Graph here.
Initialize the Scene
@@ -234,7 +234,7 @@ Look at rest of the code sample. The- +simpleInitApp()method is auto The initialization code of a blue cube looks as follows:public void simpleInitApp() { - Box b = new Box(Vector3f.ZERO, 1, 1, 1); // create a 2x2x2 box shape at the origin + Box b = new Box(Vector3f.ZERO, 1, 1, 1); // create a 1x1x1 box shape at the origin Geometry geom = new Geometry("Box", b); // create a cube geometry from the box shape Material mat = new Material(assetManager, "Common/MatDefs/Misc/Unshaded.j3md"); // create a simple material @@ -288,7 +288,7 @@ A typical JME3 game has the following initialization process:Conclusion
@@ -326,7 +326,7 @@ The now following tutorials teach how you accomplish these tasks with the jMonke Continue with the Hello Node tutorial, where you learn more details about how to initialize the game world, also known as the scene graph. -
+
See also: @@ -349,5 +349,5 @@ See also:
AbstractHeightMap heightmap = null; +
AbstractHeightMap heightmap = null; Texture heightMapImage = assetManager.loadTexture( "Textures/Terrain/splat/mountains512.png"); heightmap = new ImageBasedHeightMap(heightMapImage.getImage()); heightmap.load();- +What is Texture Splatting?
@@ -301,7 +301,7 @@ Now you start painting the texture:- +Looking at the Texturing Code
@@ -357,7 +357,7 @@ Use- +setWrap(WrapMode.Repeat)to make the small texture fill the widWhat is a Terrain?
@@ -395,7 +395,7 @@ Create a TerrainQuad with the following arguments:- +Looking at the Terrain Code
@@ -430,7 +430,7 @@ You have created the terrain object.- +What is LOD (Level of Detail)?
@@ -446,12 +446,12 @@ Close parts of the terrain are rendered in full detail. Terrain parts that are f- +Exercises
- +Exercise 1: Texture Layers
@@ -470,15 +470,16 @@ You see it's easier to swap layers in the code, than to change the colors i- +Exercise 2: Randomized Terrains
- \ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/build_jme3_sources_with_netbeans.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/build_jme3_sources_with_netbeans.html index fa8326467..c5268f50c 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/build_jme3_sources_with_netbeans.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/build_jme3_sources_with_netbeans.html @@ -148,7 +148,7 @@ If you are working on a game project that depends on jme3: This tip works for any third-party JAR library that you use. (You may have to download the javadoc/sources from their home page separately). --The following two lines generate the heightmap object based on your user-defined image: +The following three lines generate the heightmap object based on your user-defined image:
-Texture heightMapImage = assetManager.loadTexture( +
AbstractHeightMap heightmap = null; + Texture heightMapImage = assetManager.loadTexture( "Textures/Terrain/splat/mountains512.png"); heightmap = new ImageBasedHeightMap(heightMapImage.getImage());@@ -486,7 +487,7 @@ The following two lines generate the heightmap object based on your user-defined Instead, you can also let JME3 generate a random landscape for you:-
-
- What result do you get when you replace the above two heightmap lines by the following lines and run the sample?
HillHeightMap heightmap = null; +
What result do you get when you replace the above three heightmap lines by the following lines and run the sample?- +HillHeightMap heightmap = null; HillHeightMap.NORMALIZE_RANGE = 100; // optional try { heightmap = new HillHeightMap(513, 1000, 50, 100, (byte) 3); // byte 3 is a random seed @@ -528,10 +529,11 @@ You see the variety of hilly landscapes that can be generated using this method.For this exercise, you can keep using the splat Material from the sample code above. Just don't be surprised that the Material does not match the shape of the newly randomized landscape. If you want to generate real matching splat textures for randomized heightmaps, you need to write a custom method that, for example, creates an alphamap from the heightmap by replacing certain grayscales with certain RGB values.+Exercise 3: Solid Terrains
@@ -541,20 +543,20 @@ Can you combine what you learned here and in +- - \ No newline at end of file + + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/build_from_sources.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/build_from_sources.html index 78c88b0bc..e387c87b0 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/build_from_sources.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/build_from_sources.html @@ -46,7 +46,7 @@ We recommend downloading theConclusion
-You have learned how to create terrains that are more efficient than loading one giant model. You know how to create generate random or handmade heightmaps. You can add a LOD control to render large terrains faster. You are aware that you can combine what you learned about collison detection to make the terrain solid to a physical player. You are also able to texture a terrain "like a boss" using layered Materials and texture splatting. You are aware that the jMonkeyEngine SDK provides a TerrainEditor that helps with most of these manual tasks. +You have learned how to create terrains that are more efficient than loading one giant model. You know how to generate random or create handmade heightmaps. You can add a LOD control to render large terrains faster. You are aware that you can combine what you learned about collision detection to make the terrain solid to a physical player. You are also able to texture a terrain "like a boss" using layered Materials and texture splatting. You are aware that the jMonkeyEngine SDK provides a TerrainEditor that helps with most of these manual tasks.
Do you want to hear your players say "ouch!" when they bump into a wall or fall off a hill? Continue with learning how to add sound to your game.
-
+
See also: @@ -572,5 +574,5 @@ See also:
+
Sources used: , @@ -160,4 +160,4 @@ Sources used:
- +
+
- (For colored Materials) In any RGBA color, the first three are Red-Green-Blue, and the last float is the Alpha channel. For example, to replace ColorRGBA.Red with a translucent red:
mat.setColor("Color", new ColorRGBA(1,0,0,0.5f));
- - (For textured Materials) Supply an AlphaMap that outlines which areas are transparent.- \ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/multi-media_asset_pipeline.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/multi-media_asset_pipeline.html index c03c50b16..144caf8de 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/multi-media_asset_pipeline.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/multi-media_asset_pipeline.html @@ -8,11 +8,11 @@ Assets are files that are not code. Your multi-media assets includes, for exampl
setTexture("AlphaMap", assetManager.loadTexture("Textures/window_alpha.png"));+(For textured Materials) Supply an AlphaMap that outlines which areas are transparent.mat.setTexture("AlphaMap", assetManager.loadTexture("Textures/window_alpha.png"));(For textured Materials) If the DiffuseMap has an alpha channel, use:- +mat.setBoolean("UseAlpha",true);@@ -326,7 +326,7 @@ getAdditionalRenderState().setAlphaFallOff(0.5f);Enables Alpha Testing Deactivate Alpha Testing for gradually translucent objects, such as colored glass, smoked glass, ghosts. It is possible to load a DiffuseMap texture that has an Alpha channel, and combine it with an underlying Material Color. @@ -339,7 +339,7 @@ Deactivate Alpha Testing for gradually translucent objects, suc- +(Optional) Wireframe
@@ -356,7 +356,7 @@ Additionally to the above settings, you can switch off and on a wireframe render-getAdditionalRenderState().setWireframe(true); Switch to showing the (textured) Material in wireframe mode. The wireframe optionally uses the Material's Colorvalue.Use wireframes to debug meshes, or for a "matrix" or "holodeck" effect. +- - \ No newline at end of file + + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/math.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/math.html index 91afc1e1e..a66f936a6 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/math.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/math.html @@ -123,4 +123,4 @@ float z = FastMath.sin(phi)*r;-
-
- You create textures in a graphic editor, for example Gimp, and export them as PNG or JPG.+
- You create textures in a graphic editor, for example , and export them as PNG or JPG.
-
- You create models in a 3D mesh editor, for example Blender, and export it in Ogre Mesh XML or Wavefront OBJ format.+
- You create models in a 3D mesh editor, for example , and export them in Ogre Mesh XML or Wavefront OBJ format.
-
- You create sounds in an audio editor, for example Audacity, and export them as WAVE or OGG.+
- You create sounds in an audio editor, for example , and export them as WAVE or OGG.
- +@@ -37,16 +37,19 @@ Assets are files that are not code. Your multi-media assets includes, for exampl
Convert original models to JME3's .j3o format. Move .j3o files into assets/Models.Don't reference original Blender/Ogre/OBJ files in your load() code, because these unoptimized files are not automatically packaged into the final JAR. + Agree on naming schemes and folder schemes with your artists early on to avoid confusion. E.g. keep naming schemes for bones and certain model parts. Try to keep your assets folder clean, its like your codes class structure. Don't mindlessly import downloaded models and other assets into your project without keeping a structure and knowing the files work. You can reimport, delete junk. +Read on for details.
- -Use The Assets Folder
+ +Use The Assets Folder
- -@@ -88,7 +91,7 @@ Example: For car models, create
Textures/vehicles/car1/,Mate- +
@@ -102,8 +105,8 @@ See also:
Create Textures and Materials
+ +Create Textures and Materials
- -@@ -128,16 +131,17 @@ Install a graphic editor such as Gimp or Photoshop. Consult the graphic
-Storing the textures inside your project directory is necessary for the paths in JME's binary model files (.j3o) to work. Treat the paths of your assets like class names of java classes, they define a specific asset. When you later generate .j3o files, compile class files, and distribute the project, paths and files need to be available in their final absolute form. It is imperative to keep the same directory structure from beginning to end. +Storing the textures inside your project directory is necessary for the paths in JME's binary model files (.j3o) to work. Treat the paths of your assets like class names of java classes, they define a specific asset. When you later generate .j3o files, and compile class files, and distribute the application, all paths and files need to be available in their final, absolute form.
-If you ever change the assets directory structure, you will have to do manual refactoring (just as for Java package name changes): You will need to re-export all affected models, regenerate all affected .j3o files, and manually update all affected paths in your code. +
It is imperative to keep the same directory structure from beginning to end. If you ever change the assets directory structure, you have to do manual refactoring (just as for Java package name changes): Re-export all affected models, regenerate all affected .j3o files, and manually update all affected path Strings in your code. +Create 3D Models
+ +Create 3D Models
+@@ -146,17 +150,17 @@ Install a mesh editor such as SDK. Only use Diffuse Map (minimum), Normal Map, Glow Map, and Specular Map.
-Every material feature not listed in the Materials Overview is unsupported and ignored by JME3. - Create materials for your models either in the 3D editor, or in the jME3 SDK. Only use the following material features: Diffuse Map or Diffuse Color (minimum); plus optionally Normal Map, Glow Map, Specular Map.
+Every material feature not listed in the Materials Overview is unsupported and ignored by JME3's renderer. - Unwrap the model in the 3D editor and generate a UV texture (i.e. one texture file that contains all the pieces of one model from different angles).@@ -165,9 +169,9 @@ Don't use multiple separate texture files with one model, it will break the
Don't use multiple separate texture files with one model, it will break the model into several meshes. - Export the model mesh in one of the following formats: .blend, Wavefront .OBJ/.MTL, Ogre .mesh/.material/.scene.
-
-
- Bake each texture into one file when exporting. (Create a Texture Atlas.)+
- Bake each texture into one file when exporting. Create a Texture Atlas.
-
- Save exported models to subfolders of the+
assets/Texturesdirectory, together with their Textures. (for now) - Save exported models to subfolders of the
assets/Textures(sic) directory, so they are together with their textures!
@@ -179,15 +183,14 @@ See also:
-You can transform (e.g. rotate) Geometries around their own center, or around a user defined center point. A user defined center point for one or more Geometries is called pivot. +You can transform (e.g. rotate) Geometries around their own center, or around a user defined center point. A user defined center point for one or more Geometries is called a pivot.
-
@@ -264,7 +264,7 @@ You can transform (e.g. rotate) Geometries around their own center, or around a
How do I Populate the Scenegraph?
| Specify what should be loaded at the start | Everything you initialize and attach to the rootNode in the simpleInitApp() method is part of the scene at the start of the game. |
How do I Transform Spatials?
| Scaling resizes Spatials | X-axis | Y-axis | Z-axis | length | height | width |
|---|
| Rotation turns Spatials | X-axis | Y-axis | Z-axis | pitch = nodding your head | yaw = shaking your head | roll = cocking your head |
|---|
How do I Troubleshoot Spatials?
How do I Add Custom Data to Spatials?
pivot id), you can
Conclusion
-We want to create brick Geometries from those boxes. For each Geometry with physcial properties, you create a RigidBodyControl. +We want to create brick Geometries from those boxes. For each Geometry with physical properties, you create a RigidBodyControl.
private RigidBodyControl brick_phy;@@ -482,7 +482,7 @@ This code sample does the following:
Which ever method you choose, a Java-Application works on the main operating systems: Windows, Mac OS, Linux, Android.
@@ -558,7 +561,16 @@ Which ever method you choose, a Java-Application works on the main operating sys
The distribution appears in a newly generated dist directory inside your project directory. These are the files that you upload or burn to CD to distribute to your customers.
+ +
+See also: +
+-
+
| .JPG, .PNG, .GIF | image | Textures, icons | .OGG | audio | OGG Vorbis music and sounds |
-
dist directory! If you or your customers try to run games containing code that loads non-.j3o models, you get a AssetNotFoundException Runtime Error (resource not found). Your final application code should only reference .j3o files. ??? Note that your developers will not get this runtime error when running development builds straight from the SDK.
See Also
-
@@ -255,5 +264,5 @@ Use the jMonkeyEngine SceneComposer to add these properties.
Avoid creating new objects
Avoid large objects in physics
Check the Statistics
- - \ No newline at end of file + + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/simpleapplication.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/simpleapplication.html index db385d0bc..61087b02c 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/simpleapplication.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/intermediate/simpleapplication.html @@ -145,15 +145,15 @@ getRenderer();tpf in the simpleUpdate() loop to time actions according to the time per frame.tpf in simpleUpdate() below to learn about timers.SimpleApplication Class
| SimpleApplication Method | Purpose | The default first-person fly-by camera control. This de | setDisplayStatView(false); | A default SimpleApplication displays mesh statistics on the screen using the com.jme3.app.StatsView class. The information is valuable during the development and debugging phase, but for the release, you should hide the statistics HUD. |
|---|
| SimpleApplication Interface | Purpose | The default first-person fly-by camera control. This de | public void simpleInitApp() | Override this method to initialize the game scene. Here you load and create objects, attach Spatials to the rootNode, and bring everything in its starts position. See also Application States for best practices. |
|---|---|---|---|
| public void simpleUpdate(float tpf) | Override this method to have access to the update loop. Use this loop to poll the current game state and respond to changes, or to let the game mechanics generate encounters and initiate state changes. Use tpf (time per frame) as a factor to time events. For more info on how to hook into the update loop, see Application States and Custom Controls. | +public void simpleUpdate(float tpf) | Override this method to hook into the update loop, all code you put here is repeated in a loop. Use this loop to poll the current game state and respond to changes, or to let the game mechanics generate encounters and initiate state changes. Use the float tpf as a factor to time actions relative to the time per frame in seconds: tpf is large on slow PCs, and small on fast PCs. +For more info on how to hook into the update loop, see Application States and Custom Controls. |
| public void simpleRender(RenderManager rm) | Optional: Override this method to implement advanced modifications of the frameBuffer and scene graph. | +public void simpleRender(RenderManager rm) | Optional: Advanced developers can override this method if the need to modify the frameBuffer and scene graph directly. |
app.setShowSettings(true); to present the user with a splashscreen and the built-in display settings dialog when starting the game; or use app.setShowSettings(false); to hide the buil-in screen (in this case, you may want to provide a custom splashscreen and settings panel). Set this boolean before calling app.start() in the main() method of the SimpleApplication. See also AppSettings.
@@ -231,7 +232,7 @@ getFlyByCamera()Default Input Mappings
F5
As long as the flyCam is enabled, the following so-called "WASD" inputs, including MouseLook, are available:
@@ -307,9 +308,9 @@ As long as the flyCam is enabled, the following so-called "WAS
Defaults and Customization
-
-
- Either In your application's contructor, you create the SimpleApplication with only the AppStates you want to keep:- - \ No newline at end of file + + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/ios.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/ios.html index 73c77bfcd..0e2ab365d 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/ios.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/ios.html @@ -98,4 +98,4 @@ Java code for iOS should be in the
public MyAppliction() { +public MyAppliction() { super( new StatsAppState(), new DebugKeysAppState() ); }Or in thesimpleInitApp()method, you remove the ones you do not want to keep:public void simpleInitApp() { +Or, in the@@ -350,5 +351,5 @@ The following example shows how you can remove one of the default AppStates, insimpleInitApp()method, you remove the ones you do not want to keep:public void simpleInitApp() { stateManager.detach( stateManager.getState(FlyCamAppState.class)); ...ios/srcfolder as well for clean
-To install the development version of jme3, , unzip the folder into a directory named jme3. The filenames here are just an example, but they will always be something like jME3_xx-xx-2011.
+To install the development version of jme3, , unzip the folder into a directory named jme3. The filenames here are just an example, but they will always be something like jME3_xx-xx-2011.
mkdir jme3 cd jme3 @@ -47,11 +47,11 @@ ant run cd ..
-If you see a Test Chooser open now, the build was successful. Tip: Use ant to build the libraries without running the demos.
+If you see a Test Chooser application open now, the build was successful. Tip: Use just ant instead of ant run to build the libraries without running the demos.
Sample Project Directory Structure
Libraries
Sample Code
Build and Run
Recommended Asset Directory Structure
-For media files and other assets, we recommend creating the following project structure: +For multi-media files, models, and other assets, we recommend creating the following project structure:
cd HelloJME3 mkdir assets @@ -167,12 +167,12 @@ mkdir assets/Sounds mkdir assets/Textures
-This will allow the default assetManager to load media files stored in the assets directory, like in this example:
+This directory structure will allow SimpleApplication's default AssetManager to load media files from your assets directory, like in this example:
import com.jme3.scene.Spatial;
...
-Spatial elephant = assetManager.loadModel("Models/Elephant/Elephant.meshxml");
-rootNode.attachChild(elephant);
+ Spatial elephant = assetManager.loadModel("Models/Elephant/Elephant.meshxml");
+ rootNode.attachChild(elephant);
...
@@ -180,7 +180,7 @@ You will learn more about the asset manager and how to customize it later. For n
Next Steps
E.g. when the thigh bone moves, the leg is fully affected, the hips joints less so, and the head not at all.
Kinematics
-
@@ -467,16 +469,16 @@ E.g. when the thigh bone moves, the leg is fully affected, the hips joints less
Controller and Channel
-In the JME3 application, you register animated models to the Animation Controller. The controller object gives you access to the available animation sequences. The controller has several channels, each channels can run one animation sequence at a time. To run several sequences, you create several channels, and run them in parallel. +In the JME3 application, you register animated models to the Animation Controller. The controller object gives you access to the available animation sequences. The controller has several channels, each channel can run one animation sequence at a time. To run several sequences, you create several channels, and run them in parallel.
Artificial Intelligence (AI)
Math
Coordinates
The Origin
Vectors
Vector3f v = new Vector3f( 17f , -4f , 0f ); // starts at (0/0/0) -Vector3f v = new Vector3f( 8f , 0f , 33f ).add(new Vector3f( 0f , -2f , -2f )); // starts at (8/0/33)+Vector3f v = new Vector3f( 8f , 0f , 33f ).add(new Vector3f( 0f , -2f , -2f )); // starts at (8,-2,31)
Unit Vectors
Normalized Vectors
Surface Normal Vectors
Cross Product
Transformation
Slerp
Game Developer Jargon
-
@@ -686,7 +688,7 @@ Example: A burning meteorite Geometry slerps from "position p1, rotation r1
3D graphics Terminology Wiki book
-
@@ -695,5 +697,5 @@ Example: A burning meteorite Geometry slerps from "position p1, rotation r1
-
-
- The origin, a single point in space.+
- The origin, a single central point in space.
-
-
- This point is always at coordinate (0,0,0)+
- The origin point is always at coordinate zero, in Java:
new Vector3f(0,0,0).
- - Three coordinate axes that are mutually perpendicular, and meet in the origin.+
- Three coordinate axes that are mutually perpendicular, and meet in the origin.
-
-
- The X axis is "right/left"+
- The X axis starts left and goes right.
-
- The Y axis is "up/down"+
- The Y axis starts below and goes up.
-
- The Z axis is "towards you/away from you"+
- The Z axis starts away from you, and goes towards you.
@@ -54,39 +54,109 @@ The coordinate system consists of:
- The default camera's location is+
Vector3f(0.0f, 0.0f, 10.0f).
+ - The default camera is looking in the direction described by the (so called) negative Z unit vector+
Vector3f(0.0f, 0.0f, -1.0f).
+ - Attaching a Spatial to the rootNode (or its child nodes) adds it to the scene;+
+
- Detaching a Spatial from the rootNode (or its child nodes) removes it from the scene.+
+
-Every point in 3D space is defined by its (x,y,z) coordinates. The data type for vectors is com.jme3.math.Vector3f.
+Every point in 3D space is uniquely defined by its X,Y,Z coordinates. The three numeric coordinates express how many "steps" from each of the three axes a point is. The data type for all vectors in jME3 is com.jme3.math.Vector3f. All vectors are relative to the described coordinate system.
+Example: The point new Vector3f(3,-5,1) is 3 steps to the right, 5 steps down, and 1 towards you.
-For your orientation, the default camera's location is (0.0f,0.0f,10.0f), and it is looking in the direction described by the unit vector (0.0f, 0.0f, -1.0f). This means your point of view is on the positive side of the Z axis, looking towards the origin, down the Z axis. +
-The unit of meassurement is world unit (wu). Typically, 1 wu is considered to be one meter. All scales, vectors and points are relative to this coordinate system.
+For your orientation:
+
-
+
+This means the player's point of view is on the positive side of the Z axis, looking back, towards the origin, down the Z axis.
- + +How to move yourself through the 3D scene
++ +When you play a 3D game, you typically want to navigate the 3D scene. Note that by default, the mouse pointer is invisible, and the mouse is set up to control the camera rotation! +
+ ++By default, jME3 uses the following common navigation inputs + +
+| Game Inputs | Camera Motion | Player POV | +
|---|---|---|
| Press the W and S keys | move the camera forward, and backward | you walk back and forth | +
| Press the A and D keys | move the camera left and right | you step left or right | +
| Press the Q and Y keys | move the camera up and down | you fly up and down | +
| Move the mouse left-right | rotate the camera left/right | you look left or right | +
| Move the mouse forwards-backwards | rotate up/down | you look at the sky or your feet | +
+ +These default settings are called "WASD keys" and "Mouse Look". You can customize input handling for your game. Sorry, but these settings work best on a QWERTY/QWERTZ keyboard. +
+ +Scene Graph and RootNode
-The scene graph represents your 3D world. Objects in the jME3 scene graph are called Spatials. Everything attached to the rootNode is part of the scene graph. Attaching a Spatial to the rootNode (or other nodes) adds the Spatial to the scene; detaching removes it.
+The scene graph represents your 3D world. Objects in the jME3 scene graph are called Spatials. Everything attached to the parent rootNode is part of your scene. Your game inherits the rootNode object from the SimpleApplication class.
+
+
-
+
+ +All objects in the scene graph are in a parent-child relationship. When you transform (move, rotate, scale) one parent, all its children follow. +
+ ++
Spatials: Node vs Geometry
-A Spatial can be transformed, loaded and saved. There are two types of Spatials, Nodes and Geometries. +A Spatial can be transformed (in other words, it has a location, a rotation, and a scale). A Spatial can be loaded and saved as a .3jo file. There are two types of Spatials, Nodes and Geometries:
| Visibility: | A visible 3-D object. | An invisible "handle" for a group of objects. | |||
|---|---|---|---|---|---|
| Purpose: | Represents the "look" of an object: Shape, color, texture, opacity/transparency. | Groups Geometries and other Nodes together: You transform a Node to affect all attached Nodes. | +Purpose: | A Geometry represents the "look" of an object: Shape, color, texture, opacity/transparency. | A Node groups Geometries and other Nodes together: You transform a Node to affect all attached Nodes (parent-child relationship). |
| Content: | Transformations, mesh, material. | Transformations. No mesh, no material. | |||
| Examples: | A box, a sphere, player, a building, a piece of terrain, a vehicle, missiles, NPCs, etc??? | The rootNode, the guiNode, an audio node, a custom grouping node, etc. | +Examples: | A box, a sphere, player, a building, a piece of terrain, a vehicle, missiles, NPCs, etc??? | The rootNode, the guiNode, an audioNode, a custom grouping node for a vehicle plus its passengers, etc. |
How to Use This Knowledge?
See also
- - \ No newline at end of file + + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/webstart.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/webstart.html index 8d62c6b8a..a36246437 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/webstart.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/jme3/webstart.html @@ -126,4 +126,4 @@ In your main() method, if running under WebStart, tell jME3 it is running in a l - \ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/3ds_to_blender_to_jmp.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/3ds_to_blender_to_jmp.html index 2cfbc4498..5bab98051 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/3ds_to_blender_to_jmp.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/3ds_to_blender_to_jmp.html @@ -67,4 +67,4 @@ As you can see, the .blend model was automatically converted to .j3o binary form - \ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/application_deployment.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/application_deployment.html index d92a0bca3..796bf7b5f 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/application_deployment.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/application_deployment.html @@ -48,7 +48,7 @@ Make your game unique and recognizable:
- In the Application>Web Start category, check the box to Enable Web Start.
-
- Check the box to make the application self-signed.+
- Check the box to make the application self-signed.
- Optionally, check the box to allow offline use.
@@ -343,4 +343,4 @@ jme3-libraries-gui, jme3-libraries-physics, jme3-libraries-video, etc.
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/applymaterial.jpg b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/applymaterial.jpg
index 5298937b1..eedf04a64 100644
Binary files a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/applymaterial.jpg and b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/applymaterial.jpg differ
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/asset_packs.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/asset_packs.html
index 56de8a93c..c56d09b97 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/asset_packs.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/asset_packs.html
@@ -201,4 +201,4 @@ You can publish your AssetPacks either as a zip file or directly to jmonkeyengin
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/blender.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/blender.html
index 156f6b74c..e390c43bf 100644
--- a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/blender.html
+++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/blender.html
@@ -331,7 +331,7 @@ P.S.
This text might be edited in a meantime if I forgot about something ;)
-
+
See also: @@ -350,4 +350,4 @@ See also: -
\ No newline at end of file + \ No newline at end of file diff --git a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/code_editor.html b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/code_editor.html index 23f46bf53..7efac7e92 100644 --- a/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/code_editor.html +++ b/sdk/jme3-documentation/src/com/jme3/gde/docs/sdk/code_editor.html @@ -240,7 +240,7 @@ By default, jMonkeyEngine uses the same