Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by gester

  1. cobie toolkit throws exception after exception. mostly null pointer, some handler exceptions a.s.o. no ifc file is getting imported, although apparently prepared for cobie. admittedly, it's a big file (142 mb), exported from the vw 2015 version, but the functionality is dramatically bad. rob
  2. another option is magic mouse customisable with bettertouchtool installed.
  3. wacom 5-button mouse (wireless). i use it with intuos 3 tablet (a6 - enough for the accuracy). pen is for animating, mouse for cad/bim.
  4. so it practically duplicates all the design layers of the source project. so can anybody explain to me what was meant in this document in the first picture on the page 6 (project folder setup) ? how can i extract all sheet layers to build such a structure ? it doesn't make any sense for me. or maybe i miss something?
  5. so it was completely misplaced. mine was only a few metres away, in no case world coordinates setting. i'm just as clueless as in the beginning. rob
  6. @brian it's great news, thanks. rob
  7. dwg is not an option in my case. i don't check anything in the control exports (my main dwg usage), i want my ifc model to behave correctly. rob
  8. sometimes i've had an issue with the fills (which is btw required for the ifc exports) when the class solid fills were not set up from the beginning with the 'use at creation' checked in the class settings. adding it afterwards (and applying the changes for all elements with this class) doesn't work in some cases. rob
  9. @benson this is crazy. it does prove that the functionality storeys to ifc depends on an accident. btw, my ifc model parts offset in x and y directions, both with somehow fixed values. rob
  10. now i've deleted the foundation storey and assigned the remains of it to the ground floor storey (the bottom one). see what happens. does anybody have a clue? rob
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. i've cleaned up all additional spaces, leaving only the overall exterior storey spaces, but the gbxml export crashes the app anyway.
  18. 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
  19. so when will we know for sure?
  20. but you'll implement one in the 2016 version, right? rob
  21. 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
  22. 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
  • Create New...