Ab3d.PowerToys is the ultimate helper library to create .Net applications with 3D content.
The main features of the library are:
- The easiest to use 3D API with many great code samples
- Cameras (SceneCamera, FirstPersonCamera, ThirdPersonCamera, etc.)
- Camera Controllers (MouseCameraController, CameraControlPanel)
- 3D Models and Visuals (Sphere, Box, Cylinder, etc.)
- Generate extruded or lathe 3D objects
- 3D Lines (the fastest implementation for connected, disconnected and lines with arrows)
- 3D Text
- Event Manager 3D (simplified event handling on 3D objects)
- Complete solution for WPF 3D transparency problem
- Many helper classes to ease work with WPF 3D
- Support for touch and multi-touch to rotate, move and zoom the camera
- Import 3D models from obj files (integrated in Ab3d.PowerToys) or almost all other 3D files with Assimp importer.
- Export 3D models to Collada (.dae), obj, ply and stl files (using Assimp exporter).
- fully optimized to achive best possible performance
The Ab3d.PowerToys also works very well with Ab3d.DXEngine the DirectX 11 rendering engine for .Net and WPF applications.
With purchasing the Ab3d.PowerToys library you also get premium e-mail support for all questions regarding WPF 3D and our libraries.
Cameras, 3D Models, Lines and Text can be defined in XAML. The
results are immediately shown in Visual Studio Designer so the
whole 3D scene can be designed in Visual Studio almost as in a 3D modeling application.
Showing 3D content was never easier!
Cameras and Camera Controllers
The library defines a few new Cameras that can be used instead of the current WPF's
cameras. The main difference between Ab3d Cameras and WPF cameras is that Ab3d Cameras
does not use Vectors to define the LookDirection, but instead use angles in degrees
to define it. This is much more natural. For example if you want to look at the
scene a little bit from the right and from above, you just define the Heading to
be 30 and Attitude to be -45. You can also define the Distance from the scene. The
most important Ab3d Cameras are: SceneCamera, FirstPersonCamera and ThirdPersonCamera.
A good overview of the new cameras can be seen in the Cameras cheat sheet
document that can be opened from a link below.
Camera Controllers are used to control the camera. The MouseCameraController
can be used to rotate and move the camera with the mouse. The rotation and movement
can be configured to any combination of mouse buttons and keyboard modifiers (shift,
control and alt). For example the following XAML sets the MouseCameraController
to rotate the camera with left mouse button and to move the camera with left mouse
button and alt key pressed:
The CameraControlPanel shows nice buttons to rotate and move the
camera and also move the camera closer or farther away. There are also a CameraPreviewPanel
and CameraAxisPanel that graphically show the current orientation
of the camera.
The Ab3d.PowerToys library also contains classes to create basic 3D models in code
or XAML. It is possible to create Plane, Circle, Box, Arrow, Pyramid, Sphere, Cone
and Cylinder 3D models. The library also supports creating objects by extruding a shape or by converting a shape to 3D object with lathe algorithm.
To make the 3D objects definitions cleaner a ModelTypeConverter is used for all
Material properties used by 3D objects. This way it is possible to set the material
with a color name or code (#FFFFAAAA) or image uri.
The library support 3D Lines with optimized update mechanism
that makes the 3D lines implementation the most advanced and with the best performance
The library also supports 3D Text that can be defined anywhere
in 3D space. The text is drawn as a series of connected 3D lines that are created
from internal font definition.
The EventManager3D class is a helper class that enables user to
simply subscribe to mouse events on 3D objects. The following mouse events are supported:
MouseEnter, MouseLeave, MouseMove, MouseDown, MouseUp, MouseClick, BeginMouseDrag, MouseDrag,
EndMouseDrag and MouseDoubleClick. This way you do not need to do the
complicated 3D hit testing any more. The EventManager3D is also better than WPF's
ModelUIElement3D because it supports more mouse events (including mouse drag in
3D), provides better event data and preserves the structure of the 3D models. This
way your code is much simpler and better organized.
WPF 3D can show transparent 3D objects. But to show them correctly, the transparent
objects need to be correctly sorted. Without this some of the objects are not visible
through the transparent objects. Ab3d.PowerToys provide complete solution to this
problem. More about that can be read in Transparency Sorting page.
Obj files reader
Ab3d.PowerToys includes a Ab3d.ReaderObj class that can be used to read 3D models from obj files.
Obj file is very common file format to store 3D models.
It usually comes with mtl file that defines the materials used in obj file.
Because data in obj and mtl files is written in plain text, parsing the values can be quite slow and can consume a lot of memory (creating many string instances).
Therefore the ReaderObj has been greatly optimized to read obj files very fast and with very low memory usage.
To get some additional information about using Ab3d.PowerToys and see how easy is to create great business applications with 3D graphics see the following blog post.
Ab3d.PowerToys cheat sheets:
(click to get full pdf)
|Many basic 3D Objects
Screenshots with XAML source:
(click to see full XAML for the image)
(click to see larger image)
Related blog post
To see the development history of Ab3d.PowerToys, check out the related blog posts.
Information about changes: