Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualVangoule

Posted 31 January 2013 - 05:27 PM

The value was found by trial and error but it's the point at which the two planes overlayer eachother. Though the value came to be that number because of the scaling and things. I changed the order in which i scale and translate everything and now the value is 168 which is the equivelant of the 'right' value from 0. Here's the source code now. I'll try and upload the actual application aswell. However, i'm not sure if it'll run on your machine. This should allow you too see what's happening. The planes have different height values so you can tell them apart. Moving the camera on to a plane should subdivide it once. It can be downloaded here: http://www.mediafire.com/?lk4zn5lmga3h99c

#5Vangoule

Posted 31 January 2013 - 05:19 PM

The value was found by trial and error but it's the point at which the two planes overlayer eachother. Though the value came to be that number because of the scaling and things. I changed the order in which i scale and translate everything and now the value is 168 which is the equivelant of the 'right' value from 0. Here's the source code now. I'll try and upload the actual application aswell. However, i'm not sure if it'll run on your machine. This should allow you too see what's happening. The planes have different height values so you can tell them apart. Moving the camera on to a plane should subdivide it once.

#4Vangoule

Posted 31 January 2013 - 05:19 PM

The value was found by trial and error but it's the point at which the two planes overlayer eachother. Though the value came to be that number because of the scaling and things. I changed the order in which i scale and translate everything and now the value is 168 which is the equivelant of the 'right' value from 0. Here's the source code now. I'll try and upload the actual application aswell. However, i'm not sure if it'll run on your machine. This should allow you too see what's happening. The planes have different height values so you can tell them apart.

#3Vangoule

Posted 31 January 2013 - 05:18 PM

The value was found by trial and error but it's the point at which the two planes overlayer eachother. Though the value came to be that number because of the scaling and things. I changed the order in which i scale and translate everything and now the value is 168 which is the equivelant of the 'right' value from 0. Here's the source code now. I'll try and upload the actual application aswell. However, i'm not sure if it'll run on your machine. This should allow you too see what's happening.

#2Vangoule

Posted 31 January 2013 - 05:17 PM

The value was found by trial and error but it's the point at which the two planes overlayer eachother. Though the value came to be that number because of the scaling and things. I changed the order in which i scale and translate everything and now the value is 168 which is the equivelant of the 'right' value from 0. Here's the source code now:


#1Vangoule

Posted 31 January 2013 - 05:16 PM

The value was found by trial and error but it's the point at which the two planes overlayer eachother. Though the value came to be that number because of the scaling and things. I changed the order in which i scale and translate everything and now the value is 168 which is the equivelant of the 'right' value from 0. Here's the source code now:


PARTNERS