ReCap 360 crashes incessantly

ReCap 360 crashes incessantly

Anonymous
Not applicable
1,575 Views
9 Replies
Message 1 of 10

ReCap 360 crashes incessantly

Anonymous
Not applicable

Why does ReCap 360 Pro constantly crash?  It crashes on import, it crashes on register, it crashes on index, it crashes on realview.  Sometimes it just switches off, sometimes it says it can't import/register/index scan and removes it, sometimes it reopens with an unexpected closing error window, most times not.

This is easily the most unstable program I've seen since Windows 6.0.  Unbelievable.

1,576 Views
9 Replies
Replies (9)
Message 2 of 10

Anonymous
Not applicable

ReCap 360 Pro just crashed again.  This time, up popped the Autodesk Crash Report window-for the first time.  I filled it out and submitted it, (as I always do).

I'd like to add, that, among its other problems, ReCap 360 likes to claim indexing is done when it's not.  It'll take 5 minutes or so per scan for the first 5 or so, then magically say it's done.  However, if the rcp file is imported to Revit, much of the point cloud is missing.  Relaunch ReCap and it begins indexing where it left off.  This process is necessary several times before the indexing is actually completed.

Why?

Message 3 of 10

Anonymous
Not applicable

Ran through the available updates.  Installed 3, brought me up to V3.1.2.1.  Program crashed (disappeared) upon opening project mentioned-scan 12.  reboot just completed.  Trying again.  This is turning from a "Forum" to a "Diary". 

Message 4 of 10

daverudolf
Alumni
Alumni

Hi Steve,

 

Sorry to hear that you are having so many problems, and thanks for filling out the crash reports. That will help us track down what is happening. There are definitely lots of other people using ReCap without the kinds of problems that you are seeing, so I wonder what might be unique about your situation. What are the specs on your computer that is running ReCap? What kinds of data are you importing?

As for finishing indexing after the first scan, keep in mind that ReCap lets you start exploring the 3D data after the first scan completes, while it continues to index the other scans in the background. This sometimes confuses users. I wonder if that is what is happening with your situation.

 

Cheers,

 

Dave

0 Likes
Message 5 of 10

Anonymous
Not applicable

Hi Dave,

  I'm currently in an email conversation with Ashwini Murthy, also from Autodesk.  He's responding to my Crash report directly, I assume.  He's asked me to upload some of the scans so they can take a look.  We are using scans from a Topcon GLS-2000 scanner.  There are between 16 and 47 scans per project, depending.  Each project can run up to 105Gb or so, so they're pretty hefty.  The computer is a Lenovo Thinkpad that should have plenty of horsepower.  We take the resulting ReCap point cloud and link it in Revit MEP for modeling.

If Ashwini and his team can work this out, I'll post the solution here.  Until that time, I can only really conduct one conversation at a time.  I hope you understand.  🙂  Thanks for the help.

0 Likes
Message 6 of 10

daverudolf
Alumni
Alumni

Excellent. You are in good hands with Ashwini. She is pretty knowledgeable with the product, and has the development team behind her.

0 Likes
Message 7 of 10

Anonymous
Not applicable

I knew it!  Even as I typed "he", I knew it was wrong.  I should know better.  Sorry, Ashwini.

0 Likes
Message 8 of 10

Anonymous
Not applicable

Dave,

 While Ashwini is crunching our data, I'd like to address the indexing phenom.  Short answer, no, I'm not confused by the "look ahead" capability.  I've watched the process happening.  Index screen crunches a few, sometimes up to 8 but more often less than 5, and reports, "Indexing complete".  The resultant rcp is then linked in Revit, but most of it is missing.  I'll reopen ReCap and presto!  It starts indexing right where it left off.  Maybe, it does 4 or so of say 35 scans.  It then says "Indexing Complete" again.  Reload or reinsert link and it's not all there again.  Restart ReCap, you guessed it, it starts indexing again.  It has taken 8 or 9 cycles like this to actually complete the indexing phase on multiple projects with multiple computers and multiple operators.

It's kind of infuriating.  And a colossal waste of time.  And this is after the crashes and such in discussion elsewhere.

We must be doing something(s) wrong, but I haven't a clue what.  I saw a completed project done by a subcontractor of one of our sites that looks like you are in the room and I'm wondering what they're doing that we're not?  Gonna figure it out.

Thanks for the help.

0 Likes
Message 9 of 10

daverudolf
Alumni
Alumni

I talked to Ashwini, just to get some background info. Are you trying to import TopCon files, or some other format? Are there particular scans that it initially fails on, or is it somewhat random? 

Message 10 of 10

ashwini.murthy
Alumni
Alumni

Just adding a note - for GLS2000 scans, import issues were resolved by coping the .bin and .sta files to the correct scan location folder. These are project files and have to placed to be present in the correct location for import to complete successfully.

 

We were able to recreate the indexing problem and the development team is looking into it. The workaround would be to reopen the project, so that ReCap can finish indexing all scans. 

 

Thanks,

Ashwini

0 Likes