Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by tgm

  1. Beware of using VW output for precision CNC use. Look through the archives and see the probelms I had in the past on an output issue. VW is for drawing 'pretty' pictures and cannot be trusted for machinery output files wanting any precision. Maybe things have changed since v12.5 but I still think that even in VW2008 some of the problems still carried over. Try creating a simple bullnose with the fillet tool and you see that you will have to change the fillet size to smaller than 1/2 of the bullnose size in order for it to work. Look up the archives and se where we scrapped $5K of machine parts due to the output from VW. We only use it now for the most rudimentary of tasks. Can the newer versions even dimension in 3D yet?? Past fool time user... Tom in PA
  2. I am running a demo version of VW2008 and I am seeing differences in the final printing output bewteen the same file printed from 12.5.3 and VW2008. The font we are using is Marker Fine Point which we have used with 12.5 for years. When printing with VW2008 the final print output is faint and sometimes barely legible. I just did back to back prints and it's definitely a software issue unless there is something in VW2008 that needs to done differently, which I can't imagine. Is this just me?? Now I have a dilema in that the drawings I just did in VX2008 cannot be opened in 12.5 and I need to print them for submittals. Is this an issue with VW2008 or has it carried over to VW2009?? Thanks, Tom in PA
  3. Thanks Mike, It's amazing that it's taken up to VW2009 to resolve this issue. Whats even more amazing is NNA's lack of interest and response to all the queries about this issue. Well, I guess we have to go to VW2009 as I don't even know if 2008 is even available anymore. Thanks for the help, Tom
  4. I asked this question when VW2008 came out and I was assured that this isssue was fixed from 12.5. The issue is using the Offset command on a composed object that contains arcs. I have a very simple circular segment composed of two ars and two lines. I composed the object when designing and then had to offset the perimeter inward 1.5". The resultant inner shape, when decomposed, is made up of small straight line segments and not an arc. This type of behaviour causes major problems on our CNC output files and was the major reason we never upgraded from 12.5. I am using a demo version along with the interiorcad demo to evaluate interiorcad and low and behold this issue was never addressed or even fixed. Am I the only to complain about this issue?? This is the very subject that Katie and I had a go round on a year or so. Is this issue currently fixed in VW2009 as this is the upgrade we would be going to with interiorcad?? Thanks, Tom in PA
  5. Hans, Thanks for the info. You are correct in your thinking about Enroute being able to import WoodWOP-VARIANT(.mpr) file types. I have always seen this in the import listing but never paid attention to it. This may be the answer I was looking for as we are eager to use interiorcad. I will check with the Enroute guru's about the file importation using .mpr files. I will contact Sven after I do a little more research. Thanks again for the help,
  6. Hans, Thanks for the reply. We are currently designing in Vectorworks 12.5.3 and exporting dxf files to our toolpathing software, Enroute 4. Enroute then produces the G-code text files that we upload to a PC at the machine. Utilizing DNC software, the files are then loaded into the machine controller for processing. This is a very common practice here in the US. The other question remaining is...'is interiorcad able to export the dxf data that it produces so that we can process it normally as stated above'...?? If it does then we could forego the VectorWOP CAM module and use our existing software for toolpathing. This would be the ideal situation as we wanting to use interiorcad's parametric design features to streamline our material processing. Thanks again,
  7. Does anyone know if the older issues of offsetting composed objects has been corrected as of yet in VW2008 or VW2009?? The specific issue is when lines and arcs are composed and then offset using the offset tool and the resultant shape is broken up into various line segments and arcs. We are contemplating upgrading to VW Architect but are hesitant because of some the older lingering issues still out there, this being one of them which sparked a lot of heated discussion. Thanks, Tom VW12.5.3 WinXP SP3
  8. Not to worry. I will NEVER post another comment to this forum, nor recommend use of VW to anyone after this fiasco. As far as our use of the product after this expensive incident, which BTW cost me $5K to learn of this problem, we will be limiting its use to drawing 'pretty' pictures, no more. 'Attacks..........stabs..", give me a break. Most of the forum members are business professionals trying to use the product in their everyday business scenarios. Problems such as this only cost us money, out of our pocket, not yours. Over and out..........for good!
  9. Katie, If I have offended anyones ego, I sincerely apologize. What are you refering to as 'blatant comments and/or accusations in my post? I simply stated the fact that I cannot get a simple answer to a simple question, does it work or not? Surely it would only take less than a minute to verify using the example in my first of this thread. Regards,
  10. Check out my latest postings on Offset Issues and you will find, as I have, that this is still an issue even with VW2008. You will notice that I even asked the question of Katie directly about it working correctly in VW2008 and you don't get any answer, just a 'check with Tech Support' reply. You would think as the Lead Trainer at NNA she would just verify it and answer. I wonder how she answers the question when it comes up at a training session. To answer your question, anyone running VW has this issue. Good Luck,
  11. Katie, According the the first reply to my post above VW2008 still did not correct the issue. Can you verify is that is so? Doesn't Tech Support monitor the problems that this board brings to the forefront??
  12. Anyone from NNA want to chime in on this issue??? Or is it a sensitive topic..?
  13. It's amazing to me that such a simple tool is rendered unusable in a program of this caliber. I cannot afford to have someone work with this issue having to rely on his/her memory each time they use the tool. That is just plain ludicrous! To some of the users it's just lines on paper, to me it becomes $$$$ in the trash bucket. I sure hope someone resolves this and other issues soon. Tom in PA WinXP Pro, VW11.5.2..
  14. Katie, Yes, it's dual head card supporting both. Screen resolution has been played with and seems to make no difference. I am running one (1) 22" wide screen and I have to keep the resolution in a small area to keep screen items in proportion. Monitor refresh is set to 60hz. This has been set to 75 with no change. The FX3000 driver is set currently at We updated it a few weeks ago and rolled it back due to some other issues. The system was running with the older nVidia FX500/600 dual head card for years and the problems arose after VW11.5. Hope any of this helps.......... Thanks
  15. Pete, I have had my desktop manager disabled for quite awhile now and I still get flickering and the slow fill-in of the OIP. Don't know if it was worse when I had it on but I'll give it a shot and check it out. I have the same video card that I was using in 11.5 which exhibited none of these problems. I'll play around a little, Thanks,
  16. Where in any part of this thread is anyone being 'nasty' and claiming these bugs are done on purpose?? Show me... On the part about '...fixing things they can..', go and review the thread on 'screen flicker' that has not been addressed for the last year. All that time the hardware is to blame. I totally understand about the possible combinations and permutations of hardware and how it relates to any application, but this has absolutely nothing to do with the basis of this thread. The purpose of these forums is for users to air their problems and help NNA get a handle on all items affecting different platform and hardware configurations. If we have so called 'thin skinned' programmers who feel that this a personal attack on their work, then they should be in another business. If we don't work together as a community, nothing would ever get fixed and VW would go down in history. Remember, it's only business.......... Enough on the subject,
  17. Lumberjack.....who would have guessed! Tiny, but vocal minority, is correct. Why shouldn't we be??? We are paying customers trying to use the software to help earn our living. It may affect more VW users than we can tell, as most users probably don't contribute to this forum. They may be on the sidelines but with closed lips. Look at me for an example.... I have been with NNA and their predessors since MiniCad 1 and I joined the forum, much to some peoples dismay, in '04. I was also on the sideline group for years. Altoids is right.....we are users and NNA customers, not guinea pigs! Basic stuff should come out of the box right, period. A few glitches here and there, OK, but let's try to get it right guys.
  18. I'll make sure I update my profile to my city and country of birth also so as not to confuse anyone. Gee...the original starter of this thread must be a figment of someones imagination or an alien as he does not tell where he, she or it resides. Hmmm? Then again it's only Sunday here in the non-civilized world, Tom .....somewhere!
  19. This is the kind of issues that really gripes me. How can you design and test software and have an issue as simple as short field lengths for data entry??....and then someone labels it as a 'known bug' to be fixed sometime later. Really sad if you ask me. Come on guys this is basic.....but then again we have updated the refrigerator libraries...! Tom in PA
  20. Pete R. I agree with the 'moving target' scenario. Things can be more easily solved if they just up and die, so to speak. I agree that something else may be in play here but is the software makers responsibiliy to insure that it us compatible on all platforms that it sells. They can get the updates just as you and I can. I may sound harsh at times but I am still a staunch supporter just as I have been since the first MiniCad days. I am still here so that speaks for itself. My gripe is that more than one person has complained about these issues over the years and it should have deserved some attention then. Instead it was just shrugged off as a hardware problem and a fix was never in place. Now that the latest and greatest VW2008 is out and it too has the same issues, now it gets addressed. Why....because future sales and upgrades are now on the edge. You gotta love it! Thanks for the support, Tom in PA VW 12.5.2 and falling...... WinXP Pro SP2 nVidia FX3000
  21. Pete R. states....."The same thing happens often (talking about 12.5.2 as well here) when: entering a viewport, clicking on a window or door, editing a callout." Pete A. states....."VW appears to be doing something similar in that each time you select an object the main window flashes.." This is exactly the behaviour I have been experiencing over the last year since upgrading to VW12, as attested to my numerous posts concerning screen flicker, weird Callout happenings etc. It still gripes me that now that NNA has finally admitted to actual having an internal problem within VW that I will be forced to pony up and upgrade to VW2008, when VW12.5 suits our business just fine, in order to eliminate an inherent that was duly noted in VW12 and was not looked at or addressed in VW12.5 or subsequent updates. It just doesn't seem right...... I even remeber a post by Mr Anderson stating that these types of issues were hardware related and not VW related. So much for that thinking. I just got a call from the sales staff at NNA offering me the current upgrade as they always do and ever other time I just upgrade immediately. Yesterday I said 'NO' just due to all the issues that have come up with VW12.5 and VW2008. We are now going back to 11.5 which exhibited none of the above. When, and if, NNA gets all this sorted out. we may upgrade. Until then we will go backwards...sometimes change is not for the better. Thanks, Tom in PA
  22. Congrats.....someone at NNA finally got their screen to flicker! Operating System...WinXP Pro SP2 Software...........VW12.5.2 Fundamentals Video Card.........nVidia Quatro FX3000 256mb Screen Resolution...1440x900, dual monitors Most flicker occurs when selecting items, callouts and or dimensions. Menu bar and OIP flickers intensely and OIP slowly paints in the information. Can be timed in increments of 5 -10 secs, easily at times. Happens on any file size, most of mine are fairly small. New file or existing makes no difference. VW generated info or imported no diference also. Seems to have gotten worse after upgrading to the original VW12 from 11.5 where minimal flicker was also apparent but no where near 12.5.2 Hope this helps.... Thanks as usual, Tom in PA
  23. Pete states... ...I began to notice each time I selected a new object it seemed to take longer for the OIP to populate with the data... This is one of the issues that has been brought up in the past in a 'screen flicker' thread. Then it was always someone elses problem...ie video card issue etc. Now NNA is "...looking into the problem..". What was wrong with looking into it before the 2008 release?? There was never even any admission of a problem. Really good communication to its customers, don't you think! Back to 12.5.2 and all its issues, Thanks, Tom in PA
  24. About a year ago I submitted a file and got a new Callout Tool to replace the original in 11.5. Someone from NNA sent the file via email for to try. Result was no change. I have been complaining ever since and have gotten no where. I can't even get anyone from NNA to say they can even duplicate the problem and I am not the only with the issue. Tom in PA
  • Create New...