Mesh polygon limit?

I am trying to do extremely hi-res mesh in Steam version of Reality Capture. It works amazingly quickly but gives me blue screen of death every time I am trying anything big, while working just fine with not that big/ hi-res meshes around 5-10 mil.

In Photoscan I once did 790 mil of triangles for example in a single chunk. (took few days)

So I wonder what is maximum polycount I can set for “High Detail” ? and how could I do big things in several chunks ?

Another question is how could I get proper color texture on imported retopo mesh? Every time I tried to do it I got a kind of messy texture.

Also if it’s possible to export 16 bit color texture or even 32 bit exr file like in Photoscan? It’s important for having more delighting options.( to remove shadows etc.)

Hi kir238

I am trying to do extremely hi-res mesh in Steam version of Reality Capture. It works amazingly quickly but gives me blue screen of death every time I am trying anything big, while working just fine with not that big/ hi-res meshes around 5-10 mil.

BSOD mean your HW cant keep with RC ( make screenshot of the detailed info so we can see more details what it cause ) that can be multiple issues for the crash

Please fill out your HW spac in the signature here ucp.php?i=profile&mode=signature

So I wonder what is maximum polycount I can set for “High Detail” ? and how could I do big things in several chunks ?

there is no limit on polys as RC is not limited this way adn we have no chunks, we have COMPONENTS and the model is cut in PARTS fully automatic way so you nod need to care about it. You can reconstruct models even with Bilions of triangles without problem.

Another question is how could I get proper color texture on imported retopo mesh? Every time I tried to do it I got a kind of messy texture.

Some screenshots possible ? if you NOT move the model in external app and you have good aligned data then you get good Tx always.

Also if it’s possible to export 16 bit color texture or even 32 bit exr file like in Photoscan? It’s important for having more delighting options.( to remove shadows etc.)

Not yet possible, only 8bits

Hi Wishgranter, thank you for your help.

The texture problem seems disappeared . At least now I am getting ok textures,. Can’t recreate the problem any more. It still tells me about some missing “info” file which I always set to “true” when exporting a mesh but no “info” file is actually being recorded to a disk. I usually save retopo mesh with “lr” suffix added. Maybe it should have same, original mesh name or something?

The BSD problem with big meshes (500mil) and around 200 photos is still persistent. I still see BSD somewhere in the middle of a mesh generation. I updated my info so I wonder if it’s something with not enough memory or something else?

No other program would cause BSD on my PC.

Btw, how much free space on disk C: for temporary files such a big mesh may require? I see only 1gb left of 22gb free disk space on my SSD at the moment of crash. Can the soft use another drive for temp files?

Hi kir238

The texture problem seems disappeared . At least now I am getting ok textures,. Can’t recreate the problem any more. It still tells me about some missing “info” file which I always set to “true” when exporting a mesh but no “info” file is actually being recorded to a disk. I usually save retopo mesh with “lr” suffix added. Maybe it should have same, original mesh name or something?

just export in empty folder and you will see *.rcinfo file is present if enabled.
Then when importing the model you must have *.rcinfo file next to it and renamed to same OBJ-FBX filename so RC know what *infofile to use for that particular import task.

The BSD problem with big meshes (500mil) and around 200 photos is still persistent. I still see BSD somewhere in the middle of a mesh generation. I updated my info so I wonder if it’s something with not enough memory or something else?

No other program would cause BSD on my PC.

Its because other sw cant use CPU and GPU to their limits as RC. We have sen this many times already !
So you PSU ( highly possibly but you still have not posted precise crash info to say more about it ) is the key component causing BSOD

Btw, how much free space on disk C: for temporary files such a big mesh may require? I see only 1gb left of 22gb free disk space on my SSD at the moment of crash. Can the soft use another drive for temp files?

go to WORKFLOW->SETTINGS->CACHE LOCATION and use CLEAR CACHE button. then highly recommend to set CACHE to custom location, on some large and fast drive and clear the CACHE form time to time, but never when RC is running.

Thanks again for the tips.

It’s what I get with BSD screen : SYSTEM_THERED_EXEPTION_NOT_HANDLED(SamsungRapidDiskFltr.sys)

Samsung is my system SSD, so I tried it with Win10 on another SSD drive (same PC) and seems RC is working now. Not sure if it’s that specific drive or Win 8.1 what caused BSD. Too bad I can’t stand Win10 and bought Win 8.1 specifically for work purpose but it’s not a big deal. With W10 and that another drive I get those info files too.

Still I came to one more problem: mesh export does too many not that big parts but only single texture tiff file, even with “Export to single texture file” set to “false” . I expected each part would have it’s own texture. Is it possible somehow?

ps. Should I unwrap each of those parts manually first and re-import them back?
Can I specify parts sizse in poly ? For example something around 15 mil loadable in Zbrush?

Hi kir238

First update your BIOS, Windows updates, latest drivers and etc. Then try it again an let see how its behave after this step.