Simplify3D User Forum

Dear all,

Usually I use a certain folder where I import my STL files from and another folder where I save my gcode files to.
Currently (S3D V3.1) if I save a gcode file in lets say C:\gcodes and then I import a new STL file S3D shows the C:\gcodes folder again.
But the C.\gcode folder is not where I import my STL files from! I want to import from C:\stl.

So what I wish to have is that S3D remembers the folders separately.
On importing files S3D should always open the import folder (the last one I used for importing, here C:\stl).
On saving gcode files S3D should always open the 'save' folder (the last one I used for saving, here C:\gcode).

Thanks...

I think this is already in the software. If I click Import to load a model and browse to C:\Models and import a part from there, and then save my toolpaths to C:\Toolpaths, it remembers both of those paths correctly. Any time I go to import a model in the future, it automatically starts at C:\Models and anytime I export toolpaths, it starts at C:\Toolpaths

So I would say the current version already does this correctly

Hi CompundCarl,

I forgot to mention that I use the (latest) Mac version - May it is a Mac (only) problem?

Hi,

I double checked now.
I saved a gcode file in my filder UM2/gcode.
Then I wanted to import a new model but S3D presented the UM2/gcode folder again and not the folder I used last time for importing STL files.

May some Mac user can check this as well?

Thanks...

The mac version has the same, quite annoying problem.

They should fix it at once.

I have 2 different macs here that are both running different version of OS X and both of them work correctly. So perhaps it only affects one specific OS X version.. either way, that probably means that apple changed something that's causing the problem, because I can definitely confirm that it works perfectly fine for my Macs and I'm running the same version of the program you are

Hi,

today I tested again and I still have this problem on my Mac!

My Mac El Capitan is version 10.11.5 (15F34)

Have the same inconvenience on my Mac

What version of OS X are you using? It works fine on several of my macs, so it must be only a specific version of OS X that has this problem