Could it be a bug within the model derivative API? Or is it a setting that is beyond my knowledge?.Could it a bug within Autodesk's viewer app? I'm not too sure what the best Autodesk forum to post in would be.So my knowledge of Javascript and the Forge API is quite rudimental but I'm guessing the problem is with Autodesk Viewer's implementation of the model derivative API for when the model is translated to svf. Strangely, in the 2d sheet views all the equipment and infrastructure is there fine, just in 3D it is now. Even if I upload the services model on it's own. In the viewer though it's a different story. In the '3D' 3D view I have created everything is phased correctly, no issues from worksets, visibility graphics, view discipline is coordination (doesnt work to change to mechanical) and everything looks hunky dory in Revit. Most notably it's missing ducts, sanitary pipework, cable trays, radiators. However, I am only getting some elements from the services model come through into the Autodesk Viewer application. Could this also have been better solved by setting generateMasterViews to true during the POST job on a custom Forge viewer app?.I managed to get around this by creating a 3D view in each model just called '3D' and setting the phase and filter as I like. Initially I uploaded our services model with supporting architectural and structural models but the phase the solitary 3D view created in the viewer was 'Existing' with a filter of 'Show All'. Unfortunately though, I have encountered a couple of problems, one of which I think I have solved and one which I am guessing is more to do with the Autodesk Viewer Applications programmed interaction with the model derivative API. I've been trying to encourage some of our less Revit-savvy building services engineers to utilise the Autodesk Viewer product.

Autodesk viewer mac