I cannot remove it as I create one component at a time per project. I have to redo everything using a previous version. v12.2 opens that same project just fine but I cannot export anything from it whereas v12.1 cannot open it but I can export.
Windows 10 I believe is the common problem here.
Hi otrhan,
- Windows Version: 10.0.19042
- CPU: Intel i7-7800x 3.50ghz
- GPU: GTX 1080ti
- RAM: 128gb
- Using VM? No
- Is drive local, networked, SSD, External: local SSD
Tried installing older version of RC but because I had opened project in 1.2.2 I could not open in 1.2.1. Tried removing references to RealityCapture in registry. Didn’t work
Thanks for looking into this
Not a fix, but in the meantime we do use the CLI on these problematic RC instances (via a rccmd or directly within the console), waiting for a fix for the GUI exports of components to work again!
-exportSelectedComponentDir folderName or -exportSelectedComponentFile fileName
1 Like
The problem is still there on win10 22H2 OS Build 19045.3271. All updates installed. The previous version exports just fine. 1.2.2 PPI - licenses the inputs, then nothing pops up regarding export format and such.
Hi Lucky_Fox_777, have you tried some of the possible solutions?
Hi @OndrejTrhan! I don’t want to install windows 11 for this matter. Can not have a clean win10 install. I tried to uninstall RC with deep cleaning of the registry and such. Same. I can not use CLI cmd code proposed by jochemla with PPI type of licensing. Is there other solution I missed in this thread?
Hi Lucky_Fox_777, I am sorry for this but for now there is no other solution as this bug seems to be connected to Windows and not RC itself.
Why is it not possible to use CLI for you? PPI supports CLI commands, too.
1 Like
Is there any update on a potential fix for this coming in the near future? Tried several suggested solutions (can’t reinstall Win) that did not work, only thing that does is going back to the older version (…& reprocessing projects 
).
Month and a half and still no update on this from Reality Capture or Epic? What’s the point of this software if we can’t export models 
I tried the CLI commands mentioned above by jochemla and maybe I’m not doing things correctly in the console (I’ve never used that before) but it says that those commands don’t even exist. Anybody know if I’m doing something wrong in the command console? I just copy/pasted: “-exportSelectedComponentDir” and I also tried “exportSelectedComponentFile” (both without quotes).
1 Like
Hi 3dSpecialist and DotScott3, we are working on a solution for this, but as this is not happening on our machines it is harder to find the solution. As mentioned, the workflow which worked for everybody was Windows clean install.
Again, we are sorry for this and we are looking for the solution.
The commands exists (RealityCapture Help). Have you also used folder name or file name in your command?
It should look like this in console view:
-exportSelectedComponentDir "C:\Documents\Testing\Outputs"
But using these commands you export just components.
1 Like
Hello everyone, the Capturing Reality team was able to figure out what is causing this issue.
The issue occurs to customers that have installed the Nikon RAW codec.
The workaround for this issue is to uninstall this codec or you can reach out to our support at support@capturingreality.com and we will provide you a version with a fix for the issue.
This fix will be also included in the next RealityCapture public release.
Thank you for your patience and for your assistance in finding the cause of this issue.
5 Likes
Wow, thanks for that. Uninstalled that codec and it works just fine. Thanks for finding out, that’s great!
Several weeks of head scratching finally resolved. thank you so much. To any one wondering it is listed in programs and features as NEF CODEC