Hey all,
So… I’ve been working on a project for a few months and had to put it on hiatus. There is a region in my model that has RC crash. I’ve started the model from scratch at least 10 times (which is a ton of time as it’s close to 2k 20mpx pictures) and hit the same error.
It seems to do with some 100 pictures when I texture - when I turn those camera angles off I can texture parts of the model, when on, it crashes.
Had Wishgranter and a few others invested in this issue about 4 months ago, sent about 6GB of files up for inspection but never heard back (understandable). I can still send a link if requested, I think you’d be interested in this issue as it is bound to the raw image set rather than some error that I introduced (I’m pretty sure about that). I think it’s the way I captured the large scene (inside building, swing outside where the reconstruction didn’t align perfectly with the inside of the building, having an outside wall clip an inside wall, etc.). No way to tell which image or set of images is causing the crash.
I can find workarounds for the texturing area, but would be great if the problem is identified so I know how to avoid it or make sure people know what the problem is. PM me if you need an updated link to the RPROJ and image files.
Thanks
Castlenock wrote:
Hey all,
So… I’ve been working on a project for a few months and had to put it on hiatus. There is a region in my model that has RC crash. I’ve started the model from scratch at least 10 times (which is a ton of time as it’s close to 2k 20mpx pictures) and hit the same error.
It seems to do with some 100 pictures when I texture - when I turn those camera angles off I can texture parts of the model, when on, it crashes.
Had Wishgranter and a few others invested in this issue about 4 months ago, sent about 6GB of files up for inspection but never heard back (understandable). I can still send a link if requested, I think you’d be interested in this issue as it is bound to the raw image set rather than some error that I introduced (I’m pretty sure about that). I think it’s the way I captured the large scene (inside building, swing outside where the reconstruction didn’t align perfectly with the inside of the building, having an outside wall clip an inside wall, etc.). No way to tell which image or set of images is causing the crash.
I can find workarounds for the texturing area, but would be great if the problem is identified so I know how to avoid it or make sure people know what the problem is. PM me if you need an updated link to the RPROJ and image files.
Thanks
Hello,
have you also tried to do all of that anew in the latest version of RealityCapture? Which version and build?
Can I please also have you PC configuration like the one in my signature?
Links to the forum topics dealing with this issue would also help a lot.
These seem to be similar to your issue:
Problem of reconstruction
Surface issues
Hi Castlenock
Somehow cant find any data on my disk, ( had some issues with HDDs in RAID ) so it could be they get lost and so have not seen them again… 
Can take a look with TeamViewer directly on your data ? If yes send me a email.
Lubenko,
Thanks for the reply - here is the original request back in the day, before I got my head wrapped around it - the last post there is part of the reason I had a hiatus but also has pictures of the project: Need a bit of help
My specs are i7 4Ghz, 64GB of RAM, raided SSD drives, 2 x 980 ti’s. I’ve tried this on entirely different machines with high specs and had the same result, I’ve also completely rebuilt my computer twice from the ground up and have hit the same error. Really think it’s something you haven’t seen before which is why I’m underlying it.
RC crashes with a dump file, that I spent some time analyzing with the likes of Wishgranter, I’ll see if I can dig those messages/threads up.
There isn’t a big rush on this at the moment, I’m just not sure if my ‘back up’ plan on rendering that part of the scene can work, if it can’t (it should), than I’m in a bit of a spot, but I’m not anxious about that for a while yet.
Wishgranter, I’ll PM you, I think I loaded the most recent set of files onto Dropbox, so will send you that link. Teamviewer is possible later in the week when I can carve up some time.
As per usual highly appreciative, but again flagging it more as something you might find interesting than ‘I need this fixed’ at the moment. Pretty darn sure it isn’t a setting error, happens only at the final stage of texturing a part of the model when those 100 images or so have the ‘texture and colorize’ box ticked.
Ah should note regarding the thread I linked - at that point it was a myriad of issues (such as not having proper PSU power) - I managed to widdle all the problems with that project down to this texture - everything works fine (alignment, unwrapping), including texturing, unless I try to texture with those pictures on than it crashes out (sometimes with a dump report, sometimes not).
I’ve used every version of RC released since Feb for this model, hit the same crash every time.
Wishgranter, once I manage to send you the link, it’s the back room (just so a viewer can peak their head in there, don’t need a ton of detail) with the image set in there. You’ll notice how I went to the front of the building, outside to scan some artwork, and wrapped around the building for parallax and detail for the eventual skydome. I think that ‘wrap around’ of the outside wasn’t dead on accurate and clipped the inside of the back room - that’s what it looked like when I started cleaning up the model in Modo…
More detail, sending Wish a link in 2 seconds, thanks all!
Room Issue 1.jpg
Room Issue 2.jpg
Hey Castlenock,
would also be interested in the outcome.
By clipping you mean an outside surface is overlapping one on the inside so that the back of the outside surface is visible on the inside?
Have you tried adding a CP in a window there just to give RC a shove in the right direction?
Would not solve the issue in RC itself but at least you would be able to finish.
And ideally, such a situation should not occur at all.
On the other hand it might just explain a few mysterious crashes…