Page 2 of 4
Re: PRP Importing
Posted: Tue Apr 14, 2009 9:34 pm
by ardent red
I've just tested, and it works with 2.5, thanks GPN

. It makes sense, in a way- there were some pretty huge material revisions for the BBB project.
Re: PRP Importing
Posted: Mon Jan 11, 2010 3:54 am
by kaelisebonrai
Sorry about the thread necromancy, but, it is a relevant addition to the thread, along with a query.
The PyPRP Importer link at:
http://www.gpnmilano.bplaced.net/filema ... porter.rar is now a dead link. Is there any chance anyone has the files?
The reason I'm asking is I'm looking to test out some ideas with an imported prp. =)
Re: PRP Importing
Posted: Mon Jan 11, 2010 10:13 am
by GPNMilano
I can't do it right now, but later today I'll update the link in the wiki for the files. I noticed the other day that it was dead but haven't gotten around to fixing it yet.
Re: PRP Importing
Posted: Fri Jan 29, 2010 12:20 pm
by Ashtar
GPNMilano wrote:I can't do it right now, but later today I'll update the link in the wiki for the files. I noticed the other day that it was dead but haven't gotten around to fixing it yet.
Did you ever get the chance to put the importer up on a new link? I also had some importing issues recently and the reason may have been the mods done to the importer. Just want to make sure I have the latest version

Ashtar
Re: PRP Importing
Posted: Mon Feb 01, 2010 6:35 pm
by GPNMilano
Update on the Importer:
Sorry I haven't had time to do anything with this. Some of the errors that people receive when importing are one of two things:
1. The importer was/is an earlier version of PyPRP that was outdated, it unfortunately was based on code of older versions of Blender. as the Blender code was updated so was PyPRP but the importing functions of it were not fixed for newer versions of Blender. So support for importing ages fell by the wayside to make room for age creation and blender compatibility.
2. In order to fix the errors of 1. People played with the code a bit to get around some of the errors, this caused more errors in the long run than it really solved.
I haven't had the time to do anything with the importer but it is on a very long to do list. what I intend to do is strip out all age creation and just repackage it as an importing tool for blender. This means also updating it for newer versions of blender. (currently, if you want to use it, it's compatible with blender 2.45 and should import any age from CC with that version. If you wish to import Drizzled Myst V or MOUL ages it will do that but requires alot of work arounds to do so.)
If you're in dire need of it right now, I'd suggest downloading Blender 2.45 if you can find it and use that with the import scripts. And if one of the ages you wish to import are from Myst V or MOUL I can help you with the workarounds.
If you can wait a bit though, at some point I will fix the importer fully so that it's compatible with newer versions of blender and will import the drizzled ages without the need for workarounds.
Sorry again for the delay. I haven't forgotten about the importer, I've just had to much on my plate at the moment and this is one of those things that hasn't taken a huge priority for me as I just use 2.45 for importing at the moment. But I do intend to get to this, as I'm a bit tired of having to use two blenders and having to do work arounds for Drizzled stuff.
Chloe
Re: PRP Importing
Posted: Tue Feb 02, 2010 3:01 am
by diafero
what I intend to do is strip out all age creation and just repackage it as an importing tool for blender
Don't importer and exporter share a lot of code (i.e. the knowledge about all the Plasma classes), so that this sounds like huge duplication?
Re: PRP Importing
Posted: Tue Feb 02, 2010 9:30 am
by GPNMilano
diafero wrote:what I intend to do is strip out all age creation and just repackage it as an importing tool for blender
Don't importer and exporter share a lot of code (i.e. the knowledge about all the Plasma classes), so that this sounds like huge duplication?
Not really. Every plasma class in PyPRP has specific definitions seperated. The import and read functions are the most important for importing stuff. While the write and export definitions are the age creation stuff. (Materials, Layers and a few other things use ToBlender/FromBlender instead of import/export). So, in theory, i should be able to go through and get rid of the export functions without damaging the import stuff.
Re: PRP Importing
Posted: Fri Feb 05, 2010 10:39 am
by Stefan
Is there any chance to get the 1.3.0 pyPRT files for the importer? I downloaded blender 2.45 and want to try to get it working, as it doesnt do on any other comination... please contact me. Thx!
Re: PRP Importing
Posted: Fri Feb 05, 2010 11:57 am
by Mekeretrig
Same. I have the Blender 2.45/Python 2.5 setup with other specified files for those versions, but neither the one on Alcugs or the importer listed on the GoW wiki work.
I keep getting this message in the Blender console,
Traceback (most recent call last):
File "<string>", line 48, in <module>
ImportError: No module named alcconfig
EDIT: Nvm, fixed.
Re: PRP Importing
Posted: Fri Feb 05, 2010 12:40 pm
by Mekeretrig
Okay, I've almost got it working.
However, it appears that part of the importer is disabling itself?
File: "C:\Documents and Settings\machineowner\Application Data\Blender Foundation\Blender\.blender\scripts\alcresmanager.py", line 163, in import_all
self.prp.setname(self.age.name)
Import is disabled by default, you must agree that you are not going going to use Cyan
protected material without their permission.
So... if I get permission, how will it impact the functionality of the importer? This is the importer I downloaded from GoW (or to be more correct, the link to the downloaded listed on GoW).
Btw, why have an importer that is going to be disabled for everyone who downloads it?
I'll only be using The Cleft to help create a heighmap, so I won't be attempting to port the age itself or use any part of it in another age for Uru.