Revision as of 23:47, 8 June 2008

Disclaimer :
This FAQ is not exhaustive, it is always 'under construction', and many things might be missing. If you found a problem that is not covered here, please add it or post about it on the forum.

What is this FAQ?
For now this FAQ focuses on problems with Uru and the Tools (essentially PyPRP). Problems that are related only to Blender and modelling/texturing/animating/sound are located in the Blender FAQ.

Common advice:
- Make sure you have the latest version of the tools.
- Make sure to always keep various back-ups of your Age files. Save your Age Blend file with incremental numbers (MyAge01.Blend, MyAge02.Blend etc)
- If you have enough space on your hard drive, keep a 'clean' back up installation of Uru. It is always usefull for testing; or getting back missing/corrupted files for your 'regular' Uru installation.
- Whenever you have a problem with an Age, try to remember the last things you changed; the source of the problem is certainly here.
- Patience is your best tool. :)
- If all else fails, ask on the forum.

I - PyPRP export error messages

"Blender error pop-up saying: Python script error: check console"

The console is that small black and white window that opens up with Blender. So whenever you get that error open the console and look at what the last line says. That error may be listed in this FAQ, if it isn't ask on the forum.

"Couldn't load image data in Blender"

Sometimes Blender 'forget' some images. Solution: Reload the image in question in UV/Image window, or by simply selecting the problematic object, open a UV/Image window and hit 'F', this will display the image and fix the problem. This happens often.

"TypeError: 'NoneType' object is unsubscriptable"

I'm not sure why but this has to do with an object having multiple materials.. Try to remove materials from your objects.. If your objects needs several material try to subdvide it into more objects, one for each material.

"ValueError: Need more than 0 values to unpack"

This is most likely because your object use one (or more) vertex groups. Remove them. Select your object and go to the 'Editing' panel, and in the leftmost part of the panel there is the Vertex Groups area, click 'delete'.

"ValueError: face has no texture values"

The mesh has a texture assigned but it is not yet UV mapped. Select the object and hit 'F' to edit its UV mapping.

"Checking for installed Python... No installed Python found."

There is a problem with Python. You need to install Python; find it here: http://www.guildofwriters.com/wiki/Installing_PyPRP

"ImportError: No module named glob"

There is a problem with Python. Make sure it is properly installed, or re-install it.

"ImportError: No module named Image"

You need to install the Python Imaging Library. Find it here: http://www.guildofwriters.com/wiki/Installing_PyPRP

"ImportError: No module named yaml"

You need to install YAML. Find it here: http://www.guildofwriters.com/wiki/Installing_PyPRP

"ImportError: No module <anything other than glob, image or yaml>"

The python file mentionned is missing. Make sure that the various PyPRP files are installed in blender's /script folder. The default path for this : C:\Program Files\Blender\.blender\scripts

"UnboundLocalError: local variable 'col_r' referenced before assignment"

This error can be related to vertex painting if you are using an "alpha" layer but no "col" layer. If you do vertex alpha the "col" layer is also required, even if you don't use it. So make sure to have one.

"WindowsError: [Error 2] The system cannot find the path specified: 'C:\\DOCUME~1\\user\\LOCALS~1\\Temp\\..."

You may be trying to export an age from a .blend file that you opened within a temporary ZIP file folder (obtained by double-clicking on the ZIP file in Windows); and the plugin is unable to find the files it needs to in this temporary file. To fix this, exit Blender and right-click on the ZIP file, then choose Extract from the popup menu. Once the file has been extracted into a folder, double-click the .blend file and try again.

II - Uru problems/errors messages

"Files are corrupted or missing"

This is the most frequent problem and the easiest to fix. Some files are indeed corrupted or missing. If you have worked with the PRP files by hand then this is related to the .sum file of the Age either it is out of date and need to be updated (by any tool like Plasmashop,UruFun, ULM) or some of the PRP files for the Age are missing. Make sure you haven't deleted or renamed any files..
If you have this problem when you start Uru, this is a problem with the Personal Age files, or some of the other necessary Uru files. Make sure you haven't deleted or renamed any files.

"Black screen when linking"

There are several possibilities:
It might be a problem with the linking point for the Age. Either you don't have one, or it is placed in an improper place (inside a wall, under the floor etc) or it is incorrectly named.
This could also be a problem with the .Fni file. If it is corrupted in any way some graphic cards will display a totally black fog in the Age instead of the fog you have set in the .fni file. Make sure it is not corrupted in any way. The best way to avoid this is to create the .fni file in Blender, and never touch it outside of Blender unless you know exactly what you are doing.

< This section needs to be expanded >

"Uru crashes on startup"

This is most likely related to the lastest Age you have added or modified. Try removing it and launch Uru again. If this solves the problem, then something is wrong with this Age; and if you have a .Pak Python file for this Age it is most likely the problem. Make sure it is properly compiled, not corrupted, and doesn't have any problem of any kind.

"Uru crashes to desktop when I try to load my Age"

There are several possibilities:

1) This is often related to a Sequence Prefix error. Have you registered a Sequence Prefix for your Age? Make sure it is not an existing number. Register your Age here: Obtaining your own unique Sequence Prefixes.

2) Another possibility is a problem with the way the Age is registered in ULM. Try removing the Age from the book and move it to a new slot on the book, or move it to a different book. It is unknown what causes this, but this fix sometimes work.

3) PyPRP version 1.4.0 and above support dynamic shadows for all objects, not only the avatar. Unfortunately this is enabled by default in all Blender materials which means that if you haven't manually disabled it it is enabled for all the objects in your Age. This is too much to handle for most computers, and it may be the reason why your Age crashes.
So if your haven't done it yet you will need to update all the materials in your Age and disable the 'Shadowbuf' button in the Material. (it is in the 'Links and Pipeline' pannel).To make things easier you can download this python script that will do it automatically. Install it in your Blender Scripts folder (where you installed PyPRP). Then in Blender open a Scripts window and in the Scripts menu go to Materials>Clear Shadbuf.

"Uru crashes when I try to load my Age and displays a 'Stack Dump' window"

Unfortunately there could be many sources for this.. Try to remember the last things you changed to the Age or to Uru before that happened; the source of the problem is certainly here. It may also be because of a Python problem; if you use Python in your Age check that there is nothing wrong with the code or with the .pak files.

Users can send stack dumps to Tahgtahv. Browse to your game directory. Include the contents of log/stackdump.log (if it exists) along with a description of the problem and he will look into it.

"My object doesn't appear in my Age, although I had no error on export."

Check that your object isn't assigned a non-existing page_num property. It could also be a problem with the normals, in edit mode check that your object's normals are not inverted.

III - ULM/ULM related problems

"Application couldn't initialise properly (0xc0000135). Click OK to stop the application."

To run ULM you need to have .Net 2.0 installed. Find it here.

"My Age doesn't appear in the 'Personal Ages' tab."

There are several possibilities:
1) Some (or all) of the Age files are missing in the /Dat folder. Check if they are here, especially the .age file.
2) ULM can't read the .age file. That file is broken for some reason. Fix it manually if you know how to do it, or try to export the Age again.
3) The sequence prefix for the Age is less than 100 or is already used by one of your other Ages. Make sure to use a unique sequence prefix number, and make sure that it is above 100. (Numbers bellow 100 are reserved for Cyan Ages)

< This section seriously needs to be expanded >