Guild of Writers

I stand corrected. =P

Still, if the old importer does random shittles like have every material a seperate object... *shudders* That was the whole reason I started using the importer instead of prp2obj. =P objects being the original objects. >.>

EDIT: @Chloe: Right, but, for a long time, they suggested pyprp2 would support import, and would be the magical solution to all problems. (note the wiki page even notes pyprp2 will make it obselete, due to doing import better), this isn't the case anymore. =P

I still don't really understand how it was ever considered a good idea to drop it, though its been explained to me many times (so no point in explaining it again), I just don't, personally, agree with the choice. However, as I cannot contribute to the project, I (mostly) try and keep my mouth shut about it.

I know you don't want another explination so basically this is for other readers of these posts:

Importing was dropped from the plugin mainly because the people who were doing most of the development at the time were not contributing to it and felt that it would be better to concentrate on exportation and the actual components being used. Not everyone thought that way, but again, the people that were working on it were not contributing to it either.

I think it was around version 1.2 or 1.3 I mentioned something and either Robert or Paradox (can't remember, forgive me), made some changes and gave them to me, but also explained the "why" it was being dropped.

I felt that dropping it was actually a mistake, as by importing Cyan's Ages, you can learn so much from them. Sort of like having "Hands On" training. I know many things that I've learned to do, I did so by seeing it done in one of their Ages. But I also was not contributing anything to the development of the plugin (except loud noises and comments, ).

I will say that having the ability to import has saved my bacon as far as this latest Age I'm working on. When the blend file was erased, it was being able to import my Age files that allowed me to continue.

Where do I have to look for that folder "TMP_textures"? It looks like I'm missing that after using the importer.

Corvus wrote:Where do I have to look for that folder "TMP_textures"? It looks like I'm missing that after using the importer.

You can find it in the dat folder for Uru. (Where all the age files are located on your system.) It's usually located in C:\ProgramFiles\Ubisoft\Myst: Uru Complete Chronicles\dat

Not having done this before, I'm not sure if this is a silly question or not, but would there be any conflicts if I wanted to use the Alcugs plugin to examine textures, and the GoW plugin to look at how the objects/meshes are structured? Is this even necessary? I'm just interested in taking a look at some of Cyan's UV layouts and, of course, the way they assemble their environments...
(On second thought, I'm pretty sure this is a silly question, but I'd like to know the answer anyway. )

I haven't installed the Alcugs version in a while but I remember it wasn't possible.. I remember because at some point I installed PyPRP and it wouldn't import Ages correctly anymore, so I reinstalled AlcPyPRP and I imported all the Cyan Ages before reinstalling GowPyPRP.. (took me a while to import all those Ages)

You can get versions of Blender that just run out of a folder, including saved settings. That's what I do, and how I have multiple versions of Blender with multiple versions of Pyprp.