Jump to content

arquitextonica

Member
  • Posts

    45
  • Joined

  • Last visited

Reputation

11 Good

Personal Information

  • Location
    Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Completely agree. In fact the thing that "building" naming comes up in the export menu is a nonsense, as it is an Ifc Property and should be suitable for assignment to the different objects in the model.
  2. But there is an important difference between keeping Marionette OSS, and keeping "the tools built with Marionette" OSS. The first does not imply the second.
  3. Perhaps the answer is not useful to you anymore @Stéphane but I can share our approach. We named the storeys according to the different buildings. For that we made also different reference heights, each with a preffix corresponding to the different builidings. In our case, the three buildings are connected, so it is just natural that all buildings "share" the level designation, but I still want to get three different IFCBuilding definition and can't manage to do it in VW. I was told by the German Support from ComputerWorks that it is actually not possible, albeit in the export menu I saw "Building number" and an option that only allowed me to state "1" so I hope it is in the making...
  4. Sorry to reopen this old thread but I´m having problems converting my Marionette Node Objects into Intelligent Symbols. When I do it, they appear in the Palette, but they remain "editable" as marionette networks... Am I missing something?
  5. Thanks @Wes Gardner. I´ve arrived to the same conclussion. I mistakedly advocated DLVP as I thought that the LIR was "outdated" or going to be deprecated, but the thing that in order to layout the different levels we have to "multicopy" the references is a no-no... so Layer Import it is. Thanks!! PS: DLVP have the option of using the current class state, so a single DLVP can be layouted with different Class-States. Everything would be all right if the Layer-State could be inherited in the same way. Actually I don´t understand why it isn´t already...
  6. I "can't believe" it is so hard. Referencing is a core feature of BIM process and in this case, where I have 3 buildings with 5 floors, it means I'll need 15 DLVP at the same time and spread over the whole modeling area so I can manage all??? 🤪
  7. Thanks for the advice @Samuel Derenboim. Those are indeed advanced issues that should be regarded. My point is still how to handle the basic floorplan layouting... Do you work by referencing layers (old way) or by generating DLVP? If by DLVP how do you layout the different levels? Do you use different "master" files? Otherwise we'd have to copy the refenreces' DLVP as many times as wanted floorplan levels, right? Am I missing something there? Thanks in advance!
  8. Thans to @zeno and @zoomer for the precious imput. If I may ask deeper... I believe I´d go with a mix of both workflows. Master file with "everything" (layers, storeys and reference heights with no-layers) but my problem is ONCE I have the master file and the different guest files, how do you manage the references? Do you lay them all in a single design layer? Do you copy them repeatedly to create the different floorplans for all the different levels? That is the problem I can´t tackle!!
  9. I thought about this rather drastic measure. A reknown competitor software package uses this method that could be "translatable" by having just one DL and all the needed reference heights. This would have some advantages. E.g. we would achieve walls spanning several storeys... In any case, my concrete problem is with the referencing. When I place a complete model in the host file, the cross-DL system does not allow me to have the same control as I have with classes, right? IMHO this would solve ALL problems as we could manage the referenced file AS IF it were in the host file...
  10. Thanks, @Hans-Olav you seem to have gotten rid of the problem alltogether in a swift stroke... 😆
  11. I was actually politely asking for ideas on a good setup/workflow... 😄 I´d hope there to be some kind of whitepapared general recommendation that one can tailor to particular needs.
  12. Hallo All! I'm currently involved in a rather big project with several buildings that together make a block. We are thinking of splitting it into several files and federating them together in a master file, and I wonder if there is already a concrete workflow for this as, after my first attempts, I've hit some thick walls and I don't know if I'm doing something wrong. Let me explain... I make a file with all the correct storeys with the corresponding design layers attached to the correct reference heights. I open a new empty file with the same design layers and reference heights and reference the 1st file (is that right?). 1st problem is that the "reference object" is in the DL where I placed it and I can't control the reference visibility from the main file (yes from the object Layervisibility)... BUT I can configurate the reference so that it uses the same classes visibility as the host file. Is it possible to do something similar with the layers? My solution is to copy the reference in each design layer and adjust the reference layer visibility accordingly (i.e. copy the reference from GF to 1stF and turn off GF). This is painstaking! I get a "legoed" result. 2-3-4 references on top of each other... it "looks" right but it is horrible... you understand the problem as when I make a section of the frankensteined building, it must cut through several references and VW becomes crazy! Is there a correct way to do what I want to? Next question would be how to proceed when the references have different reference heights, but first things first... Thanks in advance!!!
×
×
  • Create New...