Jump to content

Will

Member
  • Posts

    137
  • Joined

  • Last visited

Reputation

27 Great

Personal Information

  • Occupation
    Architect
  • Homepage
    www.thornewyness.co.uk
  • Location
    Isle of Mull

Recent Profile Visitors

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

  1. Well this question is pointless, I just realised that it doesn't matter. Imagine standing looking a roof panel, one side clips over the other side so you need to know which side has the covering bit (the 'overcloak') and which side has the seam the fits under the covering bit (the 'undercloak') If your panel is flipped vertically then the observer is rotated 180 to stand looking at the panel but the overcloak and undercloak have stayed on the same sides as before the flip so when you stand rotated 180º looking at the panel from the front the overcloak and undercloak have swapped sides. Likewise, if you stay in the same place and flip the panel. the overcloak and undercloak have swapped sides. So the answer to my question is 'it doesn't matter' because I am an idiot... If the panel is flipped the undercloak has swapped sides with the overlcloak regardless of whether it was a horizontal flip or a vertical flip. So when I report the panel in my list if IsObjectFlipped() returns true I report left as right and right as left and everything is golden!
  2. Does anyone know how to find out if a PIO object has been mirrored horizontally or vertically? I've tried testing using IsObjectFlipped but this doesn't tell you if its been flipped about the X or the Y axis. So then I tried using FlipHybridMatrix and testing again but this Function doesn't seem to do anything inside a PIO. (note the handle to the PIO instance is stored in self.handle) def isFlippedHorizontal(self): if vs.IsObjectFlipped(self.handle): vs.FlipHybMatrixObj(self.handle, 1) #flip vertical and test again then flip back. If still flipped then rerturn true r = vs.IsObjectFlipped(self.handle) vs.FlipHybMatrixObj(self.handle, 1) return r else: return False In theory GetObjectVariableReal(h, 102) should return the scale of the PIO object, and it should be negative if it is flipped about the X axis but it always returns a very small positive number when used on a plugin handle. Anyone got any other ideas for how to hack a workaround for this problem?
  3. Can I tell the builder to download Nomad so he can view a 3D model on his iPad? Does he require a paid account to be able to do this? I can't seem to figure this out from the VW Nomand help docs.
  4. Try to redeem the code... OK this code has been redeem great that was me. Try to install twinmotion... Uh oh. The only options are EDU and Trial. Try to
  5. I only see Trial and EDU versions in the dropdown in the unreal launcher, is that normal?
  6. My experience is the same as Zoomers
  7. Model it from scratch, you'll save time in the long run. The roof tool doesn't work for a lot of edge cases. It's ok for a rectangular bungalow with a hipped roof and big eaves overhang but not much else.
  8. Edit the extrusion and check that the 2d shape you extruded is a closed shape?
  9. I notice that Vectorworks have deprecated the screen plane. That's fine, I've always found it annoying. But I have templates with a lot of details and such in them that I would like to be able to disable the 'Enable legacy features' checkbox in and there always seem to be some screen plane objects in them somewhere. The reason I want to move to the new format is because I know in the future there will be a load of weird glitches and problems if I am still using features that vectorworks no longer want to provide and are trying to get rid of. So, a couple of questions: Is there a recommended workflow for converting older templates and symbol files to no longer use the screen plane? Do objects in symbols need to be moved to the symbol definition plane? Also has anyone else noticed that when you try to do this all the objects disappear, but if you click where they were they are still selectable? Thanks W
  10. I get this on my intel MacBook as well. After updating lots of section viewports Vectorworks uses lots of memory and becomes very sluggish. It’s like there is a memory leak in the section generation process. I also have to quit and reopen to be able to continue working.
  11. Thanks for this, we already set up the agreed origin of the model, the 'site origin', to be as close as possible to the internal origin of the file, ideally smack in the middle of the building, and it doesn't affect wether the issue occurs or not. What does seem to affect it is the layer scale that the layers are set to. If you need to zoom right in on a detail, then you need a layer scale of 1:10 or something, but if you want to see a whole 300x300m terrain model, you need a layer scale of 1:500 so you can work with appropriate sized text labels.
  12. I have found with this one that placing a 3d locus will snap so I do this then I can snap to the locus.
  13. Sometimes objects become unsnappable. As in, their key points are not detected by the tool I am using to edit another object. In the attached video I edit a solid and try to adjust an extrude to snap to another solid object on the layer below. As you can see from the attached video, none of the points on this solid subtraction object are detected by the snap tool, but other solid objects on the same layer are detected. I think this must be a bug, I've noticed it several times in many different projects and versions of vectorworks over the years. The only thing I can think is that there is some way to make objects invisible to the snap tool. Its quite an irritating bug as I really disrupts my train of thought trying to come up with a workaround. Also, if I am working inside an Auto Hybrid object I cannot snap to objects outside of the hybrid object group when in a 3D view, I think this also must be a bug. Screen Recording 2021-04-26 at 15.05.40.mov
  14. I have a problem where the object info palette does not update when I select an object. Sometimes it just starts happening randomly or sometimes it's like that when I first open the file. Often, but not always, it can be cured by repeatedly right clicking on an object until it responds and starts showing the correct info. Also, when you have something selected, it sometimes doesn't update when you change the size of something in the drawing, which can lead to problems if you then try the +5mm trick in the width or height fields as it adds 5mm to the old values not the new ones and then resets the object in the drawing to the wrong size.
  15. Will

    Thanks

    Vectorworks 2021 SP2.1 on MacOS Big Sur 11.1 I didn't change any settings that I'm aware of, I just noticed that it started happening recently, not sure if it was a macOS or a VW update that did it, just thought I'd say thanks to someone!
×
×
  • Create New...