Hi,

I am trying to set up views of 2d drafting elevations, that I must first draft rotated around a plan (normal drafting method).
To do this I need to set up custom views for each elevation view, and these will need me to rotate the 'z axis by 90, -90, or 180.
The preset views are actually based on a 3d model (top, sides, bottom), which are not relevant for my 2d drafting.

When I try to rotate the view box the view itself remains as before.

If I try to set up a custom view I cant find out how to rotate the z axis.

Any tips?

Cheers

Hi,

Yes, I need exactly what you are talking about, but none of that comes with my copy of Viacad 2d, (even though what I need is based on 2d drafting requirements).

Any other ideas? Would you, like, me, expect the 2d viacad version to provide that 'Rotate z" field?

Edited by user Monday, August 21, 2017 5:57:08 AM(UTC)  | Reason: Not specified

Seems you have to rotate your floor plan then.

Fred

Can you explain a little more what you are after here, I am not understanding, my fault but I want to help you here.

Regards

Jason

OK, thanks everyone for your assistance and thoughts, much appreciated.

After exploring this question & a few others, my current conclusion is that Viacad 2d (v10) can't serve my 2D architectural drafting purposes, although it comes extremely close.
I say this with heavy heart as it has many great features and is great value.

Here are 7 issues I feel if overcome would to enable effective 2d architectural drafting using Viacad 2D:

1) [Update: SCHEDULED FOR FUTURE VERSION]: can't rotate each viewport on Z axis (this issue)
2) can't shift hatch origin
3) [[Update: SOLVED- use 2 hatch objects, one at 90degrees]: can't specify rectangular hatch spacings (x spacing, vs. y spacing)]
4) need either:
all objects in Paperspace need to always be shown above all objects in Modelspace view (then apply layer order hierarchy, then within each layer apply 'Arrange' order hierachy)
<or>
enforce layer order hierarchy irrespective of whether an object is in Modelspace or Paperspace (then within each layer apply "Arrange' order hierarchy)
5) fill (or solid hatch) needs to stop displaying over objects that it is meant to be behind, including the Gripper
6) ensure a new object is displayed 'above' all other existing objects in it's layer (not behind as it currently seems to do) - prior to any 'Arrange' function. [Too much time spent 'bringing to front' new objects unnecessarily from behind existing filled shapes.]
7) dimension text ('Breakin' style) needs to be both horizontally and vertically centred, in order to position multi-lines appropriately (eg. split by a line break (\P))

Perhaps some of these are straight forward to address, or perhaps they are fundamental characteristics of the system design.
Am hoping they might only exist due to the nature of pruning down functionality from the 2D/3D product to the 2D one.

Am guessing that if I buy the 2D/3D version only issue #1 would be addressed?

Thanks again

Edited by user Friday, August 25, 2017 5:47:15 PM(UTC)  | Reason: Updated with current status

This is addressed.



I understand what you are looking for and this can be accomplished by using groups and arrays



Not currently avaliable, but you could use groups to accomplish this



Not sure about hierarchy and how all the elements behave currently.



The gripper is occluded by filled polygons, but not 3d objects, maybe Tim can look at this.



It would be good to understand how this was designed to work in the program and then we can document any issues if it is not working as expected, but I do not know the logic for display order for objects.


submitted bug report for this issue

Regards
Jason