Game Engine - multiple buttons to change scene #44486

Closed
opened 2015-04-22 18:34:26 +02:00 by Jeremy Baker · 8 comments

System Information
Windows 7, Intel Core i5-2450M CPU 2.50ghz

Blender Version
Broken: 2.74

I was making a small dummy game. In the main menu I wanted several buttons, each leading to a new scene in blender. The scenes were: menu, level one, how to, and credits. I ran into several problems and remade a smaller game to bug test where clicking on one of two cubes takes you to either scene two or scene three. The same problem happened.
Detailed below is the smaller game with two cubes. Sorry if this isn't a bug. This is my first report.
Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

  1. set to game engine
  2. Duplicate and rename scenes with full copy.
  3. Set Shading to GLSL. (I've also tried it with multitextured)
  4. Add a new cube in the first scene. Add text above each cube to label the cubes. One cube should lead two scene two and one to scene three. Label scene two with text. Label scene three with text.
  5. Go to logic editor. In scene one with the two cubes, with one text selected, add an 'always' sensor, hook to an 'and' controller, and hook to a 'mouse' actuator. (this should allow the mouse to always be seen within the game window.)
  6. select the cube you want to go to scene two. in logic editor add Mouse sensor with left click, and controller, then a scene actuator with set scene to go to scene two. Repeat with second cube going to scene three.
  7. Test within 3d view by hitting 'p'. Both cubes go to scene three. Exported as game engine runtime. Names bug game.exe
  8. Run bug game.exe. Both cubes go to scene three.
**System Information** Windows 7, Intel Core i5-2450M CPU 2.50ghz **Blender Version** Broken: 2.74 I was making a small dummy game. In the main menu I wanted several buttons, each leading to a new scene in blender. The scenes were: menu, level one, how to, and credits. I ran into several problems and remade a smaller game to bug test where clicking on one of two cubes takes you to either scene two or scene three. The same problem happened. Detailed below is the smaller game with two cubes. Sorry if this isn't a bug. This is my first report. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps 1. set to game engine 2. Duplicate and rename scenes with full copy. 3. Set Shading to GLSL. (I've also tried it with multitextured) 4. Add a new cube in the first scene. Add text above each cube to label the cubes. One cube should lead two scene two and one to scene three. Label scene two with text. Label scene three with text. 5. Go to logic editor. In scene one with the two cubes, with one text selected, add an 'always' sensor, hook to an 'and' controller, and hook to a 'mouse' actuator. (this should allow the mouse to always be seen within the game window.) 6. select the cube you want to go to scene two. in logic editor add Mouse sensor with left click, and controller, then a scene actuator with set scene to go to scene two. Repeat with second cube going to scene three. 7. Test within 3d view by hitting 'p'. Both cubes go to scene three. Exported as game engine runtime. Names bug game.exe 8. Run bug game.exe. Both cubes go to scene three.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @JeremyBaker

Added subscriber: @JeremyBaker
Aaron Carlisle self-assigned this 2015-04-22 19:45:48 +02:00
Aaron Carlisle removed their assignment 2015-04-22 19:46:08 +02:00
Member

Added subscriber: @JorgeBernalMartinez

Added subscriber: @JorgeBernalMartinez
Member

Hi,

I can not reproduce the bug as it is working fine for me. Always is better to attach a blend file to be sure that the steps to reproduce the bugare followed well.

I upload an blend example with your description set_scene.blend.

Hi, I can not reproduce the bug as it is working fine for me. Always is better to attach a blend file to be sure that the steps to reproduce the bugare followed well. I upload an blend example with your description [set_scene.blend](https://archive.blender.org/developer/F165877/set_scene.blend).
Author

Sorry, was in a hurry this morning. I'll try to add the dummy scene I made to retest this. Thanks.

Sorry, was in a hurry this morning. I'll try to add the dummy scene I made to retest this. Thanks.
Author

Hopefully this will show it. This is a third time it's happened.stupid_game_demo.blend

Hopefully this will show it. This is a third time it's happened.[stupid_game_demo.blend](https://archive.blender.org/developer/F165976/stupid_game_demo.blend)
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Jorge Bernal self-assigned this 2015-04-23 06:50:18 +02:00
Member

Hi,

I checked your blend but this is not a bug I guess is a fail in your game logic.
I mean, you have set that when you push left mouse click you make the following actions simultaneously: to change to scene 2 and to change to scene 3. Therefore, to fix the logic you should differenciate both actions.
For example, if you see my uploaded blend set_scene.blend you will see that adittionally to left mouse click I use a mouse over sensor to diferenciate if I am clicking over "go to scene 2" or "go to scene 3" objects.

I'm going to close this report as it is not a bug (see above reasons).
Thanks for reporting.

Hi, I checked your blend but this is not a bug I guess is a fail in your game logic. I mean, you have set that when you push left mouse click you make the following actions simultaneously: to change to scene 2 and to change to scene 3. Therefore, to fix the logic you should differenciate both actions. For example, if you see my uploaded blend [set_scene.blend](https://archive.blender.org/developer/F165877/set_scene.blend) you will see that adittionally to left mouse click I use a mouse over sensor to diferenciate if I am clicking over "go to scene 2" or "go to scene 3" objects. I'm going to close this report as it is not a bug (see above reasons). Thanks for reporting.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser Project (Legacy)
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#44486
No description provided.