You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TressFX provides sample implementations of TressFX 4.1 in DX12 and Vulkan. I am aiming to implement either 4.0 or 4.1 in an existing DX11 engine, however the TressFX 4.0 implementation, while technically DX11, is opaque due to the fact that it is implemented to interface with a closed-source engine for some reason (Sushi). While the documentation for 4.1 does not explicitly mention DX11, it also does not indicate that support for DX11 has been completely dropped. Would implementing TressFX 4.1 in DX11 be doable by porting DX12EngineInterfaceImpl.cpp to DX11, or is there a hard incompatibility between DX11 and TressFX 4.1?
Additionally, are there any existing code snippets or open-source projects that might help with getting started implementing TressFX 4.0 with raw DX11, rather than one that relies heavily on the closed-source Sushi DLLs?
Thanks!
The text was updated successfully, but these errors were encountered:
TressFX provides sample implementations of TressFX 4.1 in DX12 and Vulkan. I am aiming to implement either 4.0 or 4.1 in an existing DX11 engine, however the TressFX 4.0 implementation, while technically DX11, is opaque due to the fact that it is implemented to interface with a closed-source engine for some reason (Sushi). While the documentation for 4.1 does not explicitly mention DX11, it also does not indicate that support for DX11 has been completely dropped. Would implementing TressFX 4.1 in DX11 be doable by porting DX12EngineInterfaceImpl.cpp to DX11, or is there a hard incompatibility between DX11 and TressFX 4.1?
Additionally, are there any existing code snippets or open-source projects that might help with getting started implementing TressFX 4.0 with raw DX11, rather than one that relies heavily on the closed-source Sushi DLLs?
Thanks!
The text was updated successfully, but these errors were encountered: