Kizza
-
Posts
994 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Kizza
-
-
Maybe to articulate further:
A saveable set of class visibilities (a resource perhaps?) that is attachable to a design layer (and viewports?). Saved Views can be relegated to static views of the filtered design layer.
Of course, this would go hand in hand with program wide, user definable auto classing.
P.S. adding a "Show in 3D" option to a class when created may be an additional way to refine the workflow: i.e. furniture displays in a floorplan but not required in a 3D view.
-
Luckily I think with this current and the upcoming release we are either done or nearly done with that conversion, so we will see how fast the features start coming once engineers can be freed up to do way more user-facing tasks.
Sounds like any real progress on new features won't be made until VW2016...
-
One of this board's members has already done the hard work for you.
It looks as if the site has been reformatted so as to be even easier to read and navigate through. And much of the content is the same as last year.....
-
Wouldn't this be just as much work as a Saved View, but only ties to a design layer instead of being a separate, manageable view? Or am I misunderstanding what you mean?
Yes I guess my wish is to incorporate the saved view functionality into the design layer and relegate saved views for the specific views you need to create. (maybe for stair details, design alternative/options etc). Then Design Layers become WYSIWYG at all stages of the project.
-
Design layer's class and layer visibility settings should be saveable on a layer by layer basis. i.e. a saveable layer/class template applicable to each design layer.
For example:
Your roof plan shows different info to your floor plans and landscape plans. If I want to make changes to the roof but the last plan I worked on was the landscape plan, then I have to tango with the class/layer visibilities to get the required info to show. So I'm happy now with the roof and I want to work on the landscape plan again. I then have to undo everything I've done with my visibility settings.
VW has a workflow structure that requires too much time to maintain i.e. Layers, Classes, Saved Views, Viewport Overides.
How about incorporating Saved View funtionality into the design layer itself and to be able to save, edit and apply different combination of settings as a pre-set to the design layer, which you can then apply to future design layers etc. Should work for all disciplines.
-
Although I can't specifically confirm the UK's position on this, Australia's building standards I think are aligned more towards the British Standards generally.
In Australia it is as per image one.(how you've always drawn it) IMO, it also makes logical sense that the point of the arrow indicates the handle/lockset.
VW2014 has the capability to choose the hinge direction.
Windoor (which is now only available for existing Windoor licence holders and Australian users) has this capability also.
If you don't fall into either of the above categories, then you need to add the door swing manually, either as linework directly on the door surface or to to your door symbols.
-
Can HL be set as the default render mode in VW 2014?
As I previously mentioned, rarely do I work in wireframe.
-
Thanks JimW,
Useful insight on how hidden line geometry is generated but still doesn't explain the omission of Live Hidden Line Rendering in VW.
Can I speculate the reason is because Hidden Line Rendering is yet to be ported to the VGM?
-
Thx.
Is the limitation due to not being 64 bit, or something thats currently omitted from the VGM?
Or is it because hidden line rendering in VW is raster based? (although open GL is raster based and nudging works in that mode)
Nudging in hidden line doesn't seem to be a problem in Revit or Archicad.
-
In front view, hidden line render, nudging is not possible. (only in wireframe)
Why?
or has this been added to 2014?
I also wish for global render setting i.e. everything in hidden line instead of wireframe (rarely do I work in wireframe)
-
How about selecting the object, invoke the move command (or Ctrl M), press the required arrow key once (or click in the direction of movement and VW will intelligently decide for you) and enter the movement distance in a floating data bar?
Forget this -number +number business - reminds me of Autocad...
-
Sadly I have pushed for the view cube a few times before. I like it too, but Autodesk has patented the bejesus out of it and many other 3D-view UIs, so it may be awhile before they can implement something similar.
I see.
Not a good position.
-
Back, front, right, left makes sense if modelling an object but not when working with a building - especially when you are working with existing documents where the building is orientated North, south, east, west.
Sometimes I like it how it is now - my wish was to make it customisable....
-
While we are at it, add a feature similar to the view cube and steering wheel View Cube
-
I would like to be able to change the view names from left, Right, Front, Back to say, North South East West.
Basically user defineable on a project level.
-
Hi,
I've tried converting to 3D poly and sending to surface but it disappears.
Restarting VW fixed this.
-
Basically I want to present a shadow study to a client of a large site with multiple lots.
I want to show the outline of each lot on the site in an ISO view.
Creating multiple property lines and sending to surface seems like the correct way to do it. When I send the property line to surface the property line disappears in all but Top/Plan views.
If I draw a 3D polygon and send to surface it shows in 3D and Top/Plan but in TOP view the 3D poly is partially obscured by the contours of the site (centre of poly is sent to surface).
Basically inconsistent results. Am I missing anything?
-
Hi,
Cant get my property line to show on the site model. I've created a property line and sent to surface but doesn't show.
I've tried converting to 3D poly and sending to surface but it disappears.
Nothing in the Designer manual to assist.
-
Imported a basic single page pdf into vectorworks, a simple bathroom plan with elevations, then ungrouped the pdf to access some of the linework.
Once ungrouped, Vectorworks slowed down to a crawl until the spinning beachball required me to restart.
-
But there are some who feel we should take a slower and more deliberate pace and continue new feature additions while improving the older components at the same time.
Tell em that mindset is why VW is in the predicament it's in today. Very experienced users wishing for items they shouldn't have to in 2014. For example, why is it that certain annotation objects cannot be autoclassed?
I agree with Grant, VW has the potential to be great.
But the current status quo reveals otherwise.
R&D and the programming engineers have their work cut out, thats for sure. Ban leave, approve overtime and cut the excuses...lets see some results.
-
Not sure if this is a similar issue I had a while back but hope it helps..
-
It's being touted as a pretty week version from users...their just getting sketchy line renderings.
http://revitoped.blogspot.ca/2014/03/new-feature-list-for-revit-2015.html
I dont think Revit LT has had the stability and useability issues that VW has had - whereas VW has lots to do on multiple fronts. That's why the expectation is greater with each VW release IMO.
That said, I was hoping for a bit more but you have to remember that the LT Suite does include ACad LT also so I think a well rounded package.
I cant keep waiting for NVW to catch up...at least not without a documented commitment/roadmap from them. Which is unlikely to come from this board...
-
I use both platforms and found that VW is much more stable on Mac than Win.
:cry:
-
I'm about to migrate Vectorworks 2012 to Windows 7 (from OSX)
Is there any reason to expect file compatability issues between the two platforms?
Edit:
Or licensing issues??
Speed of development?!
in General Discussion
Posted
If you're biggest advantage over the competition is you are the cheapest, you won't ever be the best.