I tried the same pair of models again today and it can't be loaded after 1.5 hrs even after I reduced the number of meshes greatly (to only 0.5 million triangles). I started to doubt it may be because I used COLMAP for reconstruction and meshlab for conversion from .ply to .obj with texture computation from vertex attributes. The meshes of model is generated to be round which have many subdivisions after conversion. So even though the texture image size is also 8192 x 8192 pixelwise, the file is 152 MB so cannot be loaded. I will leave it loading tonight.

1.5 hours definitely sounds excessive!

Are you importing with collisions enabled? If so, I'd recommend switching them off for the time being - if you're using the simple model import wizard, it's the 'Collision Type: No Collision' setting you want:

https://developer.valvesoftware.com/wiki/File:Tutorial_objimport.png

Also, try opening the model in something like Blender just to make sure it looks reasonably sane. I've used Meshlab for some cleanup tasks before, but I don't think I've ever gone directly from Meshlab into the import tools.

Hopefully we'll get you sorted out sooner or later!

Yes, SteamVR successfully loaded it in after one night. I don't know how long it has spent. Thanks! I disabled collision generation at the first step since its geometry is already complex. I noticed console was stuck at generating .vmat and .vtex during the long wait, so (still) texture is the main problem. I don't know if it's due to COLMAP or conversion from .ply to .obj. I will try to converting to .fbx type today.

Also hope SteamVR developers can add hang watchdog also in the process when loading model into model editor. Every time when I don't see a hang detection window, I may assume there is some internal error.

What format are your texture images in? They should certainly not take anywhere near that long to import.

(To compare, one of my photogrammetry scenes typically takes something like 10-20 minutes to import, complete with physics collisions enabled. I'm wondering if you've hit a pathological case somewhere in the tools. If possible, it would be very useful to have a look at your source files in order to get a better look at what's happening!)

Sorry for late response. I was trying other algorithms for the same dataset. I have identified the reason causing long loading and that is the model. My texture file is in png and it is fine. The model generated by COLMAP is distinct from those generated by other softwares like RealityCapture or openMVG+openMVS. It has an overly complicated mesh for model so when looking into the texture file, I found every several pixels (texels) in a square is mapped to a small triangle mesh in the model, which should just be a smooth surface! Consequently, even a plane has been divided into a lot of pieces, the loading is extremely slow. I always follow the same steps to load model in SteamVR environment so I can tell it is fine.