PyPRP 1.6.1 Released!

[Tsar Hoikas]

Building upon the success of PyPRP 1.6.0, PyPRP 1.6.1 has now been released!

You may download PyPRP 1.6.1 from the usual place. A relatively complete changelog can be found on the wiki.

This release has been assembled from various floating "fixed" files from GPNMilano, Tachzusamm, and D'Lanor that many users have been running to supplant vanilla PyPRP 1.6.0, so I am hoping that there won't be any need for extensive documentation This release is an attempt to reduce the number of steps required to get a working blender plugin

Enjoy!

[Mystler]

I believe that is where your first link should point to?
http://guildofwriters.org/wiki/PyPRP:Downloads#Releases

[Tsar Hoikas]

That does help slightly...

[Rabbit]

Look forward to giving it a try.

[Jojon]

Thanks, Adam. :)

[Render]

Guys, I was thrilled to see an updated version of PYPRP, so I downloaded and put it to the test.
Although I can't immediately see the improvements, there is something that struck me as odd and also a little annoying.
Everytime you change the blenderfile name (to reflect a new version), all the textures are cached again, slowing down the export process considerably.
Is there a way to avoid this??

[dendwaler]

Saving blendfiles and exporting are different things.
If you export you can use your the chosen agename without the version number.
You will overwrite the old export and there will not be a cache tex update.

[Render]

I would think so too, but with PYPRP1.6.1 it is now my experience that it does.
I agree that the export is still to the same prp files and with the same name, but it Does do a total refresh of the tex cache, I don't know exactly what triggers it, but it does.

[Render]

Feeling pritty stupid right now
I forgot I had my export set to uru directly with the age name without version number.
Installing the new PYPRP killed that and I have been exporting directly to my blender directory instead, including the version number, hence the rebeuild of the cach.
Sorry for my stupidity

[tachzusamm]

Thank you for updating the PyPRP 1 tools, Tzar.
Really good to know that PyPRP 1.6 is still maintained.

I've updated the chapter in the Wiki which suggested my now obsolete patch to reflect the new situation.
(http://guildofwriters.org/wiki/Proper_t ... cy_support)