With people testing 2.5 for the GE, I thought it might be interesting to start a thread relating to bugs that people have found, but aren’t sure if they are reproducable or not ( the focus of Durian will of course be on non-GE development, but if bugs are easy to fix then I’m sure they’ll get sorted out in a timely fashion ).
Here are a few game related ones that we’ve found ( we have a work placement student here for a week, and I’m showing him the ropes of Blender and GE using 2.5 )
When zooming in on the logic panels, the Move Up and Move Down icons don’t scroll well ( it looks like a character is used, rather than an icon, and it doesn’t scale )
In some panels ( eg Motion Actuator ), it’s near impossible to see the non-zero values, except if you REALLY zoom in.
When you enable Display Debug Properties, nothing appears on-screen during game play ( should be showing the properties with the i selected )
If you add in a coin pickup ( add a cylinder, rotate it 90 degrees ), now try to scale the cylinder to be a flat coin using the scale gizmo. The axis do not correspond to the visual scale, as if the 90 degree rotation is ignored.
Mouse sensor issue - add a box, set up a Mouse sensor ( left button ) into a Movement Actuator ( move forward ). It now seems impossible to set up a scenario where you hold down the mouse button and the box moves forward, and releasing it stops movement ( this works if you use a Keyboard Actuator ( space key ) ).
These are just a few, but if they can be confirmed, I can report them to the bug-base. Feel free to add your own - if we can report as many of these small issues now, then Blender 2.5 will be in a better shape to use for the up-coming GE competition.
This was a bug in a 2.49, but may still be applicable.
-When setting the alpha IPO to play using the ‘obcolor’ option, if you play the game sometimes you’ll find the alpha value in the material options resets itself for no reason, this is not only seen when playing the game, the slider really does go back to 1 sometimes.
The layout of the GUI for the buttons menu, logic bricks/physics settings messes up, re-scales etc.
I also have problems with the GUI. For example, I can not scoll down to see all the logic bricks on an object when the object has more than 30 or 40 logic bricks in a row.
Another problem is that the GUI lags even on a powerful computer. For example, I used to be able to edit large amounts of logic brick in the GUI smoothly on an intel integrated graphics chip. Now the same amount of logic bricks lag even when using an Nvidia GTX 260M graphic card. =/
I don’t think you’re supposed to use 2.5 for BGE work until it is ready and stable. But it would be nice to get the GUI problems fixed, I have a problem myself with the modifier panels being speghettified if I try to scroll down to see more in horizontal mode.
Erwin, I would assume you would take charge in making sure these things are fixed due to your long history with Blender and working on it before it became open source?
little offtopic: will first beta of 2.5 have bge back as we know it in 2.49b?
if yes will be there new bge python API present?
(I’m asking cause want know on which version build game for a 2010 bge contest)
Mouse sensor issue - add a box, set up a Mouse sensor ( left button ) into a Movement Actuator ( move forward ). It now seems impossible to set up a scenario where you hold down the mouse button and the box moves forward, and releasing it stops movement ( this works if you use a Keyboard Actuator ( space key ) ).
There’s a bunch of problems with mouse related logic in general in 2.5, the cursor doesn’t disappear by default, mouselook scripts/setups won’t work ect… no one is going to make intuitive games in 2.5 period if the mouse issues aren’t fixed
Well I do hope we can get another nice big round of bugfixes for the 2.5 GE from Ben2610 then, he did bring the engine out of the buggy state it was in before 2.46. I wonder if he’ll have time for that since he’s working on the new IK stuff.
> 3) I am not sure why it isn’t showing up your comp, it is working fine for me…
The debug properties appear if the Show Framerate etc is selected ( the Show Debug Properties can be on or off at this stage ). If Show Framerate is deselected, then no debug properties are shown here.
CyborDragon wrote…
> That’s not a BGE specific bug, it’s a general bug in Blender 2.5, people working on scenes for animation or rendering see this too.
Yep, but naming objects is an important feature for making games in GE ( if you have to refer to an object eg for Adding, or if you want to keep your scene tidy ) - so not GE specific, but an important one to fix.
You should try PM’ing Ben2610 or contacting him on the developer mailing list, if you need to know his real name its Benoit Bolsee, I wouldn’t worry about him not responding since his last commit was only 2 days ago.