Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

Author
Message
madcaddy
23
Years of Service
User Offline
Joined: 20th Jan 2003
Location:
Posted: 26th Aug 2003 01:04
I saw this new command in U5 which looked great! Ive had a play with it and achieved great results with cubes, but use it with a humanoid model for example and its no good.. anyone else found this?
Dreamora
23
Years of Service
User Offline
Joined: 20th Sep 2002
Location: Switzerland
Posted: 26th Aug 2003 02:34
what do you mean exactly by "its no good"?
Codger
23
Years of Service
User Offline
Joined: 23rd Nov 2002
Location:
Posted: 26th Aug 2003 04:20
are you using the default camera (0)? This command only is effective with default camera. I have used it with models and they are fine in my program

System
PIII 650 MZ H.P. Pavillion
394 Mem GeForce 4 400MX
Mentor
23
Years of Service
User Offline
Joined: 27th Aug 2002
Location: United Kingdom
Posted: 26th Aug 2003 12:26
it`s pixel perfect object selection? how can it be no good?, works perfectly here, maybe a code example rather than some vague "no good" would be in order.

Mentor.
madcaddy
23
Years of Service
User Offline
Joined: 20th Jan 2003
Location:
Posted: 26th Aug 2003 15:06 Edited at: 26th Aug 2003 15:08
ok sorry for the vagueness, yep im using the default camera and i tried it with the Colz model that comes with darkbasicpro. he was inside a cube with the cull flag set to 0 if that might have affected it. i just used a line like this:



by no good i mean there wasnt the pixel perfectness that i had with cubes - there were often large areas that didnt return a 2.

thanks
madcaddy
23
Years of Service
User Offline
Joined: 20th Jan 2003
Location:
Posted: 26th Aug 2003 15:24
well waddya know i tried the same thing with the ship model and its perfect! could the fact that colz has animation data have affected it?
spooky
23
Years of Service
User Offline
Joined: 30th Aug 2002
Location: United Kingdom
Posted: 26th Aug 2003 15:59
I see your problem! Run code in source box below and you will see where problem lies. It's as if the object is in a different place for the pick object command. I also note that pick object is SOOOOO SLOOOOWWWWW with that particular object.

The programmer formerly known as sonic
spooky
23
Years of Service
User Offline
Joined: 30th Aug 2002
Location: United Kingdom
Posted: 26th Aug 2003 16:26
Weird - happens with some objects and not others - I will post as a bug!

The programmer formerly known as sonic
spooky
23
Years of Service
User Offline
Joined: 30th Aug 2002
Location: United Kingdom
Posted: 26th Aug 2003 16:37
Here is what code produces:



I have now posted in bug forum to see what the mods think.

The programmer formerly known as sonic
haggisman
23
Years of Service
User Offline
Joined: 26th Aug 2002
Location: United Kingdom
Posted: 26th Aug 2003 18:12
Im not supprised its slow, you are doing something like 768 pick tests on a 2000 poly object. It could come to figure of 1536000 intersection tests every frame.
spooky
23
Years of Service
User Offline
Joined: 30th Aug 2002
Location: United Kingdom
Posted: 26th Aug 2003 19:16
Yes, I know haggisman, it was a stupid statement to make as you would only ever do one pick object command each frame. I had to do that many picks to point out bug. However, replace object with a few simple cubes and pick object is blindingly quick.

The programmer formerly known as sonic
madcaddy
23
Years of Service
User Offline
Joined: 20th Jan 2003
Location:
Posted: 26th Aug 2003 19:32
yep that seems to be exactly what i noticed. the miko.x object has the same problem however use the .3ds version and its fine again. i wonder what it is about certain models that gives the bug..

Login to post a reply

Server time is: 2026-07-23 03:27:16
Your offset time is: 2026-07-23 03:27:16