Codemonger
Good call on the unhiding entities. I may use a hybrid of that idea. But i really want to load the meshes as the player gets closer to them, rather than having them already loaded. it would save on memory and allow higher meshpoly counts in smaller areas.
LT entitydistance would prolly be the best bet to check to see if anything was in view. I will automaticly load one more tile around what ever tile the player is sitting on. IE the diagram:
[1:1][2:1][3:1]
[1:2][ P ][3:2]
[1:3][2:3][3:3]
all of the terrain/land squares aroung the player would be drawn.
I think the most difficult part about this is making sure that i can check *which* ones should be drawn. To do this i would certainly need an index or a lookup process. Its really too bad that blitz3d doesnt have db support. This would be an excellent database solution.
Good call on the unhiding entities. I may use a hybrid of that idea. But i really want to load the meshes as the player gets closer to them, rather than having them already loaded. it would save on memory and allow higher meshpoly counts in smaller areas.
LT entitydistance would prolly be the best bet to check to see if anything was in view. I will automaticly load one more tile around what ever tile the player is sitting on. IE the diagram:
[1:1][2:1][3:1]
[1:2][ P ][3:2]
[1:3][2:3][3:3]
all of the terrain/land squares aroung the player would be drawn.
I think the most difficult part about this is making sure that i can check *which* ones should be drawn. To do this i would certainly need an index or a lookup process. Its really too bad that blitz3d doesnt have db support. This would be an excellent database solution.