As I have said in other posts, since the new version I experience a lot of crashes.
That was not the case before - it was very rare (if it ever happened).
You guys at RC should have quite a few of crash reports from me by now - anything you can deduce from them?
Hi Götz
Crashing at what part of the processing ?
what is your email used for reporting/uploading the crash reports ?
Sent address via PM…
Another crash after exiting…
Log has been sent.
Error message:
Hi Milos,
not quite sure what screenshots you expect me to provide (by PM that was). :?
I thought there would be enough info in the crash log – silly me! 
Uploaded one with the red failure beam and the console message.
Shouldn’t be any settings because it worked in between with NO CHANGE whatsoever.
I’m still trying to narrow it down.
No luck so far - sometimes it works, sometimes it fails.
Settings unchanged, everything unchanged.
More tomorrow cause I’m off to bed now… *yawn*
I’ve been finding I’m getting a lot more crashes during the alignment stage than i was.
though I’ve sort of figured out why. and can mostly work around it.
I don’t think i was getting this in the past.
you should have lots of crash reports from me.
Hey chris,
good to hear I’m not the only one… 
Although with me it seems to focus more on reconstruction.
I wonder if it’s got something to do with hardware limitation?
What setup do you have?
Mind sharing your work-around?
i’ve got other issues, with reconstruction…
mostly just what happens in the last 10% after all the parts are done. that only has a single core being used.
that is taking more time than depth map generation and all the parts of the mesh…
but crashes in reconstruction i find can be avoided with enough virtual memory, and enough cache space.
I’ve also been getting crashes on texturing, when i use coloured laser scan together with photos. I have to disable the laserscan from texturing to get it to work… could just be with the data i have…
but for me the aligmnent stage has generated many crash reports.
i find i can’t align photos from different days at the same site. always must align each day shoots by itself, and then i can align those components only is i have component only to true. otherwise it will crash.
I can’t remember ever having this issue with old versions of rc.
You might have given me a crucial hint - I did indeed set my virtual memory rather low.
Thanks for that one!
I will report back.
The issue with the days seems really odd.
Did you try just with one image of another day - will it still crash?
Tha has to be some bug…
I think its to do with trying to match too many points, or matching points with images that don’t come after each other.
it is strange. i don’t think it did this before.
The virtual memory was a nice try, but even though I have 2 files on different disks, I still get the same error during reconstruction.
Is it possible it has something to do with the imported component?
Do I need to run another alignment?
chris wrote:
I think its to do with trying to match too many points, or matching points with images that don’t come after each other.
it is strange. i don’t think it did this before.
And you’re not really a newbie - I guess you did quite some work with RC so far.
Did you try it with older images where you know it worked before?
Would be a way to pin it down to the new version…
Wisjgranter,
would it be possible in our cases to have I rollback to the older version at all?
yeah it would be nice if we could roll back versions…
Yet another crash on exit!
It worked fine at the beginning, including a 1200 camera setup.
Then it did the funny freezing at opening again but after a minute or so (usually within a couple if seconds) it opened after all.
Just to be sure I quit and … crash…
Where is the crash report stored so that I can have a look at it myself?
Edit: Forget the last question - its in the error message… duh
Edit 2: Although it is not where it says it is…
how big is the scene your doing?
you might want to test a smaller reconstruction region
1200 and a bit cameras @ 12mpx
Nothing too fancy.
It did the reconstruction alright, but then after loading another project (2400 @ 12mpx) it hung and then after loading crashed on exit.
It’s a quite common thing after the update… 
Do you have experience with reconstructing models in smaller parts?
I never tried it in RC because in Photoscan I wasn’t pleased with the result - after meshing there were visible seams between the parts.
I could merge components before meshing but I don’t think that works in RC with the dense clouds being preserved. Or does it?
I’m trying this at the moment.
I’m not too worried about seems, because i should be able to hide them.
you can use the info panel to see and edit detail’s about the reconstruction region and save out different ones.
or edit the files in a text editor.
I use exporting reconstruction region already quite a lot.
Have to look into the geometric options though…
Editing them in a text editor is something I wasnt aware of yet - thanks for the tip!
Seems to me liket that could be quite convenient to use…
How would you hide the seams?