|
I don't think a bounty necessarily fixes anything. Warp3D is proprietary software, protected by NDAs. I signed one years, I guess decades ago, to work on it.
Perhaps an option today is to see what can be done to add specific chipset support to Wazp3D.
I've often thought a less indirect solution might be better for old systems. Not many people have more than one RTG card and certainly not more than one supporting any 3D output. Warp3D was built with good intentions, separating the RTG side and 3D sub driver side. I wonder if today, where there are just two RTG standards, you could just use CGX functions, eliminating the need to have the RTG component libraries. Properly template out the code for drivers and have a single file driver solution where the installer just makes sure you put the right one in. Such a driver could be a little more efficient on older systems by cutting down the indirection needed.
|