@Stinkfist0 reported that on his computers the initial load of 2d map images is the current perf bottleneck - stalls a compu for even 20secs before the images are loaded and then normal use works ok.
this is not too surprising as those map images are a quite a lot of data and are processed in a perhaps bit heavy way to gl textures.
i bet e.g. loading DDS textures directly might be lighter.
vizi 0.1 didn't have this prob as it didn't use textures at all in fact but created the roads also as 3d geom .. which, weird enough, is I think faster and lighter.
this is not a showstopper but if / when we get to perf optimizations seems worth a check if this bottleneck can be improved.
even pre-converting to DDS and hosting the required set of tiles ourselves (in s3 or somewhere) might be worthwhile - Adminotech's Meshmoon asset service which can automatically convert etc. might help there.
@Stinkfist0 reported that on his computers the initial load of 2d map images is the current perf bottleneck - stalls a compu for even 20secs before the images are loaded and then normal use works ok.
this is not too surprising as those map images are a quite a lot of data and are processed in a perhaps bit heavy way to gl textures.
i bet e.g. loading DDS textures directly might be lighter.
vizi 0.1 didn't have this prob as it didn't use textures at all in fact but created the roads also as 3d geom .. which, weird enough, is I think faster and lighter.
this is not a showstopper but if / when we get to perf optimizations seems worth a check if this bottleneck can be improved.
even pre-converting to DDS and hosting the required set of tiles ourselves (in s3 or somewhere) might be worthwhile - Adminotech's Meshmoon asset service which can automatically convert etc. might help there.