line-weight

Member
  • Content count

    535
  • Joined

  • Last visited

Community Reputation

97 Excellent

About line-weight

  • Rank
    500 Club

Personal Information

  • Location
    London, UK
  1. Completely agree with all this. Another problem with the current stair tool is that what it produces in 3d is made up of polygons rather than solids. So it's not even possible to get it to build you a "nearly right" version, convert to solids and edit manually.
  2. - how would you draw the dormer cheeks? - how to make the dormer cheeks join properly with the roof and wall elements? - would VW know to cut the dormer cheeks at the right height? - can the slab you use for the ceiling have angled edges to meet the roof neatly? My view is that making all the above work (especially if wall/roof components are to be shown), if it's even possible, would probably be more time consuming and less easily editable than just doing it all as directly modelled solids.
  3. I also feel that it has gotten worse, although it's hard to be sure, because maybe I am also using VW in different ways. But at the moment 2018 does feel very glitchy in general. I'm half considering going back to 2017.
  4. Yes, I have discovered this has been causing some (but not all) of my problems.
  5. I've tried copying the symbol into a new file; the problem remains. Attached with this message if anyone wants to see if they can replicate. Go to saved view called "perspective view" You'll get an OpenGL view of a 3 panel sliding window, consisting of some grouped elements, some of which are symbols. Go into the group and double click on either the middle or right hand window panel to edit the 3d component of those symbols. For me, this throws me into an orthogonal/wireframe view. (I've not yet been able to replicate the problem I was having with objects disappearing in a top/plan view multi pane.) vwsymbol.vwx
  6. Ok: I think I may have found where the problem is - I use saved views quite a lot, to switch viewpoints and visibilities. In some of these, the "restore unified view" checkbox is ticked. It seems that a couple of these restore unified view to "off". I've checked opening the same file in VW2017; the same applies but it doesn't seem to cause problems when there are no multiple view panes. For now I've unchecked the "restore unified view" boxes and will see how things go.
  7. Turning on unified view improved things for a bit. However, it seems that it keeps getting turned off without me doing anything. For now I think i'm going to have to come to the conclusion that multiple view panes is unusable, at least with this file.
  8. And going in to edit the 3d component of some symbols, but not all, I am inexplicably thrown into a different render mode and projection (I am working in openGL/perspective, double click to edit a symbol, and suddenly I am in orthogonal/wireframe) What a mess.
  9. Additionally, I seem to have a situation where an object (a symbol within a group) does the "invisible" thing when in a top/plan pane, with unified view *on*. Turning UV off makes it appear, but then the other pane gets messed up.
  10. @JimW I've realised that turning off UV doesn't solve this side issue ^
  11. I've send you the file by private message. Thanks.
  12. Ah - turning on unified view sorts it. I'm not sure I understand why. Maybe I need to do some homework. In light of unified view having seemingly solved things - would you still like me to post a file?
  13. That doesn't seem to make any difference.
  14. See the attached screen recording. When I attempt to enter a 3d symbol to edit it - all the components become invisible. They are still "there" as they highlight under the cursor. Those components which are extrudes: editing the extrude renders the polygon visible. If I edit the same symbol via the resource browser, the same does not seem to happen. Also: the symbol's name does not appear in the OIP as I think it ought to. (These problems are arising in a file which has been converted from 2017) vw3dsymbol.mov
  15. Have just tried this and I see that disabling colour: - does remove colour - does remove the image maps associated with the textures (whereas you might expect that it would make them greyscale) - doesn't remove the transparency associated with the textures As ever with VW not exactly intuitive but useful to know. The reason I like to have the colours on is that I find it makes models more legible whilst working on them - provides distinction between materials (or whatever you use your classes to control) without the distraction of the tiled image maps, which can make edges hard to see.