python addobject #40097

New Issue

castanier · 2014-05-08T16:53:20+02:00

castanier commented

2014-05-08 16:53:20 +02:00

System Information
windows 7 nvidida 560 ti

Blender Version
2.70 a

function: scene.addObject (object, other, time = 0) does not create object
and produces no error console

code:

from bge import logic as gl

rainObj = gl.getCurrentController().owner

new = gl.getCurrentScene().addObject("rain",rainObj,70)
new.position = [0.0, 0.1, 0.6]

**System Information** windows 7 nvidida 560 ti **Blender Version** 2.70 a function: scene.addObject (object, other, time = 0) does not create object and produces no error console code: from bge import logic as gl rainObj = gl.getCurrentController().owner new = gl.getCurrentScene().addObject("rain",rainObj,70) new.position = [0.0, 0.1, 0.6]

castanier commented

2014-05-08 16:53:20 +02:00

Changed status to: 'Open'

castanier commented

2014-05-08 16:53:20 +02:00

Added subscriber: @moaaa_user

Mitchell Stokes commented

2014-05-09 01:28:54 +02:00

Added subscriber: @Moguri

Mitchell Stokes commented

2014-05-09 01:28:54 +02:00

I cannot reproduce the bug (KX_Scene.addObject() appears to be working fine). Please supply a blendfile demonstrating the problem. I've attached the file I'm using, which works correctly for me.

addobject_test.blend

I cannot reproduce the bug (KX_Scene.addObject() appears to be working fine). Please supply a blendfile demonstrating the problem. I've attached the file I'm using, which works correctly for me. [addobject_test.blend](https://archive.blender.org/developer/F87952/addobject_test.blend)

castanier commented

2014-05-09 09:23:42 +02:00

I'll put the piece of code that I have always used

solarlune commented

2014-05-09 17:20:20 +02:00

Added subscriber: @solarlune

solarlune commented

2014-05-09 17:20:20 +02:00

Maybe you could provide a blend file of your own that provides the problem, as the code itself doesn't do much.

castanier commented

2014-05-10 09:18:14 +02:00

the code is in exemple blend file look my last comment

solarlune commented

2014-05-10 15:25:57 +02:00

Ah, I see. Thank you.

However, this isn't a bug at all - it's just a user error.

The rain object in your example was set to Billboard, and you had the front of the plane facing -X, The front face should face +X. Since the material had backface culling enabled and Billboard was on, Blender was turning the back (invisible) face to the camera (which it should have been doing).

Solution: Rotate the rain object plane 180 degrees in edit mode, or disable back-face culling in the material options.

Something that could have helped you see what was going on:

You could enable static physics on the rain objects and turn on physics visualization, or attach a Python controller and print out a statement to ensure they're being created.

Please ask for help on the BlenderArtists forums to ensure everything is working correctly on your end before reporting possible bugs to help save resources in the future.

Ah, I see. Thank you. However, this isn't a bug at all - it's just a user error. The rain object in your example was set to Billboard, and you had the front of the plane facing -X, The front face should face +X. Since the material had backface culling enabled and Billboard was on, Blender was turning the back (invisible) face to the camera (which it should have been doing). Solution: Rotate the rain object plane 180 degrees in edit mode, or disable back-face culling in the material options. Something that could have helped you see what was going on: You could enable static physics on the rain objects and turn on physics visualization, or attach a Python controller and print out a statement to ensure they're being created. Please ask for help on the BlenderArtists forums to ensure everything is working correctly on your end before reporting possible bugs to help save resources in the future.

castanier commented

2014-05-11 00:17:18 +02:00

sorry

as file work perfectly in the three latest version of blender.

I can not think of anything other than a bug

sorry as file work perfectly in the three latest version of blender. I can not think of anything other than a bug

solarlune commented

2014-05-11 00:24:39 +02:00

I believe the requirement for Billboard and Halo was changed between those versions from the face needing to face -X to +X intentionally. Anyway, no problem. I take it this bug can be closed?

Mitchell Stokes commented

2014-05-11 05:42:20 +02:00

What version was it first flipped in? 2.70? I'm not seeing anything in the release notes; it would be good if these kind of changes were documented.

solarlune commented

2014-05-11 06:48:17 +02:00

@Moguri - I'm not sure. I think I recall it being a patch from vitorbalbio that was committed somewhat recently (in the past few months), but I'm only able to turn up a patch from October that was committed but then reverted. If it were committed finally in October, then that would be 2.69, I think.

@Moguri - I'm not sure. I think I recall it being a patch from vitorbalbio that was committed somewhat recently (in the past few months), but I'm only able to turn up a [patch from October that was committed but then reverted](http://lists.blender.org/pipermail/bf-blender-cvs/2013-October/059717.html). If it were committed finally in October, then that would be 2.69, I think.

Jacob Merrill commented

2014-05-14 05:24:45 +02:00

Added subscriber: @JacobMerrill-1

Jacob Merrill commented

2014-05-14 05:24:45 +02:00

Yeah, it was flipped in 2.7 (I had to flip normals on all halo objects in my game)

Mitchell Stokes commented

2014-05-16 04:47:44 +02:00

Added subscribers: @ideasman42, @brecht

Mitchell Stokes commented

2014-05-16 04:47:44 +02:00

Campbell, Brecht, do either of you know what happened here (why are our halos flipped now)?

Bastien Montagne commented

2014-05-23 09:00:57 +02:00

Added subscriber: @mont29

Jorge Bernal commented

2015-05-17 02:16:00 +02:00

Added subscriber: @JorgeBernalMartinez

Jorge Bernal commented

2015-05-17 02:16:00 +02:00

Can I close this report?
after 5 releases, It doesn't seem a good idea flip halo normals breaking compatibility again. Then, I propose leave current behaviour as it is and to close the report.

Can I close this report? after 5 releases, It doesn't seem a good idea flip halo normals breaking compatibility again. Then, I propose leave current behaviour as it is and to close the report.

Porteries Tristan commented

2015-05-23 17:02:44 +02:00

Added subscriber: @panzergame

Porteries Tristan commented

2015-05-23 17:02:44 +02:00

Changed status from 'Open' to: 'Archived'

Porteries Tristan closed this issue

2015-05-23 17:02:44 +02:00

Porteries Tristan self-assigned this 2015-05-23 17:02:44 +02:00

Porteries Tristan commented

2015-05-23 17:02:44 +02:00

Edit mode -> ctrl + F -> flip normal

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

python addobject #40097