Matt Overton

This video doesn't inspire confidence. Making it works as it should is not an "improvement" but minimum viable project.

Shame the video sound doesn't seem to be working for me but "Ready" implies there isn't a structured plan to spread features just let them slide if they become problems. "ready" does nothing to instill confidence. If a feature doesn't require a file format conversion as it is new or overlay on existing then it shouldn't be in the version release it should be planned for another non-version monthly release. 5 years seems to be the minimum for even bug fixes. Yes the only thing that is really going to speed this up is more revenue so more staff can tackle the issues, or open source parts and let the community battle test their own improvements. Even that requires an investment in better scripting and tools. Both really require a solid push to bring more users on board and into the community and pushing pricing higher is not conducive to increasing user base. Is the program really moving fast enough at this point to be an acceptable down grade to pull customers from the "Big Guys"?

The way it's been talked about I though it would be monthly not bi-monthly. it's only really 1 maybe 2 more than current and doesn't say anything about rolling feature updates over year so they get better testing. calling them service packs seems more of just the same system of slamming the test team with a full year of features and expecting good coverage.

There was a change in the license for MacOS a few years ago so you can run any old MacOS X as a VM on Apple hardware. There is a developer API and command tools to 'help'* set them up from install images hosted by Apple** to grab and configure. Maybe a should set up a few old vw machines while I'm doing another painful project. * still painful enough but easier. ** might require developer account to access.

Yes choose action then object instead of the other way. Would be a handy logic to many tools.

Yes the system has a lot of odd things it wants to check-out in order to do simple things like this. the ones I hit all the time:- - Every title block in a file to add a sheet layer. - Data tags in some odd random viewport annotation to move a window in a door.

We are running project server on a local synlogy NAS set up as per guides. We are getting getting the following file pollution in our main projects storage on the NAS, any idea how to get it to stop. Files appear to be log files that have exceed size limit but a 100MB in an irregular period so not a scheduled flush. 100MB in what seems to be 6 to 7 working days seems like an excessive amount of logging. Is it a sign of something wrong and how do it stop it? Also can I just delete them?

Add tiers for Students and Seniors. the Former to make sure there is a good supply of staff coming in to the market. The later to keep those trained and at the late stages or post career able to stay current and activity if they want to keep a tool they know for retirement hobbies and play. but all in all get the price down and be aggressive in getting new customers to expand revenue and get faster development happening. If the plan is just to squeeze the orange harder, then we might as well jump ship and retrain.

With great interest I kept clicking links to find nothing but 404.

I'm sure it was an old wish but new version day and search doesn't find it.... Could we have different colour icons for Vectorworks versions? Or maybe a traffic light system we could set in preferences of the version. Black - current version to use. Green - old version still in use. Orange/Amber - New version testing. Red - Don't use except for pulling old files up to current. Added: Bonus Points. Company wide setting of the colours from a server.

Sure not the most complex plugin and offered without warranty. Add to your plug-in folder, then workspace and shift the key command you are use to. Close-Auto.vsm Save-Auto.vsm

Yep 4 years later finally got run to making Plugin that does this. Works rather nicely. Also made one for close that switches close and release if a working file. If anyone wants it let me know.

Thanks for the update but that just doesn't seem promising for even 2024 edition inclusion.

Shame Viewports styles hasn't managed a late streak... Sorry couldn't resist. 😉

The roadmap has 2 of the features in this video as "active research" not "scheduled" like the features for the industry packs.. How is the roadmap meant to read as a guide to what is coming?

Cautiously optimistic after seeing that. Shame "open in 3D" hasn't become a per viewport setting.

What's this easy grid markers you speak of? Last known feature in that direction didn't seem any easier that having a symbol with the full grid marker run including section markers. Features seem tied to the same per viewport visibiliities interface that make sections lines on plan which is both irksome and inconsistent.

Not really a workaround for us as we break up files that way then kind of just discovered it. But yes dimension handling needs work.

We actually generate our elevations and sections in a reference file so we can set the file units differently to get dimension tools like the benchmark to display correctly. Every dimension like thing should be able to change the display dimensions.

Also means your QA and beta testers get to pace themselves and can be active all year instead of a release crunch that might not time well for some. Let’s them concentrate on a smaller set of features at a time. would like to see a published schedule as part of say the road map. Even go as far as say certain months will concentrate on the same feature group each year. finally a plug for cleaning out the workspace make a new best practices one that allows improvements to slot in more effectively

I believe you can also use a roof with 3 sides set to be gable ends then the roof will add in the walls to infill each side of the roof.

How does BIM/IFC want this to occur? One of things needed in BIM to seperate responsibilities this would seems to be one of those areas where demarkation is required. Say separating Structure from General building envelop and further separating fit-out/interiors from General building envelop. I know, I know the answer is probably that it wasn't considered how to divide up roles as these "standards" seem to have come out of an everything under a single umbrella approach. Still how we work needs either demarkation or double handling. Basically double handling will continue, technology won't make our lives better but everyone will expect higher productivity because of it. Still if there is an answer to the question it might suggest how the feature wants to work if implemented?

Don't quote me if I'm off here going by memory... In Custom Renderwork you can turn off Anti-aliasing as the anti-alias pixels aren't transparent and don't work to a the background* so often end up making a halo instead of a blend. To me mind photo matching anti-aliasing isn't your friend anyway as things like plants are fuzzy to start with and building edges are hard and shouldn't be fuzzy. *this might be just because I cheap out and set it to low which might make to the pixels to big. Edit to add: Nice work on the entourage. Had so much trouble getting 3D cars to sit nicely aligned to the road surface like that in my last images.

@inikolova It wasn't hard to find. It wasn't labeled as such allowing for unwarned destructive action to occur. Also poor UI that it looks visually the same as the non-destructive close window button.

You can then explode the viewport to linework if you want to change a lot of things. or draw over annotation space. Second option is best as It means you need to fix model issues if they are too far out to mask in annotation space.