lissesul, probably because your level geometry is tiny. If it works then it works :) I was just pointing out one of blitz's problems that relates to the camera ranges. If you use a viewer like the B3D viewer in pipeline which lets you specify ranges you can see the effects pretty easily.
you should check what scale your level geometry is built to. I have mine as 1 blitz unit = 1 meter. So the largest level I can do would be about 10 kilometers, not that I'll be doing one that large. But my current level I'm working on is 500x500 meters and has the camera set to 1:500
you should really try an fit your camera range to the scale of your level as longer ranges can slow thing down and cause visual glitches, same with fog etc.
also sometimes gometry cn load up with the normals cacing the wrong way so the model is infact insid out, surprisingly it can sometimes be hard to tell lol.
you should check what scale your level geometry is built to. I have mine as 1 blitz unit = 1 meter. So the largest level I can do would be about 10 kilometers, not that I'll be doing one that large. But my current level I'm working on is 500x500 meters and has the camera set to 1:500
you should really try an fit your camera range to the scale of your level as longer ranges can slow thing down and cause visual glitches, same with fog etc.
also sometimes gometry cn load up with the normals cacing the wrong way so the model is infact insid out, surprisingly it can sometimes be hard to tell lol.