search

vicentecarloscisnerosolivo / blender2ogre

Automatically exported from code.google.com/p/blender2ogre
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Blender 2.66 Compatibility #63

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start Blender 2.66.
2. Export a scene with a model that has a texture applied to it's material.
3. Read the error.

What is the expected output? What do you see instead?
Expected exported scene got a few errors.

What version of the product are you using? On what operating system?
Blender 2.66 from blender.org, Windows, 0.5.9.

Please provide any additional information below.
Attached below is a fixed file. Blender has apparently moved the use_alpha 
property from bpy.types.ImageTexture to bpy.types.Image.

Haven't seen other incompatibilities other than that.

Original issue reported on code.google.com by mindcalamity on 23 Feb 2013 at 2:16

Attachments:

GoogleCodeExporter commented 9 years ago 
I can confirm that this version works on 2.66. However, it seems that the axis 
swap is wrong. Previously the model was exported facing the positive Z, now my 
model is exported facing the negative Z, causing a mismatch with any skeletons 
we've already exported.

Original comment by syb...@stuvel.eu on 21 Mar 2013 at 5:05

GoogleCodeExporter commented 9 years ago 
Ok, changing the axis swap to -xzy fixed my axis issue. All that's left is a 
confirmation that the patch works!

Original comment by syb...@stuvel.eu on 21 Mar 2013 at 5:34

GoogleCodeExporter commented 9 years ago 
This repository has been inactive for months, so I hosted a new version on 
BitBucket, if I add some fixes they'll be found there:

https://bitbucket.org/MindCalamity/blender2ogre-exporter

I will also be accepting patches from other users on the OGRE forums.

Original comment by mindcalamity on 21 Mar 2013 at 6:07

GoogleCodeExporter commented 9 years ago 
Excellent!

How will you handle other issues that have been logged here?

Original comment by syb...@stuvel.eu on 21 Mar 2013 at 6:26

GoogleCodeExporter commented 9 years ago 
I think re-reporting them would be the best course of action. You have any 
other ideas ?

Original comment by mindcalamity on 21 Mar 2013 at 7:19

GoogleCodeExporter commented 9 years ago 
I think it depends on your goal. If you want to fix all of the issues tracked 
here, you can just keep them here. On the other hand if you're only going to 
fix a subset, it may be clearer to (ask people to) re-report them on Bitbucket.

I'm fine with re-reporting the issues I reported to Bitbucket.

Original comment by syb...@stuvel.eu on 21 Mar 2013 at 7:23

GoogleCodeExporter commented 9 years ago 
My goal is to have an easy way to patch things up as soon as they break, given 
the maintainer's absence it's impossible to do that in this repository.

Unfortunately, I'm too inexperienced with Python, nor do I have enough time to 
try all the reported issues, but I do have the time to apply patches, and I can 
always just allow write access to people willing to help maintain the exporter.

Original comment by mindcalamity on 21 Mar 2013 at 9:07

GoogleCodeExporter commented 9 years ago 
Ok, count me in! I've got quite a few years of Python and Blender experience, 
so if you need any assistance let me know.

Original comment by syb...@stuvel.eu on 21 Mar 2013 at 9:47

GoogleCodeExporter commented 9 years ago 
Good to hear, PM me your email or BitBucket username and I'll give you access 
to it. :)

Original comment by mindcalamity on 21 Mar 2013 at 4:34