RCPCreatorSample - E57Codec.rcip

[martin.graner]

When using the provided Codec E57Codec.rcip out of Bin/plugins (not self compiled) together with the RCPCreatorSample, or own code on a structured E57, then I will receive always a *.rcp project without mirrorballs.

When I create a new project in ReCap and import the *.rcs scans which are in the *.rcp's Support folder, then the mirrorballs are there.

Is this a bug of the SDK or is this wanted behaviour?

A workaround would be to create the rcp project with RCProjectImporter::importFiles(...), then delete the *.rcp project file and use createProjectFromScans() or importFiles() with the *.rcs files in the Support folder to create a project with mirrorballs, but my guess is that these steps should not be neccessary.

To check that I have taken the provided RealitySolutionSDKSampleProject.rcp opened it in ReCap Pro and exported it as a structured *.e57 file (Option Complete, not 3d-only)

After that I have started the CreatorSample with the following commands:
./RCPCreatorSample.exe -i "C:/temp/RealitySolutionSDKSampleE57.e57" -o "C:/temp/" -c "C:/temp/Codecs" -p test -s

One can test this with my compiled RCPCreatorSample.exe and the codec from here:
RealitySDKSampleX64.zip

I can upload the generated e57 file as well if this is helpful.

[yan.fu]

Thank you for your feedback.

If the raw  .e57 file is structured scan, it is expected that the mirror ball should show up in the .rcp file. We will investigate on it and reply back later.

Thanks again for your feedback.

Regards,

Yan

[yan.fu]

Hi @martin.graner,

I tried the following steps:

1. Export the sample project to complete .e57 file which keeps the structured scan information.

2. Build RCPCreatorSample project in RealitySolutionsSDK\Doc\samples\RCSamples.sln

3. Import the .e57 file using RCPCreatorSample.exe 

4. The .rcp project is generated and then open it in ReCap.exe. The mirror balls are shown in ReCap. 

Did you try to toggle mirrorBall button in ReCap UI to show it? Does it make the mirror balls show up?

Thanks,

Yan

[martin.graner]

Hi @yan.fu,

thanks for the reply. I didn't think of the UI option in ReCap, so I retried it:

I created a video of my test, but was not able to resolve it.

Video showing RCPCreator.exe without mirrorballs

[yan.fu]

Hi @martin.graner,

Thank you for your efforts on creating this video. It's helpful to learn about the issue.

I noticed that .rcc files are generated for the project, but when it is opened in ReCap, there is no realview button shown, it means the project is treated as unstructured project. 

We will keep investigating this issue, try to reproduce it and reply back later.

Thanks for your patience.

Best,

Yan

[yan.fu]

Hi @martin.graner,

I cannot reproduce it in my developer environment. Could you attach your .CodecTest.rcp file for me to take a look?

Thanks again,

Yan

[martin.graner]

@yan.fuSure.

If something else can be useful please let me know.

A compiled version of the code is in here as well:
RealitySDKSampleX64.zip

[yan.fu]

I downloaded the package you uploaded and tried with sample e57 file but still cannot reproduce it. 

We will try other machine to see if it can be reproduced. 

Could you please share the problematic .rcp file that doesn't have mirror ball with me? Thank you!

[martin.graner]

Hi @yan.fu,

sorry, somehow the file was not uploaded in my last post and I can't upload using attachments so here again a link:
CodecTest.rcp projectfile only

I will have a look at the video later today, thanks for sharing it.

Best regards

Martin

[martin.graner · Accepted solution]

Heureka!

After watching your video and seeing the difference in our paths I retried it and solved the puzzle:
I used the paths with slashs ("/"), you used backslashs ("\").

When using the same with backslashs everything works perfect, when using slashs the project file is somehow not written correct.

I'll adapt my code to it. Would be much appreciated if you add something like wstring::replace("/","\") in the SDK so other developers won't face the same again.

Thank you very much @yan.fu

[yan.fu]

Glad to know the puzzle is solved 🙂

Thanks a lot for your suggestions. We will fix it in later update. 

Thanks,

Yan