RWGltf_CafWriter skipped node 'xxx' without triangulation data

Hi,

I am trying to convert the step file to gltf file.
While writing the gltf file using the RWGltf_CafWriter class I am getting this message on console.
Can anyone help me to get rid of it.
I am using the 7.7.0 version of open cascade.
My machine configuration is Linux Ubuntu 22.04.1 LTS 64-bit

I have attached a main.cpp file where my complete code is there.
I have attached the step file too for which I am getting this issue.

Attachments: 
Dmitrii Pasukhin's picture

Hello.

What kind of message do you see on console?

Best regards, Dmitrii.

 

Dmitrii Pasukhin's picture

Sorry, I see it on the title.

Can you share a result gltf file? It will be better to share full console too.

Best regards, Dmitrii.

Vikas Beske's picture

Hi Dmitrii,

Please find the attached snapshot of the complete console and the created glb file too.
i guess due to this error the glb file is not getting correctly exported.

Dmitrii Pasukhin's picture

The step file can't read correctly. That is why, there are not any shapes to transfer. Result document contains only empty compound.
I will analyze it. It takes some time. But now, there is not problem in your code. It is a problem on file or read process.

Best regards, Dmitrii.

Vikas Beske's picture

I am facing the same issue for the multiple step files.
These step files are opening in the other CAD applications like Creo.
Even though if there is some missing in the step file, I think reader should read the partial model and operate on that. I don't know it is appropriate or not.
I hope we will find some solution for this ASAP, I am stuck on this.

Best Regards,
Vikas

Dmitrii Pasukhin's picture

Hello,

New ticket has been created. You can monitore fixing or analyzing process.

0033261: Data Exchange, Step Import - Empty shape after reading process - MantisBT (opencascade.org)

Best regards, Dmitrii.

Vikas Beske's picture

Hi Dimitrii,

It seems like releae 7.8.0 will take some time.
Until that can you suggest some work around through open cascade?
If not using open cascade then can we do something locally to make some changes to input so that it will work in open cascade.

Dmitrii Pasukhin's picture

Hello,

Don't worry. Tag 7.8 means that is should be descripted in 7.8 release notes. The bug will be resolved before release.
Unfortunately, I can't tell anything without analyzing a file. As soon, as I analyze a file I write a description message or create commit with solution ( if it is faster ).

Tasks from the community are solved in order of priority. At this point, you need to wait a little longer. If you need an instant solution, please contact the marketing department directly.

Best regards, Dmitrii.