Jump to content
AutoDesSys Forums

setz

Members
  • Content count

    496
  • Joined

  • Last visited

  • Days Won

    75

Posts posted by setz


  1. 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.


  2. 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.)


  3. 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.


  4. 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.  :)

    post-176-0-20434300-1494033297_thumb.png


  5. 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


  6. 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.

    post-176-0-85465600-1493655314_thumb.png

    post-176-0-20601300-1493655319_thumb.png


  7. 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.

     

     


  8. 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.


  9. Set Interval used to be very important!  It was my go-to option when making terrain when using V6 - with joined open and closed lines.  You're right though, without being able to join all types of contour lines now, more complicated terrains from contours at the same elevation are no longer practical using Set Interval.   (I haven't been required to make terrain since I switched to V8 full time about 6 months ago).


  10. Oops,  My bad.  This technique works well in V6.

     

    The new Join Tool in V8 is very limited in what it can do.  No more joining of open lines, no more joining of solids and surfaces.  It would be VERY helpful to have full functionality returned to this tool.  I understand the reasoning for which ADS did this, Joined objects of different types behave badly in some situations but the functionality FAR outweighed the issues that could occur.

     

    Make Reference is not a very good substitute option because it limits full functionality that Join used to allow.

     

    Another related bummer is the lack of "Status of Objects - Single Volume" option.  Kills me every time I join a lot of similar objects together only to have a boolean tool blow them all apart each time it's fired - it's like herding cats all day long.


  11. I had a presentation this morning during which I had to make live edits in front of a group of people.  Everything went very smoothly.

     

    I work with others who primarily use Rhino, and once again I heard "You can do that with Form Z?"  There was clearly admiration for the efficiency, speed and flexibility of Form Z in a pressure situation.

     

    Thank you to all of you there at ADS for making it easy to impress.


  12. In Object Attributes, when "Override Edge Display - Always Off" Is selected, the Cross Section lines and hatching are not shown, as would be expected.

     

    In the project I am working on, I have a very high poly objects for which I do not want to see all the surface facet outlines but do want to see the cross section lines when a clipping plane is active.  Can a feature be added to accommodate this type of situation?

×