Christiaan

For CMD-5 to take you to Rotated Top/Plan you would already need to be in a rotated view. Tap CMD-5 when Plan Rotation is at zero degrees and you go straight to Top/Plan. If you're in a rotated view and want to go to unrotated Top/Plan, then you just tap CMD-5 twice. It couldn't make more sense.

I've posted a separate solution to this problem here, which I think is far more likely to be implemented:

The Top/Plan keyboard shortcut (CMD-5 on macOS) should take us first to Rotated Top/Plan view (if Plan Rotation is currently active), with a second tap required to go to Top/Plan view. This would match the behaviour of the zero key on the numeric keyboard, providing the same behaviour on the lefthand side of the keyboard. Reason: My favourite way to set up projects is to orient everything to real-world coordinates so that you never have to rotate anything when referencing files or copying and pasting across files. It saves time for those working on the project and avoids placement errors. But there have been a few sources of friction that make this way of working a bit tedious. Some of those things are bugs, some of which have gone away (e.g. editing a Space used to unrotate the plan), some which haven't gone away (e.g. Interior Elevations get distributed very badly on Sheet Layers) but the biggest source of friction is that Top/Plan command unrotates the view. This is an alternative solution to the same problem identified here: https://forum.vectorworks.net/index.php?/topic/112034-ability-to-lock-plan-rotation/ VE-105235

That's what I do now but this doesn't solve the problem of CMD-5 unrotating the view. Changing CMD-5 behaviour to go first to Rotated Top/Plan before Top/Plan (like the 0 key on the numeric keypad) would solve the problem.

Not sure if it's what I'm meant to do but clicking on 'Request map tiles' in the OIP helped.

When I try to take a Geo Image I get this message, none of which helps.

We now have the ability to add a Railing to stairs as a separate object but how to show on two floors? We need the "top graphic" feature that the Stair tool has. (Quick workaround at the moment is to copy and past to upper floor then turn off uncheck Draw 3D in the OIP)

yeah, it's already sorted for 29.0.4 Juan 👍🏼

I think it makes a lot of sense for CMD-5 and 0 to work in exactly the same way. Same command, different sides of the keyboard.

ah huh! Is this a trick question? I see the zero key works in exactly this way (single tap for Rotated Plan, double-tap to go to Top Plan). CMD-5 should work this way too.

A little bird at Vectorworks ran a great idea past me that might just work, which is to make CMD-5 a conditional command: if you're in a rotated view tapping CMD-5 would take you to Rotated Top/Plan, and if you want to go to Top/Plan (unrotated) you just tap CMD-5 again.

Yeah I think people go down a bit of a rabbit hole trying to write these things sometimes 😆

There is this option, but I'm still trying train myself to do it:

Edit: I've posted a different solution to this problem here (suggested by somebody on the VW team), which I think is an eloquent solution, more likely to be implemented and more easily implemented: https://forum.vectorworks.net/index.php?/topic/112096-topplan-shortcut-should-take-us-to-rotated-topplan-before-topplan/ --- I want to be able to lock Plan Rotation. Crucially, when locked, Top/Plan View would obey the rotation and not unrotate the plan. This could be done by providing a checkbox next to the Plan Rotation field in the Viewbar, providing a quick and visible way to toggle it on and off. Or it could simply take over from the current behaviour, which is when you click on the Plan Rotation icon in the Viewbar it deactivates the field, a soft lock. Nothing would unrotate the plan, unless you toggle off the lock. Reason: My favourite way to set up projects is to orient everything to real-world coordinates so that you never have to rotate anything when referencing or copying and pasting across files. It saves time for those working on the project and avoids placement errors. But there have been a few sources of friction that make this way of working a bit tedious. Some of those things are bugs, some of which have gone away (e.g. editing a Space used to unrotate the plan), some which haven't gone away (e.g. Interior Elevations get distributed very badly on Sheet Layers) but the biggest source of friction is that Top/Plan View unrotates the view. A rotation lock toggle would make working in rotated plan view seamless.

I've just discovered this setting for the first time. How long have we had this?! I'm guessing forever, lol. It allows you to use standard views (View > Standard Views) to look at your building model at right angles when the plan is rotated. To trigger this setting: say you have a site plan with north up the screen and your building is it at an angle. You rotate the plan so that your building is at right angles to the screen and then activate one of the standard views for the first time.

Yes, actually, perhaps that was the problem. I'm so used to working with Styles with 'By Style' parameters.

If you're a UK user applying Min./Max. Settings to their stairs, please be warned that the current Saved Set for a UK building regs "General Access Stair UK" is incorrect. The max. riser is currently set to 220 mm, when it should instead be 170 mm. The max. tread is also set to 300 mm but should be 400 mm.

Yeah I think we had "Replace IFC data" but the Mark field was independent of that at that point.

Oh man, thanks Tom. You're right, all I needed to do was edit and check "replace data"! Duh! In fairness to myself I don't think we always had the "replace data" option did we? We used to be able to just change the Mark field in the Style and save.

I'm finding that VW does not remember that I want to view primary views (front, back, left and back) in orthogonal and everything else in perspective.* In my experience it's the kind of bug that is highly unlikely to be reproduced by engineers any time soon, so rather than wait around for years for somebody to reproduce it and fix it, and then for it to come back as a regression, can we instead change the way this setting works? I was so happy to see it arrive in v2023 (with some input from myself) but was a little dubious of it being a "remember last mode" instead of explicit settings. In my experience over the decades VW is not good at remembering such things. So could we try it this? Start with making the remembering part at the application level instead of the file level. (Yes, it's an application preference, but I believe the activity of remembering your last render or projection mode is done at the file level, so different files can remember different view settings).** If the above doesn't fix the problem, can we have explicit settings (as attached mock up), either instead of "Remember render mode and projection for 3D views" or in addition to it? If, in addition to it, if a user checks "Remember render mode and projection for 3D views" then the explicit settings could be greyed out. * This settings needs to be rock solid, we need to be able to rely on it. I didn't like the way things were before but at least it was predictable; what we have now is worse in some respects because I'm switching to a view expecting a certain projection only to find it in a different projection. ** This may or may not be the source of the problem but I disagree with it being done at the file level anyway. Most professionals deal with similar files every day and have no need for different view settings across different files. All it does it give the setting an unreliable feeling, because every time we edit a new file we have to activate our preferences again.

I haven't edited any data in the Wall Style but the wall itself does come from older files. I'll try creating the Styles afresh and just replace them.

Why do I have this problem then?

When I right-click on a Wall Style in the Resource Manager I don't see an "IFC Data" option to choose.

Why do we have this field if the Wall Data Tag doesn't use it? Or why doesn't it sync with IFC data, which the Wall Data Tag does use?

Are you hitting the V key by chance?