Climbing region issue

[Kierra]

an object in one of my ages is a bit unconventional as a ladder, so I've had to do quite a bit of guess-work in making it climbable.

So far my best results have been with using the making it climbable tutorial, and it works alright, except one slight problem: when the avatar gets to the top of the object, if you try to move forward, the avatar begins climbing down on the wrong side.

If I get off of the object and approach it to climb down the correct way it will climb down the correct side, but that initial dis-mount makes the avatar climb down incorrectly.

Here's a video of the issue.

does anyone know how to fix this?

~Kia

[Trylon]

Heh, very interesting.

What method are you using to make the climbable? (As the tutorial you mentioned names three different ways)

If you are using manual placement of the top and bottom regions, you may have a shift or something in the climb-down region at the top.

[Kierra]

The very last one, named " Making it climbable - The old yet very flexible way"

What do you mean a shift?

Thanks,

~Kia

[Trylon]

That the top region isn't in the place or doesn't have the size it is supposed to have in-game.
An export glitch. One way to find out if that's the case is by re-importing your age.

[Kierra]

heh, well its probably not that, then. I've exported the age several times since then

~Kia

[Trylon]

No, I meant that if you import your own age, you can check if the region is in the same space as it is supposed to be.

[Kierra]

Ah I see what you mean. I'll try that

~Kia

[Kierra]

ok I think I found the problem with the climb region, but now when I try and export my age to test it out, I'm getting a python console error:

Code: Select all

Compiled with Python version 2.5.
Checking for installed Python... got it!
Exporting C:\Program Files\Ubi Soft\Cyan Worlds\Uru - Ages Beyond Myst\dat\Realm
.age ...
Args are e_age_final
['e', 'age', 'final']
Exporting age Realm
#########################################
##
## => Exporting page Textures -1 <=
##
#########################################
[0004] 4361.jpg
[0004] 4361.jpg
Traceback (most recent call last):
  File "<string>", line 174, in open_file
  File "<string>", line 83, in export_age
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\alcresmanag
er.py", line 304, in export_all
    page1.setRaw(o.data.Key.page_id,o.data.Key.page_type)
TypeError: setRaw() takes exactly 4 arguments (3 given)


When I imported the age into blender, I saw that the upper region had several (about 5) duplicate regions in the wrong position. So I deleted those, then saved the file under a different version number, then tried exporting it. It gave me that error.

So I closed that and opened the version before that, tried exporting and got the same error. So I closed blender (it gave me an error-"blender encountered an error and had to be shut down") reopened, and tried again, but I'm still getting that error.

any ideas?

~Kia

[Trylon]

Owww, you're probably using a non-latest version of the plugin.

Old behaviour in the plugin is to save all raw objects imported into a subfolder named [Your Age Name], and on subsequent exports it tried to re-integrate those objects, with all misbegotten consequences of the sort. The latest version removes this irksome behaviour.

Please remove this folder (easily recognizable by it's contents, folders named "Builtin", "Textures", etc. with numbered subfolders in them), before doing an export.

Sorry.