Sign in to follow this  

All things are the same but render result

Recommended Posts

Living    110
In our games, there is one problem about rendering speedTree. We start our game without changing anything, but all the speedTrees are rendered correctly sometimes and all are disappear sometimes.

I doubt that this problem may be caused by occlusion culling first. But I found that the vertexes were pushed to render queue. All the object in render queue would be rendered.

Then, I debug the program. I delete all the speedTrees but the test one on the map. I contrast the data about the vertex of speedTree disappeared with the correctly situation.

The vertexes, indexes, matrix and bounding box are the same when building the speedTree. And all the vertexes and indexes would pass to the D3D function called DrawIndexedPrimitive(). Before the function calledd, the vertexes and indexes are the same.

At last, I printed the render state in these two situations before calling DrawIndexedPrimitive(). And the render state are also the same.

I don't know why the speedTree can be render correctly.

Share this post

Link to post
Share on other sites
remigius    1172

Well, if the data & states are the same, it'll be hard to point out what can be causing this. Isn't there anything different at all between the two cases? Maybe something a bit more remote from the rendering, like a missing texture or alpha map?

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this