Autodesk Community, Autodesk Forums, Autodesk Forum
forums.autodesk.com.web.brid.gy
Autodesk Community, Autodesk Forums, Autodesk Forum
@forums.autodesk.com.web.brid.gy
Find answers, share expertise, and connect with your peers.

[bridged from https://forums.autodesk.com/ on the web: https://fed.brid.gy/web/forums.autodesk.com ]
lisp to calculated drafting
Hi need a help to make a lisp. 1. User will pick the big line first. 2. Then user will pick the small line. 3. User will enter a percentage value (%). 4. Program must find the endpoint of the small line that is closest to the big line edge. 5. From that endpoint, program should draw a perpendicular line to the big line (connect small line to big line). 6. Then program must divide this connection line using the entered percentage (measured from the big line toward the small line). 7. Find which part (big percentage or small percentage) is longer. 8. Use that longer value as offset distance and offset the big line in the direction away from the small line. 9. Where this offset line meets the connection line — trim the small line at that intersection. 10. Final result: small line is trimmed based on the percentage and the perpendicular offset from the big line. This is my idea, i m sure there would be different concept to reach the result better way 🙂 thank you (defun c:SmartTrim ( / bigEnt smallEnt pct ) (princ "\nStep 1: Pick the BIG line.") (setq bigEnt (car (entsel "\nSelect Big Line: "))) (princ "\nStep 2: Pick the SMALL line.") (setq smallEnt (car (entsel "\nSelect Small Line: "))) (setq pct (getreal "\nEnter Percentage (e.g. 25): ")) ; ; ; ; ; (princ "\nSmartTrim proceess Compleated sucessfully.") (princ) )
forums.autodesk.com
December 11, 2025 at 3:17 AM
How to get Automatic property objectID value
HI! I want to get the value of ObjectID which is assigned automatically to 3dsolid,but I can't... please help me private string GetAutoObjectId(DBObject dbobj, Transaction tr, ObjectId propSetDefId) { var psId = PropertyDataServices.GetPropertySet(dbobj, propSetDefId); var propSet = tr.GetObject(psId, OpenMode.ForRead) as PropertySet; if (propSet == null) return null; foreach (var name in new[] { "オブジェクトID", "ObjectID" }) { try { //int pid = propSet.PropertyNameToId(name); var value = propSet.GetAt(propSet.PropertyNameToId(name)); if (value != null) return value.ToString(); } catch (KeyNotFoundException) {} } return null; } Before this code,  I add propertyset to Entity. using (Transaction tr = db.TransactionManager.StartTransaction()) { var dictPropSetDefs = new DictionaryPropertySetDefinitions(db); if (!dictPropSetDefs.Has("ID", tr)) { MessageBox.Show("プロパティセット定義「ID」が見つかりません。"); return; } ObjectId psdDictId = dictPropSetDefs.GetAt("ID"); PropertySetDefinition propDef = tr.GetObject(psdDictId, OpenMode.ForWrite) as PropertySetDefinition; foreach (SelectedObject so in selectionResult.Value) { Entity ent = tr.GetObject(so.ObjectId, OpenMode.ForWrite) as Entity; if (ent == null) continue; if (!ent.ExtensionDictionary.IsValid) ent.CreateExtensionDictionary(); PropertyDataServices.AddPropertySet(ent, psdDictId); } tr.Commit(); }
forums.autodesk.com
December 11, 2025 at 3:17 AM
Random Response Anomalous results (stress and displacement)
I have recently performed a set of random response analyses in the X, Y and Z directions separately for a small assembly of two mated housings. In short, while I was receiving reasonable results in two of the three separate analyses, the remaining axis results (X in this case) were anomalous. Specifically, the maximum von mises stress from the RMS output was an order of magnitude lesser than observed in the other axes (0.1594 MPa in the X-direction as opposed to 5.783 MPa in the Y-direction). By itself, this result wouldn't necessarily be problematic or erroneous. However, for the displacement results, the displayed gradient shows mostly solid colour for the majority of the mesh, and with localized extremes in two locations. This is contrary to the expected displacement gradient as shown in the other axes. For comparison, the von mises stress and displacement results from the Y-direction Random response analysis can be seen in the next two screenshots. I should note that different PSD Accel vs. Frequency plots are used for each of the three axes. X-Direction Y-Direction Z-Direction (Note row values of 1.1 g^2/Hz vs. 1480Hz, and 0.1 g^2/Hz vs. 2000Hz are cut off) **I do not have an intuitive feel for how a particular set of how these profiles should affect the stress and displacement results, and so I do not know if these can explain away the seemingly anomalous results I am seeing in the X-direction Random Response.** **I appreciate any guidance or feedback on how the X-direction Random response results could be so different from the other axes, especially if it is not related to the dynamics setup profile values.** _**Further context on the analysis setup:**_ A view of the model's full setup and UCS used for each of the Random Response analyses can be seen below. Bolted connectors between the front and rear housings, using bearing surfaces (split feature) on the front housing: Two separate concentrated masses are connected to the front housing using rigid connectors: The (4x) mounting interface holes on the bottom of the rear housing are connected using interpolated rigid connectors on each hole (with bearing surfaces on both upper and lower faces of the flange), and rigid body rigid connectors to the main constraint and load point. A surface contact is added between the front and Rear Housings: Mesh Controls had also been added to the bearing surfaces and internal diameters of the bolted connection, and mounting interface holes: The Damping and Modal Setup is as follows: The Load and Constraints have been setup as follows: Finally, the Dynamics setup was as follows:
forums.autodesk.com
December 11, 2025 at 1:17 AM
"DerivedAssemblyComponents.Add" Fails to Function Reliably
Hello, As part of my custom add-in, I need to derive an assembly file to the new or existing part. Below is a code I am using simplified to the basics, it appears to work for a lot of people, but in my case it only works with periodic success, meaning that while it sometimes works, it can also result in "Error 0x80004005", or just outright crash Inventor completely. So far the only consistent logic I was able to observe is that "Error 0x80004005" is being thrown every time I try to use the command in Sheet Metal Parts, but only if at least one Sheet Metal Command (Face, Flange, etc.) has been used, if the document is completely empty, the command appears to be working normally, albeit with the risk of Inventor crashing. Public Sub DeriveAssy() Dim oPartDoc As PartDocument Set oPartDoc = ThisApplication.ActiveDocument Dim oDerAsDef As DerivedAssemblyDefinition Set oDerAsDef = oPartDoc.ComponentDefinition.ReferenceComponents.DerivedAssemblyComponents.CreateDefinition("<< Insert Assembly Full Path Here>>") Dim oPartDef As PartComponentDefinition Set oPartDef = oPartDoc.ComponentDefinition Dim oDerivedAssembly As DerivedAssemblyComponent Set oDerivedAssembly = oPartDef.ReferenceComponents.DerivedAssemblyComponents.Add(oDerAsDef) End Sub I have tried running it on multiple computers, with different files, as well as in multiple versions of Inventor, and the issue is present in every case I tried, which is strange seeing that there is a number of mentions for this command everywhere, even in one of the samples that Autodesk provides, but not a single mention of any issues that I could find. Right now I am mostly curious to see if anyone else ran into any issues trying to derive an assembly to the part with a VBA code, or if anyone else could try and replicate the issues described. Any information would be helpful!
forums.autodesk.com
December 10, 2025 at 11:20 PM
Inventor Nastran 2026.2 list of changes
Inventor Nastran 2026.2 has been released. This is my list of changes that I believe are important to users, taken from various sources. To install the update, go to manage.autodesk.com and click “All Product and Services” (on the left or across the top), or use the Autodesk Access app installed on your computer. (Autodesk Access is used to update any installed product.) **Item** | **Change in version 2026.2** ---|--- 1 | Report generation added for Linear Buckling analysis. 2 | Results become outdated when loads or constraints are edited. 3 | Units for additional shell results are now shown when viewing a shell contour result. 4 | The right-click command “Results > Show in folder” in the Model Tree now searches for files with extensions of FNO, LOG, OUT, NAS. If found, File Explorer opens and highlights the first one found. A message indicates if none of the files exist. 5 | Units for rotation results are now shown in the results contour. **However, the results show “deg” when the values are actually radians**. See Unit of rotation results is wrong in Inventor Nastran For previous releases, see * Inventor Nastran 2026.1 list of changes * Inventor Nastran 2026.0 list of changes * Inventor Nastran 2025.3 (No software changes. Released to match version of Inventor 2025.3.) * Inventor Nastran 2025.2 list of changes * Inventor Nastran 2025.1 list of changes * Inventor Nastran 2025.0 list of changes * Inventor Nastran 2024.3 list of changes * Inventor Nastran 2024.2 list of changes * Inventor Nastran 2024.0 list of changes * Inventor Nastran 2023.2 list of changes * Inventor Nastran 2023.1 list of changes * Inventor Nastran 2023.0 list of changes * Inventor Nastran 2022.2 list of changes * Inventor Nastran 2022.1 list of changes * Inventor Nastran 2022.0 list of changes * Inventor Nastran 2021.2 list of changes * Inventor Nastran 2021.1 and 2021.1.1 list of changes * Inventor Nastran 2021.0 is available * Inventor Nastran 2020.2 list of changes * Inventor Nastran 2020.1 list of changes * Inventor Nastran 2020 list of changes
forums.autodesk.com
December 10, 2025 at 11:18 PM
Fasteners Tool Keeps Renaming Bolts/Nuts/Washers and Breaking Our Custom Naming Workflow
Hi everyone, I need help with an issue we are facing with the Fasteners tool in Fusion. Our team already has a large library of bolts, nuts, and washers inside the **Standard Components** folder. These components were previously inserted, renamed, and organized with **our own internal codes**. However, when we insert the _same_ fasteners again using the Fasteners tool, Fusion automatically **renames** the components and ignores our custom naming. Every time we open Fusion for the first time and insert a fastener, we need to rename it manually again. The worst part: * If we **restart Fusion** , all the custom names are lost. * When we insert the fasteners again, Fusion renames them once more. * This also causes **lost references** in assemblies because the renamed components no longer match the previously used ones in the library. We need a way to: 1. Prevent the Fasteners tool from renaming components that already exist in the Standard Components folder. 2. Keep our custom names persistent after restarting Fusion. 3. Ensure fasteners maintain the same reference so assemblies don’t break. Has anyone found a stable workaround or setting to stop this automatic renaming behavior? Any help is greatly appreciated. Thank you!
forums.autodesk.com
December 10, 2025 at 9:09 PM