DMcD

Am I the only one to find that the changes to the 2024 interface compared with 2023 are… daft, unnecessary, pointless and measurably slow down workflow to a large extent, especially if you've used VW before? Moving the classes, layers, views drop downs and reducing the drawing space does not seem to achieve anything in usability… or am I missing something? There's now some odd icons between the tool palette and the tool options which used to be on the right side and could largely be ignored. They're now on the left side. Why?? It looks like change for change's sake when you've run out of ideas to add properly usable features. Or am I missing the bigger picture? There's another thread on the View Bar Sort Order requesting customisation of the view bar or whatever the top of the window is called. I'd certainly vote for anything which allowed see to revert to the functional top bar of the previous decade or more! D

I have had this problem intermittently. I can leave the splash screen for 30 minutes or so and VW has started. Then I have no problems for a month or more. I just restarted the computer for another reason and VW is stuck on loading Cineware. I'm on SP2 and Monterey so I don't think it is Ventura related. Probably VW or Cineware. I got two suggestions from support (who also have had the problem)… 1. Remove Redshift from Cineware / plugins and launch VW. 2. If you still have the same issue, rename Cineware folder and launch VW. HTH D

Thanks for the replies. We own our own CNC machines from multi axis mills and turning centres to flatbed routers, some with Siemens controllers (mainly dreadful) and others with other controllers and software so I know well the limitations with post-processing VW DXF files for CNC. For production parts, I only do use lines, arcs and circles. However it's the VW surface extract tool which converts arcs in polylines to beziers, not me! Useful entities like rounded rectangles (for a machined slot) are converted into a mess of points. I have to go back and either redraw or manually extract the original arcs and lines profile from the model and paste it into the 2D file. Is this what we use CAD for? Not me! You suggest doing a paper PDF print… it's this which is the major time sink. You might accurately draw a shaft or a bore in VW to 1" but when you come to dimension this in a viewport, VW will rarely give you an even number like 1.00 any more, it's aways inaccurately to one or two decimal places which of course is useless for production of anything other than cheese. And trying to extract a diameter from a circle doesn't seem to work at all unless you draw the circle again in the viewport annotation. All this leads to mistakes and a loss of precision which oddly, is what we started using CAD to avoid. You should not have to draw a part twice. I had a Morgan Plus 8 once. Morgan specified the length of the car to ±2"! You would not get away with that any more. But as they said to a parliamentary enquiry, "We have a five year full order book, and you?" Post processing software varies enormously. One program takes groups but insists on the outlines of polys being decomposed. Another won't see a group but is OK with contiguous polys. You learn this. For work done outside, we normally take the dumbest option. However, it's for outside work that we get the most problems where either their post-processing software is different to that which we use, or more usually, the operator doesn't know enough about CAD to run it or they require drawings to an accuracy which VW seems unable to offer without a lot of workarounds. In most cases, in-house, we decide in the post processing software how to sort the paths because it's a tool path then, not a drawing. So with round holes in a perimeter, what we do is based on the tools used to cut the shape. Most of this is tedious but well understood. "Nesting - I can always beat the nesting software" You're using the wrong software! I've been nesting since MiniCAD 4 and I would bet you that there isn't a human out there who can do better than the best nesting software unless the shapes are simple and/or the time really long. As a test, I have nested really complex toy puzzles in 10 seconds which would take almost anyone minutes to complete. I have nested files with hundreds of shapes over 3000 feet long down to a fifth of this in under 20 seconds and got results which were 5% better than I could achieve in hours. D

Hello. Does anyone still use VW for drawing things which need manufacturing with any degree of accuracy? For example, metalwork which needs CNC cutting on a mill, laser or waterjet? I find that VW's 3D modelling is generally great but extracting geometry for real-world machining is like having teeth pulled. 10 times as complicated and not entirely accurate. Even though objects are drawn by numbers to a precise size, when it comes to dimensioning a viewport, VW seems to be only somewhat accurate. It's almost always a decimal point or two out. And when it comes to actually making a DXF file to send out for production, the drawing has to be almost always done again in 2D because arcs become beziers, arcs are split and circles become semi-circles etc. Snapping seems also to have become a bit vague and I find myself deconstructing models and realigning objects over time in spite of rigorously aligning them in the first place. Or is this just me? D

I have a Mac Pro and a 16" MBP with the M1 Pro chip. VW works better on the MacBook than the Mac Pro. That being said, screen drawing appears to have slowed in current versions of VW 2022.

That world "legacy" fills me with dread. While I have been working in 3D 100% for some time, there are occasions when 2D is essential. All water jet, plasma and laser cutters are 2D and many will throw a wobbly when given anything which is not 2D. So for a lot of real world work (in other words, anything which isn't printed or emailed) abandoning 2D could be the end of the line for many VW users. Yes, VW is not great at converting 3D objects to 2D. The extract tool is useful but riddled with bugs and anomalies such as converting arcs in polylines to bezier curves and converting circles into two 180º arcs. What I find concerning is that VW might think that nobody uses 2D and rather than improving these tools, they'll abandon 2D altogether. Please say this is not so!

HA, What do people use as a crash recovery technique to make sure that work is not lost somewhere in the wreckage? Using VW 2020, 2021 Mac OS 10.15 etc. I get three or four crashes a day (before coffee time) (and we take coffee early around here) and sometimes it's difficult to know what's been lost. A backup is saved every 10 operations. Once upon a time, VW would tell you if something could not be regenerated. This appears to be no longer the case, lulling the user into a false sense of security that a backup is similar to the work in the original file lost during the crash. Since I discovered that VW crashes a lot less with small files, I have been working on sections of a drawing and copying them into the main drawing only after a nervous save (a lot of the crashes are just after saving, losing the saved work). The problem with this strategy is that when you have multiple windows open with multiple structures in different states, it gets confusing to know what's what during a recovery. When the time comes to work on larger files, it just a lottery. If there was some routine to check and compare two files after a crash, it would make me a lot less insecure. I guess the usual suspects will say reinstall VW, update to the latest version, trash prefs, redo templates etc. I've done all these with no apparent improvement in stability and really, my job is designing not IT. It's not even as if I am guilty of doing anything. The most recent crash happened while VW was sitting in the background all by itself. It's not even as if any other software that I use bombs as often as VW. Adobe stuff bombs but you'd expect that. However it recovers gracefully which is something VW does not do. It's up to the user to pick their way through the wreckage and salvage something. So what's your strategy? D

HA, I'm having many fairly consistent problems with Undo (triggered by a keyboard shortcut) with VW 2021 on a Mac. Instead of stepping through a series of undos, performing one undo reverts to the first version in the stack and doing a Redo doesn't restore the previous state of a drawing. The big problem with this is that I've no longer any sure way of knowing what state the drawing is because things I wanted to keep may have been deleted. D

HH, I can't see that as being a problem if you upgrade your CAD software annually. Apple does change the OS, frequently to cope with security problems but it also issues beta versions of operating systems which developers can download. The problem with VW is mostly that their release cycle is just one month away from Apple's. If it was delayed, then they would have a better chance to fix bugs caused by changed APIs. Well that's certainly something I could do… but wait a minute, I'm a designer! I could not sit in front of Windows for more than a few minutes without wanting a headache pill! Some years ago, we had a French intern who had big design aspirations and was a big Windows fan. I grabbed his laptop and turned it upside down alongside mine and asked him which, as a designer, he preferred. One looked like the underside of a 55 Chev. The other didn't. But that's just a matter of taste. If I go into our computer graveyard, there are as many PCs as Macs. But we use 6 times more Macs than PCs. My previous Mac was 2013 and still works brilliantly. I do hear what you are saying about constant updates through. I'm well over it. However Adobe is not the best example to use since every update is just moving the furniture and increasing their interface nightmare! We're all on an update bandwagon which is impossible to get off. D

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff71f1733a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff71fd3e60 pthread_kill + 430 2 libsystem_c.dylib 0x00007fff71e9e808 abort + 120 3 libGPUSupportMercury.dylib 0x00007fff5921b0a5 gpusGenerateCrashLog.cold.1 + 95 4 libGPUSupportMercury.dylib 0x00007fff5921218f gpusGenerateCrashLog + 89 5 com.apple.AMDRadeonX4000GLDriver 0x000000011fd688b1 gpusKillClientExt + 9 Possibly: gpus_ReturnNotPermittedKillClient causing huge number of crashes https://forums.developer.apple.com/thread/30896 The crash happens mostly after a save action. The file isn't saved. D

"Good luck" is about right. Not a professional standard though. Rather than having to reset everything, I bought a new Mac Pro running Catalina, new monitors etc and did a new, clean install of VW 2020. Isn't this. troubleshooting 100? Currently running with a backup every 10 actions and the lowest, worst graphics settings, I regularly get crashes (well, regularly within each hour) and lost time and work in backups. It's a miserable state of affairs. What's worse is that with SP3 now, VW 2021 is just around the corner. I feel that it's time some software companies concentrated on stability rather than new features and at some time, said sorry to their users and gave a year or two free until the software was (at least in this case) at professional level. D

>>please contact (or prompt, or get back to) the tech support provider for your region about this so they can either establish a path to resolution or escalate to Vectorworks software engineers. You also have the option of submitting a bug report directly to engineering. Use the 'Bug Submit' link at the bottom of this page to do so. Done all that and the replies were… 'nobody else is experiencing this, or 'your computer config is unusual' or 'wait for the next bug fix release.' And also, on submitting a complete working bomb and procedure with a file, "that bug is really obscure, don't expect a fix any time soon.' I have been religious about submitting well documented bug reports over the years and on every new release looked to see if my bugs were squashed and the answer is overwhelmingly no. This thread is about Catalina compatibility. VW 2020 is compatible with Catalina under some circumstances but bombs a lot for me, often many times a day. What else can I say? D

Honestly, I think this is a huge cop-out and an abdication of responsibility to the customer. I pay for VW service select every year and dutifully install increasingly buggy upgrades and lose time and work from continual bombs. This is on several computers with everything from old messy drives to brand new top of the line clean computer installs… and the behaviour of VW is the same. While I know that Apple is to blame for a lot of the problems, I'm not paying them for system upgrades, but I am paying VW for service select. Any yet I have to search VW Help for advice which is normally 'nobody else is experiencing this, or 'your computer config is unusual' or 'wait for the next bug fix release.' The alternative is to call a live human at Apple (who I have not paid) for a chat about the problems with a third party app? 2018 was pretty solid. Sure there were feature limitations which largely still exist in 2020 but it did run reliably. •• Only two crashes yesterday and one was VW leaving the room while it was in the background. Probably only 15 minutes lost reconstructing files from backups. D

>>It is logical to me that the problems you have described have absolutely nothing to do with the compatibility of Vectorworks with Catalina. I guess it's always logical unless it's happening to you. Since I cannot downgrade to Mojave or VW 2019 (which were good in the last 6 months I used them) I have to sheet this home to both the current version of VW and its relationship to the current OS… Oh, and VWs reluctancy to do much about this sort of thing unless it's stating 'it must be something you are doing' or 'it must be your video card' or 'perhaps try using just one monitor' or 'what happens if you don't turn your computer on?' Since VW 2020 had so many problems with my previous Mac Pro and Cataina demands it, everything is on the main HD in the docs folder. No network, no external drives. Clean install of everything. I can't see that saving onto the desktop would make any difference. The crashes happen for all sorts of reasons… perhaps saving or autosaving being one of them but by the time the crash has happened, the times on the autosaved files are not exactly current so you can't say that it was one keypress or another which caused the bomb. It's largely a graphics kernel error which happens when changing layers, changing views, saving, etc. >>If Step 1 works fine and Step 2 let crash the application, then let try to split Step 2 in several smaller steps. It's difficult to split saving into more than one step. That being said, the menu highlights for a while after pressing the save command and the crash happens afterwards, and the file itself is not saved suggesting that VW collects everything before spitting the dummy and does not save anything. Only in the last few frustrating hours has it has been when pasting a group from an autosaved file back into the main file and saving I have had crashes. If I don't save, I can work for a few minutes… but what's the point? The group copied from the autosaved file has the same geometry as the main file and is opened from a saved… obviously. But the backup file has a warning that shapes cannot be regenerated so all I'm interested in is the last 10-20 actions on the objects in the copied group. However, it's not just that. There are a lot of oddities with this version of VW, from the inability to dimension anything other than corner points in viewports to inaccuracies with dimensions in general which were in most cases, not there in earlier versions of VW. I have submitted many repeatable bugs over the years but rarely if ever seen any fixed, even to the point that in one instance I was told that 'this is unlikely to get fixed since (though repeatable) it's fairly obscure. Really, any full bomb signifies a problem somewhere which should be fixed. For me, VW 2020 and Catalina are the most buggy versions of VW since… well VW 2019 and Mojave in the early months. Normally obsessive saving and autosaved backups mean I only lose about 1/4 of the day. I don't need most of the new features but I do need stability. I also don't need being told that my setup, whatever it happens to be that month, is unusual and therefore a cause which doesn't need following up. D

HA, I wonder if the work 'compatible' needs defining in the context of VW and Catalina? I am running the latest version of VW 2020 and Catalina and getting a crash every few minutes, mainly while saving. The error msgs claim it's a graphics kernel bug but the bombs happen after a save. This is a bit of a catch 22 since I have my version autosaving after every 20 operations. I guess I'm only losing 20 minutes of work an hour recovering from each bomb. Is this normal compatibility? D