Blender bpy/bge Brussels workshop #4

blender-bpy-bge-brussels-4

So, François and I are organizing monthly Blender workshops at Constant Variable where we play around with python code and the Blender Game Engine (BGE). The point of these meetings is to get together and exchange ideas and experience around the use of code and 3D realtime rendering with open source software. Last meeting was this friday and here’s a quick explanation of what was achieved.

François came with a little .blend file he set up with a cube rotating randomly. We looked through the code, studied it and improved it by making it shorter and easier to duplicate. The file is available on our shared github repository and is called bge_cube_animation. The cube can be duplicated without changing the code so that all cubes will perform their own random animation.

The next project was to get the BGE to send and receive OSC messages. We looked through different python OSC libraries and studied the great example provided by Labomedia. We didn’t start studying OSC by chance. It’s a well known protocol for exchanging data between realtime visual or audio programs but it’s also what comes out of Melon (a kinect based controller) that François has been working on at Numediart.

To get it all working together, the pyOSC library had to be updated a little to handle OSC messages that were not yet implemented. The new version of the code is available on my gitorious fork (pyOSC v0.3.7), waiting to be merged with the official one.

We then rushed to finish the workshop by recording a self satisfying video of François pushing blocks around using the Kinect -> Melon -> pyOSC -> BGE set up. The file is also available on our Github repo. (See bge_cube_osc.blend in user/frankiezafe/ directory)

Next meeting will be in a month or so and announced on Constant and Blender Brussels Meetup websites. Feel free to join us.

3 thoughts on “Blender bpy/bge Brussels workshop #4”

  1. Hello,
    I can’t find your updated pyosc code. Does “handle OSC messages that were not yet implemented” mean that you managed to handle sent osc address that didn’t have handler?

    1. Hello Trier.

      The pyosc code is not available because Gitlab bought Gitorious and they obviously are messing up with the server. It was my intention to drop this code somewhere else. But haven’t done it yet. About or modification, if I remember well, we just added the some type of OSC messages that the original script was not yet recognizing. Nothing to do with “sent osc address that don’t have handlers”. Hope this helps.

Comments are closed.