PanosandClaude Opus 5 9fe2e4fa58 fix(view): hold ZOOMFACTOR to its own range, finish the exponential zoom
The exponential camera step is the right call. `0.9 ^ delta` is strictly
positive for every real delta, in and out cancel exactly where the
subtraction lost a percent of the view on every round trip, and the file's
own header has promised an "exponential feel" since it was written. Three
surfaces were left behind it, and the wider range exposed a fourth thing.

The range of the system variable. 3 to 100 is the range ZOOMFACTOR has, and
the User Preferences page was built against it; `SETVAR ZOOMFACTOR` accepts
that and nothing else again. A faster wheel is the Options window's business
instead: the slider covers the variable's own range, the field beside it
reaches 500, and a read-out says what a notch actually does ("10.0% a
notch") so the number being set is readable rather than implied. A value
above 100 therefore lives only in this application's own configuration file,
where it is nobody else's to read, and a bare `SETVAR ZOOMFACTOR` still
reports it. The bounds and the clamp live in one place now
(`settings::clamp_zoom_factor`): four literal copies of `3, 100` are what
let a surface be missed in the first place.

A floating viewport in MSPACE. It zooms its own view through
`zoom_active_viewport`, which kept subtracting: the factor reached zero at
6.67 steps, so from ZOOMFACTOR 360 up every notch inside a viewport bottomed
out on the clamp — a tenfold jump a notch, and the top third of the slider
doing nothing at all. Exponential there too, from a base of 0.85 so the
default notch still moves a viewport the 15% it always has. Each surface
keeps its own long-standing feel rather than inheriting the other's.

The trackpad pinch. `pinch_zoom_steps` was calibrated against the
subtraction (`1 - step / 10 = 1 / (1 + m)`) so that a pinch of m leaves the
view exactly 1 + m times closer — the property docs/trackpad.md documents
and the reason the gesture tracks the fingers at all. Inverting the zoom law
by hand is what let the two drift apart, so the step is asked of the camera
now (`Camera::zoom_steps_for_ratio`), which cannot drift by construction.
`pinch_is_one_to_one` recomputed the old formula rather than the camera's,
so it kept passing through all of this; it zooms a real camera and measures
the distance it lands at instead.

Also: `zoom` had a floor and no ceiling, and zooming out multiplies. At
ZOOMFACTOR 500 a notch out is x2.4, so about ninety notches — a couple of
seconds of scrolling — ran the distance past what an f32 far plane
(`distance * 1000`) can hold, and the viewport went black on an infinite
projection. A degenerate pinch magnification of -1 or beyond reached the
same place through the other side. Both are bounded now.

Also: two doc comments quoted the linear law (`zoom_view_at_cursor` and the
one on `pinch_zoom_steps`), and docs/trackpad.md stated the pinch identity
and claimed the tests covered it against the camera. All updated, with what
a notch does and where each surface's range comes from written down.

Tests, each confirmed against the behaviour it describes: the zoom law at
every factor the application can hold (positive, monotonic in the setting,
in and out cancelling), the ceiling under a long scroll out in both
projections, the published inverse and what it does with a nonsense ratio,
the viewport factor and a real viewport zoomed three notches at the top of
the range, the SETVAR range including a value the Options field set, the
Options field (above 100, above the ceiling, cleared, not a number), its
agreement with the slider, Close putting both the value and the field back,
and the read-out's percentages. 1882 lib tests pass.

The two new Options strings are not in the locale catalog yet, so they
render in English until it is regenerated.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-10-02 10:51:26 +03:00
2026-03-22 14:53:51 +03:00
2026-08-22 09:33:38 +03:00

English · Български · Português (Brasil) · Čeština · Nederlands · Français · Suomi · Deutsch · Ελληνικά · Magyar · Italiano · 日本語 · 한국어 · Polski · Русский · 简体中文 · Español · 繁體中文 · Türkçe · हिन्दी · العربية

Open CAD Studio logo

Open CAD Studio

Open-source 2D drafting and 3D modeling for desktop and web, built with Rust.

Latest release Release downloads GitHub stars GPL-3.0 license

Launch the web app · Download the desktop app · Join the discussion

Open CAD Studio workspace

Overview

Open CAD Studio is a cross-platform application for technical drawing, layout work, and solid modeling. It reads and writes DWG and DXF drawings natively, with a shared editing core across the desktop and browser versions.

The project is under active development. Keep backups of important production drawings and report reproducible problems through GitHub Issues.

Highlights

  • Native drawing workflow — open, edit, recover, and save DWG and DXF files without a conversion service.
  • Precise 2D drafting — lines, polylines, curves, splines, hatches, object snaps, tracking, layers, blocks, and external references.
  • Documentation tools — text, dimensions, leaders, tolerances, tables, model space, paper space, viewports, and plot styles.
  • Kernel-backed 3D modeling — solid primitives, extrusion, revolution, sweep, loft, Boolean operations, and ACIS entity tessellation.
  • GPU rendering — accelerated 2D and 3D viewports through wgpu, with orthographic and perspective cameras.
  • Extensible workflows — native plugins, command scripts, headless conversion, and a line-based JSON automation API.

3D model in Open CAD Studio

File workflows

Format or workflow Support
DWG Read and write; versioned save targets from R14 through 2018
DXF Read and write; versioned save targets from R14 through 2018
BAK / SV$ Open drawing backups and autosave files
OBJ Import polygon meshes
LandXML Import CgPoint survey points
STL Export 3D mesh data
STEP AP203 Export 3D mesh data
PDF Plot layouts and selected geometry on desktop
CSV Extract entity property data
CTB / STB Load and edit plot style tables

Desktop or web

Use the web app for immediate access with no installation. Drawings are selected through the browser and saved as local downloads.

Use the desktop application for native file associations, file-manager thumbnails, system printing, PDF output, external plugins, command scripts, and headless automation. Release builds are available for Windows, Linux, and Apple Silicon macOS.

Install

Download all current packages from the latest release.

Windows

Choose one of these signed x86-64 packages:

  • OpenCADStudio-*-windows-x86_64-installer.msi — recommended installer with Start Menu shortcuts, DWG/DXF file associations, and drawing thumbnails.
  • OpenCADStudio-*-windows-x86_64-portable.exe — standalone application; no installation required.

Linux

Download the x86-64 AppImage, make it executable, and run it:

chmod +x OpenCADStudio-*-linux-x86_64.AppImage
./OpenCADStudio-*-linux-x86_64.AppImage

Or install it as a Flatpak from FlatPark, which installs the official AppImage and follows new releases:

flatpak remote-add --if-not-exists flatpark https://dl.flatpark.org/flatpark.flatpakrepo
flatpak install flatpark io.github.HakanSeven12.OpenCadStudio

The Flatpak opens and saves drawings through the file chooser. External references and underlays that point at other files need home access:

flatpak override --user --filesystem=home io.github.HakanSeven12.OpenCadStudio

macOS

The published macOS package supports Apple Silicon:

  1. Download OpenCADStudio-*-macos-arm64.dmg.
  2. Open the image and drag OpenCADStudio.app into Applications.
  3. If Gatekeeper blocks the first launch, approve the app from System Settings → Privacy & Security.

The application is ad-hoc signed but is not currently notarized by Apple.

Languages

Open CAD Studio can follow the system language or use any of these 21 interface languages:

Arabic · Brazilian Portuguese · Bulgarian · Czech · Dutch · English · Finnish · French · German · Greek · Hindi · Hungarian · Italian · Japanese · Korean · Polish · Russian · Simplified Chinese · Spanish · Traditional Chinese · Turkish

Change the language from the application settings. The browser version also uses the browser's preferred locale when System is selected.

Build from source

Desktop

Requirements:

  • Git
  • Current stable Rust toolchain
  • Platform graphics and font development libraries

On Ubuntu or Debian, install the native dependencies with:

sudo apt update
sudo apt install libgl1-mesa-dev libx11-dev libxcursor-dev libxi-dev \
  libxrandr-dev libxkbcommon-dev libwayland-dev libfontconfig1-dev \
  libfreetype6-dev

Then build and run:

git clone https://github.com/HakanSeven12/OpenCADStudio.git
cd OpenCADStudio
cargo build --release --bin OpenCADStudio

The resulting binary is written to target/release/OpenCADStudio (OpenCADStudio.exe on Windows).

Web

Install the WebAssembly target and build tools once:

rustup target add wasm32-unknown-unknown
cargo install trunk wasm-bindgen-cli

Start the development server:

trunk serve

Automation

The desktop binary supports one-shot conversion, a persistent headless server, and a client-neutral MCP endpoint for AI applications:

OpenCADStudio --export input.dwg output.dxf
OpenCADStudio --export input-r12.dxf output.dwg --target-version R14
OpenCADStudio --serve
OpenCADStudio --serve --port 4242
OpenCADStudio --mcp

The automation server exchanges one JSON object per line over standard input/output or a local TCP socket. The self-contained MCP endpoint exposes the live desktop editor through the same tools to every compatible client. Its audit and save_verified operations check an explicit DWG/DXF target version, lossy records, raw DXF handle references, reopen the output, compare its semantic manifest, and return a SHA-256 hash. To connect a client, configure it to launch OpenCADStudio --mcp. See the MCP control guide.

Plugins

Desktop plugins run in separate processes and communicate with the host through the versioned plugin API. The browser build does not load native plugins.

Project documentation

Contributing

Bug reports, focused pull requests, translations, documentation improvements, and plugin contributions are welcome.

  • Search existing issues before opening a new report.
  • Use Discussions for questions and ideas.
  • Report vulnerabilities privately by following the security policy.

Application translations live in locales/*/opencadstudio.ftl; source labels map through src/locale_catalog.rs. After editing translations, run python3 scripts/export-locales.py to refresh web and desktop packaging labels. Validate with python3 scripts/test_site.py and cargo test --lib i18n::tests.

Project growth

Stars

Open CAD Studio star history

Release downloads

Open CAD Studio release download history

Support the project

If Open CAD Studio helps your work, support continued development through GitHub Sponsors or Patreon.

License

Open CAD Studio is distributed under the GNU General Public License v3.0.

S
Description
OneBSpace rebrand of OpenCADStudio -> OneCAD Draft (2D drafting / 3D modeling studio) + native Odoo Documents integration (open/save/write-back). Member of the OneCAD family. Upstream: opencadstudio-upstream. Addon: one_cad_draft.
Readme GPL-3.0
249 MiB
0 Stars 1 Watchers 0 Forks
Languages
Rust 70.8%
Fluent 27.8%
WGSL 0.5%
Python 0.3%
TypeScript 0.2%
Other 0.2%