Jump to content

Mik

Member
  • Posts

    87
  • Joined

  • Last visited

Everything posted by Mik

  1. The problem was with OpenGl on design layers for me. It doesn't matter what kind of texture it is and it is not selective about the nature of the texture content. I try clicking around on things, moving in/out, changing views, etc. These things sometimes get it to come back. Other times, delete and recreate, close and reopen, etc.
  2. This problem persists in SP 5.3.
  3. Same here on SP5.3 ! For a while I was having luck getting textures to display by selecting the last item in the drop-down Part menu of the OIP. I did not even have to change that item - just selecting it would cause the other side I wanted to texture to appear. But then it would stop working altogether. Sometimes it will render the next texture from the list of textures chosen. So I would chose the wrong texture to get the correct one to display. But that stopped working as well. It just doesn't work reliably. Extremely frustrating when you have clients that need rendered work for review.
  4. It's usually like this for me: one glitch turns into the discovery of a bunch of them and halts progress. Trying to join a curved 2x6 wall to a straight 2x4 wall. It worked on the lower side (see first image below) but the top side continues to give error that the "parts do not completely intersect". Zoomed in close to the failed join and saw the curved wall is .022" short of the straight. Given that it is a curved wall based on a center point, I can see why it would reject the join but just bombing isn't very helpful. A message like, "You need to increase/decrease the radius of the curved wall or reposition the intersecting wall ..." would be more instructive. Anyway, I pulled the straight wall down .022" and made the join but it caused the whole thing to be hollow - shown in second image. When hollow like that, it can only be seen in plan view. Any other 3d view leaves an odd 90-degree line echo of the wall: So, reboot, etc. - no change. Fresh file with nothing but a design layer and a few walls below and it won't join at all regardless of alignment. The only thing it will do is alter the course of the straight wall if you start the curved wall from the middle of the straight wall. (Which I do not want - I need an intersection.) Since it worked in one location, failed on the other side, caused one to disappear, and fails to get anywhere on a fresh file, I am inclined to think this is a bug. I am on VW2019 SP5.3 On the shy chance someone has an idea or workaround for this, I am "all ears". Regards, Mik
  5. michaelk, If we turn off a class that contains high-vertex count meshes (for say plumbing fixtures), will VW quit trying to process them or does it process them anyway? I believe I tried this and did not notice any gains but was done on a more complete project where there was plenty else to process so hard to say what is happening.
  6. Thanks Wes. What is the proper way to use this? When I place it on my floors it shows a caution symbol. When the point is dragged, it shows 0 sq. ft.
  7. Thanks Wes but my VW 2019 said this was from a previous version and would convert it but then could not do it.
  8. Hats off to you for creative workarounds but Vectorworks should just show it in the OIP like they do for other things. Basic functionality and usability is really lacking in this app.
  9. grant_PD: I'm with you. Its a completely simple thing for Vectorworks to just show the area in the OIP but it is bereft of a lot of data. The Vectorworks help shows a lot of data including area for slabs in the OIP but that is not true for floors. And the Volumetric properties as someone suggested gives the area all around the slab (top, bottom, sides) so that is useless when trying to get floor square footages for various purposes. Consequently, to reference the size of a floor, we have to go back and draw another polygon over it to find out. It is this kind of thing that makes Vectorworks so frustrating to use.
  10. Mik

    OpenGL died

    I created a new file, copy/pasted only the relevant things from the old file to new, and fixed a bunch of things that broke from the copy. (Alignment seems to break for some things like columns, some plumbing fixtures, 2d objects, etc.) Everything was running smoothly until I started messing with the door that is highlighted in the first screen shot. The problem wasn't coming from Microsoft's coincidental update or drivers, etc., it was that door. I had been experimenting with a lintel and noticed when I made changes to the thickness or protrusion that it would remove the door from the wall. It was still in the same location but it was no longer identified as "Door In Wall" in the OIP. I would try to pull it out and replace in the wall unsuccessfully. Undoing the changes would get back to "Door In Wall" but would sometimes leave the changes I made to the lintel intact anyway. I originally ignored the annoying pop out since it seemed to get the changes in place despite using Undo. Once this happens, however, I notice that the door will not highlight under the mouse at all from any view. But if you click on it, you can select it. Anyway, after running into this door popping out problem, the strange disappearing act of views from left to front quadrant return and OpenGL looked wonky again. I have now gone to a backup from before the door changes. Things are fine and have now made several modifications to the door and it has not flipped out yet. Crossing my fingers because I need to finish this to meet with client. But hope VW people are going to look into this. While working with my door, I am stymied by another VW limitation: muntin options available for door transoms are less than regular windows. In fact, muntins in general for VW are limited to a sort of elementary "popular" set of options. Often standard product orders just can't be created w/VW. I have to go manually draw lines all over elevation sheets which takes time while perspective views are just about off the table. We need the ability to set muntins wherever we like - which leads me back to a previous complaint I posted about the disappearing element of an intuitive WYSIWYG interface to VW. Why not just show the window/door diagram in the settings box and give us the option to visually lay out the muntins? We can move around till we like and/or place by measurement entries. (This includes curves as well as straight lines.)
  11. Mik

    OpenGL died

    I found that if I did not zoom and move "manually" over to the 0,0 XY location, I could select the object and delete. This was from an .obj that had 40 meshes. With it removed, I seem to be able to move around without anything crashing now but the original problem persists: the model disappears altogether when trying to view from the quadrant of left to front and OpenGL looks wonky in any view (but still blank in left-to-front quadrant). Should my model be at 0,0 ? Why are sheet lines lined up with my model but several hundred feet away from 0,0? I am going to try copying everything out of this file into a new file with the origin in center.
  12. Mik

    OpenGL died

    Okay, so I realize that in going back and forth from BSeigel's instructions and the screen, I skipped over turning on all layers as well as classes. In trying different layers, I found something but have not been able to select it. As soon as I zoom out enough and try to select, VW locks up. And here's the thing: the small line or whatever at 400'-600' away from my model is showing up at 0 center on the XY measurements at the edges. It is the model that is way out from 0 but the sheet lines indicate the model is in the proper area. I managed to get a screen shot before crash:
  13. Mik

    OpenGL died

    Dave, I should have checked that. The driver did need updating but the problem persists after updating to the current NVIDIA driver.
  14. Mik

    OpenGL died

    An update: hidden line will render correctly where OpenGL will not. It takes 5 minutes but it gets there. Though I have never needed to wait 5 minutes for a hidden line rendering before. I have been working on this file successfully for some time. One coincidence: Microsoft updated my system last night. These problems started after the update. But other files seem to function fine. I have mountains of work in this particular file and right before I was finishing things up for presentation, !@#$ I am stuck if I cannot even get a front elevation.
  15. Mik

    OpenGL died

    BSeigel, Thanks for the quick reply and pointers. I tried your steps above and turned up nothing out of bounds. I edited my post just as you had replied: So the display problem appears to be consistent: OpenGL is blank in the quadrant from Front to Left views, funky on Back and Right views, looks accurate in top and bottom views. If I rotate, it turns blank when I get around the front and left sides. Wireframe disappears in that Front to Left quadrant as well but when it is visible in other views, it looks accurate as opposed to missing stuff like OpenGL. If I close VW and load up, the last view it was in (right isometric) comes up in wireframe and switching to OpenGL is good. But its flaky. As I see proper OpenGL in all selected views, I cannot use the CTL-mouse function to drag the view around. The cursor does not change to the arrows when buttons are pressed, nothing moves. And when I turn on another layer, the OpenGL goes bonkers again.
  16. Mik

    OpenGL died

    Anyone seen OpenGL do something like this before? (Should be seeing a finished house exterior with walls, windows, etc. all around.) My system specs: NVIDIA® Quadro® P4000 (8 GB GDDR5, 4 x Displayport 1.4) Intel® Xeon® W-2133 Processor (3.6 GHz, up to 3.9 GHz w/Turbo Boost, 8.25 MB cache, 6 core) 32 GB (2x16 GB) DDR4-2666 ECC Memory Windows 10 - current VW2019 SP 5.3 I've already reboot, reloaded, etc. Rotating the thing sometimes leaves the viewing field completely blank depending on where you stop. Front & left views are blank. Back & right views are like the above. Top & bottom look correct. Wireframe looks like everything is in place. This model has slowed down quite a bit as I have been adding detailing. But this is only about a 5000sf house. Is my hardware adequate? (Spec'd to VW website "high-end" recommendations.) Anyone else seen symptoms like this?
  17. Well this is alarming, confounding, and angering all at once! The hardware recommendations on VW site say a lot about needing a powerful graphics card - load up on VRAM: https://www.vectorworks.net/sysreq And their tested hardware page has a long list of NVIDIA QUADRO cards: https://www.vectorworks.net/support/quality-tested-hardware This is precisely why I purchased an expensive workstation last year with: NVIDIA® Quadro® P4000 (8 GB GDDR5, 4 x Displayport 1.4) Intel® Xeon® W-2133 Processor (3.6 GHz, up to 3.9 GHz w/Turbo Boost, 8.25 MB cache, 6 core) 32 GB (2x16 GB) DDR4-2666 ECC Memory In JimW's post, not only does he say NVIDIA QUADROS tend to have problems with Vectorworks but he also says, "(As a general rule and as of the writing of this article, you should not nomrally need to spend more than $150 on a video card to use with Vectorworks.)" What?! Can you find a video card for $150 that has Vectorworks' recommended minimum VRAM and OpenGL2.1 compatibility? His post was edited January 2017. If it is/was valid information, I wish I would have seen it before I purchased my system last year. I think JimW has a long history with Vectorworks so I don't think his post can be dismissed as uninformed. I hope he is listening/watching this. It is an old thread but I do not understand the conflict between his post and Vectorworks' information on their website. I happen to be having a SLOW problem right now myself. I think I will start a new thread for it.
  18. Nikolay, Sending separately, thanks. Sheet numbering appears in the format x of y sheets. Makes sense. In the TBM you can set the total number of sheets manually. But what sheet number any particular sheet is must be set in the sheet itself - I have been doing it from the Organization window since I read the post about checking the "Automatic Drawing Coordination" in Document Preferences. (Although I am not sure what all that setting is actually doing.) Actually, automatic drawing coordination sounds like what would be helpful but either I am not using it properly or rather I see that phrase to mean something like I recommend as follows. If this manual process of applying sheet numbers is the only way we can number the sheets in a set, it seems rather clumsy to me. During the course of a project development, any number of sheets may be created and added to the project. And where they go in sequence may change. Wouldn't it be easier if there was a toggle on each sheet for "Include" or not in an output set? Then VW can automatically arrange them numbered in sequence from the stacking order in the Organization window. And this leads to the cover sheet index list. I have started to try to set that up with the little spreadsheet so that the index reflects the actual sheets in use after reading through its documentation. I am not finished with that but it looks like it is limited as well. Again, if we could just "toggle" in a sheet for an output list, VW could not only number them from the stacking order but list them in an index. Why not make things more direct and easy to understand like that? (And please forgive me if you can actually somehow do this and I am completely ignorant of it!) Okay. The terminology makes sense to me now. And the reason it was doing this was because every time I load VW, it opens a blank "Untitled" file. I have been just ignoring that and now understand it is triggering this window about multiple files. Can we set VW to stop opening up blank files? Understood. Okay now I think this is a good example of where sophistication is becoming complication. Having multiple title blocks for the same sheet may be something that is routine for some but I am guessing most of us use only one title block on a sheet. I never imagined having many for one sheet. Thank you Nikolay for your effective answers. I learned from this already.
  19. I skipped from VW2015 to 2019 so maybe others have already become accustomed to the new title block system but honestly: This is the most confusingly organized thing I have ever seen. What happened to the old concept of WYSIWYG? It would be really useful if VW gave us a simple WYSIWYG option to use when all this complicated stuff becomes impossible. I would like my bloody business address to show up in the Design Firm cell and if you open the Title Block Manager it is indeed showing up in fields multiple times but only the name on the sheet. Getting my address to show up isn't the only problem I have had with this thing. I found someone talking about problems with the sheet number (I had too) and a response suggested some steps in places I would have never imagined to check. I got it to change but it is not really what I want and I still don't understand it. The below window pops up all the time and I can understand the idea of either changing all Title Blocks in a file to be consistent or just the one on that sheet. I think that is what this window may be referring to but maybe not. I mean, what is it referring to when it says, "... load the opened files now"? If the files are opened, why would they need loading? What files are they anyway? And if I need to select sheets for edit, that sounds like I am working on the sheets in the file I already have loaded, right? What is the difference between a "currently opened file" and an "active file"? The way this window is worded, I don't really understand what it is saying and trying it different ways does not seem to produce an understandable result. Sorry VW, I don't enjoy reading rants and hate to be the ranting party even more, but it just seems that the software team needs to step back and give more common sense, consistent language, plain English, logical menus, and a rigid limit on how many steps it takes to do what seems like ought to be the mundane. If you must have the super-sophisticated features for your sophisticated large-firm clients, okay. But you are leaving the smaller of us in the dust. Keep a simple option in addition to the sophisticated ones so the rest of us can keep working. Hmph! Okay, stepping down from the soap box ... (And if anyone still has the patience to offer a pointer or two on the Title Block, grace be to you.)
  20. When I click "More info" on the VW update window, my PC asks if I want to allow it to make changes to my computer (yes) and then I get the following window: I click update, it counts to 100%, then asks if I want to allow it to make changes to my computer again, I click yes and the "updater needs to be refreshed" window again. Anyone else seeing this?
  21. I recently upgraded my PC (details at end) and have seen no noticeable improvement in VW2019 speed over VW2015. (I am on the subscription, tried VW2017 and had so much trouble I stayed on VW2015 as it was at least stable. But alas, Windows 7 & VW2015 are no longer supported.) A file created in VW2015 with a fair amount of single-family home detail (corbels, curves, etc.) was miserably slow for any of the "fleshed out" renderings. With VW2019 upgrading the file to 2019, not much difference. BUT - I notice when in Hidden Line mode, grabbing the model and spinning it shows the hidden line view move around as fast as you can move it but when you let go of the mouse, it asks if you want it to be rendered and then have to wait the usual delay for hidden line rendering. If the reason for this extra delay is the final hidden line rendering quality is better than the real-time spinning it around, okay but I'll take the "quickie" version of hidden line any day! That would save a huge amount of time and it appears the program already has that ability. Why won't VW let us opt for that use of hidden line? Anyway, after thousands of dollars in upgrading I feel like I just wasted a bunch of money "to get current." OLD: VW2015 SP5 Build 290108 Windows 7 Pro SP1 HP Z1 Intel Xeon E3-1245 V2 @ 3.40ghz 8mb cache 4-core RAM: 16gb NVIDIA Quadro K3000M 2gb GFX NEW: Fresh install of VW2019 SP2 Build 463397. Windows 10 Pro for WS v1809, Build 17763.195 HP Z4 G4 Intel Xeon W-2133 CPU @ 3.60GHz 8.25mb cache 6-core RAM: 32gb NVIDIA Quadro P4000 8GB GDDR5 HPZ38c display
  22. Thanks Matt. Will pass along if I see anything else. Regards
  23. Switching back and forth from OpenGL to hidden line works until I include the roof. When switching from OpenGL to hidden line, the whole app will often just disappear. Have tried numerous views, roofing materials and the crashes are not consistent. Exclude the roof and things appear to be working. But with the roof, it crashes just about every time. Did this with a fresh file: 4 walls and a hipped roof without any other details and crashed immediately in top view after switching from OpenGL to hidden line. I have seen some complaints about hidden line crashes here but could not find a direct correlation or something from VW acknowledging or doing anything about it. Maybe my searching skills have been subpar but a google search yields much more salient results than the search bar in forum.vectorworks.net. In either case could not find resolution. Anyone else seeing this? And all after getting everything in my setup all current! - Mik Fresh install of VW2019 SP2 Build 463397. Windows 10 Pro for WS v1809, Build 17763.195 New PC: HP Z4 G4 Intel Xeon W-2133 CPU @ 3.60GHz 8.25mb cache 6-core RAM: 32gb NVIDIA Quadro P4000 8GB GDDR5 HPZ38c display
×
×
  • Create New...