@Zoltan3D As a very junior who rarely posts anywhere, I have to agree with Trippy on this one. you are unproductively offensive.
@jstadt I am sad to read your lines. Rarely have I read a more bland and nondescript text that says "I do not care about this topic" more than yours. What makes me sad is that, at least according to your description, you seem to be product manager for exactly what is lacking in Fusion for years now.
It is clear what this otherwise very serviceable software needs. It needs a, and I'm going to quote you partially on that, a "convenience of push button renders" that uses the already locally available hardware of the user. There is no wait, there is no cloud credits, there should just be an image popping out after a few seconds of my 4090 doing it's job.
@jstadt I'll assist you on your task as a product manager:
User Story: Speedy Local Rendering with GPU-Accelerated Path Tracing for Autodesk Fusion
Title:
Implement GPU-Accelerated Path Tracing for Rapid Local Rendering in Autodesk Fusion
As a
CAD designer using Autodesk Fusion,
I want to
leverage the local GPU to perform high-quality, path-traced rendering directly within the application environment,
So that
I can achieve near-real-time, photorealistic visualizations of my designs with enhanced lighting, material effects, and shadow accuracy, ultimately improving my design iteration speed and overall productivity.
Details:
Rendering Performance:
The rendering engine must utilize the computer’s GPU to accelerate path tracing, reducing computation times compared to CPU-bound methods. This ensures that even complex scenes render promptly, enabling a fluid design experience.
Quality & Accuracy:
The path tracing algorithm should accurately simulate global illumination, including light scattering, reflections, and refractions, without compromising the fidelity of materials defined in Autodesk Fusion. This precision is vital for designers to validate their concepts under realistic conditions.
User Interface Integration:
The solution must seamlessly integrate with the Autodesk Fusion interface, offering intuitive controls for switching between preview and final render modes, as well as adjustable quality settings (e.g., sample rate, resolution) that allow users to balance between speed and visual accuracy.
Local Processing & Security:
Rendering should be performed locally, ensuring that proprietary design data is processed on the user's machine. This approach minimizes data transfer concerns and enhances security by keeping sensitive design information within the local environment.
Resource Management:
The implementation should include dynamic GPU resource allocation, ensuring that the system can handle multiple simultaneous tasks without significant performance degradation. It should also provide fallback mechanisms or notifications if the GPU is insufficient for high-detail(extreme resolution) renderings.
Extensibility & Maintenance:
The solution should be modular, allowing for future updates or integration of additional rendering techniques, and designed with robust logging and error handling to assist in maintenance and troubleshooting.
Non-Goals:
No Dependency on Cloud Rendering: The feature does not require cloud rendering for its operation.
No Replacement of Cloud Rendering: The feature is not intended to fully replace cloud rendering for customers who currently rely on it for their workflows.
Acceptance Criteria:
Performance Benchmark:
Quality Metrics:
Demonstrates photorealistic output with accurate global illumination, soft shadows, and reflective properties.
Allows user adjustment of quality settings without significant loss of rendering speed.
Seamless Integration:
Fully integrated into the Autodesk Fusion interface with clear, user-friendly controls.
Offers smooth transitions between design editing and rendering views.
Data Security & Local Processing:
Robustness:
Notes:
The development team should collaborate closely with the product management and UI/UX teams to refine the user interaction elements, ensuring that the advanced rendering features do not complicate the overall user experience.
A phased rollout with initial beta testing among a group of experienced users could help in refining the performance benchmarks and quality settings prior to a full-scale launch.