Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!


1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


#ActualBrother Bob

Posted 22 July 2013 - 12:02 PM

It sounds like you might want to implement a distance check to delete and create VBO's and texture data as the you move around the scene.  If a model will soon be visible, then run an initialization function for that model.  If it's not going to be visible anymore then delete it.  You might have some hick-ups when you move from one area to another.

I certainly would not want to do this every frame for every component.

 

So far as reusing VBO's that have already been created, I'm not sure this would offer you any benefit.  The VBO that is being reused would have to be resized and rewritten, it seems to me that just creating a new one would be the way to go.   I don't imagine that reformatting an existing VBO would offer any performance advantage over simply creating one, it seems like you'd have the same overhead either way.   Then again, I've never tried this, maybe it would. 


#2marcClintDion

Posted 22 July 2013 - 03:05 AM

There is far too much arrogance and out right abuse by site moderators, they are teaching other people to behave this way.  The posts I've made will all be shorty removed and replaced with this notice.  Game development is not the only thing being taught here, bad behavior is being taught as well.


#1marcClintDion

Posted 06 July 2013 - 05:10 PM

It sounds like you might want to implement a distance check to delete and create VBO's and texture data as the you move around the scene.  If a model will soon be visible, then run an initialization function for that model.  If it's not going to be visible anymore then delete it.  You might have some hick-ups when you move from one area to another.

I certainly would not want to do this every frame for every component.  

 

So far as reusing VBO's that have already been created, I'm not sure this would offer you any benefit.  The VBO that is being reused would have to be resized and rewritten, it seems to me that just creating a new one would be the way to go.   I don't imagine that reformatting an existing VBO would offer any performance advantage over simply creating one, it seems like you'd have the same overhead either way.   Then again, I've never tried this, maybe it would. 


PARTNERS