[FIXED] Factory File name missing from UI

[ambrosia3d]

Hi, I would like to report that in Simplify3D, the Factory File Name is completely missing form the UI.
I go back and forth a lot between different factory files, and I find this issue really annoying not knowing which file you are working on.

Not only this, when doing a Ctrl+S to save and update the factory file you are working on, the program instead proposes to save the file under a different name!
This is not good, as it can lead to mistakes saving over a different file and loosing all your previous work.

I have S3D installed on both my MAC and Windows and they both act this way.
Does anyone else notice this issue?

[DarthRevan]

I think I've seen something similar in the past. Any time I report something to the support team through S3D's contact page they always ask for what exact steps they can take to replicate the issue. I'd assume this situation has a lot of variables, so it'd be great if you gave an exact sequence required to make this ctrl + s behavior incorrect.

[ambrosia3d]

Thanks for replying.
Anyone can replicate this experiment, please try this simple sequence and tell me if you get the same results, I included 4 pictures to help explain:

1-Choose a factory file (slice-1.factory in this example)
2-Open the file, you will notice that the file name is missing from the UI
3-Move your model
4-Press Ctrl+S or Cmd+S for Mac, and a "Save-as" window opens up with the wrong file name inserted (test-rectangle-holes.factory instead)

[DarthRevan]

I think there may be other steps needed, as mine prompted me with the name of the model being saved. Not the name of some other factory file. (This is the default behavior I've observed in the past for saving factory files when it doesn't have the name loaded already)

[dkightley]

I've tried your test sequence and at step 2 the file name IS displayed correctly. Windows10 & S3Dv4.0.1

[S3D-Chris]

I’m happy to announce that this issue the factory file name missing from the UI's top menu bar was resolved in the 4.0.1 release. Our team successfully tested several factory files and this issue remains fixed in version 4.1.0. This was just one of many improvements to the software. All of which are detailed on our Release Notes page.

Thank you for your help reporting this issue!