Re: [CrystalSpace] #970: Clipping problems for space warping portals

"CrystalSpace" <[email protected]> Fri, 03 Aug 2012 16:52:27 -0000
Newsgroups gmane.comp.graphics.crystalspace.tracker
Message-ID <[email protected]>
#970: Clipping problems for space warping portals
--------------------+-------------------------------------------------------
 Reporter:  kickvb  |       Owner:  jorrit
     Type:  defect  |      Status:  new   
 Priority:  minor   |   Milestone:        
Component:  engine  |     Version:  V2.1  
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by jorrit):

 Having only one sector per movable isn't really possible. Let's take a
 case where the origin of a mesh is in sector A but the mesh is big enough
 to traverse a portal to sector B. In the solution of only one sector per
 movable the mesh would be registered in sector A and have a list of
 portals containing the portal to sector B. That's fine when you are
 rendering sector B through the portal. However, if you are in sector B and
 the portal from A to B is not visible you have no way of knowing that you
 should actually render that mesh.

 I don't understand the third solution?

-- 
Ticket URL: <http://www.crystalspace3d.org/trac/CS/ticket/970#comment:1>
CrystalSpace <http://www.crystalspace3d.org/>
Free open-source 3D SDK.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/