Talk:Blender 3D: Noob to Pro/An aMAZEing game engine tutorial

When I hit "P" everything disappears until I hit ESC again, it does not seem to matter if I am in perspective or orthographic mode. I made sure I have a lamp but that did not help.

When I make a cone it keeps linking to the grid and they are considered the same object. Can anyone tell me why they do this?
 * ANSWER: You have to create the Cone in Object mode. If you create a mesh while in edit mode, you are just adding another mesh to that object. The cone needs to be its own object in order to be distinguishable from the grid.

This is just a question: This Engine can be fully programmed? Or we only can use functions that are already in Blender?

I'm stucked with a strange behavior (at least, I find it so). When I start the game, I can see only the big cube (from inside). However, when I render the scene, I can see also the maze and the "hero". I'm pretty sure that I have selected both layers. Another strange thing: this only happens if I press PKEY while in perspective mode. In ortographic mode, I can see the maze and the hero.
 * ANSWER: This is because you cannot be "inside" an object with orthographic view, whereas in perspective view, you can. Cameras render in perspective view by default.

I added the sensors and actuators exactly the same as it shows, but for some reason my cone turns when i press A and D, and nothing at all when i press W and S. Also, when i make the cone turn and press W or S it wobbles and starts turning. How can i make it work?
 * ANSWER: A and D are supposed to make the character rotate, not strafe. To make them MOVE left and right, and not rotate, change the force from Torque to Force. As for the force controls not working, the cone used in the tutorial's local Y is equivalent to your cone's local Z from the viewing point. Thus, to move forwards and backward, fill in the force settings as you normally would but in the third/right integer box instead of the second/middle integer box. Also here noting that I added the multiple-goal win condition information, but I forgot to sign in first, so it's uncredited. Loki Clock (talk) 16:56, 1 February 2008 (UTC)

I copied all the details in the Cone logic picture (sensor=keyboard, etc.) but when I pressed PKEY, the cone just uncontrollably stumble to the ledge in front of (before I even pressed a key) it that pressing a control key will topple it to the abyss, and stop on the ledge. How I can fix this? Any help will be appreciated. 202.153.251.2 (talk) 22:42, 31 March 2008 (UTC)
 * ANSWER: Solved the problem myself. Move the gravity center to the cone. 202.153.251.2 (talk) 00:36, 6 April 2008 (UTC)

Whenever i test the scene, the cone bounces off the maze, how do i fix this?

In Blender 2.49 there's no button for Dynamic, it now appears in the drop down list along with Rigid Body. How do I select both, or do I even need to?

Testing

 * I had different problem when following this part of the tutorial. I have done the tutorial several times to make sure I haven't skipped a step.  Anyway when I got to test the maze/game my "cone character" keeps floating off the map.  ****Do you know of any reason this may happen or how to corret it?****

Barrier
the barrier cubes keep repelling away from one another, how do I fix this? when I make the radius smaller the bricks sort of merge together.

Also a big problem I had was that the restarting cube wouldn't work for otherlevels, I found that you solve this by changing all materials on all your protagonists to coneMat


 * About the barrier cube, do you have the bounds set to box? If you don't set the bounds, the default shape is sphere, which poses problems for emulating cubes.  About the new levels: I forgot that making a full copy also makes a copy of materials, etc rather than just using the old datablock (i.e. A material named coneMat would, in a full copy, be replaced with one called coneMat.001).  So this is an annoying problem that can be circumvented.  However, the only way I can think of right now is to just make an empty new scene, then select everything and CTRL LKEY and select the new scene.  This will link everything to the other scene, basically duplicating the objects to the next level.  You have to UKEY 2 to make these objects actually on the scene, rather than just linked.  This should work, and materials will be shared between levels.--Malaz (talk) 18:56, 26 March 2008 (UTC)

All the obstacle blocks flew off before I even touched them. It's like someone put a dynamite there. Any help? 202.153.251.2 (talk) 01:24, 6 April 2008 (UTC)


 * When this happens, it means that the objects are intersecting--you made the objects inside each other, or with their boundaries touching. Your roblem is basically the same as the previous, except to a greater degree.  Your objects may be too large, may not be box-boundaries, or might have been created intersecting.  See the previous answer; it should fix your problems.--Malaz (talk) 15:24, 9 April 2008 (UTC)

Raised levels
You really don't go into how to make those, if you were planning to then that would help because when I try to raise a section that is touching a corner the corner it touches rises in a weird way.

Levels and multiple goals
I was wondering how I would force the player to get one object before the other one...

Just my note about this section: * Sensor: Message, goalget * Controller: And * Actuator: Property, Add, wincon, -1

* Sensor: Property, Equal, wincon, 0 * Controller: And * Actuator: Scene, Set Scene, Scene.001 (or whatever you named your level 2)

As I understood the tutorial, these would be placed in the cube surrounding the maze. It SHOULD be put in the goal box.

Adding Scene:

Whenever I add a new scene my first scene is all black when I play the game. At first I thought I was messing something up with the logics page (I was attempting the new level part of the tutorial), but just simply adding a scene creates the problem. What am I doing wrong?

Mist
Erm, I think I'm also having problems with the bit that has been crossed-out in the tutorial... My game engine isn't rendering the background, not to mention the mist, the "use blender materials" option was checked and the Blender version is 2.46. Any help would be appreciated. 129.67.86.247 (talk) 16:02, 8 June 2008 (UTC) --Sorry, problem solved... Reminded the importance of ALT Z...

I added the mist and my game has stopped working. I haven't added any new objects, just changed the mist settings and now I can't see anything when I start the game. I am using 2.48a and I have made sure I am in texture mode and perspective mode. Turning the mist off did not help. The only other thing I did was apply a material to the maze. (update) This actually seems to be a problem with the display, if I close Blender and re-open the file it works again. I have an ATI card

Maze moving away from camera
Whenever i go to test the game the controls work fine but the maze and character keeps moving away from the camera until they disappear

If it is going down, it might be because you made the maze an "actor" in the logic, so it is bing pulled down by gravity. --The Fist

Barrier Fall Through
The blocks in my barriers keep falling through the maze. The logic settings are actor, dynamic, rigid body, mass .5, bounds, box, compound (selected by default). I'm in blender version 2.46. For the record, I did not use the exact size settings in the tutorial but they are similar sized. Could this be a problem. Does anyone know how to fix this? Any help would be appreciated.

CAMERA NOT FOLLOWING
The camera does not follow the protagonist when I parent it to the protagonist and follow all of the requirments

Make sure you set the camera to parent of the protagonist(ctrl+P). you can do this by click on the camera then shift+clicking on the prtagonist then pressing (ctrl+P)

i have done those steps but nothing seems to work, any idea why this might be happening?

Missing Step
I'm working in 2.49b, and I found that if I followed the tutorial to the letter, my cone would collide with every edge in the grid that I made the maze out of. To fix this, I just has to turn on Convex Hull Bounds on the maze just like you do on the cone. I wasn't sure if this was a problem with just my version or if I made some mistake along the way, but I figured I'd post it in the discussion in case someone else had the same problem. Edit: I tested this again, and the cone wouldn't fall in between the maze paths; it would only fall when it went off the edge of the entire object that made up the maze. I fixed this by changing the Bounds from Convex Hull you Triangle Mesh. The tutorial should really have this step, but I could be wrong again. I don't want to add the step in myself without someone else's feedback. Jdwolfears (talk) 21:21, 24 May 2010 (UTC)

And I WAS wrong again. I have the same collision issues that I started with. Maybe someone with a bit more experience can give a better fix? This tutorial should really be updated to work with the most current stable version. Jdwolfears (talk) 15:58, 25 May 2010 (UTC)

Friction
Hi, I've followed every step of this tutorial. Unfortunately, the movement of the cone are very difficul to make, because he hasn't any friction on the maze. I don't know how to explain it... When I press "W" the cone go like the maze is made of ice. It takes much spaces to stop, making game frustating.

How can I fix it?

Shape falls through maze
I went through this tutorial as best I could, but when I push "P", the cube falls through the maze. Could it be because I'm using Blender 2.37? Any help would be appreciated.--Thekmc (talk) 16:41, 27 November 2010 (UTC)

PDF
I think books should be available in PDF format for download.

Tutorial Updates
Someone can update the Tutorial or I'll rewrite the page by myself.Ichiro-kun22 (discuss • contribs) 10:18, 30 October 2015 (UTC)