stiv uploaded file blender-pie.patch (13.7 KiB)

update blender pie import scripts

stiv changed type from bug to patch

stiv commented

Fix for bug http://developer.wz2100.net/ticket/1545

stiv uploaded file blender-pie-2.patch (16.5 KiB)

latest greatest. import discards bad polygons

MaNGusT commented

change status to fixed pls. I can't download new version of plugins.

i-NoD uploaded file blender.zip (10.2 KiB)

Here are the plugins from 'blender-pie-2.patch'.

MaNGusT commented

thanks. now it works great with pie=3 and floating points. bugs are fixed.
Question. Can I use now only floating points when I convert my new models? instead of integer Pie=2. I think that we can forget about integer now, don't we? :-)

i-NoD commented

Replying to Warzone2100/old-trac-import#1584 (comment:3):

thanks. now it works great with pie=3 and floating points. bugs are fixed.
Question. Can I use now only floating points when I convert my new models? instead of integer Pie=2. I think that we can forget about integer now, don't we? :-)
Somehow I missed the notification e-mail for your post.
AFAIK the engine itself is float-capable for 3 years now, but it wasn't usable without proper exporter. :)

I guess you've already figured if we can use floats in pie?

Buginator changed status from new to pending

Buginator commented

stiv, is it OK to commit this?

What about #359 ?

i-NoD commented

Please wait until I enable a complete support for floating point in PIE3 (#1678). Then scripts should be changed accordingly...

stiv commented

The Blender plugins already handle floating point coords both for verts and texture coords. I don't see any reason not to commit them. They are PIE 3 compatible.

i-node: what do you mean by floating point support? Are you thinking of changing the texture space to 0.0-1.0 or simply changing the 0-256 space from ints to floats?

Is the WZM format up to date?
http://developer.wz2100.net/wiki/WZM_format

It looks like it is using 0.0-256.0 for the texture coordinate space.

stiv changed status from pending to new

i-NoD commented

texture space to 0.0-1.0

Current PIE 3 format can handle FP for vertexes, but only 8-bit integers for texture coords.
The root cause is that game engine isn't capable of FP tex coords yet. I will fix this, but we shouldn't mix integers and floats.

The idea is to use PIE2 format for integers (for PieSlicer compatibility) and PIE3 for FP (blender and such). Current trunk models will be rolledback to PIE2 state as they will gain nothing from PIE3 format. Plus renewed PIE3 format will lack ANIDATA structure, so any effects in .pie should be in PIE2 format. New TCMask flag will availabel on PIE3 format.

PIE3 format will be a test ground before WZM format, although I think whole WZM is in a 'idea' state...

Per changed status from new to closed

Per changed resolution from `` to Needs reevaluating for current version (3.1.0)

stiv commented

Can we get a definitive declaration of what the PIE* format state is with regards to 3.1? I stopped working on this because it seemed the format and usage was in flux, although I'm not sure anything ever came of it.

The scripts also need to be re-worked for use in new Blender (2.6x) since it has a completely different Python API and mechanism for registering plug-ins, something I have been poking at a bit lately.

dak180 commented

Replying to Warzone2100/old-trac-import#1584 (comment:10):

Can we get a definitive declaration of what the PIE* format state is with regards to 3.1? I stopped working on this because it seemed the format and usage was in flux, although I'm not sure anything ever came of it.

It is my understanding that the format for 3.1 will not be undergoing any more changes; 3.2 on the other hand may be getting support for the the wzm format (see #3905) but i do not think there are any plans to change the pie support.