Jump to content
AutoDesSys Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by setz

  1. When the cursor is over the Objects Palette can the Key Sct for "Fit All" have a secondary function which would both expand the object's hierarchies and then highlight the selected objects? I don't remember if Cmd+F is the default Key Sct for "Fit All", but it is the one which I use, and it would also conveniently represent "Find" when used as described above.
  2. setz

    Creating faceted objects ?

    Currently, Sweeping is most functional when "As Positioned" is used. The interactive widget defaults to centroid which is not very useful most of the time. Is there a way to snap move it to a different position on the profile? I tried key modifiers to drag and reposition, which could work well for editing, but found nothing that would work. Adding a "flip vertical" and "flip horizontal" option would also be of great help. As Pipo states, reversing path sometimes works but not always. +1 for non parametric option for rounding @rod - Are you using the Polygon Mesh Tool for converting to facetted? There are a few ways of converting an object to facetted, but this tool is IMHO the most useful. See the settings below as to how they affect the top of an extruded cylinder. I did first convert from an Extruded Objet to a Plain Object although I don't know if that matters.
  3. setz

    Website update imperative

    Sorry for you Bart. These users love everything I do! apdeznep bpdeznep cpdeznep apdezneg gpdeznep kpdeznep ypdeznep zpdeznep....
  4. setz

    Creating faceted objects ?

    The work around is to use the Polygon Tool and set the number of sides you want there. It's really the same as a polygonal circle, but you wouldn't think so at first glance. Just Choose "By Number of Segments" and enter the resolution -number of sides- as you like.
  5. There is a work around in the meantime.
  6. setz

    Join Tool

  7. setz

    Attach object to plane or grid

    The 3 point align script would help this type of challenge. Please update it for use in FZ8.
  8. setz

    formZ 9

    Note that in the spirit and rhino UIs that the actual working space in your examples appears to be about 50% of screen area. My current working space in FZ is around 85%. Any modifications should focus on maximizing working area and include flexibility to minimize the interface.
  9. It's also good insurance to "Export Workspaces" from the workspace manager in case you need to reset to your custom setups. In the event something goes wrong, you can easily Import the clean versions back in. A real timesaver.
  10. setz

    formZ 9

    Math input +1
  11. setz

    Maximum Size of Underlay???

    I typically break down underlays down to 4096x4096. I believe FZ up-samples all images (underlays, textures, billboards) internally to base 2 increments: 512,1024,2048,4096,etc, so, getting close to but not over these numbers will increase speed. A 4096x4096 image will be significantly faster than a 4096x5000 image which will be seen internally as 8192x8192 - 4X larger. (Tech, correct me if I'm wrong about this.)
  12. This may (or may not) help, an old façade material from maxwell's mxm site: 100 Windows AGS Facade.zip
  13. setz

    View parameters consistency

    I think what has happened is this. The way zoom worked in V6 was different than the way it works in V8. In V6 If you save a view and then zoom in with the school wheel and then save that second zoomed in view, you will notice that the view parameters for the two views are the same even though the actual view is different. I'm guessing that the view which was saved way back in 2011 was zoomed in with the scroll wheel prior to saving. I have been trying a number of ways to recreate or convert a zoomed view in V6 to an identical non zoomed view without success. I suppose for now you may have to do your edits in V8 or V6 and then go back to V6 to re render with your original saved view. Pylon has a great knowledge of the inner workings of views and he may well be able to look at your original file and be able to decipher how to extrapolate the amount and center of the mouse zoom in comparison to the saved view parameters.
  14. setz

    View parameters consistency

    Very intriguing. Can you upload the original V6 file with the camera and some reduced basic geometry to test with?
  15. setz

    Rhino Import

    I get a lot of Rhino files that have objects with faces that have mixed normals. An object will have some faces pointing inwards and some facing outwards. Can the importer be modified to fix these objects or can the Object Doctor have an additional feature to repair these types of issues? Currently I am taking one object at a time, deriving all of its faces into separate objects and then restitching back together. In files with hundreds of objects this is very time consuming. On a side note, when I select many objects to do these restitching operations simultaneously I often get a "System was unable to complete the Boolean operation" msg. The same objects stitched separately boole fine. Perhaps the stitching algorithm could skip problem (coincident geometry etc) objects and continue stitching the valid faces. Bad faces could then be found and fixed manually more easily.
  16. setz

    Trim Tool

    The Trim Tool used to be able to close a single open line. Can this functionality be reinstated? The workarounds are very time consuming. It is notable that this used to be an option of the Close Line Tool; which did work, but was a less desirable option because it involved the extra steps of adjusting options within the tool.
  17. setz

    Trim Tool

    The first example shows the test example. The second example shows the desired results of using Trim Tool as it functioned in FZ V6. The third example uses the current Close Line Tool. I mentioned the "extra steps" because in V6 the Close Tool had three options; Trim, Join, Connect. In V8 the Close Line Tool performs only the Connect function. I would much rather have the Trim Tool be able to function as shown in the second example rather than have the Close Line Tool have the old V6 options added to it - I'm just second guessing how ADS may choose to resolve this, and I have a strong preference.
  18. setz

    Layout Bugs and Quirks

    Hoping the following will appear in the next update: In the Note, Text and Leader Tools the input interface doesn't seem to utilize conventional behavior regarding key input. Can they be modified to behave as follows: Escape key - cancels the dialog Return key - performs a carriage return Enter key - enters the input in the text field and closes the dialog
  19. setz

    In memory of Paul Helm

    Paul was always very helpful, thorough, considerate, professional and amusing as well. I am sad to hear of his passing. I will miss corresponding with him greatly.
  20. I want to write a quantize script for facetted objects. When group of objects is selected and the script is fired it will highlight points on the objects whose coordinates do not match an increment typed into an input field. There will be an option to then apply a given quantized amount to all those points. I will use it to help clean up imported garbage. I may even add live sliders for global or independent XYZ quantize values. What should I begin to learn, and can you recommend a good beginners resource? It's been awhile since I have done any programming; back in the days of fortran, pascal and basic... even a little punchcard experience, lol.
  21. Chris, that may be related to the issue of the Define Reference Plane Tool not functioning accurately while in Wireframe view mode.
  22. setz

    Material Name and Modelling Axis

    +1 showing the name. ADS responded positively to this when it was mentioned previously, maybe it will make it into the next WIP?
  23. setz

    What to learn?

    Thanks Chris! I still have your Attention Script in my folder hoping one day it will be reanimated. How is scripting actually done? Is it like creating a text file and then compiling it with the SDK or was the SDK an actual interface for writing, syntax checking and testing? Do you think there will be much overlap between the old SDK and a new Python based one? I don't really understand why some of the old scripts stopped working and wonder how much effort learning the previous system will help with the new. I am looking forward to seeing some examples to dissect.