PyPRP2 Information

[Branan]

The latest PyPRP2 release is Beta 1

PyPRP2 requres Blender 2.57. It will not work in older versions of Blender 2.5, so don't even ask.

A PyPRP2 introduction video is available to help you get started using PyPRP2 and Blender 2.5, narrated by yours truly.

PyPRP2 is still in development, and is missing some features you might have used in PyPRP 1. Let us know what you need so we can prioritize!

more FAQs will be added as they come up.

[Fuchida]

Thanks for the hard work put into this.

You made my day.

[dendwaler]

Thank you very much!,
and ofcoarse this big thx goes for everyone who helped to make this release possible.
I will immediately install it and use it.

[Rabenschwinge]

I´ve watched the video - looks very intriguing, I think the new GUI of Blender and PyPRP will make things a lot easier and more comfortable!
Thanks for the hard work to everyone involved!

I´ve refrained from using the most complicated scripts, be it ALCScript or Python, with the hope I´ll be able to add these functionalities to my ages without having to do too much programming, as I´m not good at it at all So, PyPRP2 is a huge gift for me!


If I might ask a little question: with the new export-functionality, will it make sense to make an age compatible to URU:CC, and MOSS/MOUL at the same time?
Or should each age be split into two "forks" (if one may call it like this) and developed independently of each other?

[Calena]

I watched the video and all I can say is, "WOW!". You guys are really good at this. Nice video too.

I'm not downloading 2.57 or PyPRP2 yet. My head might explode if I add any more challenges to it right now, but looking forward to finishing my age and starting again with the new tools.

Great work.

[Branan]

If I might ask a little question: with the new export-functionality, will it make sense to make an age compatible to URU:CC, and MOSS/MOUL at the same time?
Or should each age be split into two "forks" (if one may call it like this) and developed independently of each other?

You should be able to use one .blend file to target every Plasma version you want. You'll have to do the export, copy the files someplace, change the version, then export again. The version selector only determines how the age is exported, the UI is complete version-independent

[Rabenschwinge]

If I might ask a little question: with the new export-functionality, will it make sense to make an age compatible to URU:CC, and MOSS/MOUL at the same time?
Or should each age be split into two "forks" (if one may call it like this) and developed independently of each other?

You should be able to use one .blend file to target every Plasma version you want. You'll have to do the export, copy the files someplace, change the version, then export again. The version selector only determines how the age is exported, the UI is complete version-independent

Cool! That´s awesome, thanks!

[Aloys]

Thanks for that video; very handy.
Also, funny, I always pronounced PyPRP "Pie-PRP" (as in Python) not 'Pee-Why PRP'. Is that the 'official' pronunciation?

[Paradox]

Also, funny, I always pronounced PyPRP "Pie-PRP" (as in Python) not 'Pee-Why PRP'. Is that the 'official' pronunciation?

There's a reason programmers prefer text communication

I've always said "Pee-Why PRP", but I'm not sure how other projects (like PyPy, or PyQt) are officially pronounced.

[Wamduskasapa]

Thanks for that video; very handy.
Also, funny, I always pronounced PyPRP "Pie-PRP" (as in Python) not 'Pee-Why PRP'. Is that the 'official' pronunciation?

LOL and here I have been saying Pie-purp