View Issue Details

IDProjectCategoryView StatusLast Update
0033412CommunityOCCT:Data Exchangepublic2023-08-07 16:02
Reporterwinfried_156604 Assigned Tobugmaster  
Status closedResolutionfixed 
Product Version7.7.1 
Summary0033412: Fix issue importing TRIANGULATED_FACE from STEP where there are no pnval entries
When testing, we encountered an issue importing some TRIANGULATED_FACE entries from a step file.

Currently, OCCT is unable to import entries where no pnindex identifiers are specified. In this case, it seems like the correct behaviour is to fallback to indexes in the underlying coordinate set.

The entries that fail to import look as below;


Here is the relevant entry from the standard

Attached is a patch that fixed the behaviour in internal testing, and an example step file that fails to import with OCCT 7.7.1
Steps To ReproduceImport example.step before and after applying the provided patch
TagsNo tags attached.
Test case number

Attached Files

  • occt_import_no_pnvals.patch (1,924 bytes)
  • example.step (9,056 bytes)


duplicate of 0033410 verifiedvglukhik Data Exchange, Step Import - TRIANGULATED_FACE from STEP where there are no pnval entries 



2023-06-21 03:37


occt_import_no_pnvals.patch (1,924 bytes)
example.step (9,056 bytes)


2023-06-21 14:29

administrator   ~0113669

Dear bugmaster, please close an issue.
This ticket is dublicated. The problem is know and now dublication on fixing stage.


2023-08-07 16:02

administrator   ~0113911


Issue History

Date Modified Username Field Change
2023-06-21 03:37 winfried_156604 New Issue
2023-06-21 03:37 winfried_156604 Assigned To => ika
2023-06-21 03:37 winfried_156604 File Added: occt_import_no_pnvals.patch
2023-06-21 03:37 winfried_156604 File Added: example.step
2023-06-21 14:28 dpasukhi Relationship added has duplicate 0033410
2023-06-21 14:29 dpasukhi Assigned To ika => bugmaster
2023-06-21 14:29 dpasukhi Status new => feedback
2023-06-21 14:29 dpasukhi Note Added: 0113669
2023-08-07 16:02 vglukhik Status feedback => closed
2023-08-07 16:02 vglukhik Resolution open => fixed
2023-08-07 16:02 vglukhik Note Added: 0113911
2023-08-07 16:02 vglukhik Relationship replaced duplicate of 0033410