Change Details

Here are some test imports I did on my R5 7600: | Faces | 180k | 270k | 450k | | Time | 200s | 500s | 1800s | These data points **very** closely match a runtime complexity of n^2. I highly doubt quadratic time is actually required for what should be a simple file format conversion, the code is probably just written in a very inefficient way and could be improved. While this issue only has a small effect on the average model import, it is //extremely// limiting when high poly imports //are// necessary. For example, I was trying to import reconstructed point clouds as reference for terrain making, which can easily have over a million faces.

Here are some test imports I did on my R5 7600: | Faces | 180k | 270k | 450k | | Time | 200s | 500s | 1800s | These data points **very** closely match a runtime complexity of n^2. I highly doubt quadratic time is actually required for what should be a simple file format conversion, the code is probably just written in a very inefficient way and could be improved. The fact that the time can be significantly reduced by separating the object into multiple meshes also indicates this (e. g. splitting the 450k object into 16 objects resulted in only 5m). While this issue only has a small effect on the average model import, it is //extremely// limiting when high poly imports //are// necessary. For example, I was trying to import reconstructed point clouds as reference for terrain making, which can easily have over a million faces.

Here are some test imports I did on my R5 7600: | Faces | 180k | 270k | 450k | | Time | 200s | 500s | 1800s | These data points **very** closely match a runtime complexity of n^2. I highly doubt quadratic time is actually required for what should be a simple file format conversion, the code is probably just written in a very inefficient way and could be improved. The fact that the time can be significantly reduced by separating the object into multiple meshes also indicates this (e. g. splitting the 450k object into 16 objects resulted in only 5m). While this issue only has a small effect on the average model import, it is //extremely// limiting when high poly imports //are// necessary. For example, I was trying to import reconstructed point clouds as reference for terrain making, which can easily have over a million faces.