Jump to content

P Retondo

Member
  • Content Count

    1,704
  • Joined

  • Last visited

Posts posted by P Retondo


  1. PS: a tip - windows contain a single plane rendered as glazing, doors contain 2, leading to a noticeably different attenuation of light. If you render a glazed door as a panel, assign your glass texture to either exterior or interior panel, and a class that has no texture and zero line weight to the other panel, you can spoof the door object to transmit light the same way a window does. This also leads to significantly improved rendering times. But :-( you can't fix your transom windows or sidelites.


  2. Does anyone have advice on how to handle textures from 2010 and earlier? We just did some testing and found that replacing a glazing texture converted from 2010 with a "native" 2012 glass texture cut our rendering time by about 60%. A reflective metal texture, same issue, especially if it was customized in any way.

    How can one easily tell if a texture is "native" to 2012? We have a lot of legacy symbols with 3d content, plus we'd like to be able to re-use objects from previous projects that we've invested time into. Is there any way to convert a pre-2012 texture to a similar current texture? Any thoughts about texture substitution a la the font substitution window that pops up when your file contains an absent font?


  3. Christiaan, I've listed this problem as a bug. One of the ideas for dealing with it is to have a preference in the DLVP info palette that allows "ordinary" class settings to override, and to have all layer links translated from earlier versions automatically check this override.

    Katie, the problem simply stated is that with class visibility controlled by DLVPs, we now have to look in multiple places to control how objects appear in a design layer. This adds one, or possibly numerous, extra steps, and is particularly difficult when a saved view from a version 11 or 12 file is converted to 2008. If that saved view shows a layer that contains layer links, and was dependent on class visibility settings, the visibility of objects in the 2008 version of the file can be very different from what was set up in the original.


  4. Interesting comments by all, especially the research from Dr. Mike M!

    From a software engineering point of view, there is a very interesting and pragmatic solution - terminology tables. All the key words in VW's user interface have a more correct term in the various markets. So the answer is to have all these key terms represented by variables in the code. This set of variables can be mapped to a series of regionally-based terminology tables, and displayed on screen to the user according to whatever regional preference is selected.


  5. In my experience VW's pdf export converter does not embed fonts. I use PDF995, available on the web, which has an option to embed fonts. I can work around this with my print services by sending them the fonts that I use, which makes it possible to use the VW converter. But I also find that VW pdfs are larger files, and won't reduce using Acrobat's Reduce File Size command. So with the VW conversion yesterday I had a 7.9 MB file from VW pdf that couldn't be reduced, and by contrast a 6.5 MB file from PDF995 that was ultimately reduced to 112 KB.


  6. kenzo, set your model layer z value to 56.2 m. Then you can work on it with a "datum" of zero relative to the layer, and stack layers and layer linking will show it at the absolute height you desire. It looks as though your model setup should have done that for you, but since the results don't look right, go into the layer and look at the layer z values to check.

    I do agree strongly with Petri's request for a better system of setting a datum. I've always thought Archicad had the better idea - you can toggle between viewing objects relative to a user-defined z value datum and absolute z value.

    Islandmon, by now you are probably shaking your head over the silly refusal of EU folks to use a proper decimal point! (Just a joke - wait! Ow! Ooof! Stop!)


  7. Christiaan, I have complained about the ability to set class overrides in DLVPs. This now makes it more complicated to use classes to sort the visibility of objects in design layers. As you point out, this is an inconsistency in light of the philosophy that design layers are for design, sheet layers are for output.

    I understand the occasional need to have text in a design layer to make notes, etc. But why does it need to be through the vehicle of annotations? You can put the notes right in the layer. The reason for annotation space in a regular Sheet Layer VP is so that you can have VP's with different scales on the sheet and easily control scaling issues by having things "belong" to each VP's annotation space.

    I would never use a DLVP to bring something into a design layer at a different scale, and I can't imagine the need to do such a thing. I think this is the reasoning behind not having a separate annotation space for the DLVP.

    I know you're thinking, "well, if it's a type of viewport, WHY NOT have annotations?" I think the answer there is that DLVPs might be based on different technology - my understanding is that they are an adaptation of layer links. Just a guess on my part, maybe Katie could confirm that.


  8. Hi Katie, looks like we have 2 screen flicker threads now!

    As reported in the other thread, I have two computers, one a laptop, and neither has the ipoint.exe process. Both have nearly identical flickering problems (blue bar at top of window flickers at ~4 cps, number of flickers varies from 0 - 30). One computer (Dell 690) has the NVIDIA Quadro 3450/4000 SDI video card with the driver supplied by Dell tech support (v 9.1.3.6) and a Dell optical mouse with MS driver 5.2.3790.1830. The other (HP ZD8000) has the ATI Mobility Radeon X600 video card with driver v 6.14.10.6483 and both Synaptics touchpad (driver 7.11.14.0) and MS Intellipoint bluetooth mouse with driver v 5.1.2600.0.

    HTH!


  9. I have flicker on two computers, one of which is a Dell and the other of which is an HP laptop. The latter has an MS Intellipoint bluetooth mouse, but neither shows ipoint.exe as a process.

    Steve, was your flicker the same as mine (i.e., a ~4 cps flicker of the blue band at the top of your application window)?


  10. James, change the fill attribute of your polyline to "none." Then decompose your polyline and it will become a series of lines and arcs, etc.

    The reason your fill is so wonky is probably because VW adds a connecting side when you have something like an "S" shaped polyline. That side connects the two ends, crosses over the shape, and causes the fill to be odd. If you decompose the two sides of your road, put lines at the ends to create a completely enclosed space, then select all the objects and compose them, you can then fill successfully.


  11. Hi Katie, that was a great piece of research, but unfortunately it doesn't apply to my situation. I have no ipoint.exe process.

    I also notice that during the flickering associated with selection of an object, the OIP does not register any object data until the flickering has ceased.

    The above applies to both v12.5.2 and v2008. The flickering is worse in 2008.

    Pete, thanks also for your input. I don't think I'll be cracking the case on my Dell 960 anytime soon, much less tinkering with the wires inside! But next time I'm there I'lll look around for that, and if I find something I'll call Dell tech support.


  12. I don't have an Intellipoint mouse or Intellipoint driver. I have a version of the screen flicker where just the top blue bar of my application window flickers at about 4 cps. This occurs on the final click of creating an object, or when I select an object. The duration of flickering seems to depend on whether the object or type of object has been recently created or selected. It can be as little as one blink (or none), or as many as 20 or 30 blinks.

    I'm curious - how would you describe the flicker you have been experiencing?


  13. I use Petri's method to remove voids in the poly, very efficient.

    I wouldn't care to have each modified 2d poly carry with it it's history of clipping, adding, etc. I think it would add too much overhead to the file size. Besides that, if you notice, 3d boolean objects are no longer extrudes, they are a different object type (a necessary complication, if you think about it). So if your idea were implemented, once you clipped a 2d poly it would then become a different object type and couldn't be clipped or otherwise modified with 2d reshape, etc.

    With Petri's method and with multiple-vertex reshaping, I think there are sufficient methods to deal with the issue. And a solid subtraction isn't a bad way to go, by the way. Just extrude all your holes or cutting shapes at once to make a single subtraction solid. Then you can add to, subtract from, or edit the set of 2d objects to make changes in your hole pattern. I do it all the time, and no complaints!


  14. Assign a class to the label in your window or door PIO dialog box (ID Class field). With Info Editor (an inexpesive 3rd party plugin) you can do this en masse in one operation. Make that class not visible where you want the display suppressed.


  15. Christiaan, thanks for that link. Though it addresses mainly Mac issues, by generalization the same applies to Windows. What comes through to me is the "clean break" notion. In rewriting programs to conform to 64 bit, all software will be able to part ways with a bunch of accumulated crud. It means some transition headaches, but we've been around long enough to know that we can deal with it. I don't think any of us would like to go back to the 16 bit days of MiniCAD.

    Also, it's good news for 64 bit advocates that new Macs by default will be on a 64-bit capable OS.

    Katie: I think it is true that 32 bit emulation on Windows x64 systems is slightly faster than execution on a 32 bit OS. The driver problem you talk about has been my most negative experience - plus, there is the problem in the case of older 32 bit software, that would otherwise be able to run on a 64 bit OS, if they have a 16 bit INSTALLER, they can't be installed.


  16. Mike, I agree. If we can just get the conversion from legacy files to work properly (i.e., multiple links can now be consolidated into one VP with multiple-layer visibility, but the converter won't do that).

    We asked for better management tools for layer links some while back, and though the 2008 literature doesn't seem to trumpet it, this is just what we got with Design Layer Viewports.

    I'll be really interested to see how Stack Layer Views stacks up against Design Layer VP's as a way to explore and work with a 3d model.


  17. Christiaan, if you batch convert, I'd recommend not converting layer links to Design Layer Viewports. I've discovered what I think is a bug in the saved-view treatment of class visibilities when that option is selected.

    I'm sure you're going to test this on a couple of projects first, no?

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×