Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by markdd

  1. You can add a glow texture to the lens part of the lighting device using a combination of Spotlight preferences (modify lighting device colour) and Data visualisation. The key to this is to get data vis to put an object attribute colour glow texture into any object with the lens parts record field checked. Works a treat.
  2. The intention behind the two angles is so you can specify elongated lenticular beams like the ones you find in wide par lamps. Beam angles and Field angles are both part of the beam from a Spotlight. Typically (If my memory is correct) the field angle is the last 10% of the intensity of the centre of the whole projected beam of light. This is always the outside edge.
  3. A nice feature of the tool is actually in the Object Information Palette. Each overridden face will highlight when it is clicked on which I have found is incredibly useful.
  4. Once you have shift-clicked, the new tool would have already textured the faces because the cursor holds the texture. Don't you think your wish adds extra clicks? You can select multiple faces of an object from the Object Information Palette and that way you can swap out textures or do some of the rudimentary mapping that the Object Information Palette allows. I think the new Texture Tool is very intuitive and has been extremely well designed.
  5. I believe you need to have a Data Visualisation Active in the Sheet Layer Viewport and you also need to be in the Annotation section of the Viewport as well.
  6. My approach would be a little different and the Subdivision tool is perfect for this. Once you get the hang of the tool which is admittedly quite a learning curve, then the actual modelling of the shade is a synch. If you don't know the tool then this is a perfect project to learn with. There are several steps, but the first thing you need to do is create a SubD Object from a simple 6-sided Polygon which can be made using the Regular Polygon tool. Use the Convert to Subdivision command to do this. Thereafter you need to extrude the shape to the thickness you want and then use the scale mode to create the cone shape with the top vertices. When you have finished modelling and you are happy with the shape, then you are probably best copy the SubD object and convert it into a Generic Solid. Then apply a lattice texture. The SubD object is great for creating geometry like this but will only accept rudimentary texture mapping, so the conversion to the Generic Solid will probably be a necessary step. Here is the result.
  7. If you go the the quick preferences bar there is a button that will do just that.
  8. The number pad can be used inside the data bar by selecting the Data Bar and Edit Group options from the Quick preferences bar. There is an option to allow the Number Pad to activate the data bar and therefore work inside the data bar. The Number Pad will always prioritise the entry of Data when the cursor is inside a data field or in a text block. Otherwise, the number pad will only act as a quick way to activate the preset views which most users find incredibly useful. What the number pad will not do though is act as a way of using the numbered keyboard shortcuts. For those in a Mac and I believe a PC as well, you must use the main keyboard.
  9. You will need two text blocks. One without a record (Type of) and then the text block with the record.
  10. @Pat Stanford Can you use the Substring to strip all text from a field. Sometimes I have Watts wrongly abbreviated as a lower case W. It would be great to remove either 'W' or 'w" or 'kW" Thanks Mark
  11. Make a symbol you want to attach the data tag to with all the records attached as you require Attach the data tag to the symbol and make sure that it is reporting all the data as you want Select the Symbol and the data tag and convert that selection into a Blue Symbol (Create Symbol command and check the convert to group check box) When the symbol is placed, the symbol is added to the drawing area along with the Data tag. Both of these items will be inside a group. The Data tag will be reporting the data that is attached to the symbol. This way you should achieve the workflow you are looking for without the scaling issues that @Nikolay Zhelyazkov has pointed out.
  12. Did you specify the Cut Plane parameters in the dialog box? The command does not use a section line in the same way as the Create Section Viewport command.
  13. Make sure you have Colors enabled in your Renderworks Style
  14. For the most part, the Spotlight Numbering tool will do most of what you need. However, you will need to set up Label Legends for Lighting Devices first. Any data generated by the numbering tool will be displayed using these.
  15. Turn off the Snap to Tangent button in the snaps palette.
  16. As far as I can remember the snap to grid settings are a document preference. So if you are opening from a Template you will need to change that setting to whatever you need and resave the template.
  17. You need to explore the Create Report command. If you Right-click on the Row header named 2 and select edit report you will open the Edit report dialog. This will give you the criteria and parameters currently active in the worksheet. To make a fresh worksheet, use the Create Report Command. It's like an old fashioned Microsoft "wizard" tool and it will make the worksheet for you based on the criteria and parameters you set. Hope that gets you started.
  18. Total Pipe length is the parameter you need. Take a look at the sample file. TOTAL PIPE LENGTH.vwx
  19. Trim height for lighting pipes is the Z field in the Object Information Palette
  20. Render buckets are the tiles that you see as each section of the view completes. And yes, I think that is the jargon. The layer dpi controls the dpi of rendered objects if you print from the design layer. I think it has a bearing on the pattern attribute as well but that is very much “legacy” these days. As not many folk print from design layers let alone render them and then print the render from the design layer, then this setting is mostly redundant. Here are two pdf images printed from the design layer. Design Layer 72 dpi.pdfDesig Layer 300 dpi.pdf
  21. Completely agree. If the render bitmap tool could be modernised so that it displayed the render buckets as they are created rather having to wait for the complete render, that would be a big step forward.
  22. This button will make the title block accessible from the Title Block manager. It will also add it to the count list so that it is part of the “Total number of sheets” criteria.
  23. End markers are page based. This means that they are always drawn at 1:1 scale. (These are defined in the Edit Marker dialog.) They do not automatically scale with other objects on the same layer. This is intentional. The reason for this is primarily to do with consistency and legibility. If your design layer scale is the same as the viewport scale then you you will see how they will look when they are shown in a Viewport of the same scale. If a viewport is a different scale from the design layers it contains then the end markers will look different. This should not be a problem and you can rescale the end markers from the Advanced Properties section which is found in the Object Information Palette of the individual viewport.
  24. Not with the built-in tools. However, there is a set of plug-ins that you can purchase for a few dollars. One of the commands will do exactly what you are looking for. There are also over a hundred other useful lighting related commands that I could not do without. http://www.autoplotvw.com Most folk swear by these. They have been developed over a number of years by @Sam Jones and are worth every penny.
  25. I suspected as much! I wonder if there is a way to push the depth value to an attached record using the Data Manager. I had a quick look but couldn't find the criteria. I am sure someone cleverer than me will know the solution with that. Once the data is in a record then all should be well with the data visualisation.
  • Create New...