Guild of Writers

That bug happened to me several times too. But I'm not sure who was the culprit here.. That hasn't happened in a while though; so maybe it was some older version(s) of PyPRP who used to create spawnpoints with typo'd names..

Mar: do you use a recent version of PyPRP?

I have tried your suggestions but it is not THE solution.

Trylon,
Your were right the "T"was gone. I have add the "T' in LinkInPointDefault in my blenderfile. I can now see the file is loaded and when I link in the book I get the black screen. The only difference is now that CC is not crasht but the black screen is holding on, further it gives a error that files are missing and that I must reinstal the game. But when I link in a CYAN book nothing is going wrong.

Aloys,
I have checked my PRP file but it is the file from januari 2007 So far I know is that the most newest PRP file.

I give you the logfile from the age again.

Exporting c:\agebuilders\bouwtekeningen\wereld5testd.age ...
Args are e_age
['e', 'age']
Exporting age wereld5testd
#########################################
##
## => Exporting page Textures -1 <=
##
#########################################
#########################################
##
## => Exporting page plane 0 <=
##
#########################################

[Lamp Lamp.002]
Damnit! Need reimport alcurugeom.py

[Lamp Lamp]
Damnit! Need reimport alcurugeom.py

[Camera Camera.001]
Camera Brain: fixed
Exporting Camera Modifier Object
Calculating FOV for lens is 35 mm
Exporting CameraBrain1
Exporting CameraBrain1_Fixed
WARNING: Camera has NO regions associated

[Visual Object Cube.003]
Drawable object has 16 vertices

[Visual Object Cylinder.012]
Drawable object has 63193 vertices, processing can take some time...

[Visual Object Cylinder.018]
Drawable object has 2722 vertices

[SpawnPoint LinkInPointDefault]

[Visual Object Tube]
Drawable object has 11704 vertices, processing can take some time...

[Camera Camera]
Camera Brain: fixed
Exporting Camera Modifier Object
Calculating FOV for lens is 35 mm
Exporting CameraBrain1
Exporting CameraBrain1_Fixed
WARNING: Camera has NO regions associated

[Visual Object Cube]
Drawable object has 0 vertices
WARNING: AutoMaterial created, since object has no material

[Visual Object Tube.001]
Drawable object has 12395 vertices, processing can take some time...
#########################################
##
## => Exporting page BuiltIn -2 <=
##
#########################################

@ Saving page plane 0
=> Storing 84000 vertices of geometry...
=> Storing 370404 vertices of geometry - this can take some time....
=> Storing 71376 vertices of geometry...
@ Saving page Textures -1
@ Saving page BuiltIn -2
\/ Unloading page plane 0
\/ Unloading page Textures -1
\/ Unloading page BuiltIn -2
Writing wereld5testd.fni
Writing wereld5testd.xml
Writing wereld5testd.sum
done in 2405.90 seconds

CONTINUED

Mar

A files are missing or corrupted error generally means one of two things. Either

1.) The files are missing, make sure you copy all the .prp files, the .fni file, the .sum file, and the .age file into the dat folder (though I don't think the .fni is required, it doesn't hurt).

or

2.) The checksum is wrong. Use UruFun to create a new checksum file for the age.

It may be a different problem altogether, but when I get this error, one of these two things are almost always the problem.

Continued story off........

I have looked at the files and I have noticed that everytime I copied the prp files in the "dat" file and I have run CC the prp files where gone.

I have run urufun and I saw that there is a "pak"file and that is something I not have see after exporting my testage. So now I have copy that file and change the name into that from the testage and copied it in the python file. Maybe this is a stupied move.
I run CC and linked in the book but the screen is changed in black and that is it. When I looked to the files I see that the prpfiles aren't dissappaerd :huh:

When I run the urufun age everything is going well so the CC installation is good.

I can't change my checksum because first I didn't know what it is.
Second I didn't know how I must do that. So, can I find a tutorial of that somewhere? :unsure: :unsure:

Haha Sorry, I laugh because I had this exact same problem on my test Age several months ago, but no one else had that problem. Now I feel better, I am not alone.

I'm afraid I don't know how to fix the problem in your Age.

I couldn't fix the problem in my own Age, I spend several days on it and I didn't understand what happened... In the end I had to start a new Age and import the objects of the broken Age into it. I imported a couple objects, exported the Age to check it worked, imported more objects, exported it again, etc etc.. Until I had all the Age working again.. Which was quite long. Also, because it was a whole new Age I had to use a different sequence prefix.

(To import objects from another Age use Shift-F1 and go into the .Blend file you want to import)

Note: for my broken Age the problem was clearly not in the Age itself but in Uru, during a test I had removed all the objects in the Age except the book and a spawnpoint, and it still didn't work..

hmm, wait a microsecond....

Have you ever imported your age before?
The plugin then saves all prp obects to a subfolder named "[yourage]/" with some subfolders, and from that folder prp objects are imported back into the age files you're building on an export.

If not done carefully, that behaviour can cause all kind of strange happenings....

If so, please try removing that folder compleateld

Trylon I haven't import files so your suggestion can I not used. But it is good you mention it because I didn't know that. :huh:

Aloys, I have make a new age because all the time I have spend to trying it to get better was not rewarded.
It was indeed a lot of work to do but now my "new"age works.

So everyone thanks for all suggestions and thinking about my problem. :rolleyes:


Regards Mar

Mar: Sorry that you had to go through the work of reconstructing your age. But I'm glad you're finally able to explore it!

So - when do we get to see pictures?

Sounds like it was a typical "ghost object" problem. Does anyone know why Blender does that and whether or not it's possible to fix?