• NVIDIA crash fix on latest drivers (~December 2023)
• DXR Inline Raytracing
• AMD FSR 2.2 integration & quality modes
• Increased 200 FPS hard lock in player config to 999 FPS
• Tangents for texture overlays fix (community)
• Level geometry sometimes wrongly rotated fix (community)
• Texture compression with DDS files (adapt community implementation)
• Test DDS texture compression (especially super transparency, emissive, overlays)
• Overhaul options menu to be clearer to use
• Change back buffer count from 3 to 2 to reduce input lag a little bit
• Test AMD FSR with low FPS for ghosting
• Add output & render resolution to render debug menu
• Add FPS and frame time to render debug menu
• Check all materials for proper FSR2 reactive mask flags
• Test debug, release, and ship builds (both with DispatchRays and Inline)
• Prepare post (mention that without upscaling TAA is the better option)
• Add guidelines for pull requests (reference images, testing, etc.)
• Release 1.1.0
• Post post on Discord, but probably also Reddit and YouTube since the NVIDIA issue is very consistent on all cards with latest drivers

The cave in the cutscene after the end of the first level, from which you fly out, does not look right

The program crashes with DEVICE LOST (GPU device hung) inside the indirect_lighting.hlsl shader. For some reason the tracing of rays inside that shader broke, which is very odd because the shader table for the previous two shaders were valid. Will investigate further and hopefully find a fix.

I have no sound/music and got artefacts too with the "improved" Descent Version.
Some years ago, I was able to get the Mac Version (.hog and .pig files) because the "crosshair" and the cockpit looks way better as on DOS (320x200).
The normal "shareware" stuff runs well so I think your DXX-Raytracer might not be "compatible" with the MAC files?
Maybe you can fix that.

Please ... The game crash after to enable Pathtracing.

My GPU : RTX 3060 (DX12 Ultimate, Windows 11).

Note : only PBR enabled the game works and it show reflections.

Dump file ( https://file.io/Nqr2aXqVts1I ) after to click "Enable Pathtracing" :

Already works, just pushed a commit on branch dxr-inline-raytracing.
TODO:

• Integrate AMD FSR 2.2 into the DX12 render backend
• Transition render targets to the correct states
• Have upscaling and anti-aliasing options in both the raytracing and debug menus. TAA and FSR 2.2 exclude each other
• Separate render and output resolutions, match the upscaling factors with the recommended factors from AMD
• Add sharpen to the FSR dispatch (skipped, we have our own)
• Add recommended mipmap bias
• Add the correct frame time to the FSR dispatch
• Generate reactive mask Fill reactive mask for texture animations, and add a reactive mask scale
• Set FSR reactive mask flag for all texture animation materials

We are already using DispatchRays as if it was DXR's Inline Raytracing, so we might as well switch to it, we just never had the time to rewrite our shaders for this. I think its worth doing now especially if I can't find a solution for the indirect lighting crash.

Just writing these down here for reference:

• Saving/loading of light settings for global lights and weapon lights.
• Fix behaviour in the material editor when trying to save a material with its parameters set to default.
• Add ability to change texture paths in material editor.
• Add options for configuring headlights.
• Add menu option for bilinear filtering.
• Fix NaNs that can show up in shading.
• Fix quick save loading
• End level cutscenes are not lit properly
• Spaceship in end-level cutscene is not visible
• Weapons seem to shoot at changing intervals
• Seems to be a later fix of a source port, the OGL version from DXX-Retro does the same
• UAV barriers for ping-pong render targets do not work correctly
• Empty energy bar visible through UI elements

Black squares covering the amount of energy are visible in the menu/options/F2

We no longer actively work on this, so the best chance you will have at reporting and resolving bugs is to head over to our discord server and post a message with details in the support channel.

From what I understand Descent 2 is very similar for the engine? Might that be a possibility here or is it too different to work? Is that something you might think about also supporting? It boils down to one question though.