CadWare TechCustom CAD application development
CoreCAD.NET / RenderingCoreTracing.NET · planned module

Photorealistic viewport.

A path-traced display mode inside the CAD viewport, powered by AMD Radeon ProRender. Switch it on to present a design with physically based lighting and materials; switch it off and keep editing.

PLANNED ▸

Planned. CoreTracing.NET is under active development and is not yet part of the standard installer; availability and hardware requirements for your scenario are confirmed on request.

How it runs

Your application never waits, and never crashes with the driver.

The CAD viewport in your application process hands the scene to CoreTracing.NET on a worker thread, which renders with AMD Radeon ProRender. The graphics hardware is checked by an expendable child process: if the driver crashes, only that process dies.YOUR APPLICATION PROCESSCAD viewportedit, undo, navigateas usualrealistic mode ONCoreTracing.NETworker thread ·incremental scene syncprogressive framesUI never blockedAMD RadeonProRenderSDK 3.1.6CPU or GPUbackendlaunchexit codeEXPENDABLE CHILD PROCESSGPU probechecks the graphics hardwareand the driver before useIf the driver crashes,only the probe dies —never your application

Scroll sideways to see the whole diagram.

Availability verdict reported to the host: available · module absent · licence denied · hardware unsuitable · start-up error. The host never references the module at compile time: it discovers it at runtime and degrades gracefully when it is missing.

Realistic mode

Switch it on to present, switch it off to edit.

Image

  • Progressive rendering: the image refines while the camera is still, with a fast preview during navigation
  • Incremental updates after edits and undo — per entity geometry, transform and material
  • Frame metrics and save frame as PNG

Materials & light

  • PBR materials: base colour, roughness, metalness, emission
  • Image-based lighting with intensity and rotation; Reinhard or clamp tone mapping
The complete list

Every planned capability.

Open an area to read what it covers.

01Realistic viewportPlannedPath tracing inside the existing viewport, with the image refining over successive iterations.8 capabilities
  • The realistic mode replaces the normal view of a single-viewport layout with a path-traced image rendered by AMD Radeon ProRender, while the view cube, the toolbars and the other viewport overlays stay visible on top.
  • Turning the mode on keeps the normal view on screen until the first traced frame is ready, and turning it off brings the normal view back at once.
  • The image refines progressively over successive iterations and stops refining once it has converged, so a still view does not keep the processor or the graphics card busy.
  • The traced camera follows the viewport camera in perspective and orthographic projection, with quick coarse feedback while the user orbits, pans or zooms and full refinement as soon as the gesture ends.
  • Document changes made while the mode is on, such as adding, deleting, moving, recolouring or reshaping a solid, update only the affected objects in the render, and the host can request a full refresh at any time.
  • The render shows the visible solid bodies and meshes on visible layers, with curved faces smoothly shaded at the drawing's tessellation quality, while curves, texts, dimensions and block references are not rendered.
  • Rendering runs on a dedicated thread and new frames reach the screen at a capped rate, so the user interface stays responsive while the image refines.
  • The session reports a progress line with the active backend, the samples accumulated and whether the image is still refining or has converged, for the host to show in its status bar.
02Materials & lightingPlannedPhysically based materials, derived automatically from the drawing or assigned explicitly, lit by a built-in studio environment or by HDRI images.6 capabilities
  • A document needs no preparation, because each rendered object gets a physically based material derived automatically from the Eyeshot material of the entity, otherwise of its layer, otherwise from the entity's own colour.
  • The derivation turns a material's diffuse colour into the base colour and its shininess into an equivalent roughness, while image textures are not rendered yet.
  • Scenes are lit by a built-in studio environment with a bright overhead, a neutral horizon and a dark floor, generated in memory, so a document without lights still renders a readable image and no image file has to be deployed.
  • Every material is built with the same physically based recipe on both render backends, so switching backend does not call for different materials.
  • HDRI images can light the scene in place of the built-in studio environment, with the light's intensity and rotation set by the host.
  • Physically based materials can be assigned to objects explicitly and saved with the document, image textures included.
03Image qualityPlannedTone mapping, colour handling, denoising and saving of the rendered image.5 capabilities
  • Each frame is tone mapped before display, so bright highlights are compressed gradually instead of being clipped to flat white.
  • Drawing colours are converted to linear light for rendering and frames are encoded with the sRGB curve for display, so rendered colours stay consistent with the colours of the drawing.
  • Pixel values that the engine returns as not-a-number, infinite or negative are shown as black or white instead of corrupting the frame.
  • An optional denoising pass gives a clean image after fewer iterations, and the image is shown without it when the denoiser is not available.
  • The realistic view can be saved to an image file.
04Hardware & reliabilityPlannedRendering runs on the processor by default, with an experimental GPU backend; GPU checks run in a separate process, so a driver failure cannot bring the application down; the module is optional.6 capabilities
  • Rendering runs by default on the processor with the Northstar backend, so no particular graphics card is required, and the GPU-accelerated HybridPro backend can be switched on for an application session as an experimental option for faster refinement.
  • GPU checks run in a separate helper process, so a graphics driver that crashes or hangs during the check ends only that process and comes back as a classified result instead of closing the application.
  • A GPU fault that the application survives is caught and classified instead of propagated, and further GPU checks in the same session are then refused without calling the driver again.
  • If the engine fails while rendering, the realistic mode switches itself off, the normal view returns and the host receives a classified reason with the full diagnostic report.
  • A machine check, run on request and never at application start-up, verifies the engine files before loading them, renders a small test frame and returns a plain-text report of the devices found, the SDK version and the outcome, kept for the rest of the session.
  • The module is optional and needs only the 2D core among the CadWare libraries: a host loads it at runtime without a compile-time reference, and the availability contract in CoreCAD.NET gives a classified reason whenever it cannot be used, namely module absent, licence denied, hardware unsuitable or start-up error.
Let's talk

Have a CAD problem worth solving?

Tell us what you're building. We'll give you a clear assessment of whether we're the right team, and how we'd approach it.

Start a project →See our work
sales@cadwaresoft.com
Features and figures may change. Eyeshot is a product of devDept Software. DevExpress is a trademark of Developer Express Inc. AMD Radeon ProRender is a trademark of Advanced Micro Devices, Inc. Claude is a product of Anthropic. All other trademarks belong to their respective owners.