EDIT
Trying it from the command line and I see the problem: a message is posted to stderr complaining that the file does not exist, probably because this is an smb path and it (f3d) is doing some weird thing trying to open the path itself instead of going through the default filesystem apis.
Copying the file to the local fs and then opening it with f3d works, so as far as I'm concerned, this is at the very least a bug in that f3d doesn't forward fatal errors to the UI and only posts them to stderr, which is hidden/swallowed by default when opening f3d via the desktop environment or by double-clicking on the .stl file (as no terminal is shown), if not to also mention a bug opening files from smb or network shares or more generally through the gvfs extensions.