View Issue Details

IDProjectCategoryView StatusDate SubmittedLast Update
0022485CommunityOCCT:Data Exchangepublic2011-05-10 12:512014-10-31 16:49
ReporterszyAssigned Togka 
PrioritynormalSeveritytrivial 
Status closedResolutionno change required 
OSAll 
Summary0022485: Bug of Iges reader
DescriptionPost from the Forum - http://www.opencascade.org/org/forum/thread_20603/.
"Tod Courtney | reply 2011/05/06 07:48
We have a problem importing IGES files generated by Pro/E that contain 508, 510, 514 surfaces. A simple example is in 'test03_bad.iges'. This example is a flat circle created by a circular trimming curve applied to a flat plate. When we load this file into OCCT, either within our software, or using the precompiled ImportExport sample program on windows, we see the two component pieces: the square and the circular trimming curve.

However, if we load this IGES file into the Rhino CAD tool and save it using their 'default' variation of IGES, we get a file that can be loaded into OCCT. This file is based on 126, 128, 141, 143 surfaces. It is test03_good.iges.

I am looking for some help with this. I want to understand what is wrong with the "_bad" version of the file. It is produced by Pro/E and can be read/written using Pro/E and other CAD tools. So I assume it is valid, or at least mostly valid. Is there something we need to do (ie another method to call) with OCCT so that we can read the "_bad" version of the file. If someone has OCCT 6.5 could they see if it will read it and display it correctly?

thanks,
Tod"
TagsNo tags attached.
Test case number

Attached Files

Activities

2011-05-10 10:51

 

20603.zip (5,308 bytes)

pdn

2014-10-07 19:07

reporter   ~0032787

It looks that problem is caused by default handling of "visible" mode. If we process only visible parts the results of both files looks the same (circular face)

szy

2014-10-08 11:19

manager   ~0032797

I suggest to make treatment by your own => bug : not bug.
If not a bug also some solution (for example, correct setting of parameters) can be proposed to avoid the specified problem.

pdn

2014-10-09 12:48

reporter   ~0032879

Not a bug

abv

2014-10-31 16:49

manager   ~0033968

Closed as no change seem to be required

Issue History

Date Modified Username Field Change
2011-08-02 11:12 bugmaster Category OCCT:DTE => OCCT:Data Exchange
2011-11-24 14:48 szy Fixed in Version EMPTY =>
2011-11-24 14:48 szy Description Updated
2011-11-24 14:50 szy Assigned To bugmaster => pdn
2011-11-24 14:50 szy Status acknowledged => assigned
2011-11-24 14:50 szy Resolution suspended => reopened
2014-10-07 19:07 pdn Note Added: 0032787
2014-10-07 19:07 pdn Assigned To pdn => szy
2014-10-07 19:07 pdn Status assigned => feedback
2014-10-08 11:19 szy Note Added: 0032797
2014-10-08 11:19 szy Assigned To szy => pdn
2014-10-08 11:19 szy Status feedback => assigned
2014-10-09 12:48 pdn Note Added: 0032879
2014-10-09 12:48 pdn Assigned To pdn => gka
2014-10-09 12:48 pdn Status assigned => resolved
2014-10-31 16:49 abv Note Added: 0033968
2014-10-31 16:49 abv Status resolved => closed
2014-10-31 16:49 abv Resolution reopened => no change required