Jump to content

Peter King

Member
  • Posts

    17
  • Joined

  • Last visited

Everything posted by Peter King

  1. @Jeremy Best Apologies for not acknowledging it before but many thanks for your reply. In the current version of VW (2024) this issue seems to have been addressed - partially at least. Inserted objects such as RHS sections do now get moved when inside a reshape marquee but the screen doesn't update instantly, at least it doesn't on my M1 Macmini. After a refresh or deleting the items and bringing them back with a cmd+Z they have been moved as intended. I seem to remember this happening on an earlier version of VW some years ago so hopefully the issue will be resolved in a later service update this year.
  2. A useful trait of the reshape tool always used to be that if you included an inserted object inside the reshape marquee, (eg a 'wide flange' steel section) it would get moved along with the lines and other elements that were being stretched or shortened. Unfortunately this no longer seems to work! I have noticed this since about VW2020 and have up until now just put up with it, using a workaround by reshaping the lines etc first and then moving any included inserted objects manually. I just wonder if there is a setting somewhere that inadvertently got changed that is causing this to happen. I have trawled through preferences and settings but cannot find anything. I can't seem to find any reference to this on the forum or even on a general Google search so if anyone out there has any ideas I would love to hear from them! As an addendum I would just like to point out that any home-brewed symbols that are included in the marquee continue to be moved as before, it seems only inserted elements such as steel sections that don't get moved.
  3. Installed SP3 yesterday and so far, great news, most, if not all, of the problems regarding slow text editing and getting artefacts etc. seem to have been resolved, along with a number of other niggling issues. At long last! Still slow in opening the 'Title Block Border Settings' interface which is still a pain in the workflow but other than that, VW is again a pleasure to use. Regarding the 'Title Block Border Settings' box, perhaps it could be broken down into smaller units so it's faster to load? You mainly want to edit the revision data and the sheet data for a new sheet. Therefore you don't usually need all the myriad options available as you only update the Project data, Sheet Border, Title Block etc once or twice in the life of an entire project. So double clicking a title block you want a small options box where you can set default actions and then select 'Don't show this box again'. One option needs to be 'Edit Sheet Data and Revision Data only' that you can set as a default action and voila, you have a smaller box that should open much faster.
  4. Thank you Nikolay. I think it opens marginally faster after the first time as presumably the code/data is cached in RAM. I wonder if it could be split into two dialogue boxes somehow, so the larger, slower box deals with less frequently used aspects of the drawing such as Project Data, Document Options, Drawing Stamp etc and then a smaller, faster box deals with frequently used aspects like Sheet Data and Revision Data? Kind regards, Peter King
  5. Does this happen with the OIP undocked? Yes it does as I have the OIP undocked all the time.
  6. Also still got the problem mentioned above: ... when double-clicking on a title block (2019 SP2 Mac Pro) to update it takes an age for the 'Title Block Border Settings' box to come up. Just measured that with my stopwatch and it takes on average about 2.4 seconds for the box to appear after double clicking on a title block.
  7. Hi Marissa. When editing text blocks on screen, moving the cursor with the arrow keys can be a bit erratic, yes. Editing text in a call out box is quite annoying as the cursor leaves artefacts - please see attached screen grab.
  8. Yes on the whole VW is an excellent program - I've used it for about 6 years on Macs now after about 20 years using AutoCAD on PCs and much prefer it but these current problems are quite a major issue I think.
  9. Hello there. The problems I outlined above still exist without being resolved at all which is quite disappointing. Currently I'm just putting up with them but I live in hope that there will be a SP3 soon which will address some of the problems. As the problems don't seem to exist on the Windows version I can only assume that the VW software just hasn't been written to integrate properly with the Mojave graphics system. I'm currently trying out other CAD programs like Bricscad which seem to work perfectly well on the Mac, so I'll certainly be thinking very hard about renewing my VW subscription later this year if the problems persist as they are really slowing down my workflow.
  10. Hi Melissa. Another problem that I didn't mention before and that may be relevant is that when double-clicking on a title block (2019 SP2 Mac Pro) to update it takes an age for the 'Title Block Border Settings' box to come up. Literally about 2 seconds which is a real trip wire in your workflow!
  11. Thank you Marissa. Glad it is being looked into! Kind regards, Peter
  12. Thank you for your suggestion Marissa. I did as you instructed but I'm afraid it didn't make any difference. Still the slow/hesitant text editing and the artefacts in the Callout editor. My gut feeling is that the problem lies at a low level in the graphics area, as strange things do happen from time to time. I won't go into great detail here as they are quite difficult to describe and too time consuming! A common thing is that artefacts sometimes get left on screen after move and erase operations (I can easily get rid of them) and also some operations when using split screen mode cause a number of 'ghost' images of the entire window at varying sizes to appear. When this happens I have to close and reopen the file I'm working on. These problems only occur on the Mac Pro & MacBook Pro (never on the PC) and only when using VW, never with other software, so I am certain there is nothing wrong with either machine. (As I said before though, the current text editing problem is only on the Mac Pro running Mojave, not on the MacBook Pro running High Sierra). None of the problems are critical, just a bit annoying!
  13. Hi Marissa - many thanks for your rapid reply. I can indeed confirm that, as stated in my post, I am running VW 2019 SP2 on MacOS Mojave 10.14.1 Mac Pro (Late 2013) 3.5 GHz 6-Core Intel Xeon E5, 2 * AMD FirePro D500 3072 MB, 64GB RAM) The problem occurs on all files that I am working on, newly created ones as well as ones created on older versions of VW. As I say, running the same version of VW on my MacBook Pro, which I have not yet upgraded from High Sierra, it runs perfectly acceptably. I have sent you one of the VW files that I am currently working on, but as I say, the same VW files that I have problems with on the Mac Pro are absolutely fine on the PC and the MacBook, so I am sure it isn't a problem with any particular VW file. I have also sent you a screen grab of editing Callout text where you can see the artefacts caused by simply back-moving the cursor. I have just noticed that this doesn't seem to occur on the first line of text, only on subsequent lines. Strange! The problem must be something to do with the Mac Pro's outdated technology and VW's coding. I have a trial version of VW 2019 SP2 running on my PC (Windows 7, which is also quite ancient) which does not have the problem and also a licensed version of VW 2019 SP2 running on my MacBook Pro (Retina, Mid 2012, 2.6 GHz Intel Core i7, 16 GB 1600 MHz DDR3, Intel HD Graphics 4000 1536 MB running High Sierra 10.13.6) which does not have the problem. The delay is quite slight, so it is not making the program unusable, just a little frustrating and annoying when you know it should just fly along like any other piece of software on high end (albeit dated) technology! Denmead.vwx
  14. Running VW 2019 SP2 on MacOS Mojave 10.14.1 Mac Pro (Late 2013) 3.5 GHz 6-Core Intel Xeon E5, 2 * AMD FirePro D500 3072 MB, 64GB RAM Experiencing a consistent problem when trying to edit text. After clicking on the text, moving the cursor about and editing is SO SLOW! Also editing text inside the Call Out tool is slow and artefacts are left behind by the cursor. These problems only started with the upgrade to Mojave. On my laptop, which is still running High Sierra and the same version of VW, the problems don't exist. There are also still annoying incompatibility problems when importing and exporting DWG files, line thicknesses and arrow sizes especially seem to be a problem. Currently trialing Bricscad which flies along in comparison to VW and also seems to be more compatible with DWG drawings (which is unfortunately a requisite in my industry as I often need to exchange drawings with AutoCAD users). If SP3, when it eventually comes out, doesn't solve the problems with Mojave then I think when my VW subscription runs out next autumn (fall) I shall have to move on to another CAD platform - suggestions welcome!
  15. Had the same problem (spacebar-pan ceasing to work suddenly) this morning after always working fine. I also had Safari running and prompted by one of the ideas above, I quit Safari. That did the trick! The spacebar-pan shortcut was working fine again. Rebooted Safari and spacebar-pan still working fine so looks like it's possible that something in Safari scuppers that invaluable shortcut at random?
  16. Many thanks for your help. You have some interesting sounding solutions there. I have tried your suggestion of adding an 'ACAD' prefix to imported DWG layers and that works a treat. Don't know why I hadn't spotted that! Thanks again and best wishes, Pete
  17. Hi When importing a DWG file into a VW model, I am finding that if any layers in the DWG file have the same name as any of my VW classes, the settings for the DWG layer are overwriting my class settings. I am currently getting around the problem by doctoring the DWG file first in Autocad LT 2010 and putting everything on Layer 0. This works OK for the particular job I'm working on currently but isn't an ideal solution as it is time consuming and if I forget to do it then all my classes get corrupted! Is there an import setting that I can change to avert this problem? Many thanks, Pete King
×
×
  • Create New...