search

mengdalian / ifcplusplus

Automatically exported from code.google.com/p/ifcplusplus
Other
0 stars 0 forks source link

Problems converting an ifcDoor #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. convert the provided door.ifc file

What is the expected output? What do you see instead?
Solibri opens the file correctly (picture1). Instead, normals seem to be 
inverted, and the wall thickness is wrong (picture2).

What version of the product are you using? On what operating system?
I'm using https://github.com/VTREEM/IFCPlusPlus which is based on r19/SVN

Original issue reported on code.google.com by sylvain....@vtreem.com on 16 Dec 2013 at 11:45

Attachments:

GoogleCodeExporter commented 9 years ago 
Already solved with today's update :)

Original comment by fabian.g...@gmail.com on 16 Dec 2013 at 11:53

Attachments:

GoogleCodeExporter commented 9 years ago 
Weird. I do have the same (great!) result when I use the MSI installer on Win32 
(I don't have a development environment on Win32) but... I still see garbage 
when I use the IFCPPViewer on OS X (based on r19).
Any chance you still have some source files to commit ? :-/

Original comment by sylvain....@vtreem.com on 16 Dec 2013 at 10:10

GoogleCodeExporter commented 9 years ago 
Can you locate a problem with a debugger on OSX?

Original comment by fabian.g...@gmail.com on 17 Dec 2013 at 7:32

GoogleCodeExporter commented 9 years ago 
Source is completely uploaded to repository

Original comment by fabian.g...@gmail.com on 17 Dec 2013 at 7:33

GoogleCodeExporter commented 9 years ago 
(finally) Nailed it ! :-)
See https://github.com/VTREEM/IFCPlusPlus for the fix (teasing� :-P)

(I also created several branches on GitHub: for the SVN changes, the fixes to 
compile with Clang, the CMake files, and the filtering stuff I added)

The last 3 commits improve IFC++ a lot ! :-)

Sylvain

Le 17 d�c. 2013 � 08:32, ifcplusplus@googlecode.com a �crit :

Original comment by sylvain....@vtreem.com on 27 Dec 2013 at 5:55