Joy: Got my DB Pro on Thursday so decided to take Friday off work to mess with it.
Sad: Fell at the first hurdle when I found POINT CAMERA doesn't work! Check out the attached code. Can someone confirm that ir doesn't work on their copy too? Works fine in Darkbasic though.
Cheers.
P.S. Apart from the odd "funny" it;s looking good!
` Project: POINT CAMERA Bug
` DBPro Version: Patch 1 installed (Can we have the version number on the About Box please?)
` The POINT OBJECT command does not work! POINT CAMERA does though.
` Instead of pointing an object to a 3D position, it seems to setup a step value for the specified object.
` The following code shows this (you have to be quick as object 2 exits stage right very quickly in DB Pro,
` try seting the sync rate really low to see qhat it's doing):
sync on
` NOTE: In DB Pro, set the sync rate to 5 otherwise you will not see what's going on
sync rate 30
autocam off
` Create an initial object
make object sphere 1, 20
position object 1, 100, 0, 0
` Create a second object
make object cone 2, 20
position object 2, 0, 0, -100
` Put camera overhead and looking down
position camera 0, 500, 0
point camera 0, 0, 0
` Point object 2 at object 1 ( I've hard-coded the values so it's easier to read)
point object 2, 100, 0, 0
repeat
` Move object 2 towards object 1 by a unit of 1 per frame
move object 2, 1
sync
until mouseclick()
` This code works fine in Darkbasic but not in DB Pro.
` Change POINT OBJECT values to POINT OBJECT 2, 0, 0, 0
` Now the object does not move.
` Change POINT OBJECT values to POINT OBJECT 2, 1, 0, 0
` Now the object moves slowly right.
` As far as I can tell, the POINT OBJECT command is setting up a step value for the object.
` For example:
` If POINT OBJECT 2, 100, 0, 0, 0 is used, everytime the MOVE OBJECT 2, 1 command is run,
` the object moves 1 * 100 units in the X direction.
` If you enter MOVE OBJECT 2, 2, the object moves 2 * 100 units in the X direction.
` The same is true if you enter a value in the Y and Z POINT OBJECT values too.