Changeset 657 for OGRE/trunk/ogre_changes/RenderSystems/Direct3D9/include/OgreD3D9HardwareOcclusionQuery.h

Timestamp:

02/20/06 19:06:03 (18 years ago)

Author:

mattausch

Message:

added ogre dependencies and patched ogre sources

File:

• OGRE/trunk/ogre_changes/RenderSystems/Direct3D9/include/OgreD3D9HardwareOcclusionQuery.h (modified) (5 diffs)

OGRE/trunk/ogre_changes/RenderSystems/Direct3D9/include/OgreD3D9HardwareOcclusionQuery.h

@@ -34 +34 @@
 
 // If you use multiple rendering passes you can test only the first pass and all other passes don't have to be rendered 
-        // if the first pass resultet has too few pixels visible.
+        // if the first pass results has too few pixels visible.
 
-// Be sure to render all occlluder first and whats out so the RenderQue don't switch places on 
+        // Be sure to render all occluder first and whats out so the RenderQue don't switch places on 
 // the occluding objects and the tested objects because it thinks it's more effective..
 
@@ -46 +46 @@
         *
         * Updated on 12/7/2004 by Chris McGuirk
+        * Updated on 4/8/2005 by Tuan Kuranes email: tuan.kuranes@free.fr
   */
 class D3D9HardwareOcclusionQuery : public HardwareOcclusionQuery
@@ -73 +74 @@
                 bool pullOcclusionQuery( unsigned int* NumOfFragments, const HW_OCCLUSIONQUERY flag = HWOCCLUSIONQUERY_FLUSH);
                 unsigned int getLastQuerysPixelcount() { return mPixelCount; }
+        bool isStillOutstanding(void);
 
                 // These functions are optional, it's a simple filter that simply skips some hardware occlusion tests on visible objects only
@@ -82 +84 @@
           *   
                 * Remarks This function allows you to set how often the hardware occlusion query is sent to the driver
-          * if you set it to 0 every hw occlusion test is acctually made. If you set it to 1 only the half of your queries are sent 
-                * 2 will result in 25% of all queries to acctualy be sent. 
+                * if you set it to 0 every hardware occlusion test is actually made. If you set it to 1 only the half of your queries are sent 
+                * 2 will result in 25% of all queries to factually be sent. 
                 * This functionality is here because this class can keep track on visible and none visible objects for you.
           * Once you you set the SkipRate for any hardware occlusion instance it effects all others.
           */
 
-                void setSkipRate( int skip ) { mSkipInterval = skip; }                  // Using 2 only 50 % of the tests are actully made and 3 results in only 33% of the tests. So on.
+                void setSkipRate( int skip ) { mSkipInterval = skip; }                  // Using 2 only 50 % of the tests are actually made and 3 results in only 33% of the tests. So on.
                 int      getSkipRate() { return mSkipInterval; } 
 
@@ -105 +107 @@
                 int                                     mSkipInterval;
                 bool                            mHasOcclusionSupport;
+                bool                            mIsQueryResultStillOutstanding;
 };