GLROAMPatch is producing gaps and occacional stack overflows.
The gap problem was solved a few moths ago, at least I thought so, so this is a bit strange. The gaps are small but they are still there.
A much more serious problem is occasional stack overflows. The exception is raised in GLROAMPatch line 359 'Split(Base)'. I am not sure exactly when this error has been introduced, but I think it must have been within the last few months.
I will most bitmaps shortly
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The gap problem was solved a few moths ago, at least I thought so, so this is a bit strange. The gaps are small but they are still there.>>
Yes, for deep slopes small gaps appear remains. It's an old problem from 2009 after Lin's work with roampatch unit. I still can't find the bug to fix it.
PW
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is a nice idea with a tile based surface/terrain object but there are just so many problems with the terrain renderer. It is hard to make it work properly, the gap problem is still there, the tessellation in GLROAMPatch is unstable (crashes), the performance is not that good, and on top of that it does not support blank data values. I have invested many many hours struggling with the terrain renderer and I really want to use it but now I am considering not to use it any more. The whole set of terrain and height data components needs to be reworked - at the least Lin should fix the bugs introduced back in 2009. I am still a big fan of GLScene though :)
Lars
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
GLROAMPatch is producing gaps and occacional stack overflows.
The gap problem was solved a few moths ago, at least I thought so, so this is a bit strange. The gaps are small but they are still there.
A much more serious problem is occasional stack overflows. The exception is raised in GLROAMPatch line 359 'Split(Base)'. I am not sure exactly when this error has been introduced, but I think it must have been within the last few months.
I will most bitmaps shortly
Bitmaps
Lars wrote:
It is a nice idea with a tile based surface/terrain object but there are just so many problems with the terrain renderer. It is hard to make it work properly, the gap problem is still there, the tessellation in GLROAMPatch is unstable (crashes), the performance is not that good, and on top of that it does not support blank data values. I have invested many many hours struggling with the terrain renderer and I really want to use it but now I am considering not to use it any more. The whole set of terrain and height data components needs to be reworked - at the least Lin should fix the bugs introduced back in 2009. I am still a big fan of GLScene though :)
Lars