I have used ForceChildrensEval node but I believe that this is used only for running straight from the Workspace and on the second run. Sometimes the script works also if I connect the FilePath.DirectoryName straight to the Directory path but I have the same issues when running it from the player. Any idea what is causing this issue and what is the difference between running a script from the Workspace and player ?
For some strange reason the script work after pressing the Run button for the second time. I can share also the script itself it makes any difference. ( To get that 3D view I have another script in the Playlist that generates it )
for FilePath.FileName, the input for withExtension is bool not string, and it should be false in your case.
but i believe it is not the reason.
have you check if it is a permission issue ?
share it if you have no problem
Just so you know, I am trying to automate the model federation process process with a dynamo scrip. I am using it to generate a 3d View, set my view parameters, clean annotations, remove imported dwgs and at the end export the view to nwc format to federate it in Navisworks from where I can later export it to Revizto. Seems to work alright until the point of the Export which sometimes works and sometimes doesn’t. Any idea on what I am doing wrong ? I have added screenshots of the script and also the script if it help.
That might be because in the first run it is not finding the view. In the 2nd run because the view is created in first run and able to find it. Try changing the view node to string and get view by name or similar node.
Sorry little late to the party, don’t know if you had any success, it’s been a while but I had this same problem creating a data export and then utilizing the result. I had to split my script to get the data from Revit and a second script to ship the data out. we ended up just runing them sequentially in player. There is also a “pause” node (i think springs package). Might be worth a shot to see if you can stall the process as Revit creates or exports the view.
I had a similar issue exporting to navisworks and I was able to have success utilizing a transaction start/end node before the export node. I’m not sure how it causes it to work but it allows for player to actually export views.
Changed it afterwards but still not working.