If you are starting a new project, it is recommended to use Ab4d.SharpEngine. It is built from the ground up, has a cleaner API and uses a more modern .Net and graphics features (Net 6+ with hardware intrinsic and Vulkan instead of DirectX 11). Also, if you will need to port your application to another platform in the future, this will be much easier when using Ab4d.SharpEngine.
But, as it is written in the GitHub for Ab4d.SharpEngine samples (
https://github.com/ab4d/Ab4d.SharpEngine...dpowertoys), the Ab4d.SharpEngine still lacks some of the features of the Ab3d.PowerToys and Ab3d.DXEngine. Anyway, as the sample projects show, the new engine already has most of the features from the older engines, and this should be enough for most of the applications that require 3D graphics.
In the future, features from the older engine will be ported to Ab4d.SharpEngine. For example, in Q1 2024 a new Ab4d.SharpEngine v1.1 will be released, which will support pixel rendering.
So, please check the Ab4d.SharpEngine samples and see if the new engine has the features that you require for your application. If you find some missing features that you would require, please write them here and I will check if they already exist (but are not demonstrated by the samples yet), or I may try to implement them for the next version (I can send you a pre-release version with new features before the official release).
