Live Update of viewports, worksheets, site models

[Kizza]

I don't get why in 2016, we still manually have to update.

Take worksheets for example,

Imagine the lost productivity worldwide if every user of excel had to hit an update button for a spreadsheet to recalculate whenever it was edited. So questions: Why should we have to recalculate worksheets at all anyway? Why can't they be live? What technical reason permits this?

Same questions for viewports...

Same questions for site models...

[michaelk]

I *think* worksheets are still a single thread process. (Jim?) And when you update a worksheet it updates all the worksheets. So the more worksheets you have the longer the update takes. (In drawings with a lot of intricate worksheets, the recalculate time can be very "noticeable".)

In that case you wouldn't want to wait while changing parameters on a door or window for an update in the worksheets between every parameter you wanted to change.

But I agree. It would be great if worksheets (and viewports!) just quietly updated in the background. The trick is to do it fast enough that you don't wait for syncs.

mk

[PVA - Admin]

I *think* worksheets are still a single thread process. (Jim?) And when you update a worksheet it updates all the worksheets. So the more worksheets you have the longer the update takes. (In drawings with a lot of intricate worksheets, the recalculate time can be very "noticeable".)

^ This is indeed the main reason.

Once these processes become multi-threaded (which will happen eventually, but likely not all at once) it would be a viable option to allow the user to let these update in the background. For ow, if we added that option, it would drive you completely nuts and you'd end up turning it off in short order.

[digitalcarbon]

yes, jim is correct all worksheets update and that is why there is a slight lag when you update one worksheet (its really updating all)

[michaelk]

Once these processes become multi-threaded (which will happen eventually, but likely not all at once) it would be a viable option to allow the user to let these update in the background.

Viewports first?? :-)

[Kizza]

JimW, two questions if you don't mind..

Isn't it simply a matter of automating a process which is at present manual?

Is there any other BIM application on the market today that relies on it's users to manually update viewports, site models and worksheets?

Not wanting to rant here, but if worksheets can't automatically update in the background because of not being multi threaded, how did you pull of the subdivision tool?

And, if in 2016 our site models can't update in the background (but may, eventually), what hope do we have for simultaneous multi 3D model views?

[PVA - Admin]

Subdivision was written from scratch, so it was designed for multithreading from the start. Same with the eventual introduction of multiple 3D views, that system will be based on the VGM (Vectorworks Graphic Module) which draws on your GPU and is multithreaded, it was designed to function this way since its inception.

Site models though to give an example, -if we implemented multi view first,- would still be a single core process, but all of those 3D view windows would show the updated site model at the same time once the single threaded recalculation of the site model completed. It wouldn't have to update a separate instance of the site model in each view one after the other.

[Kizza]

At the very least then, give me the ability to update a site model without having to select it.

And somehow give us a visual cue that a worksheet is outdated (similar to out of date references maybe?)

[PVA - Admin]

Submitting both now!