Falling on a Collision Mesh: Weird Error

If you feel like you're up to the challenge of building your own Ages in Blender or 3ds Max, this is the place for you!

Falling on a Collision Mesh: Weird Error

Postby Jennifer_P » Wed Dec 12, 2007 4:53 pm

Well, major weirdness going on now. I'm not sure where the problem might be. :|

Here's what happens: I link into my Age, and my avatar falls in a standing position onto my collison-enabled mesh (w/Property: String, col_type, 4). Here the weirdness begins. As soon as it lands on the mesh, earthquake! The avatar and the mesh both begin to shudder and shake. After this goes on for a few seconds, then the avatar and the mesh zoom slowly down into the periwinkle-gray abyss that serves as my default sky. While they are still visible, they fade out into periwinkle-gray. A short pause occurs during which only the blank sky is visible. Then my mesh returns from whence it came, zooming rapidly upwards with the link-in point moving towards the center of my screen. However, my avatar--which I never moved off the link-in spot--is now gone! One of the times I was observing this I waited over two minutes to see what would happen after the mesh passed my POV and disappeared. Nothing; my avatar didn't even link out. Other times, when I linked in I tried messing around with the keyboard movement arrows and the mouse trying to make my avatar move from standing position, but to no avail. Interesting effects did result nevertheless; in various runs the avatar was standing in the nothingness and shuddering, or would fall smoothly to the plane and then both the plane and the avatar would fall smoothly down together, or the avatar might stand on the plane and shudder for a little while longer than usual before falling with the plane down into the periwinkle abyss. During all of this, my avatar could only stand and turn in place. No jumping, no running, no walking, no arm waving as it fell. I suspect 3 culprits: The camera, the link-in spot, and the collision mesh. I've tried moving the link-in spot around and it doesn't fix anything that I've seen. In fact, my avatar doesn't even link in at the spot I specified; instead, it links in at one of the corners of my mesh, the one closest to the round, separated hill seen in the screenshot. As for the collision mesh and the camera, I'm not sure what to think. It does say in the export console, "WARNING: Camera has NO regions associated." Well, I'm stuck. If you have any clue as to what might be the problem, I would sure love to hear from you! Preferably before 8 pm Cavern time Thursday, but after that it won't matter when it gets corrected (since I'm presenting the Age (or at least the Blender geometry) to the rest of my programming class on Thursday). Okay, thanks for your help! :geek:
Image


Here's the output produced by exporting:

Compiled with Python version 2.5.
Checking for installed Python... got it!
Exporting C:\Program Files\Ubi Soft\Cyan Worlds\Myst Uru Complete Chronicles\dat
\carbo.age ...
Args are e_age
['e', 'age']
Exporting age carbo
[AlcScript Parser]
Contents of AlcScript:


None
#########################################
##
## => Exporting page Textures -1 <=
##
#########################################
#########################################
##
## => Exporting page BuiltIn -2 <=
##
#########################################
#########################################
##
## => Exporting page mainRoom 0 <=
##
#########################################

[Lamp Sunny]
[Light Base]

Diffuse Lighting Enabled
Specular Lighting Enabled
>>> !kLPCastShadows <<<
>>> !kLPShadowOnly <<<

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

[Visual Object Grid.002]
Object's material has 0 texture layers
Drawable object has 3969 vertices
Appending DirectionalLight Sunny as lightobject 0 to object Grid.002
[ShadowCaster]

[SpawnPoint LinkInPointDefault]

@ Saving page Textures -1
@ Saving page BuiltIn -2
@ Saving page mainRoom 0
=> Storing 27033 vertices of geometry...
\/ Unloading page Textures -1
\/ Unloading page BuiltIn -2
\/ Unloading page mainRoom 0
Writing carbo.fni
Writing carbo.xml
Writing carbo.sum
done in 2.83 seconds
Jennifer_P
 
Posts: 729
Joined: Fri Sep 28, 2007 10:54 pm

Re: Falling on a Collision Mesh: Weird Error

Postby Chacal » Wed Dec 12, 2007 5:11 pm

Delete the "Mass" and "el" properties.
Add a "rc" property, type float, value: 6

Basically, your planet is very slippery, it's falling down, and you're falling with it.

I've had days like that.
Last edited by Chacal on Wed Dec 12, 2007 5:14 pm, edited 3 times in total.
Chacal


"The weak can never forgive. Forgiveness is an attribute of the strong."
-- Mahatma Gandhi
User avatar
Chacal
 
Posts: 2508
Joined: Tue Nov 06, 2007 2:45 pm
Location: Quebec, Canada

Re: Falling on a Collision Mesh: Weird Error

Postby Pryftan » Wed Dec 12, 2007 5:11 pm

Yeah, your landscape is now considered an object subject to gravity - it's falling when you link in!
.rilvoohee vehrehnehm vokan pam mahnshootahv rub voohee taygahnehm mahtahntahv
User avatar
Pryftan
 
Posts: 312
Joined: Fri Sep 28, 2007 10:17 pm

Re: Falling on a Collision Mesh: Weird Error

Postby Aloys » Wed Dec 12, 2007 5:13 pm

Ok, first of all get rid of the 'mass' property (or set it to 0), I don't think it is the problem but giving mass to still objects is usually not a good idea.
Why do you have a mass property set to 5 anyway?

[edit]
arg, everyone posting at the same time :lol: So hu.. yeah what they said.
User avatar
Aloys
 
Posts: 1968
Joined: Sun Oct 21, 2007 7:57 pm
Location: France (GMT +1)

Re: Falling on a Collision Mesh: Weird Error

Postby Jennifer_P » Wed Dec 12, 2007 5:22 pm

Ah ha! I bet that's got to be it! I'll test it now...
And I put that in because it said to in the Alcugs Wiki lighting tutorial--Under the section for movable objects! Agh! *bonks head on computer monitor* :oops:
Thanks to everyone who replied at once! :D
Jennifer_P
 
Posts: 729
Joined: Fri Sep 28, 2007 10:54 pm

Re: Falling on a Collision Mesh: Weird Error

Postby Jennifer_P » Wed Dec 12, 2007 5:34 pm

Good bye new friend, hello old friend! Uru has gone back to crashing to the desktop without an error message as soon as I link in. This time though, I suspect the problem may be explained in the error message (see below, bolded) in the Blender console window. Anybody know what the message is trying to say? :|

Compiled with Python version 2.5.
Checking for installed Python... got it!
Exporting C:\Program Files\Ubi Soft\Cyan Worlds\Myst Uru Complete Chronicles\dat
\carbo.age ...
Args are e_age
['e', 'age']
Exporting age carbo
[AlcScript Parser]
Contents of AlcScript:


None
#########################################
##
## => Exporting page Textures -1 <=
##
#########################################
#########################################
##
## => Exporting page BuiltIn -2 <=
##
#########################################
#########################################
##
## => Exporting page mainRoom 0 <=
##
#########################################

[Lamp Sunny]
[Light Base]

Diffuse Lighting Enabled
Specular Lighting Enabled
>>> !kLPCastShadows <<<
>>> !kLPShadowOnly <<<

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

[Visual Object Grid.002]
Object's material has 0 texture layers
Drawable object has 3969 vertices
Appending DirectionalLight Sunny as lightobject 0 to object Grid.002
[ShadowCaster]

[SpawnPoint LinkInPointDefault]

@ Saving page Textures -1
@ Saving page BuiltIn -2
@ Saving page mainRoom 0
=> Storing 27033 vertices of geometry...
\/ Unloading page Textures -1
\/ Unloading page BuiltIn -2
\/ Unloading page mainRoom 0
Writing carbo.fni
Writing carbo.xml
Writing carbo.sum
done in 2.83 seconds
Exporting C:\Program Files\Ubi Soft\Cyan Worlds\Myst Uru Complete Chronicles\dat
\carbo.age ...
Args are e_age
['e', 'age']
Exporting age carbo
[AlcScript Parser]
Contents of AlcScript:


None
#########################################
##
## => Exporting page Textures -1 <=
##
#########################################
#########################################
##
## => Exporting page BuiltIn -2 <=
##
#########################################
#########################################
##
## => Exporting page mainRoom 0 <=
##
#########################################

[Lamp Sunny]
[Light Base]

Diffuse Lighting Enabled
Specular Lighting Enabled
>>> !kLPCastShadows <<<
>>> !kLPShadowOnly <<<

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

[Visual Object Grid.002]
Object's material has 0 texture layers
Drawable object has 15625 vertices, processing can take some time...
Appending DirectionalLight Sunny as lightobject 0 to object Grid.002
[ShadowCaster]

[SpawnPoint LinkInPointDefault]

@ Saving page Textures -1
@ Saving page BuiltIn -2
@ Saving page mainRoom 0
C:\Program Files\Blender Foundation\Blender\.blender\scripts\alc_hsStream.py:118
: DeprecationWarning: 'H' format requires 0 <= number <= 65535
def Write16(self,data):

=> Storing 107881 vertices of geometry - this can take some time....
\/ Unloading page Textures -1
\/ Unloading page BuiltIn -2
\/ Unloading page mainRoom 0
Writing carbo.fni
Writing carbo.xml
Writing carbo.sum
done in 16.04 seconds
Jennifer_P
 
Posts: 729
Joined: Fri Sep 28, 2007 10:54 pm

Re: Falling on a Collision Mesh: Weird Error

Postby Aloys » Wed Dec 12, 2007 5:37 pm

And I put that in because it said to in the Alcugs Wiki lighting tutorial


Hahaha.. :)
To avoid that in future I added a short warning in the wiki article.
User avatar
Aloys
 
Posts: 1968
Joined: Sun Oct 21, 2007 7:57 pm
Location: France (GMT +1)

Re: Falling on a Collision Mesh: Weird Error

Postby Aloys » Wed Dec 12, 2007 5:45 pm

About that new error:
I see your Grid.002 object (I guess it's the ground) has over 15000 vertices, that is a lot. Way too much for a single object. I'm not sure that's the cause of your crash but it's worth giving it a try.. Try cutting your object in two pieces or more like this:
Go to Edit Mode, select a large amount of vertices by using the Border Select tool [b] and drawing a large rectangle. Then hit [P] to separate these vertices and create a new object.
User avatar
Aloys
 
Posts: 1968
Joined: Sun Oct 21, 2007 7:57 pm
Location: France (GMT +1)

Re: Falling on a Collision Mesh: Weird Error

Postby Jennifer_P » Wed Dec 12, 2007 6:04 pm

You've done it Aloys! The error has disappeared! /dance Whoopee, yeah, hooray!!! :D :D :D
But man, I feel weird linking into a stable Age now... :P
Jennifer_P
 
Posts: 729
Joined: Fri Sep 28, 2007 10:54 pm

Re: Falling on a Collision Mesh: Weird Error

Postby Aloys » Wed Dec 12, 2007 6:09 pm

Jennifer_P wrote:You've done it Aloys! The error has disappeared! /dance Whoopee, yeah, hooray!!! :D :D :D

:)

Jennifer_P wrote:I feel weird linking into a stable Age now...

I can help with that too if you want.. :D
User avatar
Aloys
 
Posts: 1968
Joined: Sun Oct 21, 2007 7:57 pm
Location: France (GMT +1)

Next

Return to Building

Who is online

Users browsing this forum: No registered users and 0 guests