Import Scan Error

Import Scan Error

subs
Collaborator Collaborator
1,587 Views
7 Replies
Message 1 of 8

Import Scan Error

subs
Collaborator
Collaborator

If you get an error importing scans....

KEEP GOING!!!

I import 40 scans at 3am, then wake up to find it stopped in Scan 15 with an error.  A lovely dialog awaits that I can only select "OK" to.  And now I wait for 16 to 40 to import.

 

Give me the feedback but DON"T STOP IMPORTING! 

Time is wasted.

Buck Wyckoff
1,588 Views
7 Replies
Replies (7)
Message 2 of 8

subs
Collaborator
Collaborator

It's even worse.

It's got Scan 17 to Scan 40 sitting there as black disk icons and I'm now realizing no further importing is going on.

More wasted time. (Not to mention a virtual bohica).

Suspending the job and restarting the job got the importing process to really start going again.

Enough of that please.

Buck Wyckoff
0 Likes
Message 3 of 8

anil_mistry
Autodesk Support
Autodesk Support

Hi @subs,

 

What version of ReCap Pro you are using? What is the scan data format (.fls, .las). Are these scans located on local drive or network drive? 

 

Thank you and have a great day!



Anil Mistry
Technical Support Specialist
0 Likes
Message 4 of 8

anil_mistry
Autodesk Support
Autodesk Support

Hi @subs,

 

I’m just following up to see if you were able to gather the information I had previously requested to assist me in troubleshoot your issue.

 

Thank you and have a great day!



Anil Mistry
Technical Support Specialist
0 Likes
Message 5 of 8

subs
Collaborator
Collaborator

Raw Faro fls scan folders located on my local drive and imported.

5.0.2.41.

This isn't the first time over the years this has happened.  It's rare that I have a bad scan.  ReCap always stops when getting an import error and presents an "OK" only dialog, waiting for the user to respond.  The program just needs to function such that it reports errors, but skips that file and continues importing.  Don't stop for something the user cannot do anything about anyway.

thx

 

 

Buck Wyckoff
0 Likes
Message 6 of 8

sreed
Enthusiast
Enthusiast

I feel your pain.  Agree that Recap should keep going after a failed import.  Nothing is worse than getting to your computer after all night just to hit "OK" and let it resume - only to have to close and restart in order to index.  What should take 2-6 hours of CPU time can take days.

 

5.0.2.41 is MUCH better than previous release, but imported errors still require babysitting.  

 

0 Likes
Message 7 of 8

daniel_musick
Advocate
Advocate

I agree with you all that ReCap should default to the most User-Friendly behavior.

 

Has anyone of you tried the DeCap.exe CLI-Tool and do your import problems occur with that as well?

Have a look at this thread. It is the best explanation i could find and an interesting read.

 

When i experienced such behavior from ReCap as you two described, i found that ReCap was not really at fault.

One time it was a lack of storage space on the hard disk(s).

  • Import of raw scans means ReCap transforms them to RCS format, which is about 1.5 times as big as your raw format.
  • Don't forget the various Temp folders and caches of your Operating System.

Another time the power saving options of my Operating System interfered.

  • ReCap can't work when the OS goes to sleep 
  • or when the OS turns off the hard disk
  • or someone closes the lid of your laptop causing an instant sleep cycle
  • and so on and so forth

I'm sorry if i'm stating the obvious, but the Power Options Problem happened to me twice Robot Frustrated

0 Likes
Message 8 of 8

Anonymous
Not applicable

I am having same.issue

 

Recap 2020 raw (ordered) .FLS

 

Please help lol

0 Likes