3D Interoperability

[stress97]

I encounter problem when writing catia (InteropR18sp1).

I get the following error message

"Output file could not be saved".

I don`t know why error message was happened.

Usually, when was  this error message happened.

What do I must any action !!!!   

I need your help.

[ybiyani]

Hello Stress97,

We will need more information to help with this issue

1) Is this the first time you are seeing this issue?

2) Do you see this behavior with all the files?

3) What is the behavior with InterOp samples?

4) What is the behavior with InterOp R20SP1 (Please note InterOp R18SP1 is no longer a support version)

etc...

Regards,

Yogesh

PS- You might want to log this issue as an incident with Spatial Support Services.

[stress97]

Hello Yogesh

We upgraded to InterOp18Sp3(sorry, not InterOp18Sp1).

And we still use legacy APIs.

writing acis and iges have no problems. But, writing catia have a problem.

Writing catia have no problem when we use InterOp18sp3 previous version.

So, I don`t know why this error message was happened.

we write to catia file following steps.

1. api_xparasolid_read( (int*)parts, n_parts, NULL, acis_lst, n_acis, &parRes)

2.

 ENTITY_LIST entlist;
 for(int i = 0; i < n_acis; ++i)
 {
  entlist.add(acis_lst[i]); // ENTITY -> ENTITY_LIST
 }

3. api_catiav5_convert_acis_entlist_to_catiav5( catiaFileName, entlist, NULL)

at step3 , error message happen "output file could not be saved "

when we upgrade to InterOp18Sp3, we didn't change codes.

I attach log file at step3.

Regards,

kihoon

[Sarvnaz]

Kihoon,

 Let me ask one question. Are you using our connect interface for writing CATIA V5 file?

Or are you using the legacy interface?

It sounds like you are using the legacy interface. IS this correct? If so, is there a reason you are not using the connect interface?

[stress97]

Sarvnaz.

Right !!. We use the legacy interface.

There is not any special reason we not using the connect interface.

I know that using connect interface is simple and easy.

but, there is no problem using legacy interface.

I don`t think that any problem was generated by using the legacy interface.

some time, we will change to connect interface. 

Now, I want to know when and why "output file could not be saved" error message is happened .

and  at InterOp18sp3,

Is there a reason that we must not using the legacy interface.

Best regards,

kihoon

[ybiyani]

Hello stress97

I know that you have spent time intergrating the product however as this issue is related to legacy interface and R18SP3 -both of which are unsupported.So please seriously consider moving to connect interface and the  latest version of our product.

Anyways here are some pointers

1) Review the R18 docs and check if you have followed the V5 installation setting

2) Please check if the V5 dlls in the path

3) Run the application in the dependency walker and see which dll is causing the issue

4) Please make our samples work

5) Did you run setcatenv.

6) Please check if you need to install the vc runtimes which ,if needed, is in the redist folder under InterOp installations. I know that we require this for R19 and R20 but I do not recall what was the case for R18.

In many cases such issues are seend improper path or V5 settings.

Please note we can help you migrate to connect interface and the latest version. If you arre interested in doing that please create an incident.

Regards,

Yogesh

[Sarvnaz]

If the recommendations Yogesh gave above didn't help, please create an incident with this problem and please attach the code to the incident. we will look at your code and try to find out a solution.

Thanks

Sarvnaz