Accessing Hardware Buffers using Python-Ogre

[Stefan Stammberger]

Hi,

I recently updated python-ogre on ubuntu 8.04 to the latest version.
It works very well but I'm having one problem with this version,I
can't access hardware buffers anymore. Basically I have been using the
Opcode Demo code to get the mesh information, but with the new version
I've been compiling I get an crash there:

vbuf.readData(0, pSubMesh.vertexData.vertexCount * 3 *
ctypes.sizeof(ctype.c_float), ctypes.addressof(test))

And this is the exception I'm receiving:
http://img354.imageshack.us/img354/8632/hardwarebufferexceptionwl0.png

Is this a bug or is this change intended?


Thanks,
Stefan

[Andy Miller]

Not an intentional change -- Looks like a bugs with the Linux code generation (it's OK on Windows), I'll take a look at this further and post a fix..

Andy

2008/7/2 Stefan Stammberger <some....@gmail.com>:

[Andy Miller]

Problem was that the ogre patch file was incorrect and wasn't being applied (it still had 'ogrenew' as the base directory, not 'ogre')..

 

So if you do:

• cd ~/development/python-ogre
• svn up
• rm code_generators/cache/ogre_1.4*
• cd ..
• patch -s -N -i ./python-ogre/patch/ogre.patch -p0
• python python-ogre/BuildModule.py ogre -g -c

 

You should see an improvement (I'm still running my tests at the moment to be sure..)

 

Andy

 

2008/7/2 Andy Miller <nzmi...@gmail.com>:

[Stefan Stammberger]

I have tried it but I still get the same error. I'll do a full rebuild
tomorrow.
I have made sure the patch is applied (when patching again its saying
the patch is already applied).

On Jul 2, 10:58 am, "Andy Miller" <nzmill...@gmail.com> wrote:
> Problem was that the ogre patch file was incorrect and wasn't being applied
> (it still had 'ogrenew' as the base directory, not 'ogre')..
>
> So if you do:
>

> - *cd ~/development/python-ogre*
> - *svn up*
> - *rm code_generators/cache/ogre_1.4**
> - *cd ..*
> - *patch -s -N -i ./python-ogre/patch/ogre.patch -p0 *
> - *python python-ogre/BuildModule.py ogre -g -c*

>
> You should see an improvement (I'm still running my tests at the moment to
> be sure..)
>
> Andy
>

> 2008/7/2 Andy Miller <nzmill...@gmail.com>:

>
> > Not an intentional change -- Looks like a bugs with the Linux code
> > generation (it's OK on Windows), I'll take a look at this further and post a
> > fix..
> > Andy

> > 2008/7/2 Stefan Stammberger <some.fus...@gmail.com>:

[Andy Miller]

Oh, don't forget to install the new module onces it's built

python python-ogre\BuildModule.py -b install

Andy

2008/7/4 Stefan Stammberger <some....@gmail.com>:

[Stefan Stammberger]

Thanks, I tried it before but even installing didn't help. But a full
rebuild did the trick.
Maybe I did something stupid, don't know :)

Thanks again,
Stefan

On Jul 4, 8:59 am, "Andy Miller" <nzmill...@gmail.com> wrote:
> Oh, don't forget to install the new module onces it's built
>
> python python-ogre\BuildModule.py -b install
>
> Andy
>

> 2008/7/4 Stefan Stammberger <some.fus...@gmail.com>: