What's the process for locally saving and displaying SVF files in Autodesk Viewer using Angular and .NET Core?

Frontend
1

Hey everyone, I’m working on a project that uses Autodesk’s Model Derivative API to convert design files to SVF format. The thing is, I want to save these files on my own server instead of using Autodesk’s cloud storage. Here’s my setup:

  • Frontend: Angular
  • Backend: .NET Core with Autodesk Forge SDK
  • Storage: Network File System (NFS)

I’m struggling with a few things:

  1. How do I grab the whole SVF package and save it to my NFS after the conversion is done?
  2. When my frontend needs to show a model, how should my backend send the SVF files from the NFS?
  3. How do I set up the Autodesk Viewer to use these local files instead of Autodesk’s cloud?

I tried downloading the translated output, but I only got a .sqlite file. I’m not sure what to do with it or how to get the full SVF structure. Any ideas on how to make this work with my .NET backend and Angular frontend?

Thanks for any help you can give!

2

yo lucaspixel, have u looked into the derivatives api’s download endpoint? it can grab the whole svf package for ya. for serving files, maybe set up a static file middleware in .net core. viewer config’s a bit tricky, but try tweaking the ‘path’ option to point to ur local files. goodluck mate!

3

hey lucas, thats an interesting challenge! have u considered using the Model Derivative API’s GET manifest endpoint? it might give u more info on the SVF structure. for the viewer, you could try setting up a custom resourceloader to fetch local files. what about using signalR for real-time updates between ur .NET backend and Angular frontend? just brainstorming here - curious to hear ur thoughts!

4

I’ve tackled a similar challenge in my work. The key is utilizing the Model Derivative API’s GET derivative manifest endpoint to retrieve the full SVF structure. For local storage, implement a custom file system provider in your .NET Core backend to manage SVF files on your NFS. When serving models, create dedicated API endpoints that stream SVF components from your storage to the frontend. Modify the Autodesk Viewer configuration to use these local endpoints instead of Autodesk’s cloud URLs. This approach ensures efficient local file management while maintaining compatibility with the Viewer.