Jump to content

  • Log In with Google      Sign In   
  • Create Account

Interested in a FREE copy of HTML5 game maker Construct 2?

We'll be giving away three Personal Edition licences in next Tuesday's GDNet Direct email newsletter!

Sign up from the right-hand sidebar on our homepage and read Tuesday's newsletter for details!


We're also offering banner ads on our site from just $5! 1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


#ActualShawn619

Posted 30 June 2013 - 05:02 PM

Update:

 

I randomly thought of a method that allows me to create a short list of faces to test intersection each frame, instead of testing all faces in the terrain(O(N)) on every frame.

 

With my method, I was able to narrow down the amount of intersection tests from the original 33000(all terrain faces) to ~100 each frame, which is quite manageable and resolved the FPS issue.

 

In computational complexity, I was able to reduce intersection tests from O(N)->O(sqrt(N)).


#1Shawn619

Posted 30 June 2013 - 05:00 PM

Update:

 

I randomly thought of a method that allows me to create a short list of faces to test intersection each frame, instead of testing all faces in the terrain(O(N)) on every frame.

 

With my method, I was able to narrow down the amount of intersection tests from the original 33000(all terrain faces) to ~100 each frame.

 

In computational complexity, I was able to reduce intersection tests from O(N)->O(sqrt(N)).


PARTNERS