Leaderboard

"What I’m saying is, the design is not the problem at all. That part is done. " You may be satisfied with the "design" but the CAD model is not sufficient for use with the rendering capabilities of any 3D CAD system. Rendering software assumes a 3D model that has surfaces. The surfaces do not have to define a solid object but they could be part of a solid model. Rendering software uses the surface normals to determine how to color a portion of the surface. A simple form of rendering computes the angle between the surface normals and the direction to the light source and uses the cosine of this angle to determine the intensity of the surface color at that point. In your 2D model all the surface normals are pointing in the same direction, perpendicular to the XY plane. In addition, the fronts of the letters that form the word "superman" do not include a surface. Your 2D model provides a pseudo form of transparency via hatching. A true 3D model is needed for transparency rendering. If you really want to be able to generate a CAD rendering of the geometry I suggest you do the following. Create a 3D model of "superman" by isolating the 2D geometry of the outline of the letters. Trace over each letter to make it composed of just lines, arcs, and splines. The profiles of the curved portions of the letters could be greatly improved through the use of splines yielding a model that looks as good, if not better, and would also be much more efficient for rendering. The current model is extremely bloated. Convert each letter to a region. This step is not necessary but doing it will help to ensure that you have closed shapes for each letter. Extrude the regions. Rotate the object or change your viewpoint to as required to get the image you seek. It looks like you you want an axonometric projection (not perspective) for the final render so do not use a camera or a perspective view for rendering. Assign a transparent material to the model. You will need to experiment with the material finish to get the results you want. It looks like you don't want shadows in your final render so turn those off. I think one or two light sources may be sufficient. Be careful of specular reflections. This is a function of the location of the light source and the surface normal. It can affect the appearance of surfaces as you look at the model from different angles. Good luck!

In a nutshell, annotative text gives you multiple copies of the same text item, each at a different scale. You can define the assortment of scales for each item. If the text in a viewport is annotative and doesn't match the viewport scale, it doesn't appear in that viewport. If the scales do match, you see the copy at the appropriate scale. To enable annotative text, you must toggle it for that text object. You automatically get the current scale, so pay attention to that. You can then add whichever scales you need. The mechanism depends on how you like to work. In the Properties window, for instance, the Annotative property and scale list are under Misc. If you have any questions, don't hesitate to ask. Annotation can be a confusing topic.

Which "scaling issues" are we talking about? If it's text, there's annotative text that adjusts to different sizes. If it's not text, model space objects should be the right size to begin with.

This works, thanks.

This works very simple.

My $0.05 I did look at road vertical curve it takes into account, start point and grade at that point ie tangential, end point again grade at that point, I have a paper copy of the formula looking for jpg for y=x something then can see if can replicate. But looking at shape maybe this, but note it has a R value which controls the 2 parabola curve answer. I think that is what has been used. http://onlinepubs.trb.org/Onlinepubs/trr/1994/1445/1445-010.pdf

It may have started life as 3 arcs then been splines in some way or as in road designs as suggested some form of parabolic spiral added between the 3 arcs. They are not giving the formula used to create. When construction started this was same problem how to build these concrete shells with changing radius.

Try this: (defun c:r2v (/ a b o s) ;; RJP » 2021-08-18 (cond ((setq s (ssget ":L")) (and (setq b (equal '(1. 0. 0.) (getvar 'ucsxdir))) (setvar 'cmdecho 0) (command "_.UCS" "_View") ) (setq a (angle (trans '(0. 0. 0.) 1 0) (trans '(1. 0. 0.) 1 0))) (foreach e (vl-remove-if 'listp (mapcar 'cadr (ssnamex s))) (cond ((wcmatch (vla-get-objectname (setq o (vlax-ename->vla-object e))) "AcDbMText") (vl-catch-all-apply 'vlax-put (list o 'rotation 0.)) ) ((vlax-property-available-p o 'textrotation) (vl-catch-all-apply 'vlax-put (list o 'textrotation 0.)) ) ((vlax-property-available-p o 'rotation) (vl-catch-all-apply 'vlax-put (list o 'rotation a)) ) ) ) (and b (command "_.UCS" "_World") (setvar 'cmdecho 1)) ) ) (princ) )

Is the geometry such a secret that they cannot just tell you?? Or is it a test for you and CADTutor?

Use this - AutoReplaceCAD You need to select the "Translation of texts" tab And start processing. You will receive an export, and then after the changes you can make an import.

Keyword Specifications https://help.autodesk.com/view/ACD/2022/ENU/?guid=GUID-9ED8841B-5C1D-4B3F-9F3B-84A4408A6BBF The string argument is interpreted according to the following rules: Each keyword is separated from the following keyword by one or more spaces. For example, "Width Height Depth" defines three keywords. Each keyword can contain only letters, numbers, and hyphens (-). You're trying to use filenames with a period in them. Try using (initget "monday tuesday") (setq Request (getkword "Choose your pdf [monday/tuesday] ") Request (strcat Request ".pdf")