Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by gester

  1. thanks for the yt channel, i'll take a look. the real issue is but the improper ifc export of objects in v2015 that once worked ok in v2014. rob
  2. another ifc export issues, concerning the transition from v2014 to v2015. the only advantage is the reduced ifc model size in 2015 (142 mb vs 344 mb from v2014), but that was it. - the model, correctly exported and visualised in solibri viewer in v2014 gets messed up in v2015 ifc export: the whole foundation is moved diagonally at a strange distance, the remodelling in the v2015 doesn't help. - the path along the house wall sticks out at an angle in v2015 ifc model, compared with the proper look in the v2014 model this is a field report, i'll examine the case more closely. as for now, either the storey structure doesn't work, or something bad happens to the ifc export. rob
  3. now i have installed all libraries, including the imperial ones that i don't need. another question then: is there a way to uninstall certain libraries afterwards? rob
  4. getting deeper into the gbxml topic: - the spaces assignment ignores the proposed class, everything gets created in the space-main - the gbxml export after the spaces assignment crashes the app in the v2015 either - deletion of the additional spaces messes up the walls' appearance in the sections (some of the walls disappear irretrievably - i presume the sections would have to be created a-new) more to come. rob
  5. my package manager doesn't resize and it doesn't have a vertical scroll. i can only see the first 2 and 1/2 library options, and i can only install all libraries (including those i don't need). any feedback? thx, rob
  6. ok, i understand the need for the spaces enclosing the whole storeys, but i do not get what do i need additional spaces for, when i already do have my own ones? and why are they located on the slab layers (where i have my construction and floor slab parts)? can anybody explain this part of the gbxml functionality, just for the sake of all users's understanding? thx in advance rob
  7. i've cleaned up all additional spaces, leaving only the overall exterior storey spaces, but the gbxml export crashes the app anyway.
  8. well, i have played a bit with the gbxml output, and the results are for me devastating. i'll try to summarise in points. 1. the gbxml 'place spaces' command ignores the invisible storeys (there is a storey structure in my project) and puts a space everywhere, even for small enclosed areas. 2. i've modelled the slabs as two layers: the construction one, and the floor finish one. the gaps, cut out in the floor layers for the walls wind up as space divisions for the 'place spaces' command, and the existing spaces are being ignored. i get thus doubled spaces, and all slab layers appear again as visible. 3. the gbxml export then crashes the application. can anybody explain the best strategy to use this functionality? i am helpless. thx, rob
  9. so when will we know for sure?
  10. but you'll implement one in the 2016 version, right? rob
  11. micha, i have modelled the pipe as the extrude along path in the 'none' class (which is a non-filled type), then changed the class to the solid-filled plumbing-storm class with the 'use at creation' checked, then assigned the pipe to the ifcpipesegmenttype. probably one of the steps was too late to have a filled type. btw, wes, thanks for the files, i'll check them, but can you convert the vwx to 2014 version? thanks in advance. rob
  12. i'm trying to export my building to the ifc format. i understand the message as a hint that some classes with ifc elements have no fill. i've put a few pipes (that were in the 'none' class) into an existing proper class, with use at creation checked, and with a solid fill. all to no avail, the pipes don't appear in the ifc model. is there any fool-proof method to assign the elements in order to have them ifc-exported? thx, rob
  13. ok, it's real news for me and a huge difference. apparently there are features in each release that we can't even appreciate enough for its value. rob edit: ok, i've got it. it's the wall lines setting itself.
  14. i'm gradually getting crazy. wes, yours is the same settings as for my door, but the result is like i wanted it to be. where did you set the wall lines to dashed? is it the ceiling-main for door lintel? thx, rob
  15. wes, thanks a lot, but can you convert it to v2014? actually my line setting in ceiling-main is dashed... rob
  16. no, it can't be. doors in other walls without pilasters behave the same way...
  17. jim, thanks for the reply. the wall isn't duplicated, but there is a pilaster modelled as an 'add surface' (depicted on the enclosed file). can it be the cause? rob
  18. i've tried to follow the explanations, but i can't make the door lines disappear, or at least change them to dashed lines, no matter if i check 'draw wall lines' or not, and if i turn ceiling-main (ceiling-overhead) class on or off. can anybody help? thx, rob
  19. well, my goal was to provide a working underlay for the design consultants, and they prefer model space. exporting to the paper space i get the actual design layers of the section viewport creation instead of the section itself, but possibly there are some settings i miss. checking the 'export viewports as 2d graphics in model space' check button in the 'sheets to include' section apparently brings the export in the direction i intend, but i'll have to check the options once more. thanks for the insight. rob
  20. well, it might have been that the 'use at creation' check button in the class attributes dialog (set filled as solids) must be checked before the shape is being created... edit: otherwise i don't know how to change it afterwards.
  21. with me, all extrudes are hollow, no matter if it's a 2d poly or even a rectangle (that must be closed by design). they are assigned to the class that is filled as solid, with aimed textures for all options. all to no avail, no additional vertices while scanning with oip arrows, either. the extrudes remain transparent. does anybody have a clue what could be the reason? thx, rob
  22. @damon, i usually import dwgs with centering after import, the world coordinates get set properly. i've had issues with further exporting dwgs from sheet layers: the world coordinates got multiplied by 10 or 100 - this may have been the units issue. i haven't found an appropriate fix for this, though. nevertheless, i've then tried the direct design layer export (not via sheet layer). this time the world coordinates got exported correctly. hth, rob
  23. i must push it up again. is this functionality improved in the v2015 already? for the illustration (attachment): up to v2014 the 3d appearance (axos, sections and elevations) doesn't differ for those two windows. and it _should_. thx, rob
  • Create New...