If the end result is to be extruded solids then I would recommend the “As Region” option. Though, as I mentioned in the thread at theswamp.org, some fonts (only a few found so far) have geometry definitions incompatible with that option.
If that option does produce the correct geometry then it is just a matter of Command: _extrude to get 3D geometry.
If it did not produce anything then un-checking that option should return a block reference with all the constituent geometry. You may be able to explode that try to construct the Regions yourself. Conceivably, one or more of the letters will balk at the process. That is typically due to a self intersecting loop somewhere in the outline.
Dean, I looked at the Curvy-3d drawing . . . . how did that situation come about?
I used the netload. Found the accurate file, now with the .dll extention. And T2G. But, nothing happens.
The command T2G doesn't set off the programe TextToGeometry.dll. It only returns "Unknown..."
Does it matter where the file is located on the computer? I've put it in my "Express"-folder.
FYI- if you have an older version of cad, 2010 or older the txtexp command gives a much better and more usable result for extruding text to 3D. For some reason the issue resides with 2012.
There are a couple of different issues that may arise when
trying to NETLOAD a .dll direct; I’m not
exactly sure which issue is interfering with the install.
The utility is posted here, as well, and the install format
is more AutoCAD 2012 friendly. I believe
this is Autodesk’s the preferred install method.
The .zip file contains “TextToGeometry.bundle”, which can be
loaded via the instructions found here:
SEANT61 -- using that link for the Text- to Geometry simply takes me to the Exchange home page, It may be the company PC i'm on at the moment, or adesk. searching on plug-ins eventually lead me to the second link, but nowhere did I find the Text-Geometry package.... I did dl the version from the swamp, and give it kudos.
One beef though -- I would consider it a 'good practice' to use longer. more descriptive command names in your application, and let the user alias the command in their own PGP. Whiule offhand i can't think of anything else I would have aliased as T2G, I would rather have the capability of establishing my own shortcuts, rather than settling for what a developer chooses. As a practice, that will prevent (or at least reduce) the issues of commands and functions being changed unexpectedly.
I’m suddenly not able to access http://exchange.autodesk.com/autocad/enu/store
either, even though I now that particular link worked a day or two ago.
Using a longer command name makes sense. I left the name "t2g" partly because the icon
will look like this – if we can ever get to that link again. I will keep that in mind for any future