Jump to content
AutoDesSys Forums


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by setz

  1. Select the object or objects you would like to have hatches show in the clipping plane.  In Tool Options Palette choose the Cross Section Tab.  Open the Hatch Palette and drag the desired Hatch from it into the Selected Hatch Option box.  It should show a plus-sign cursor and assign that hatch.  Note in the attached images that while an object is selected, the hatch in the cross section does not show up. 

    Hope this is what you were describing and that this helps.



    Oh, and be sure that Show Hatches is checked in the Display Options for each of the display modes you want it to show with; Wireframe, Shaded Work, Shaded Full, and Hidden Line.


  2. I use this often, and I usually create a "Master layer" which has all the other layers contained within so that all the layers in the project get the override with only one box to click.

     A key sct for that would be useful, but tricky to implement due to multiple layers.  Perhaps a key sct would trigger all layers' Material Overrides at the same time?

    An alternative solution would be to have Material Override Attribute show up in the Contextual menu when you right click on a specific layer the way that Select All Objects On Layer is specific to the layer clicked on.

  3. I ran "python ––version" in Terminal and it returned this:


    and then I downloaded Python 2.7.18, ran the installer. It created a Python folder with this in my Applications folder:


    So it looks like I have 2.7 in /Library/Frameworks but the No module named cube2 is still displayed when I run the cube2py script.

    Is the 2.7 enough 2.7.? or do I need to get the 2.7.18 installed and how?

  4. Just starting.  I don't know what I'm doing at all.  Using a Mac 10.11.6 so Python should be installed right? (how can I find out which version of Python is installed?)  I ran "cube.py" utility from the Extensions menu and I got this error msg:


    I thought there may be a permissions error so I moved the script to the desktop and got the same error message implying that it was trying to open the same file, not the one on the desktop so I renamed the one on the desktop to cube2.py retried and then got this msg:


    ...and no .pyc file was created.  What is going wrong here?



  5. 28 minutes ago, Jaakko said:

    Yes. It is handy when you need to render certain size pictures today and tomorrow.

    I use scenes for this.  And I have those scenes saved in my template file so they are available in every project I work on. Typically: Full Screen, 2K x 4K, 4K x 8K, 4Ksq, 8Ksq and 2:2.35 feature film format as well.  If you create a new window and then click on one of these, your window will be good to go.


  6. It's going to take some getting used to the Tool options palette shifting all the other palettes up and down as it expands and contracts to fit the options of the chosen tool, but with my growing collection of dinosaur-unreliable-mini-failing-trackball apple mice, scrolling works lovely as long as I haven't stacked too many pallets on the side dock.



  7. This card allows me to "Export Images" using Shaded Full Display in sizes greater than 8192x8192.  Probably 95% of my work is presented using Shaded Full Display currently. Sample attached but jpeg quality is reduced because of file upload size maximums in posting to forum.

    Victorian House.jpg


    Hey!  I Posted an 8K image but it saves as tiny!  Here is the full image:

    Victorian House.jpg.zip

  8. Nvidia GTX 980TI 6GB.  Should be fast enough.  Mine is not bumpy like ariel's but there is a few millisecond delay at the beginning of the rotation.  It's barely noticeable but it does delay.  The identical file opened in 8.6 has zero noticeable delay on my machine.  I think it may be a delay on the FZ side of things sending info to the card.  ...and yes my much loved machine is a dinosaur.


  9. Could also be related to your snaps, many are selected in the video, but cut off and I can't tell which ones are on.  As Chris says, high poly items like the terrain may be causing the issue.  When an object is selected, FZ seems to become more aware of snapping opportunities and when there are high poly objects available to be snapped to, FZ has to do a lot of calculations, especially with Intersection Snaps.  You can try reducing the selected snaps to only the one you need at the moment or turn them all off momentarily.  You can also try turning off snapping in the object attributes for just the high poly terrain objects (except for the times you actually need to snap to them).