Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Looking For Help? / Re: Solid Subtract failure DesignCAD 3D MAX 2018
« Last post by adriank on August 30, 2018, 06:07:21 PM »
OK, I get the same result.
First I tried 'reverse the order of the points' on the subtracting solid then the subtraction worked fine.

After digging a little deeper, the problem seems to be an extra point in the profile you used to extrude the subtracting solid. (see the attached) When I explode the solid and select the end profile in point-select mode there is an extra point on the top face which is a loose end-point - if I delete that point and re-extrude the solid it also works fine.

I suspect the reason the 'reverse order of points' trick worked is because if the loose point is the last one it gets ignored but if it's the first one it creates an improper solid.

Adrian
22
Looking For Help? / Solid Subtract failure DesignCAD 3D MAX 2018
« Last post by BlankMan on August 30, 2018, 05:16:53 PM »
Got a solid subtract failure. Linked YouTube video below explains it. Drawing is attached if anyone wants to try it, I'd be very appreciative if someone can determine what the problem is.

Solid Subtract fail video
23
SDK Feature Requests / Re: Sys() function for Zoom factor?
« Last post by Lar on August 30, 2018, 08:02:23 AM »

You got it, BD, except that I'll have to take back what I said about not needing an external file because the layers are read from an external file. Also, I load the images in  separate 2D file because there are lots of them and they along with the 3D model tend to slow dcad down. Everything can be kept in the same folder though.


If dcad's paper space had the viewing flexibility of model space I would fight through it, but paper space's 3D view frames have a set focal point so I had to come up with my own paper space... actually I take that back, hidden and shaded views in p-space take forever to print.


For sheets that are 100% 2D I use the regular p-space. If one or two 3D views are needed on a 2D sheet I can still load the images on that sheet in p-space. Another reason I prefer model space is I can spread all the sheets that take the same notes out and when placing notes I can duplicate the same one where ever it's needed among those sheets, then move on to the next note. This way it feels like I'm working on 1 sheet. In p-space you can only see one sheet at a time so if I have 3 similar sheets I have to note them one at a time. After finishing the first sheet I'm dreading the fact that I have 2 more to go.


Lar











24
SDK Feature Requests / Re: Sys() function for Zoom factor?
« Last post by bdeck on August 30, 2018, 04:43:21 AM »
Even without the macro I can use Dcad's built-in commands to recapture a cam's view or image, by snapping at the relevant points on the cam. The purpose of the LarCams is to stay in position so I can recapture the exact same view if the model is revised.

Aha... I think I see now.

From what can be seen in your example, and considering that you seem to have been doing this since before DC v26, a LarCam appears to comprise a group containing multiple entities.

But in its essence, a camera object could consist of just a single multi-point line, where the line's points represent at least the focus and viewer locations plus 2 opposite zoomwindow corners, and where visible layers, etc, are included as fields in the "custom properties" of the line, and where all such camera objects are on a dedicated layer.

In order to display multiple views simultaneously, with each view exposing a different set of layers, you save or copy an image of each view for later compilation.

If those images are all loaded or pasted to a dedicated 2D layer in DC, then you might be able to keep all your drawings, cameras, images, and image montages (Lar's paper views) in a single dcd file.  Paper space without the aggravation.

Very Cool.

I can place the cursor in the viewing window and drag the mouse to zoom, move or pan the view. When doing this I will see the camera object, in the other windows, adjust itself accordingly. Alternatively, from one of the other windows I can click on the camera object to select it then move or rotate it. When doing this I will see the view in the camera's window adjust accordingly.

Very Cooler.

bd
 
25
SDK Feature Requests / Re: Sys() function for Zoom factor?
« Last post by Lar on August 28, 2018, 09:48:49 PM »

The LarCam is like a real world still camera on a tripod, so it only captures one view. Any number of them can be in a single file. Each one can recapture its view without the need for an external file and display it in any window I choose, unless you consider the macro an external file. Still, it's only one macro and not a mess of external view files saved God know where on the hard drive. Even without the macro I can use dcad's built-in commands to recapture a cam's view or image, by snapping at the relevant points on the cam. The purpose of the LarCams is to stay in position so I can recapture the exact same view if the model is revised.

Just about all 3D apps have camera objects. In Cinema 4D I can place camera objects throughout the 3D model. I can activate a window then choose which camera I want to view through. In that window I will see the view but in the other windows I can see the camera object. I can place the cursor in the viewing window and drag the mouse to zoom, move or pan the view. When doing this I will see the camera object, in the other windows, adjust itself accordingly. Alternatively, from one of the other windows I can click on the camera object to select it then move or rotate it. When doing this I will see the view in the camera's window adjust accordingly.

Dcad lacks these camera objects. To return to a saved view you have to load an external file. So, to fill the gap I created my own camera object that not only can return to a view but can return the layer setup for that view and save an image to the same name and size.

Lar
26
SDK Feature Requests / Re: Sys() function for Zoom factor?
« Last post by bdeck on August 28, 2018, 08:50:51 PM »
This can all be done manually but it would be quite a task.

This might have been a simple task for DC's ViewRead command, with one exception. ViewRead restores all view windows to their previous settings, not just the one having the current focus. A perfect solution if you keep only one window open.

But if you have more than one 3D rendering window open and want to restore only one of them, a multi step ViewRead would be required, and you would still have to roll your own zoom factor. 

Hence the 12-year old OP request for a sys() variable to read/write the zoom factor for the current view.

While we're at it, how about a simple flag parameter to limit the effects of the ViewRead command to the current view window?

What I've been doing, for many years now, is using my own camera object, dubbed the LarCam.

If I understand your description, my modified vdd macro simply creates what you might call a "LarCam", allowing the viewer  to be moved orbitally or radially relative to either the nominal focus or the "virtual focus". (Please excuse the deliberate misnomer. The "virtual focus" is the actual focus, and is the location of the "LarCam lens". )  A simple concept, but it has to deal with a mess of DC "stuff" to make it suitable for general use.  Adding linear motion to the camera will not be much of a chore, but my plate is full for now.

Oh how much easier things might be if "zoom" were a simple inclusion angle, and not some arbitrary secret view window frame.

Best Regards,
bd
27
SDK Feature Requests / Re: Sys() function for Zoom factor?
« Last post by Bob P on August 27, 2018, 10:28:25 AM »
It would really be nice if the regular manual contained all the command-line and within-macro names.
28
SDK Feature Requests / Re: Sys() function for Zoom factor?
« Last post by Lar on August 27, 2018, 10:01:54 AM »

I can't find the "View Read" command.  >>>I know about the File menu> Screen Config> Load... and Save... <<<
ViewSave and ViewRead are in macros17.hlp,
Ok, I see now from Macros17.hlp that ViewSave andViewRead are the same as the File menu> Screen Config> Save... and Load... commands.

To be more explicit on my methodology, my goal is replace dcad's built-in Paper Space, which I find to be a hassle to work in (no custom shortcut keys, screen always wants to regenerate, can't use layer macros, etc). Most of paper space's shortcomings I have a workaround for but what I can't do anything about is getting the same 3D view settings that I can get in model space, mostly because I have no control of the viewer focus. To emulate paper space view windows I use saved images taken from the model. These images are loaded in a file separate from the model file, where I organize them in sheets with borders, title blocks, dimensions, notes, etc. The trick is: after saving lots of images and placing them in my 'paper-space-file', with notes that point to specific things in each image, how do I recapture those images when changes are made to the model. Recapturing these images require recreating the same view settings, having the correct layers on, setting the same 2 points for the image-save, saving each with the exact same name (the images are referenced) and rendering at the same mode (wireframe, hide or shaded). This can all be done manually but it would be quite a task.

All 3D apps, except dcad, have camera objects that you can place in the drawing. When viewing through a camera object any rotations, zooms, pans, etc., that you do to the view is reflected in the location and orientation of the camera object, so whenever you come back to a particular camera the view is the same as when you last left it.

What I've been doing, for many years now, is using my own camera object, dubbed the LarCam. But since in dcad manipulating a view does not automatically affect the LarCam what I do is, after being satisfied with a view, run a macro that loads a LarCam in the drawing (on one of a set of dedicated layers) at the viewer location, then rotates the cam so it points at the viewer focus. I then have to manually adjust the corners of the face of the LarCam to frame the area I want captured in the image. I do this manually because the framing of an image has to be artistically done. The final image can be outside of the viewer focus and isn't limited by the shape of the drawing window. It is also important that the four corners of the face of the LarCam remain in the same plane. <<see the images at Reply 55 at http://forum.designcadcommunity.com/index.php?topic=5522.45 for an example of a LarCam. In the colored image the pink box with the cross is the LarCam seen along it projection (ie, why it looks like a box). The black and white image below is the saved image from that cam>>

Each cam contains information on the view settings, the layers that need to be visible, the points for the image-save, the shading mode and the name of the saved image.

As I work I place the cams about the 3D model. At anytime I can select any number of LarCams and run another macro to capture the images of the selected cams. During the running of the macro no user input is required, except if I choose to run the macro in "no-save" mode where, instead of saving each image, the macro pauses for me to view the screen. When done viewing I can either abort the macro or let it continue on to the next image. As I said above the images are referenced so when I make changes to the model I can resave images and just opening the sheet file updates the images there. When the project is totally finished I can then use dcad's Insert Manager to embed the images so then they are then no longer referenced and saved within the file.

LarCams have lots of other benefits, eg: I can use one to just turn on all the layers associated with it. I can also add things like dashed lines or other stuff not in the model but needed for the final sheet detail. In the images in the post referenced above I placed parts of a SaveAs2D, taken from the view of the LarCam, to fill in detail dcad omitted due to its rear-camera-clipping-plane (note that increasing the view distance would bring the omitted stuff into view but then I would also have to settle on a less dramatic view and not be able to view both sides of the porch ceiling moldings at the same time).

Lar
29
SDK Feature Requests / Re: Sys() function for Zoom factor?
« Last post by bdeck on August 27, 2018, 12:02:35 AM »
Hi Lar,

Your method got me thinking.

After a little testing, I was amazed to discover that the zoom level of an existing 3D view window can be restored
by inserting archived values of sys(600-603) into the zoomwindow command.

If all the other view parameters are restored first (as in the example below) it gives an exact or a nearly exact result.

Edit : After further testing, I cannot duplicate the accuracy of prior results. Zoom factor is generally ok, but pan and scroll seem to be a bit off..


Regards,
bd


Code: [Select]
ArchiveView:
      projmd0=sys(9)
      ax0=sys(205)      'x angle
      ay0=sys(206)
      az0=sys(207)
      xc0=sys(214)     'x view center
      yc0=sys(215)
      zc0=sys(216)
      rd0=sys(208) 'view distance
     xmin0=sys(600)
      xmax0=sys(601)
     ymin0=sys(602)
     ymax0=sys(603)
return

Code: [Select]
RestoreView:
    sys(36)=2              'silent mode on
    sys(9)=projmd0
    sys(205)=ax0    'x angle
    sys(206)=ay0
     sys(207)=az0
     sys(208)=rad0 'view radius
      >SetViewerPoints
     {
        <pointxyz [xc0,yc0,zc0]    ' view center
     }           
    sys(36)=0 'silent mode off
    >zoomwindow
    {
    <pointxyz  [Xmin0],[Ymin0],0
    <pointxyz  [Xmax0],Ymax0],0
    }
return
30
SDK Feature Requests / Re: Sys() function for Zoom factor?
« Last post by bdeck on August 25, 2018, 03:53:53 PM »
What I do is record the viewer focus, the viewer distance, the projection type and the 2 zoom window points.

Hi Lar,

That's a great idea that has many applications. In this instance, where the macro might have made multiple view changes, I'm not sure that it fits the role of an "undo" method, as it requires the user to set the initial framing points manually at the start of the macro.

If, while in 3D mode, DC had sys() variables for the x,y, and z coordinates of two corners of a view, those coordinates could be used as parametes in a zoomwindow command. By comparison, the 2D xy points in sys(600-603) are relatively worthless.

I can't find the "View Read" command.

ViewSave and ViewRead are in macros17.hlp, and they may be run from the command line or from a macro. ViewRead rsstores not only the viewangles, viewcenter, and viewdistance, but also the zoom, pan, and scroll settings of the view. The result is similar to your method, except that no user input is required for viewsave. 

"Menu/View/SaveCurrentView" adds the view to the bottom of the view toolbar's drop down 'projection' list

Doh... I must be going blind. Saw the reference to the view toolbox in the user manual but could not find the list in the View Toolbox. As I keep the dropdown set to Perspective or Isometric, I had no idea, or more likely had forgotten, that user-defined views (or even default view windows)  were in the same dropdown. 

"Maybe for a macro you can figure out how to translate the info for a saved view in the ini file (DC_View.ini) to basiccad code. There's a 'ZoomBack' setting that may control the rear (back) cutting plane.

Not sure where you're seeing that info. My view.ini file appears to be a simpe 65 byte text file

bd


Pages: 1 2 [3] 4 5 ... 10