Re: pick stops working at distance >= 500 ?

New Message Reply Date view Thread view Subject view Author view

Dirk Luesebrink (crux++at++artcom.de)
Wed, 11 Sep 1996 13:30:40 +0200


i had problems with picking as well. in a project where i created
dragger/manipulator like objects in performer i found picking to be
instable, but i never was able to deduce the reason for that. the
geometries i created used transformations as well. i played around
with various attribute settings for picking and ended with configuring
picking all(not only the nearest), picking backface as well and than
manually sorting the hit list by distance. the sorting was neccesary
because to my surprise i didnt got the picks sorted in by distance.
at least not always. as i said i never could trace down the exact
condition under which the picking breaks. get all intersections and
sorting them at least gave me succesful hits and (squared) distance
sorting wasn't the computational bottleneck.

curious
dirk luesebrink
graphics coder

Jeremy Friesner wrote:
>
> Has anyone ever had a problem where pfChannel->pick() stops
> working when the channel's view coordinate is 500 or more
> units away from the origin?
>
> On our app, picking works fine as long as our "ship" stays
> withing a sphere of radius 500 about the origin, beyond that,
> clicking on objects gives us no hits!?!
>
> -Jeremy
> jfriesne++at++chem.ucsd.edu
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:31 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.