Concept: An automation tool for SAP2000 that eliminates manual data filtering. It instantly extracts and groups end-forces (Start/End) of selected frame elements based on their section profiles. Key Features: Automatic Selection Sensing: Analyzes only the elements currently selected in the SAP2000 model. Station Filtering: Focuses strictly on s=0 and s=L stations to capture critical design forces (N, V, M). Profile-Based Categorization: Automatically groups results by section types (e.g., IPE, HEB, SHS) for cleaner data management. One-Click Export: Streams structured data directly to a table or Excel, bypassing the heavy "Display Tables" menu.

The purpose of this tool is to compare two analysis models. It should provide visualizations and reports that allow users to quickly identify differences in M, N, V, PMM, and displacement at a glance

Website takes snapshot from IFC file with selected angle and render option

It would be nice if there were an opportunity to identify the Tekla version in which a model was created without opening it. Bir modelin hangi Tekla sürümünde oluşturulduğunu dosyayı açmadan öğrenme imkânı olsa güzel olurdu.

Hey everyone, Let's talk about one of the most frustrating limitations in Tekla: transferring drawing files between completely different models. We all know that .dg files are strictly tied to the 3D model's internal database and part GUIDs. If you have two separate models (maybe a heavily modified revision, a split phase, or you're just trying to salvage drawings from a corrupted model), you can't just copy the drawing files over. Cloning works to an extent, but it requires the 3D geometry and numbering to play nice. The Idea: What if we built an API tool that "strips" the raw 2D drafting data from a drawing? I’m talking about extracting the manual dimensions, text marks, view boundary coordinates, and manual linework, and exporting them into a lightweight format like JSON or XML. Then, in the new model, the "Injector" part of the plugin reads that data and recreates those 2D elements onto a new drawing view. It essentially temporarily decouples the intelligent 2D edits from the 3D database, allowing you to paste your hard-earned drafting work onto similar parts in a new model, or at least bring it in as "dummy" 2D linework/text to save hours of detailing. Has anyone ever tried to bypass the GUID system like this using the Tekla Open API, or tried parsing the raw data inside .dg files? Is this a pipe dream, or actually doable? Let me know your thoughts!

Dealing with consultant or vendor DWGs is usually a nightmare when it comes to layer management. You open a file and see layers like "WALL", "Wll", "01-Walls", "A-Wall-Full", etc. What if we built a LISP that uses fuzzy string matching (like Levenshtein distance algorithms) to analyze layer names? You run the script, and it scans the drawing, grouping similar names and maybe even checking color/linetype similarities. Then it prompts you: "Hey, these 5 layers seem to represent the same thing. Want to merge them into one standard layer?" Instead of manually scrolling through hundreds of layers and doing layer translations, it acts like a smart assistant for file cleanup. Do you guys think this is doable entirely within AutoLISP/Visual LISP, or would it require a .NET plugin to handle the fuzzy matching fast enough?

Hey everyone, We all know the pain of attaching a QR code to a title block (for project details, URLs, or revision dates), only to have the JPG/PNG go missing because someone along the line forgot to bind the XREF. I was thinking: what if we had a LISP that takes a string of text and generates a physical QR code using pure AutoCAD geometry? I'm talking about generating native 2D Solids or Polyline Hatches. No external dependencies, fully embeddable in the DWG, and you can change its color or layer just like any regular CAD object. It scales perfectly without pixelating, too. Has anyone actually written something like this, or would it be too heavy to generate? Thoughts?

What I’m aiming for is pretty simple: Just getting beams, columns, slabs, etc. into AutoCAD in a way that’s actually usable for drawings — without spending hours cleaning everything up or redrawing. I’ve tried / looked into: * DXF export → works, but the cleanup is pretty rough * Going through Rhino / other tools → kind of helps, but still not clean * A few workaround methods, but nothing feels “production ready” Main issues I keep running into: * Geometry comes in messy or broken * Layers are all over the place * Element types aren’t really preserved * End up spending too much time fixing things At this point I’m wondering what people actually do in real projects. Do you: * Have a workflow that works reliably? * Use any plugins or scripts? * Or just give up and redraw in AutoCAD? Would really appreciate hearing how others are handling this in practice. Thanks. ---------------- Kiriş, kolon, döşeme vs. AutoCAD’e düzgün şekilde gelsin ve çizim için kullanılabilir olsun. Saatlerce temizlik yapmadan ya da baştan çizmeden halletmek istiyorum. Denediğim / baktığım şeyler: * DXF export → çalışıyor ama sonrası baya uğraştırıyor * Rhino vs. üzerinden geçirmek → biraz yardımcı ama yine temiz değil * Farklı workaround’lar → ama hiçbiri tam “bu iş böyle yapılır” hissi vermedi Sürekli yaşadığım problemler: * Geometri dağınık veya kırık geliyor * Layer’lar çok düzensiz * Eleman türleri kayboluyor * Sonunda çok fazla düzeltme yapmak gerekiyor Şu noktada merak ediyorum, gerçek projelerde insanlar bunu nasıl çözüyor? * Belirli bir workflow mu kullanıyorsunuz? * Plugin / script kullanan var mı? * Yoksa direkt AutoCAD’de yeniden mi çiziyorsunuz? Gerçekten sahada nasıl yapıldığını duymak isterim. Teşekkürler.

Performance and Stability Improvements Revit users are asking for a faster and more reliable batch export experience. Key requests include: - Faster export process: Current exports take too long, especially in large projects. - Background processing: The ability to run exports without locking up Revit. - Error reporting: A logging system to identify which sheets fail during export. These enhancements would minimize wasted time and deliver smoother, error-free workflows for project teams -------------- Performans ve Stabilite İyileştirmeleri Revit kullanıcıları, batch export sürecinde daha hızlı ve güvenilir bir deneyim talep ediyor. Öne çıkan beklentiler: - Daha hızlı export süreci: Büyük projelerde export işleminin çok uzun sürmesi eleştiriliyor. - Arka planda çalışabilme: Export işleminin Revit’i kilitlemeden arka planda çalışması öneriliyor. - Hata raporlama: Export sırasında hangi sheet’in hata verdiğini gösteren bir log sistemi talep ediliyor. Bu geliştirmeler, kullanıcıların zaman kaybını azaltarak daha akıcı ve hatasız bir iş akışı sağlayacaktır.

Output Format Improvements Revit users are calling for stronger and more reliable output options in batch export workflows. Key requests include: - Simultaneous PDF and DWG export: The ability to generate both formats in a single operation. - Quality control: Revit’s native PDF output is often considered low quality, leading users to rely on add-ins such as DiRoots, Xrev, and RTV. - Missing objects issue: Reports indicate that some add-ins fail to export all visible model elements. These enhancements would make the export process more dependable, improving both quality and efficiency in project workflows --------------------- Çıktı Formatları İyileştirmeleri Revit kullanıcıları, batch export sürecinde daha güçlü ve güvenilir çıktı seçenekleri talep ediyor. Öne çıkan beklentiler: - PDF ve DWG’nin aynı anda alınabilmesi: Tek işlemle hem PDF hem DWG export yapılabilmesi. - Kalite kontrolü: Revit’in kendi PDF çıktısının düşük kalite olması nedeniyle kullanıcılar DiRoots, Xrev, RTV gibi eklentilere yöneliyor. - Eksik objeler sorunu: Bazı eklentilerde modelde görünen objelerin export sırasında kaybolduğu rapor ediliyor. Bu geliştirmeler, çıktı sürecini daha güvenilir hale getirerek iş akışında kaliteyi ve verimliliği artıracaktır.

File Naming and Organization Improvements Revit users are asking for more flexible and automated solutions in batch export workflows. Key requests include: - Parameter-based file naming: Automatically naming exported files according to sheet parameters. - Folder structure support: Allowing exports to be organized into project, discipline, or subfolders. - Bulk renaming: Eliminating the need for manual file name corrections after export through automation. These enhancements would streamline file management, reduce errors, and make workflows significantly more efficient ------------------------------------ Dosya İsimlendirme ve Organizasyon İyileştirmeleri Revit kullanıcıları, batch export sürecinde daha esnek ve otomatik çözümler talep ediyor. Öne çıkan beklentiler: - Parametre tabanlı dosya isimlendirme: Çıktı dosyalarının sheet parametrelerine göre otomatik adlandırılması. - Klasör yapısı desteği: Export edilen dosyaların proje, disiplin veya alt klasörlere ayrılabilmesi. - Toplu yeniden adlandırma: Export sonrası manuel dosya isim düzeltme ihtiyacını ortadan kaldıracak otomasyon. Bu geliştirmeler, dosya yönetimini hızlandırarak hataları azaltacak ve iş akışını daha verimli hale getirecektir.