Probe addin

Probe addin

dany.fankhauser
Explorer Explorer
507 Views
3 Replies
Message 1 of 4

Probe addin

dany.fankhauser
Explorer
Explorer

I'm using the probe addin on a daily base. Since a few days I startet to notice that Featurecam can't be closed clean as long the addin is active.

Theres always a process in RAM that has to be closed in the Windows taskmanager. And since I always have to force close Featurecam, recent files and settings are not automatically saved.

This problem can be reproduced on any Workstation here, so its not PC related.

 

We are using the latest version of Windows 10 and Featurecam 2020.1.1.0013, the probe-addin is from 3.Sept. 2019. All of that is installed in German.

 

Do you know this problem, can you reproduce it too, is there maybe a solution or a newer version of the dll?

 

I appreciate the help

0 Likes
508 Views
3 Replies
Replies (3)
Message 2 of 4

kelbie.ockey
Alumni
Alumni

Interesting! This may be something that will ultimately need to be logged with development.

 

Before going that route, there is one solid 'fix all' solution that helps with a myriad of weird add-in behaviors such as this.

 

  • Completely close all instances of FC (sounds like you may need to get the task manager involved to do this)
  • Locate the FC 2020 shortcut (if it's not on your desktop, hit the Windows key and search)
  • Right-click, and select Run as Administrator.

 

If the issue is some weird permissions issue in the background, which it often is with add-ins, this could likely resolve the issue. If not, let me know, and I'll forward this info along to development.



Kelbie Ockey
Sr. Implementation Consultant
0 Likes
Message 3 of 4

dany.fankhauser
Explorer
Explorer

I already tried that, running as administrator doesn't help. I tried giving user-rights to all the files and folders, even the hidden ones, doesn't help.

0 Likes
Message 4 of 4

kelbie.ockey
Alumni
Alumni

I'm sorry to hear that. I just reported this to the development team for further investigation. For your records, the associated task is FCAM-4796. You can always contact support if you want to get a detailed walk-through on the current status of any development task. 

 

I will try and update this thread when I hear more from development. In the meantime, I would either continue letting it run in the background if that is not a major issue for you or just end the task manually in the Task Manager - which it sounds like you've been doing.

 

I apologize for the inconvenience! Let me know if I can help answer any further questions. 



Kelbie Ockey
Sr. Implementation Consultant
0 Likes