Jump to content


  • Posts

  • Joined

  • Last visited


479 Spectacular

Personal Information

  • Homepage
  • Location
    United States

Recent Profile Visitors

5,052 profile views
  1. This sounds to me as an issue with text and viewports rather than with the Instrument Summary per se. One way to test would be to make a copy of the file and converting the IS to a group. If you still have the PDF issue, it's a viewport bug. Similarly, if you insert a callout on the design layer with the exact same text settings, that would point to an issue with PIO's and text. I know a number of users who use the IS this way, so I suspect the issue specifically affects the font you are using. That said, FYI, you can place the Summary directly on the sheet layer, using the scale parameter to set the scale. If you want the summary synchronize across multiple sheets, make it a symbol, or add it yo your Title Block Border layout. I prefer avoiding placing any objects used purely for annotations or keys on design layers, as they are outside the "world" of the design.
  2. @SamIWasYour own object or any object?
  3. For me, pDrawProvider->DrawDefault2D(); will draw a line, and not the preview of the object. I need to call: VWToolDefaultPoint_EventSink::Draw( pDrawProvider ); This is also definitely a change for 2021. Prior, I would get the object preview even without calling the default Draw() method, and that seems to be the case for all my tools. I'm also returning the two point tool status. I seem to be stuck between having the extra locus point or not seeing the object preview during rotation, which is fairly important for the application.
  4. Looks like you have a multi-cell fixture selected. Spotlight will identify a multi-cell from a symbol containing only symbols and 3D loci. If this is not desired, inserting another object in the symbol definition, like a 2D locus, will prevent Spotlight from being a multi-cell.
  5. Sam, see this thread: Note, you need a hex editor to enable an event-based tool. The biggest feature of the event enabled tool is customizing the mode bar, as well as handling multiple clicks easier to work with. Many of the limitations are still there though, for example, the code still doesn't run until after the first click.
  6. ok, that's got me in the right direction. I'm overriding VWToolDefaultPoint_EventSink::PointAdded() If at the end of the block, I call VWToolDefaultPoint_EventSink::PointAdded(), I get the extra locus points. However, if I don't call it, after the first click, I'm not getting the preview of the object while it's rotating.
  7. No, it's an independent locus point. I'm manually selecting and deleting them after the tool completes.
  8. I have a particular custom object and insertion tool that is inserting a locus point at the first click point in addition to the object. I just searched the entire code, and I'm not actually creating this locus point, so it seems to happen either as part of some default action or because I'm not flagging something as handled. Anyone have any ideas where it might be coming from?
  9. Sounds to me like a font issue. Either try a new font or select the pdf option to rasterize text
  10. I haven't had a chance to publish any tutorials beyond the documentation. BeamViz does let you set an additional focus plane, so you can visualize the min and max throw. I haven't found any projector specifications that tell you the depth of focus for the lenses, though I imagine that narrower lenses are going to give you better focus tolerances, as will higher-quality lenses. Once you have your throw differential, I would recommend contacting the manufacturer. Some projectors bill themselves for being suitable for mapping onto 3D surfaces, but I don't know how that translates to usable specifications.
  11. @jameslye, if I understand your concern, it's that the models should show that the lens intersects with the geometry of the light if put at 180 tilt. The examples you have show the fixtures from the side. Take a look at the front view. I suspect you'll find that the lens intersects with the top part of the YOKE and not the base, so while you can't see the error from the side, you can see the implications of the tilt limit in other views.
  12. I think where's waldo is still the best method: locus(0,0); waldo:=LNewObj; objH:=PrevSObj(waldo); delObject(waldo);
  13. Either should work. I believe the ID for the /Data folder is 3.
  • Create New...