25175d68ca1817c26bccdf346e14dfd7886035cf
69
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
7f2af7f729 |
Merge origin/main into smlib
Conflicts, both sides kept:
- Cargo.lock, crates/engine/Cargo.toml: smlib's solidcraft-profile/solidcraft-step beside
main's solidcraft-testkit and the image comment.
- crates/doc/src/{eval,eval_more,name_lookup,project}.rs: smlib's "a stored name finds its
face or edge or asks to reselect" logic kept; main's long-name quoting (#8673) applied to
its messages. Main's split-name hole re-lookup (#10699) dropped: names here never report
split.
- crates/doc/src/lib.rs: both exports, with main's revolve_extent_for_handle.
- crates/engine/src/cmd/silhouette.rs: main's outline()/Silhouette split, on the fallible
world_state().
- crates/engine/src/cmd/sketch_project_tests.rs: both tests.
- crates/ui-egui/src/{canvas,hole_refs}.rs: main's anchor_item/model_text on
open_meshing::session_world.
- crates/ui-egui/src/preview.rs: main's cut_tint switch around smlib's kept-surface ghost
filter; both helpers and both tests.
Seam fixes: FeatureKind::Repair in main's kind_key/type_name_to_kind_key (#10748); main's
new world_state() callers in ui-egui use session_world or unwrap in tests; a sketch test's
Spline gets nurbs: None.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz
|
||
|
|
bdce595fb3 |
Render results: retained renders, Live and render compare, render all shots (#6281) (#7375)
* Render results: keep up to eight completed renders and select or discard them * Render results: Live and render compare with a divider, and render all shots * fix: use comparison theme tint and reveal reset test targets * fix: restore Unicode expectations in render workspace tests |
||
|
|
180384fff4 |
Merge origin/main into smlib
Conflicts: Sketch Project keeps develop's exact pieces (a free-form edge as one spline) and takes main's test for a spline that follows a circle, sampling every free-form piece; the silhouette takes main's per-face facing, with develop's corner normals where a face has none; the extrude dialog caches main's automatic operation over develop's fallible call. world_state() is fallible on develop: main's new callers handle its error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz |
||
|
|
228b311a6f |
Raytracer: map faces to looks once (#10502)
* claim: Raytracer: map faces to looks once * Raytracer: map faces to looks once per body Preparing a body for the CPU raytracer walked the body's face look list one entry per work step for every triangle, so a body cost T x (F + 1) steps (each through the job host) instead of T. The face looks are now sorted once per body, keeping the first entry per face as before, and each triangle finds its look with one binary search. Pixels are unchanged; with 10 000 faces and 50 to 500 face looks, preparation drops by 40 to 88 %. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Markus Kaltenbrunner <kaltenbrunnermarkus@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
7d760a923a |
Merge origin/main into smlib
Main's open flow keeps the session's check mode: a saved model under another mode is evaluated again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk |
||
|
|
a8be28563c |
Sketch: leave out the exact roundoff estimate away from the pixel bound (#10267)
A flat node's roundoff allowance took a hypot per control point. Twice |x| + |y| bounds each hypot from above with room to spare for rounding, and rounding keeps sums monotonic, so whenever the flatness test passes with that larger allowance it passes with the exact one too. Only nodes whose chord distance comes near the 0.5 px bound (or with a non-finite term) now take the exact hypots, and they decide as before. Same result for every node: the reference comparison test still matches bit for bit. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
653bc00be4 |
Sketch: work out each sampled point's clip distances and screen position once (#10343)
Each node of the display curve sampler recomputed a control point's seven clip distances for every clip plane it tested (up to 7 times for the reject test, 3 more for the depth test, once more for the cut), and projected each point to the screen twice. They are now worked out once per node into arrays and read from there. Most nodes are split rather than drawn. A node is flat only when every control point lies within the pixel bound of its chord after adding a roundoff allowance that is never negative, so a point already farther than the bound decides "split" on its own; the allowance (four hypot and divisions per point) is now left out for those nodes. Same values in the same order: the reference comparison test from the previous commit still matches bit for bit. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
c25c2f3a21 |
Sketch: sample display curves without a heap copy per subdivision (#10342)
The pixel-bounded curve sampler that draws sketch curves and profile outlines ran again on every camera move, and each subdivision step allocated: every span's control points were a Vec, splitting one in half built a Vec per de Casteljau level, each node's projection was collected into a Vec, and every drawn part grew from two vertices. The control points now live inline in a fixed array (`Hull`, at most a degree-9 Bezier), the halves are worked out in place with the same `mix` level by level, the projection goes into a reused array, and a new part starts with room for eight vertices. The arithmetic and its order are unchanged, so the points are the same bit for bit. Tests: `samples_the_same_points_bit_for_bit_as_the_reference` keeps the previous sampler as a reference and compares paths, quality and budget use over every segment kind, slanted and far-off planes, orthographic and perspective views from far out to far in, clipped and unclipped, with ample and spent budgets. Ignored timings: `sampler_cost_against_the_reference` (render) and `sketch_scene_cost_while_the_camera_moves` (ui-egui). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
5a161e542b |
Merge main into smlib (develop): 76 conflicting files resolved
main |
||
|
|
295bd0e165 |
Render: fit the product inside the picture's frame, after the saved setup loads (#5763) (#5764)
While Frame shows the picture's frame, the preview projects into that frame rather than the viewport, but Fit Product and the fit on entering Render framed the product for the viewport's free area, so a picture taller than wide cut the product at its sides. The fit now uses the viewport layout seen from the frame (the frame as the viewport, the free area inside it with the usual 16-point margin). Entering Render fitted before the saved setup replaced the draft, so a cold workspace with a portrait setup fitted for the old draft's aspect; the fit now runs once the setup in effect is loaded. render.camera.fit takes the picture's aspect (0.000001 to 1000000) through Camera::fit_aspect, which publishes only a valid fitted camera: an aspect that would divide the distance into infinity is refused and the previous camera, document and undo stay as they were. |
||
|
|
db0c25522e |
Render: a size the CPU profile can't render names the profile that can (#8941) (#8943)
* claim: #8941 * Render: a size the CPU methods refuse names the profile that renders it (#8941) The Shots strip offers 4K UHD whatever the method. Under the default CPU raster, and under CPU ray tracing's default Compact profile, Render was then refused with English engine text that didn't say how to render that size. The refusal is now translated and names the smallest CPU resource profile that admits the size (with CPU ray tracing, for raster, which has no profiles). The size lists mark such presets. Nothing is switched: method, profile and resolution still change only when chosen, and GPU path tracing is unaffected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
738f336e12 |
Raytrace: a closed box dielectric is certified from its mesh's geometry, in any tiling
The closed-box certificate took exactly twelve triangles, two a face. The one mesher puts interior points on planar faces (a 20 x 20 x 2 box comes in more than twelve), so render.preflight refused a box as "unsupported dielectric boundary tessellation"; a box is a box however its faces are triangulated. The certificate now reads the mesh's geometry exactly: every triangle in the plane of one of the faces of the box its points span (corners on it, normal exactly that axis) facing out, and the triangles a closed, consistently oriented surface (each edge, by its ends' exact coordinates, run once each way). Such a surface is a 2-cycle on the box's boundary, a sphere, so it covers every point of it the same k >= 1 times, and its area is k times the boundary's: k = 1 is decided by the area being under 1.5 times the boundary's. Up to 65536 triangles. A thin sheet is still one or two triangles; a general closed mesh is still refused. New test: a box with its top fanned from a point in it is certified, with the same bounds; the point 1e-9 off the plane, or the top covered twice, is refused. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
d11d268597 |
Render: reject excessive pixel work during preflight (#5088) (#5728)
* claim: #5088 * fix: reject excessive render pixel work during preflight (#5088) |
||
|
|
3cc10acafa |
Render lights: uniform light list, solo and mute, and the Light editor (#6281) (#7265)
* Render lights: uniform light list, solo and mute, and the Light editor * Render lights: Lighting and Light editors to the approved design * Render lights: the scale-test frame carries the product light list * Restore the stable Render light mute target on the shared eye control * fix: validate the viewport BRDF probe with current shader dependencies * fix: compile legacy lighting controls only for tests * fix: scope the legacy lighting preset import to tests * fix: reuse the merged Add Light label and translations * test: enable the implemented Add Light radial action * fix: restrict the legacy CPU vector editor to tests * test: reveal Output before checking Lights browser focus * test: use the published Browser card rectangle for Output scrolling * test: reveal Output children before exercising editor navigation |
||
|
|
30dc4c8601 |
Section hatch by part: touching cut parts never look alike
Each body a section cuts is hatched at 45 or 135 degrees in one of three colours of one family (the cap's clay, a steel and a sage, theme tokens `section_cap` and `section_hatch`). Bodies whose cut outlines touch or overlap get different hatches, the angle changed first, then the colour (solidcraft_render::hatch, a greedy map colouring of the cut); otherwise a body keeps the hatch its name seeds, so it stays the same from frame to frame and as the plane moves. Spacing and line width are unchanged. The hatch rides on the palette (an Rg32Uint texel: colour, 1 + hatch), so the viewport, headless GPU pictures and the CPU raster draw the same. Preference Graphics > Section hatch: By part (default) or One style, the look before this change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5Lzv2n8fyKqD61NCHSF |
||
|
|
c33bae8701 |
Section cap: only closed bodies take part in the crossing count
An open body (a surface body, a mesh that does not close) has no inside: its faces counted with the rest took the cap from the closed body it lay in or behind. The body's closedness, which the kernel knows (`ModelBody::is_closed`: no shell left open, a mesh body every side of which two triangles share), goes with it to the renderer (`SceneMesh`, `PlannedBody`, `InstancedMesh`, a block's closed runs, the loose open triangles), and the count draws closed bodies only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5Lzv2n8fyKqD61NCHSF |
||
|
|
14acdc2a6d |
Render: one sRGB transfer function (#7161) (#7162)
* Render: one sRGB transfer function, geom::srgb, for the hand-written copies (#7161) Twelve places wrote the sRGB encode or decode formula out by hand (doc's glass recipe, engine's render library, glTF import, the PNG film, photographic and presentation output, the ray tracer's image, the stage, the surface decoder, texture normalisation and the theme's contrast check). They now call solidcraft_geom::srgb: encode/decode on 0..1 values, encode8/decode8 for 8-bit codes. render::surface::srgb8_to_linear stays as a re-export, so its callers are unchanged. Same results: the module's tests compare it bit for bit with the formula as the callers wrote it, over all 256 codes and a dense sweep of linear values plus the knees, out-of-range values, infinities and NaN, for each way the callers clamped (after encoding, before it, or not at all), and decoded values either side of the decode knee, where no 8-bit code falls. One change: glTF import encoded in f32. Over every f32 in 0..1, 218 of 1,065,353,217 values sit on a rounding tie that f32 got wrong and now give the neighbouring code (f64 gives the nearer one). Left as they are: render/job/image.rs (replaced by exact tables in its own change), the tests and the starter-pack validator that keep their own copy as an independent reference, and the WGSL shaders (they can't call Rust). Fixes #7161 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: the sRGB codes of five callers that had no test of their output (#7161) The glass swatch, a library surface applied as a plain appearance, glTF's fallback for a colour channel that isn't a number, a stage panel and an empty pixel in presentation output each get an assertion with their sRGB codes worked out by hand. A planted wrong conversion at each is now caught by that test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
4fa051c9fc |
View angles: an optional readout under the orientation gizmo and a command to set them (#6032) (#6249)
* claim: #6032 * View angles: an optional readout under the orientation gizmo and a command to set them (#6032) View > View angles (also Preferences > Graphics, or view.angle_readout) shows the view's pitch, yaw and roll in degrees and Ortho/Persp under the axis view or cube, updated live; off by default. Clicking the readout opens a small card to type exact angles, which runs view.apply. The angles are the camera's own (Camera::view_angles / with_view_angles), about the up axis: yaw is the heading of the line of sight (Front 0, Left 90, Right -90, Back 180), pitch the eye's elevation (Top 90, Bottom -90), and a positive roll turns the model clockwise. view.apply documents this convention and now refuses a pitch past +/-pi/2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
7b03439dda |
Navigation: Free orbit can turn around the vertical axis (#6964) (#6965)
* Navigation: Free orbit can turn around the vertical axis (#6964) A new option under Free orbit, Turn around the vertical axis, makes mouse drags a turntable without the pole limit: sideways turns about the world's up axis (reversed upside down so the model follows the cursor), up/down tilts over the top. Off by default; free orbit without it is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n: Japanese and Chinese for the vertical-axis orbit option (#6964) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n: Arabic, Hebrew, Vietnamese, German and Korean for the vertical-axis orbit option (#6964) Main now treats ar, he and vi as complete catalogs, so the merge queue's every_complete_catalog_carries_every_english_message failed on the two new ids. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UhpMr6L9PR8SJXjM6MbQrD --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: danieldimitrov86 <danieldimitrovdev@gmail.com> |
||
|
|
e29075376c |
Curvature Map: a scale that lightens steadily from flat to tight (#975) (#6136)
The blue, green, red scale's lightness rose and then fell (L* 44 up to 72 and back to 50), so a flat face and a tight radius looked alike with hue lost, and its upper part merged for a red-green loss. The stops are now dark blue, a middle grey-gold and light yellow in one straight blend, as measured in the issue: L* rises the whole way and every quarter step stays clear for normal, protan, deutan and tritan vision. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
6f5f64f2d9 |
Viewport: perspective while orbiting, orthographic on face-on views (#2682) (#6700)
* claim: #2682 * WIP: perspective-while-orbiting with auto-ortho on face views --------- Co-authored-by: Dahak Builds <dahakbuilds@users.noreply.github.com> |
||
|
|
4ced1d7bcf |
Viewport: the grid fades with the distance instead of cutting off (#4214) (#4629)
* claim: #4214 * Viewport: the grid fades with the distance instead of cutting off (#4214) The ground grid stopped at a fixed distance from the view, so its edge showed as a cut across the picture. It now fades out with the distance from the middle of the view, and it is gone before either of the two lines that used to cut it: its own edge, and the picture's far plane. Each grid line is drawn in pieces, and each piece is as faint as the fade makes it at the distance where it lies. The 'under' batch is drawn by the overlay pipeline with alpha blending, so the colour's alpha reaches the frame. * The headless grid fades with the distance too (#4214) The headless path (solidcraft-cli snapshot, the home-page thumbnail, the MCP screenshot) drew the grid from the engine's palette, where a line had no alpha: the grid still ended in a cut, and at a low camera angle the cut was in the picture. A SceneLine now carries an alpha, the CPU rasterizer blends with it and the GPU capture passes it on, so the engine's grid can fade. The fade itself moves to the engine, next to the grid's other geometry, and both paths use it: the headless grid now reaches as far on the ground as the view is wide (the ground stretches as it is seen at a slant) and dissolves into the distance instead of ending in a line. * Fix the headless/viewport grid fade divergence (#4214) The engine stretched the grid's size with the slant of the plane it is seen at, the viewport stretched it only on the ground, so on a sketch's plane the picture's grid reached further than the window's (153.42 mm against 120.00 mm). Both now share one grid_ext, which the picture and the window draw the same grid from. * The grid fades out before the picture's far plane cuts the ground (#4214) The window's grid faded against a far plane of its own: the scene's radius clipped by the projection's camera (260 mm away at 400 mm of distance), while the picture itself cuts the ground at the far plane of its own projection (223.7 mm at the same distance, because the projection frames the scene's bounds and not its radius). The grid was still a third of its strength where the picture cut the ground, so the cut showed as a straight line across the view. The fade now ends at the far plane the picture's projection uses, and the grid is gone before that plane cuts the ground. The test that watched the fade now measures the ink of each row of the picture, and checks that the grid is already gone in the ten rows above the row where the far plane cuts the ground: the point it compared before lay beyond that plane, where both renders draw nothing at all, so the comparison was always true. |
||
|
|
111dbc6855 |
Render: the radiance bound check uses a range, as clippy 1.97 asks (#6650)
`cargo clippy --workspace --all-targets -- -D warnings` fails on Rust 1.97: the reflection radiance bound in crates/render/src/raytrace/image.rs (#5494) trips `clippy::manual_range_contains` (`v < 0.0 || v > 1e12`). It now reads `!(0.0..=1e12).contains(&v)`. The two differ only for NaN, which the `is_finite` check in front of it already refuses, so nothing else changes. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
699f526429 |
Show imported mesh edges in shaded and wireframe views (#5662) (#5740)
* claim: #5662 * Show imported mesh outlines in viewport (#5662) * test: update mesh regression origin visibility setup |
||
|
|
ac53fc1e6f |
Viewport: bodies stay visible after switching to perspective and back (#5422) (#5614)
* claim: #5422 * Viewport: bodies stay visible after switching to perspective and back (#5422) |
||
|
|
9e6e0b8df1 |
Render workspace: complete experimental ribbon, resources and effects integration (#5493) (#5494)
* wip(render): reconcile completed material and image pipeline source with 0.20 (#5493) Source-only integration reference for staged review, not a merge-ready aggregate. Donor: 0xlillith/solidcraft@aea20b0115. Upstream: |
||
|
+33 |
b7b25f9e2b |
Render workspace: first basic delivery to main (#6050)
* Normalize UI container violation paths across platforms (#5599) Report repository-relative paths with forward slashes so diagnostics and the existing nested-package regression assertions agree on Windows and Unix. Keep the container detection rules unchanged. Validation: official ui-containers gate and all seven focused xtask tests passed; rustfmt and diff checks passed. Only xtask/dependencies were compiled; no application build or heavy tests. (cherry picked from commit |
||
|
|
769dfff1a5 |
Section Analysis: a Hatch option (#4563) (#4565)
* claim: #4563 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Section Analysis: a Hatch option, off for a plain cut in the body's colour (#4563) The Section Analysis dialog gets a Hatch check box beside Flip, and inspect.section a hatch?: bool (default true), so scripts, the CLI and the control channel reach it too. Hatched, a cut is its body's colour tinted toward the cap colour with 45 degree stripes, as before; off, it is the body's own solid colour. The viewport (cap alpha in the uniform), the CPU rasterizer and ui.render follow it, and the section keeps it when hidden and shown again or edited. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
920398ac53 |
Bring back the view-change glide; orbit, pan and zoom stay instant (#4596)
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
dfd58293a6 |
Navigation: opt-in free orbit and shared Normal to Selection (#1912)
* Navigation: opt-in free orbit and shared Normal to Selection Preserve the complete reviewed feature, shared camera setting propagation, rigid pivot behavior and focus/drag regressions from PR #1912. Consolidate the prior main-integration commits before rebasing, so their merge-resolution fixes remain in the linear feature history. * docs: move free orbit help beside viewport controls * Merge main into fix/solidworks-free-orbit Camera animation is gone on main, and with it the orbit snap spring: the Shift snap keeps its unsnapped orbit in orbit_free, which the free-orbit checks now read. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> --------- Co-authored-by: bherbruck <brennen.herbruck@gmail.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
cb3cabeda1 |
Remove camera animation: every view change and orbit applies at once (#4296)
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
26f42ae09b |
Snapshot: draw a see-through appearance see-through, and show a tool body inside its target (#2329) (#2330)
* Snapshot: draw a see-through appearance see-through, and give the CLI --body, --tool and --section A headless picture dropped a body's opacity: the scene carried only a colour, so a design with a translucent appearance was drawn opaque by `solidcraft-cli snapshot`, by MCP screenshots and in a design's thumbnail, although the window has always drawn it as glass. There was then no way to look at the body a cut would remove inside the material it meets: only a volume to measure and reason about, which hides exactly the errors a picture makes obvious (a tool that stops short, or lands in the wrong place). - `SceneMesh` carries the body's opacity; `view::build_scene` takes it from the design (`model_body_opacity`), and a selected body stays solid so the selection colour reads. - The GPU capture routes a see-through body into the scene's glass at its own alpha, as the viewport does; the CPU rasterizer draws the solid bodies first (they own the depth buffer), then the see-through ones blended over them, far sides before near sides and without writing depth, so what lies inside shows and a line between the two is not hidden. - `snapshot --body NAME:opacity=0.3,color=#rrggbb`, `--tool NAME` (that body solid in the tool colour, the rest see-through) and `--section z=27` run the commands the app itself runs (`appearance.assign`, `inspect.section`): the options are shortcuts, not a second renderer. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Tests: measure the tool colour as it is drawn through a see-through target The tool-colour filter was derived on paper and demanded a red more than twice either other channel, which the target in front of it tints away (measured: (200, 108, 85) through opacity 0.3); and the colour check painted the tool, which a solid target hides. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fmt * Snapshot options: strip the colour's # rather than slicing it; README Slicing `value[1..]` on an input-derived string is what the house rules ask us not to write, even where a length check has already made it safe. The error a failed assignment reports now names the body rather than claiming it came from --body, since --tool reaches it too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * --tool: assign the bodies around the tool in groups, not one command at a time Each appearance.assign is an undo step with a document snapshot behind it, so one per body made --tool cost grow with the size of the design for no reason: the bodies around the tool all get the same opacity, and the ones that share a colour can be named in one call. A design whose bodies all wear the default grey now costs two commands whatever its size. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Rasterizer: say where its glass and the GPU's differ Splitting each see-through body by facing orders its own two layers; it does not sort across bodies, which the GPU does. Worth stating rather than leaving a reader to find it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com> |
||
|
|
e887792182 |
Fix orbit about the picked point (regression in 0.16.0) (#2753)
Orbiting about the point under the cursor (or the origin) turned the camera about its target and then panned to put the pivot back. The pan works at the target's depth with the parallel-view scale, so in a perspective view the pivot slid off its pixel and the model swung about the camera. The camera now turns rigidly about the pivot: Camera::orbit_about keeps the pivot's coordinates in the camera's frame and rebuilds the target from the new orientation, so the pivot stays exactly on its pixel in both projections. The Shift snap spring and view.navigate's pivot orbit use the same. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
2ae21143ee |
Motion animation export: a study or a joint drive as an animated GIF (#1680)
Thanks @SychPL. |
||
|
|
bbd4f29ebb |
Class-A surfacing 3/3: blend curves, curved-edge fillets, the G2 corner and continuity analysis (#1642)
Thanks @midasdf. |
||
|
|
1a0b33fcf3 |
Headless pictures draw on the GPU, with the viewport's pipelines (CPU rasterizer as last tier) (#1555)
Thanks @jyviko. |
||
|
|
845f4913cf |
render: add opaque CPU sampling and bounded mip chains (#1459)
Co-Authored-By: selune <0xlillith@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
b400958c3e |
render: add isotropic texture footprint LOD reference (#1460)
Co-Authored-By: selune <0xlillith@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
061c0f3333 |
render: add perspective UV interpolation and derivatives (#1461)
Co-Authored-By: selune <0xlillith@users.noreply.github.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
5fbbc13885 |
Render preview: draw within the pixel budget on 4K/5K screens (#1464) (#1477)
The product preview asked the viewport executor for the full physical viewport, so a maximised 4K window (~8 MP) was refused against the 4 MP limit on every frame. The preview now draws at the largest size of the same aspect the executor admits (RenderLimits::fit, scratch included) and filters it up into the viewport through the existing offscreen blit. Viewports within the limits still draw at full size. PNG setups past the image limits now say what the limits are and the largest size at that aspect, and the image panel offers to use it. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
1e984c8e46 |
render: normalize high precision texture inputs (#1267)
Adds a bounded normalization path for PNG16 and ICC-bearing JPEG texture inputs, producing float RGBA with recorded color and orientation decisions. Co-authored-by: 0xlillith <0xlillith@users.noreply.github.com> |
||
|
|
a261aaa841 |
Render: integrated workspace, preview image jobs and opaque PBR (#1046)
Lands the Render workspace (R3), bounded preview-image jobs with cancellation and atomic PNG export (R4a), and opaque PBR looks as one change. - Render workspace: an overlay-free product preview on the installed GPU device. Returning to Design restores its camera. render.scene and render.settings.apply are added. - Image jobs: render.preflight/start/status/cancel/export run bounded CPU preview jobs. Export captures the job, overwrite choice and document, and checks the caller's file scope before writing. - Opaque PBR: looks can carry metal fraction, roughness and dielectric IOR. The product viewport and preview PNG use them; geometry and mass are unchanged. The v1 catalog export refuses PBR rather than dropping it. - Render setups and PBR looks are saved under design format 21. Labels are in en/de/ja/ko/zh/ru. Supersedes #706 and #800. Refs #620, #673, #756, #1004. Contributed by @0xlillith. Co-authored-by: lillith <35337584+0xlillith@users.noreply.github.com> |
||
|
|
241dac1542 |
Render: bounded PNG/JPEG texture input admission (#909)
Bounded in-memory PNG/JPEG texture decoding with explicit base-colour/data-map roles; RGBA8 pixels are published only after a complete decode. Input only: no material assignment, GPU shading or persistence. Refs #900. Contributed by @0xlillith. Co-authored-by: lillith <35337584+0xlillith@users.noreply.github.com> |
||
|
|
88432d226a |
Render: bounded opaque surface contract and numerical BRDF reference (#1019)
A renderer-independent OpaqueSurface (colour, metallic fraction, roughness, dielectric IOR) with bounded inputs, an original GGX/Smith/Schlick reference response with Lambert diffuse, and exact piecewise sRGB8 decoding. Numerical contract only: no document format, command or UI change. |
||
|
|
345c0882cd |
Renders hide edges just behind a face; lines on steep faces draw whole (#983)
The CPU renderer's line depth test allowed a fixed share of the scene's depth range (2e-4), which on large designs or close views let edges a millimetre or more behind thin sheet show through it. Each pixel now keeps the screen depth slope of the surface it shows, and a line passes where it is no further behind than that slope spans across the line's width, plus f32 rounding. Section caps use their plane's slope. Edges lying on steep faces now draw their full width; edges behind a face stay hidden. Only crates/render/src/raster.rs changes; the GPU viewport is unchanged. Co-authored-by: NOWN-DEV <NOWN-DEV@users.noreply.github.com> |
||
|
|
e99b3bd4e8 |
render: bounded cooperative HDR input foundation (#837)
A cancellable, bounded Radiance HDR decoder for render lighting input; reference images still accept PNG and JPEG only. |
||
|
|
0e500cacd3 |
Render: add backend capability discovery and strict request resolution (#650)
Adds render.backends, a metadata-only command that lists the render backends, their executors and profiles, with strict request resolution in the render crate (docs/render-backends.md). |
||
|
|
296683229d |
Rename SolveCraft to SolidCraft everywhere, with compatibility shims (#389)
* WIP deep rename (not for push) * WIP2 * WIP3 * WIP4 wxs fix * rustfmt * Rename the remaining identifiers in merged crash-report code Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RjGw4gA5ZvKrU8MQP6sBgT --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
8cce89d78a | Merge pull request #189: add Windows SpaceMouse navigation | ||
|
|
af536a7907 | Rename displayed product to SolidCraft and add header bug reporting |