PyPRP 1.6.1 Released!

[Tsar Hoikas]

You're quite welcome. If you have any other patches lying around, please let me know!

I am doing some profiling and optimizing of the plugin in my (extremely limited) spare time for a PyPRP 1.7 release. It's always fun to watch execution times drop by many seconds from some very trivial code changes

[tachzusamm]

Yes, I have a patch lying around.

Scope: Playing IPO animations controlled by Python
Problem: Plasma needs the *same* index for both "animationname" (the name) and "animation" (animated object); but AlcScript simply increments the index for each AlcScript entry, so name and object do not match, and playing an animation via Python does not work
Solution: Give the ability to force name and object to the same index where needed in AlcScript

This patch does allow it:

prp_LogicClasses_py.zip

(15.99 KiB) Downloaded 1980 times

AlcScript example:

Code: Select all

                # each line starting with "-" normally counts up the index automatically
                # ...
                # Normal stuff
                  - type: (some type)          # auto-index: 8
                    value: (some value)
				
                # Animation
                  - type: animationname        # auto-index: 9
                    value: OuterCamAnim_01  # animation NAME
                    index: 10                  # 9+1 (force to 10)
                  - type: animation            # index 10
                    ref: :TransOuterCam_01	# animated OBJECT, not animation name!
                    index: 10                  # (same index as name)
                  
                # Normal stuff again
                  - type: (some type)          # auto-index 11 (counting continues)
                    value: (some value)
                  - type: (some type)          # auto-index 12
                    value: (some value)

The patch does not affect existing ages; it only comes into play when there's an index value attached to an object in AlcScript. This is already used in Relativity.
Without this patch, a Relativity export won't behave as desired; the Transporters won't work, because their animation has to be managed by Python.


Original thread this is based on:
http://forum.guildofwriters.org/viewtop ... f=7&t=5300


Btw, cool that you do profiling to speed PyPRP up. Do you use profile of cProfile?

[Karkadann]

Any progress on a Blender age exporter for the Open Source game engine?

[Sirius]

Can't PyPRP 2 generate files for MOUL/Dirt clients ?
Anyway, if you're up to the challenge, you can try converting them with HSPlasma.
I know you can convert a prp this way:

Code: Select all

PageConvert -tomoul yourfilename.prp

But you'll have to find out for .age, .fni and .sum files.

[Karkadann]

I'm actually a Max user, the reason I'm asking is most of the Age Creators from what I understand are Blender users and I figured if their were a way to export Ages for MOUL/Dirt as easy as you can export for the Uru CC program it would increase the number of ages available for the all MOUL/Dirt shards

[Tsar Hoikas]

I'll see about getting that patch applied to the git repository soon-ish. I'm using cProfile to profile the export process. I didn't want to slow things down by using a pure python profiler . The largest slowdowns that I see in a "trivial" age are related to converting RGBA images to DDS, processing meshes, and lots of silly calls to range.

Any progress on a Blender age exporter for the Open Source game engine?

No. There is a bug in Python 3.3.0 (used by blender 2.66) that prevents me from working on it.

[tachzusamm]

If you find time to update PyPRP to 1.62, could you include this as well?

http://forum.guildofwriters.org/viewtop ... 114&t=6203