[FIXED] v5 Migration Assistant errors +

[jrpmedia]

Getting constant error trying to Migrate settings from S3D v 4.1.2 to v 5

Also cannot open v4.1.2 .factory files with v5

- MacOS Ventura 13.1.x on MacBook Pro 16", M1 Pro, 32Gb.

[S3D-Jason]

The only few times we've seen this from customers so far, it was due to an error in the file they were importing that was most likely created when someone manually edited the old V4 XML files.

For example, here was a recent post:
viewtopic.php?t=16639

If a specific file isn't importing, try opening it in V4, save the process as a new profile, then go to File > Export FFF Profile to save that profile to your hard drive. Open the file in a text editor and check for mistakes in the XML. The most common thing I've seen is <temperatureController name="XXX"> or <extruder name="YYY"> tags where XXX or YYY don't match any other temperature controllers or extruders defined in the rest of the file. Seems like a copy and paste error that someone must have made when manually editing the XML from V4.

In the few cases I've seen, once you remove those extra sections with invalid names, the file can then be improved into V5.

[jrpmedia]

Thanks,

Where can I 'manually edit the old V4 XML files.' ?

macOS Monterey and Ventura.

[S3D-Jason]

Open the factory file in V4, click "Edit Process Settings", then click Save As New to save that current process as a new profile. Click OK to exit the process settings. Then go to File > Export FFF Profile and select the new profile name you just created. That will save the .fff file to your hard drive (which is just a regular XML file that you can open in a text editor).

[jrpmedia]

OK :-O

I have about 80+ profiles in Simplify 3D v4.1.2 !
Is there an easier way or direct access to the profile as an xml file? within the Simplify3d v4.1.2 application resources in macOS?
Or a way to mass-export fff files please?

I also attach one fff file example, can you advise that is wrong with that profile please, as I cannot import even a single fff file into v5 at the moment

Thank you.

[S3D-Jason]

Reposting what I wrote above:

The most common thing I've seen is <temperatureController name="XXX"> or <extruder name="YYY"> tags where XXX or YYY don't match any other temperature controllers or extruders defined in the rest of the file. Seems like a copy and paste error that someone must have made when manually editing the XML from V4.


For your file, if you search for "<extruder" in the XML, you will see only the "Left Extruder" is defined at the top. However, at the bottom there's all sorts of stuff referencing a non-existent "Right Extruder". I'm guessing this profile must have been edited by hand to create these problems, because we've never seen S3D V4 create these issues. Similar problems exist for the <temperatureController> tags. After fixing those issues the file imports fine for me.

[jrpmedia]

Thank you
Just to let you know...

I usually delete the Right Extruder within the Simplify3D application.

I have never hand-edit an XML file, and then reimported it.

[jrpmedia]

so, I have open up the XML fff file in a text editor and can find no errors as your suggest ...

[WimJanse]

I have the same problem, I exported printer profiles from 4.1.2 (for a non-supported printer, being Felix Pro 3 Touch).
I tried to import the exported profile (no hand editing done, just a clean export from 4.1.2 and import in 5) and I got the same error message.

I'm using a Mac-Studio with an M1 Max chipset

(attached: failling .fff file)


Edit: Problem solved with the assistance of S3D: nested autoquality items in automaterial statements. After removing the nested items, putting them one level higher in the xml-file the profile could be imported without any problem.

[brunobartos]

Hello,
I'm having the same problem reported in this topic and I'm running on Windows 10 Pro operating system.
I never manually edited any xml file and also deleted an extruder which I didn't use within the settings.
I have more tham hundreds of factory files and none of the ones I tested are opening, this makes the migration to the new version completely unfeasible, something needs to be done to automatically correct these errors and import the settings from previous versions without fail.
I am attaching different fff profile and factory files here for you to review.