-
+LBL_Copyright=
- Lorc, Delapouite & contributors @ game-icons.net
- Brankic1979
- Entypo+
- Ogli (edited by grizeldi)
- Export the 3D model in Ogre XML or Wavefront OBJ format. Export Scenes as Ogre DotScene format.+
- Export the 3D model in GLTF or Wavefront OBJ format. Export Scenes as GLTF format.
- Save the files into a subdirectory of your jME3 project's
assetsdirectory.
@@ -28,53 +28,6 @@ - - -
- Open the menu File > Export > OgreXML Exporter to open the exporter dialog.-
-
- In the Export Materials field: Give the material the same name as the model. For example, the model-
something.mesh.xmlgoes withsomething.material, plus (optionally)something.skeleton.xml, and some JPG files.
- - In the Export Meshes field: Select a target subdirectory of your-
assets/Models/directory. E.g.assets/Models/something/.
- - Activate the following exporter settings:-
-
-
- Copy Textures: YES-
-
- Rendering Materials: YES-
-
- Flip Axis: YES-
-
- Require Materials: YES-
-
- Skeleton name follows mesh: YES-
-
- - Click export.-
-
- -
- - -
- - Create the model-
-
-
- Make sure your models location, rotation and scale is applied and zero / one (see “Model Checklist” below)-
-
- (Did you know? You can make any model from a box by only using extrusion, this creates very clean meshes)-
-
- - Create the armature bones, don't forget to have one root bone!-
-
-
- Start by placing the cursor at zero-
-
- Go to the Add→Armature→Single Bone menu and create the root bone-
-
-
- -
-
- - Select the bone and go to edit mode (press tab)-
-
- Select the root bone end and press “E” to extrude the bone, then start rigging your model this way-
-
- Make sure your armatures location, rotation and scale is applied (see “Model Checklist” below) before continuing-
-
- - Make the armature the parent of the model-
-
-
- Make sure you are back in object mode (press tab again)-
-
- First select the model object then select the armature object with shift pressed, then press Ctrl-P-
-
- When you do this, you can select how the bone groups will be mapped to the model vertices initially-
-
- - Set a new armature constraint in the model “Object Modifiers” settings and select the Armature-
-
-
- -
-
- - Voila, your model should move when you move the bones in pose mode-
-
- Go to the “Dope Sheet” window and select the “Action editor”-
-
-
- -
-
- - Add an action by pressing the plus button-
-
- Create the keyframes (select the model armature and press I) along the timeline-
-
-
- -
-
- - Each action will be an animation available via the animation control in jME after the import-
-
- Press the “F” button next to the action so it will be saved even if theres no references-
-
-
- The animation would else be deleted if its not the active animation on the armature and the file is saved-
-
- - The animation has to be a bone animation-
-
- Apply Location, Rotation and Scale to the mesh on Blender: On 3D View editor on Blender, select the mesh in Object Mode and go to the 3D View Editor’s header → Object Menu → Apply → Location / Rotation / Scale.-
-
-
- -
-
- - Apply Location, Rotation and Scale to the armature on Blender: On 3D View editor on Blender, select the armature in Object Mode and go to the 3D View Editor’s header → Object Menu → Apply → Location / Rotation / Scale.-
-
-
- -
-
- - Set the mesh’s origin point in the bottom of the mesh (see the image below).-
-
- Set the armature’s origin point in the bottom of the armature (see the image below).-
-
- Armature’s origin point and mesh’s origin point must be in the same location(see the image below).-
-
- Use a root bone located in the armature’s origin. This root bone must be in vertical position (see the image below) and it is the root bone of the armature. If you rotate the root bone, the the entire armature might be rotate when you import the model into jMonkey (I’m just mentioning the result, I don’t know where is the problem (jMonkey importer or blender’s ogre exporter plugin)).-
-
- Uncheck “Bone Envelopes” checkbox on the Armature modifier for the mesh (see the image below).-
-
-
- -
-
- - Uncheck “Envelopes” checkbox on the armature (see the image below).-
-
-
- -
-
- - -
- - ()-
-
- -
-
- -
-
- If you use the multiresolution modifier you only need one object. Lets look at this example:-
-
-
- -
-
- - Add a multiresolution modifier:-
-
-
- -
-
- - There are two types of modifiers: Catmull-Clark and Simple.-
-
-
- Simple is better for things like walls or floors.-
-
- Catmull-Clark is better for objects like spheres.-
-
- - When using Catmull-Clark with a higher “subdivide” value (more than 3) its good to have the “preview” value above 0 and less than the subdivide level. This is because Catmull-Clark smoothes the vertices, so the normalMap is not so precise.-
-
- Here is an example of Prewiew 1, it's more smooth than the original mesh:-
-
-
- -
-
- - Enable “Sculpt Mode” in blender and design the highPoly version of your model like here:-
-
-
- -
-
- - Now go into Render Tab, and bake a normalMap using same configuration as here:-
-
-
- -
-
- - uncheck “[ ] Bake from Multires”-
-
- switch to object mode-
-
- make a copy of your mesh (SHIFT+D)-
-
- remove the Multires modifier from the copied model-
-
- remove any materials from the copied model-
-
- remove the armature modifier from the copied model-
-
- select the original (highres) model-
-
- go into pose mode, clear any pose transformations-
-
- the highres and lowres models should be on top of each other now-
-
- select the original (highres) model-
-
- hold SHIFT and select the copied (lowres) model-
-
- in the properties menu go to render-
-
- use Bake > Normal-
-
- check “[x] Selected to Active”-
-
- use a reasonably high value for “Margin” (4+ pixels at least for 1024×1024 maps)-
-
- don't forget to safe the normal map image-
-
- Here is Blender Node example. It fixes the normal colors:-
-
-
- -
-
- - Here is the colors configuration:-
-
-
- -
-
- - Sometimes it will be needed to change R and G scale and add some blur for better effect. Do it like on image below-
-
-
- -
-
- - After rendering, save the file to a destination you want and use it with the JME Lighting Material and the lowpoly version of the model.-
-
-
- -
-
- - create a mesh in blender and unwrap it to create uvs-
-
-
- -
-
- - In the mesh tab you can see the sets of Uvs, it will create the first one.-
-
-
- You can assign w/e texture on it, i used the built in checker of blender for the example.-
-
- - In this list, create a new one and click on the camera icon so that baking is made with this set. Name it LightUvMap.-
-
- In the 3D view in edit mode select all your mesh vertice and hit 'U'/LightMap pack then ok it will unfold the mesh for light map.-
-
- Create a new image, go to the render tab an all at the end check the “Bake” section and select shadows. Then click bake.-
-
- If all went ok it will create a light map like this.-
-
-
- -
-
- - Go to the material tab, create a new one for your model and go to the Texture Tab.-
-
- Create 2 textures one for the color map, and one for the light map.-
-
- In the Mapping section be sure to select coordinates : UV and select the good set of coordinates.-
-
-
- -
-
- - Then the light map-
-
-
- -
-
- - Create material for it using the lighting definition.-
-
- Add the colorMap in the diffuse map slot and the lightMap in the light map slot.-
-
- Make sure you check “SeparateTexCoords”-
-
-
- -
-
- - It should roughly result in something like that :-
-
-
- -
-
- - -
- - Fire up blender and you'll see something like this.-
-
-
- -
-
- - The cube in the start scene is perfect for us. What we'll do is have Blender render the scene onto that cube. The resulting image is what we'll use for our sky box. So our jME sky will look like we stood inside the blender box and looked out on the scene in blender.-
-
- Start by selecting the box and set its material to shadeless.-
-
-
- -
-
- - Now we will create a texture for the box. Make sure the texture is an-
Environment Map, that theViewpoint Objectis set to the cube. The resolution is how large the resulting image will be. More pixels makes the sky look better but comes at the cost of texture memory. You'll have to trim the resolution to what works in your application.-
-
- -
-
- - Next up is the fun part, create the sky scene in blender. You can do whatever fits your application, include models for a city landscape, set up a texture mapped sphere in blender with a nice photographed sky, whatever you can think will make a good sky. I am not so creative so I created this scene:-
-
-
- -
-
- - Now render the scene (press F12). It doesn't actually matter where the camera is in blender but you might see something similar to this:-
-
-
- -
-
- - You can see that Blender has actually drawn the scene onto the cube. This is exactly what we want. Now to save the image.-
-
- Select the texture of the cube and select save environment map.-
-
-
- -
-
- - That is it for Blender. Open the saved image in some image editor (I use the Gimp from here).-
-
- You will notice that Blender has taken the 6 sides of the cube and pasted together into one image (3×2). So now we need to cut it up again into 6 separate images. In gimp I usually set the guides to where I want to cut and then go into Filters→Web→Slice and let gimp cut it up for me.-
-
-
- -
-
- - Next up is to move the image files into your assets directory and create the sky in jME. You can do that in the Scene Composer by right clicking the scene node, select-
Add Spatialand then selectSkybox.
- - - -
- -
-
- -
-
- Loading scene (only the current scene is loaded and imported as a node)-
-
- Loading mesh objects.-
-
-
- Meshes are split into several geometries when they have several materials applied.-
-
- All faces are stored as triangles (even if blender uses quads).-
-
- The mesh is 'Smooth' aware.-
-
- User defined UV coordinates are read.-
-
- Loading BMesh is supported.-
-
- - Loading textures.-
-
-
- Both image and generated textures are imported.-
-
- Textures influence is supported ('Influence' tab in blender 2.5+ and 'Map to' in 2.49).-
-
- Map input is not yet fully supported (currently working on it ;) ) so please use UV-mapping for all kinds of textures.-
-
- - Image textures.-
-
-
- Textures can be loaded from: png, jpg, bmp, dds and tga.-
-
- Both textures stored in the blender file and the outside are loaded (the outside textures need a valid path).-
-
- Image textures are stored as Texture2D.-
-
- - Generated textures.-
-
-
- All generated textures can be loaded except: VoxelData, EnviromentMap and PointDensity.-
-
- Feel free to use colorbands.-
-
- Generated textures are 'baked' into 2D textures and merged to create one flat texture. They can be freely merged with image textures.-
-
- Generated textures can be used as normal maps (but this looks poor when large amount of small triangles is used; incleasing generated texture ppu in blender key might help a little)-
-
- - Loading materials.-
-
-
- Materials are loaded and attached to geometries.-
-
- Because jMonkeyEngine supports only one material for each Mesh, if you apply several materials to one object – it will be split into several meshes (but still in one node).-
-
- Several kinds of input mapping is supported: UV maps, Orco and Nor; all projection types for 2D textures, XYZ coordinates mapping.-
-
- - Loading animations.-
-
-
- Bone animations and object animations are supported.-
-
- Armatures are imported as Skeleton. Constraint loading is not fully supported so use it carefully.-
-
- Only assigning vertices to bones is at the moment supported so do not use bones' envelopes.-
-
- - Loading modifiers.-
-
-
- Array modifier-
-
- Mirror modifier-
-
- Armature modifier (see loading animations)-
-
- Particles modifier (see loading particles)-
-
-
-
- More will come with time.-
-
- - Constraints loading-
-
-
- Constraints are basicly supported but they do not work the way I'd like it. So feel free to experiment with it. I will create another post when I get it to work properly.-
-
- - Particles loading.-
-
-
- Some features of particles loading is supported. You can use only particle emitters at the moment.-
-
- You can choose to emit particles from vertices, faces or the geometry's convex hull (instead of volume).-
-
- Currently Newtonian Physics is only supported.-
-
- It was mostly tested for blender 2.49 (so I'm not 100% sure about its use in blender 2.5+).-
-
- - Using sculpting.-
-
-
- This should work quite well for now :).-
-
- - Importing curves.-
-
-
- Both bezier and NURBS curves are supproted.-
-
- Feel free to use bevel and taper objects as well ;)-
-
- - Importing surfaces-
-
-
- NURBS surface and sphere can be imported.-
-
- - Importing sky-
-
-
- loading world's horizon color as a background color if no sky type is used-
-
- loading sky without the texture-
-
- loading textured sky (including both generated and normal textures)-
-
- - Full support for scale and offset in texture input mapping.-
-
- Full support for bone and object constraints.-
-
- More modifiers loaded.-
-
- Loading texts.-
-
- Loading meta objects (if jme will support it ;) ).-
-
- RGB10 and RGB9E5 texture types are not supported in texture merging operations (which means that you can use this as a single texture on the model, but you should not combine it with other images or generated textures).-
-
- If an armature is attached to a mesh that has more than one material the vertices of the mesh might be strongly displaced. Hope to fix that soon.-
-
- BlenderLoader that loads the whole scene. It returns an instance of LoadingResults that contains all the data loaded from the scene.-
-
- BlenderModelLoader loads only the model node and should be used if you have a single model in a file.-
-
- The last thing to do is to create a proper key.-
-
- - -
Copyright © 2025 jMonkeyEngine.\n
Please visit http://jmonkeyengine.org for more information.
Icons sets :
-
updates_not_found=
Updates: jMonkeyEngine SDK is updated to version {0}
\n URL_ON_IMG=http://jmonkeyengine.org/ diff --git a/build.gradle b/build.gradle index c86156d0c..32c0b0154 100644 --- a/build.gradle +++ b/build.gradle @@ -33,18 +33,18 @@ configurations.examplelibs { } dependencies { - - corelibs dep("com.github.xbuf:jme3_xbuf:0.9.1", false, false) corelibs dep("com.badlogicgames.gdx:gdx-ai:1.8.2", true, true) corelibs dep("javax.help:javahelp:2.0.05", false, false) corelibs dep("org.jmonkeyengine:jme3-core:$jmeVersion-$jmeVersionTag", true, true) corelibs dep("org.jmonkeyengine:jme3-desktop:$jmeVersion-$jmeVersionTag", true, true) - corelibs dep("org.jmonkeyengine:jme3-awt-dialogs:$jmeVersion-$jmeVersionTag", true, true) + corelibs dep("org.jmonkeyengine:jme3-awt-dialogs:$jmeVersion-$jmeVersionTag", true, true) + corelibs dep("org.jmonkeyengine:jme3-plugins-json:$jmeVersion-$jmeVersionTag", true, true) + corelibs dep("org.jmonkeyengine:jme3-plugins-json-gson:$jmeVersion-$jmeVersionTag", true, true) corelibs dep("org.jmonkeyengine:jme3-lwjgl:$jmeVersion-$jmeVersionTag", true, true) corelibs dep("org.jmonkeyengine:jme3-effects:$jmeVersion-$jmeVersionTag", true, true) - corelibs dep("org.jmonkeyengine:jme3-blender:3.3.2-stable", false, false) // Pin Pointed until jme3-blender has a dedicated release or support is phased out. - optlibs dep("com.github.stephengold:Minie:7.1.0", false, false) // replacement for bullet-native + corelibs dep("com.github.stephengold:Minie:8.2.0", true, true) // replacement for bullet-native + corelibs dep("com.github.stephengold:Heart:9.1.0", true, true) // requirement for Minie corelibs dep(fileTree("lib"), false, false) corelibs dep("org.jmonkeyengine:jme3-jogg:$jmeVersion-$jmeVersionTag", true, true) @@ -53,13 +53,18 @@ dependencies { corelibs dep("org.jmonkeyengine:jme3-plugins:$jmeVersion-$jmeVersionTag", true, true) corelibs dep("org.jmonkeyengine:jme3-terrain:$jmeVersion-$jmeVersionTag", true, true) + optlibs dep("com.simsilica:lemur:1.16.0", true, true) + optlibs dep("com.simsilica:lemur-props:1.2.0", true, true) + optlibs dep("com.simsilica:sio2:1.8.0", true, true) + optlibs dep("com.simsilica:sim-math:1.6.0", true, true) + optlibs dep("com.simsilica:zay-es:1.5.0", true, true) + optlibs dep("org.jmonkeyengine:jme3-jbullet:$jmeVersion-$jmeVersionTag", true, true) optlibs dep("org.jmonkeyengine:jme3-android:$jmeVersion-$jmeVersionTag", true, true) optlibs dep("org.jmonkeyengine:jme3-ios:$jmeVersion-$jmeVersionTag", true, true) optlibs dep("org.jmonkeyengine:jme3-android-native:$jmeVersion-$jmeVersionTag", true, true) optlibs dep("org.jmonkeyengine:jme3-lwjgl3:$jmeVersion-$jmeVersionTag", true, true) - optlibs dep("com.github.stephengold:Heart:8.2.0", true, true) - optlibs dep("com.github.stephengold:Wes:0.7.2", true, true) + optlibs dep("com.github.stephengold:Wes:0.8.1", true, true) testdatalibs dep("org.jmonkeyengine:jme3-testdata:$jmeVersion-$jmeVersionTag", false, false) examplelibs dep("org.jmonkeyengine:jme3-examples:$jmeVersion-$jmeVersionTag", false, true) } @@ -121,7 +126,19 @@ task copyBaseLibs(dependsOn:configurations.corelibs) { from file into "jme3-core-baselibs/release/modules/ext/" } - }else if( !isSourceOrJavadoc(file.name)){ + } else if( file.name.contains("Minie") && !isSourceOrJavadoc(file.name)) { + // Special handling of Minie, since it doesn't follow the name convention + copy { + from file + into "jme3-core-baselibs/release/modules/ext/" + } + } else if( file.name.contains("Heart") && !isSourceOrJavadoc(file.name)) { + // Special handling of Minie, since it doesn't follow the name convention + copy { + from file + into "jme3-core-baselibs/release/modules/ext/" + } + } else if( !isSourceOrJavadoc(file.name)){ copy { from file into "jme3-core-libraries/release/modules/ext/" @@ -168,6 +185,16 @@ task createBaseXml(dependsOn: configurations.corelibs) { jmeJarFiles.add(file) } + } else if( file.name.contains("Minie") && !isSourceOrJavadoc(file.name)) { + // Special handling of Minie, since it doesn't follow the name convention + if(!jmeJarFiles.contains(file)) { + jmeJarFiles.add(file) + } + } else if( file.name.contains("Heart") && !isSourceOrJavadoc(file.name)) { + // Special handling of Minie, since it doesn't follow the name convention + if(!jmeJarFiles.contains(file)) { + jmeJarFiles.add(file) + } } else if(!isSourceOrJavadoc(file.name)) { //collect external jars externalJarFiles.add(file) @@ -583,7 +610,7 @@ file('.').eachDir{ buildSdk.inputs.dir it } } -buildSdk.outputs.dir "build" +//buildSdk.outputs.dir "build" task run(dependsOn: buildSdk) { doLast { @@ -609,14 +636,14 @@ task cleanSdk() { task extractPlatformIndependent(type: Copy) { from zipTree('dist/jmonkeyplatform.zip') into "dist/temp/" - + exclude("jmonkeyplatform/etc/jmonkeyplatform.conf") } task patchPlatformIndependent(type: Copy, dependsOn: extractPlatformIndependent) { from zipTree('dist/jmonkeyplatform.zip') into "dist/temp/" - + include("jmonkeyplatform/etc/jmonkeyplatform.conf") filter { String line -> @@ -641,7 +668,7 @@ task fixPlatformIndependent(dependsOn: patchPlatformIndependent, type: Zip) { } wrapper { - gradleVersion = '7.5.1' + gradleVersion = '8.6' } //jar.dependsOn(buildSdk) diff --git a/build.xml b/build.xml index 656267f59..1afd2bea0 100644 --- a/build.xml +++ b/build.xml @@ -220,7 +220,7 @@Using Models and Scenes with jME3
To use 3D models in a jME3 application:-
-
Using Models and Scenes with jME3
Creating Models and Scenes
-
-
-
-
\ No newline at end of file
+
diff --git a/jme3-documentation/src/com/jme3/gde/docs/jme3/external/blender.html b/jme3-documentation/src/com/jme3/gde/docs/jme3/external/blender.html
deleted file mode 100644
index 0390f44f7..000000000
--- a/jme3-documentation/src/com/jme3/gde/docs/jme3/external/blender.html
+++ /dev/null
@@ -1,610 +0,0 @@
-
--To create 3D models and scenes, you need a 3D Mesh Editor such as , with an OgreXML Exporter plugin. -
- --Tip: Learn how to create for more complex models, it looks more professional. -
- --3D model editors are third-party products, so please consult their documentation for instructions how to use them. Here is an example workflow for Blender users: -
--
-
-To export your models as Ogre XML meshes with materials: -
--
-
You can now use the jMonkeyEngine SDK to load and view models. You can create scenes from them and write code that loads them into your application. @@ -82,4 +35,4 @@
Creating Models and Scenes
Creating assets in Blender3D
-
-
-
-
--This section discusses how to create and import models from Blender3D (2.62+, see bottom of page for Blender 2.49 and before) to jME3. Furthermore it explains how you can create various typical game-related assets like normal maps of high-poly models and baked lighting maps. -
- -Asset Management
-
-
-
-
--For the managing of assets in general, be sure to read the Asset Pipeline Documentation. It contains vital information on how to manage your asset files. -
- -Creating Models
-
-
-
-
--Game-compatible models are models that basically only consist of a mesh and UV-mapped textures, in some cases animations. All other material parameters or effects (like particles etc.) can not be expected to be transferred properly and probably would not translate to live rendering very well anyway. -
- -UV Mapped Textures
-
-
-
-
--To successfully import a texture, the texture has to be UV-mapped to the model. Heres how to assign diffuse, normal and specular maps: -
--
-
-Its important to note that each used texture will create one separate geometry. So its best to either combine the UV maps or use a premade atlas with different texture types from the start and then map the uv coords of the models to the atlas instead of painting on the texture. This works best for large models like cities and space ships. -
- -Animations
-
-
-
-
--Animations for jME3 have to be bone animations, simple object movement is supported by the blender importer, mesh deformation or other forms of animation are not supported. -
- --To create an animation from scratch do the following: -
--
-
Model Checklist
-
-
-
-
--Sometimes you do not create the model yourself and often times models from the web are not really made for OpenGL live rendering or not completely compatible with the bone system in jME. -
- --To export an animated model in Blender make sure the following conditions are met: -
--
-
-You can use SkeletonDebugger to show the skeleton on your game in order to check if the mesh and the skeleton are loaded correctly: -
- final Material soldier2Mat = assetManager.loadMaterial("Materials/soldier2/soldier2.j3m");
- final Spatial soldier2 = assetManager.loadModel("Models/soldier2/soldier2.j3o");
- TangentBinormalGenerator.generate(soldier2);
- soldier2.setMaterial(soldier2Mat);
-
- final Node soldier2Node = new Node("Soldier2 Node");
-
- soldier2Node.attachChild(soldier2);
- rootNode.attachChild(soldier2Node);
-
- final AnimControl control = soldier2.getControl(AnimControl.class);
- control.addListener(this);
- final AnimChanel channel = control.createChannel();
-
- final SkeletonDebugger skeletonDebug = new SkeletonDebugger("skeleton", control.getSkeleton());
- final Material mat = new Material(assetManager, "Common/MatDefs/Misc/Unshaded.j3md");
- mat.setColor("Color", ColorRGBA.Green);
- mat.getAdditionalRenderState().setDepthTest(false);
- skeletonDebug.setMaterial(mat);
- soldier2Node.attachChild(skeletonDebug);
--
-
-Also check out these videos and resources: -
--
-
NormalMap baking
-
-
-
-
--Models for live rendering should have a low polygon count. To increase the perceived detail of a model normal maps are commonly used in games. This tutorial will show how to create a normalmap from a highpoly version of your model that you can apply to a lowpoly version of the model in your game. -
- -Blender modeling lowPoly & highPoly
-
-
-
--
-
-
Remember! The actual preview affects the baking output and mesh export!
-
-
-
--
Be careful: The steps above lead to terrible normal maps - use this procedure instead:
-
-
--
-
-
Be careful: in the Outliner the camera symbol (Restrict Render) must be on!
-
-
-
-Fixing the normal colors in Blender
-
-
-
-
--Blender has its own normal colors standard. We need to fix the colors to prepare the normalmap for using it with the JME Lighting Material. -
- --To do this, go to the Blender Node Window -
--
-
-
-
-
-
LightMap baking
-
-
-
-
--The goal of this tutorial is to explain briefly how to bake light map in blender with a separate set of texture coordinates and then export a model using this map in jME3. -
- -Blender modeling + texturing
-
-
-
--
-
-
-
Importing the model in the SDK and creating the appropriate material
-
-
-
-
--Once this is done, export your model with the ogre exporter (or import it directly via the blend importer), and turn it into J3o with the SDK. -
--
-
-The blend file, the ogre xml files and the textures can be found in the download section of the google code repo -
- -- -
- -Modelling racing tracks and cars
-
-
-
-
--Follow the link below to a pdf tutorial by rhymez where I guide you to modelling a car and importing it to the jMonkeyengine correctly and edit it in the vehicle editor.Plus how to model a simple racing track. - -
- -Optimizing Models for 3D games
-
-
-
-
--Follow the link below to a pdf tutorial by rhymez where I guide you on how you can optimize your models for faster rendering. - -
- -SkyBox baking
-
-
-
-
-
-There are several ways to create static images to use for a sky in your game. This will describe the concepts used in blender and create an ugly sky 
Check the links below for other ways and prettier skies.
-
-A sky box is a texture mapped cube, it can also, loosely, be called en EnvMap or a CubeMap. The camera is inside the cube and the clever thing that jME does is to draw the sky so it is always behind whatever else is in your scene. Imagine the monkey is the camera in the picture. -
--
-
-But a real sky is not a box around our heads, it is more like a sphere. So if we put any old image in the sky it will look strange and might even look like a box. This is not what we want. The trick is to distort the image so that it will look like a sphere even if it in fact is a picture pasted on a box. Luckily blender can do that tricky distortion for us. -
- --The screenshots are from Blender 2.63 but the equivalent operations have been in blender for years so with minor tweaks should work for almost any version. -
- --So let's get started -
--
-
-
The SDK also contains an image editor, right-click the image and select “edit image” to open it.
-
-
--
-
-If you want to do it from code, here is an example: -
-public void simpleInitApp() {
-
- Texture westTex = assetManager.loadTexture("Textures/west.png");
- Texture eastTex = assetManager.loadTexture("Textures/east.png");
- Texture northTex = assetManager.loadTexture("Textures/north.png");
- Texture southTex = assetManager.loadTexture("Textures/south.png");
- Texture upTex = assetManager.loadTexture("Textures/top.png");
- Texture downTex = assetManager.loadTexture("Textures/bottom.png");
-
- final Vector3f normalScale = new Vector3f(-1, 1, 1);
- Spatial skySpatial = SkyFactory.createSky(
- assetManager,
- westTex,
- eastTex,
- northTex,
- southTex,
- upTex,
- downTex,
- normalScale);
- rootNode.attachChild(skySpatial);
-}
-
--
This example uses a strange normalScale, this is to flip the image on the X-axis and might not be needed in your case. Hint: the texture is applied on the outside of the cube but we are inside so what do we see?
-
-
-
-Further reading
-
-
-
-
\ No newline at end of file
diff --git a/jme3-documentation/src/com/jme3/gde/docs/sdk/3ds_to_blender_to_jmp.html b/jme3-documentation/src/com/jme3/gde/docs/sdk/3ds_to_blender_to_jmp.html
deleted file mode 100644
index 4d167af74..000000000
--- a/jme3-documentation/src/com/jme3/gde/docs/sdk/3ds_to_blender_to_jmp.html
+++ /dev/null
@@ -1,65 +0,0 @@
-
--
-
Using Blender as a Intermediator Between 3dMax and the jMonkeyEngine SDK
-
-
-
-
--The jMonkeyEngine SDK supports .blend files and can convert them to jMonkeyEngine's .j3o format. This means you can use Blender to convert, for example, a 3dMax file to .j3o format. -
- -Importing the .3ds file to Blender
-
-
-
-
--I'm using the blender 2.59 at this tutorial, but if you blender 2.49b, no problem ;). -After you saved your .3ds file in 3dmax, open the blender, delete the default cube, -and import your .3ds file via File—→Import—–>3D Studio. -
- -
-
-
Saving the .blend file
-
-
-
-
--Now save your .blend file so you can load it into the jMonkeyEngine SDK. -
- -
-
-
Importing the .blend file to the SDK by using the ModelImporter and BlenderSupport plugins
-
-
-
-
--Click on Import Model button and then click on Open Model button to open the .blend file. Click next, select the checkbox to import a copy from .blend file, and click finish. -
- -
-
-
Edit your model in SceneComposer and "VOILA"
-
-
-
-
-
\ No newline at end of file
diff --git a/jme3-documentation/src/com/jme3/gde/docs/sdk/blender.html b/jme3-documentation/src/com/jme3/gde/docs/sdk/blender.html
deleted file mode 100644
index 4e7236702..000000000
--- a/jme3-documentation/src/com/jme3/gde/docs/sdk/blender.html
+++ /dev/null
@@ -1,362 +0,0 @@
-
--As you can see, the .blend model was automatically converted to .j3o binary format. Now, you are able to edit it in SceneComposer ;D. -
- -
-
-
Blender importer for jMonkeyEngine 3
-
-
-
-
-Introduction
-
-
-
-
--Importing models to any game engine is as important as using them. The quality of the models depends on the abilities of the people who create it and on the tools they use. -Blender is one of the best free tools for creating 3D enviroments. Its high amount of features attract many model designers. -So far jMonkeyEngine used Ogre mesh files to import 3D data. These files were created by the python script that exported data from blender. -It was important to have always the lates version of the script that is compatible with the version of blender and to use it before importing data to jme. -Now we have an opportunity to simplify the import process by loading data directly from blender binary files: *.blend. -
- --
Before you try to import models, make sure you created them properly.
-
-
-
-Usage
-
-
-
-
--To use it in your game or the SDK you should follow the standard asset loading instructions. -By default a BlenderModelLoader is registered with your assetManager to load blend files. This means you can load and convert .blend model files to .j3o format, just like any other supported model format. -
- -Currently supported features
-
-
-
--
-
Planned features.
-
-
-
--
-
Known bugs/problems.
-
-
-
--
-
Using BlenderLoader instead of BlenderModelLoader
-
-
-
-
--You have two loaders available. -
--
-
public static class LoadingResults extends Spatial {
- /** Bitwise mask of features that are to be loaded. */
- private final int featuresToLoad;
- /** The scenes from the file. */
- private List<Node> scenes;
- /** Objects from all scenes. */
- private List<Node> objects;
- /** Materials from all objects. */
- private List<Material> materials;
- /** Textures from all objects. */
- private List<Texture> textures;
- /** Animations of all objects. */
- private List<AnimData> animations;
- /** All cameras from the file. */
- private List<Camera> cameras;
- /** All lights from the file. */
- private List<Light> lights;
- /** Access Methods goes here. */
-}
--
-
-To register the model do the following: -
-assetManager.registerLoader(BlenderLoader.class, "blend");- -
-or -
-assetManager.registerLoader(BlenderModelLoader.class, "blend");-
-
-
-You can use com.jme3.asset.BlenderKey for that. -The simplest use is to create the key with the asset's name. -It has many differens settings descibing the blender file more precisely, but all of them have default values so you do not need to worry about it at the beggining. -You can use ModelKey as well. This will give the same result as using default BlenderKey. -
- -How does it work?
-
-
-
-
-
-
-
-
--BlenderLoader (as well as BlenderModelLoader) is looking for all kinds of known assets to load. -It's primary use is of course to load the models withon the files. -Each blender object is imported as scene Node. The node should have applied textures and materials as well. -If you define animations in your BlenderKey the animations will as well be imported and attached to the model. -
- --Here is the list of how blender features are mapped into jme. -
-| Blender | jMonkeyEngine3 | Note | -
|---|---|---|
| Scene | Node | - |
| Object | Node | - |
| Mesh | List<Geometry> | One mesh can have several materials so that is why a list is needed here. | -
| Lamp | Light | - |
| Camera | Camera | - |
| Material | Material | - |
| Texture | Texture | - |
| Curve | Node | Node with Curve as its mesh | -
| Surface | Node | The surface is transformed to the proper mesh | -
-Using BlenderLoader can allow you to use blend file as your local assets repository. -You can store your textures, materials or meshes there and simply import it when needed. -Currently blender 2.49 and 2.5+ are supported (only the stable versions). -Probably versions before 2.49 will work pretty well too, but I never checked that :) -
- -Notes
-
-
-
- -
-
-
\ No newline at end of file
diff --git a/jme3-glsl-highlighter/nbproject/project.properties b/jme3-glsl-highlighter/nbproject/project.properties
index e2f681ea2..e379e8913 100644
--- a/jme3-glsl-highlighter/nbproject/project.properties
+++ b/jme3-glsl-highlighter/nbproject/project.properties
@@ -1,3 +1,3 @@
-javac.source=17
+javac.source=21
javac.compilerargs=-Xlint -Xlint:-serial
project.license=jme license
diff --git a/jme3-glsl-highlighter/nbproject/project.xml b/jme3-glsl-highlighter/nbproject/project.xml
index 6cee79cf8..52b8cf079 100644
--- a/jme3-glsl-highlighter/nbproject/project.xml
+++ b/jme3-glsl-highlighter/nbproject/project.xml
@@ -50,6 +50,15 @@
-I know that the current version of loader is not yet fully functional, but belive me – Blender is a very large issue ;) -Hope I will meet your expectations. -
- --Be mindful of the result model vertices amount. The best results are achieved when the model is smooth and has no texture. Then the vertex amount is equal to the vertex amount in blender. If the model is not smooth or has a generated texture applied then the amount of vertices is 3 times larger than mesh's triangles amount. If a 2d texture is applied with UV mapping then the vertex count will vary depending on how much the UV map is fragmented. -
- --When using polygon meshes in blender 2.5 and newer, better add and apply the triangulation modifier (if available in your version) or save the file with convertion from polygons to triangles. -Even though the importer supports loading of polygons as the mesh faces, if your face isn't convex, the results might contain errors. -
- --Not all modifiers are supported. If your model has modifiers and looks not the way you want in the jme scene - try to apply them and load again. -
- --Cheers, -Marcin Roguski (Kaelthas) -
- --P.S. -This text might be edited in a meantime if I forgot about something ;) -
-- -
-See also: -
--
-