|
|
Post by zircher on Jul 13, 2004 22:09:35 GMT 1
I tried to use the SET CAMERA TO FOLLOW command in my demo program and I'm out somewhere in the great blue yonder. At first I thought it might be a 1.054 glitch, but I was able to use the command in other programs.
When I tried to print the camera location after using the command, I got some really strange values. Is there anything in the wrapper that might be trying to override the camera location?
The POINT CAMERA command is working fine, so it isn't a rotation issue as far as I can tell.
--
TAZ
|
|
|
|
Post by Kjelle69 on Jul 14, 2004 0:49:45 GMT 1
no, nothing at all in he Wrapper that affects the camera. what were you trying to follow?
|
|
|
|
Post by zircher on Jul 14, 2004 4:59:54 GMT 1
I'm trying to follow the model, but the way that SET CAMERA TO FOLLOW works is that it applies a linear and angluar offset from a given set of coordinates. In theory, there should be no problem. But, camera position x() and the others are returning some strange values. Given:
text 10,200, "camNW XYZ "+str$(cam.Pos.x)+"/"+str$(cam.Pos.y)+"/"+str$(cam.Pos.z)
text 10,210, "model XYZ "+str$(object position x(MeshModel))+"/"+str$(object position y(MeshModel))+"/"+str$(object position z(MeshModel))
text 10,220, "camDB XYZ "+str$(camera position x())+"/"+str$(camera position y())+"/"+str$(camera position z())
I get:
camNW XYZ -1/2/50
model XYZ 2.75380516052/-6.10245275497/9.85373210907
camDB XYZ -1.#IND/-1.#IND/-1.#IND
Very strange.
--
TAZ
|
|
|
|
Post by Kjelle69 on Jul 14, 2004 5:15:56 GMT 1
wow, that'S funky. I honestly can't imagine the wrapper is causing that... but VERY strange nonetheless.
I'll take a look later and see if using Newton commands somehow messes up the camera position commands.
by the way, how's the demo going?
|
|
|
|
Post by zircher on Jul 14, 2004 16:36:47 GMT 1
It's going well, I have my son designing a second DoGA model that I plan to convert into another rag doll so I have them slug it out in a ring or a cage match. Ragdoll deathmatch puppet combat, anyone?
--
TAZ
|
|
|
|
Post by Kjelle69 on Jul 14, 2004 16:54:46 GMT 1
hmmm... in my basic ragdoll code example, the camera position commands work exactly as expected... must be something in your code that's causing it....  |
|
|
|
Post by zircher on Jul 14, 2004 18:37:31 GMT 1
I'll probably ditch it for now and just roll my own camera control code. In your demo, you have a cam UDT. Does that serve any purpose beyond holding the camera location? Does Newton use it in some way?
--
TAZ
|
|
|
|
Post by Kjelle69 on Jul 15, 2004 1:01:45 GMT 1
nope, that's just some code I usually use for camera placement / orientation. it has nothing to do with Newton.
|
|
|
|
Post by zircher on Jul 16, 2004 19:43:04 GMT 1
I found the glitch in SET CAMERA TO FOLLOW. It was my own mistake. For some reason I thought smoothing was from 0.0 to 1.0 and not 1.0 to 100.0. When I set it to 0.2, DBP did not complain, but it had a cow trying to use it.
--
TAZ
|
|
|
|
Post by Kjelle69 on Jul 17, 2004 1:56:09 GMT 1
hehehehe... I couldn't get that command to work either.. I think I was making the same mistake.
glad it isn't a problem with the wrapper! ;D
|
|
