rDesign

I just tried with the same result as you: I can’t submit any feedback on the Roadmap.

Presumably you meant to say “all content is now available” ?

A google search for “vwf file extension” says that it was created with CADvance software, not Vectorworks. You may be able to convert them online, or just ask the architect who sent you the files to convert it to DXF. Vectorworks will not be able to open those files.

I use a ‘one file’ methodology, where the Site model is referenced into the main project file, along with all of the referenced construction details (at differing scales): I always have Design Layers at multiple scales in a file. It may just be a bad habit that I’ve picked up in 25+ years of using Vw. Question: How do you deal with construction details (at differing scales) which are referenced into a base file? (Apologies if this is outside the scope of this wish-list request, but I think it is relevant to understand the need).

Not specific to MBP mice, but here’s a fairly recent thread discussing this: [Side note, I use a Logitech G502 mouse with the third-party mouse utility SteerMouse.]

Even though the Vw2025 system requirements say that macOS 13 Ventura is the minimum macOS, I have installed Vw2025 on my 2016 core i7 MacBook Pro (which cannot install macOS 13) — and granted I have not used it much (less than 1 hour this week since release), but I haven’t had any issues with Vw2025 on macOS 12.7.6 so far. In case that was one of the factors in your need for a new computer.

According to Vw’s KB article on Vw2025 System recommendations (arguably more relevant than C4D & UE) :

Others with direct experience using M-series Macs can weigh in — I’m still using my 2017 MacBook Pro (though probably for not much longer). Take a look at the KB article on Vw2025 System Recommendations, it offers some general guidance on recommended RAM amounts based on the types of projects you anticipate doing in Vw, and also whether you will be using external / multiple 4K monitors.

@MMGD But do not get any Mac with the minimum 8GB RAM. As evidenced by multiple threads on the forum, you will be very disappointed with how Vw performs with that level RAM. With unified RAM, more is still better (despite Apple’s claims), especially when it comes to Vw.

I filed a bug report / support request yesterday - I haven’t heard anything back yet. I’ll post back when / if I hear something. I don’t use it that often, but since it has been around for 4 years, it seems like it needs to be fixed — or at least brought (back) to their attention.

I don’t have any insights, but just wanted to clarify that your VWX file is 160 GB…? (1,000 MB = 1 GB) That seems very large.

I was only ever able to ‘fix’ it by restarting my Mac, it would stay away for a period of time before I needed to restart again.

It looks like it is related to a similar issue reported in several other threads. I do not know if there was ever a solution for it.

I haven't used it yet, but based on your description - in the interim - could you make the typical 18" backsplash the full-height up to the bottom of the exhaust hood (36" or 42"), and then use the backsplash modifiers to subtract areas where the cabinets are?

I just opened that same sample file in Vw2025, and it still creates the messed up Retaining Wall Site Modifier. It needs the same slight movement of one adjacent bezier points on the curve to fix it. I don't know if anyone has submitted this as a bug, but I'll submit one for it.