Is there any ways I can import the study setup from communicator files (.mfr) into my own synergy?
That way, i do not need to spend extra time to set up the same study.
Solved! Go to Solution.
Is there any ways I can import the study setup from communicator files (.mfr) into my own synergy?
That way, i do not need to spend extra time to set up the same study.
Solved! Go to Solution.
Solved by PascalGosset. Go to Solution.
Solved by bernor_mf. Go to Solution.
Hi,
from what I know this is not possible to import .mfr file to Synergy.
It contains the study file .sdy, and resultfiles .o* , and aimed for Moldflow Communicator only.
When opening the .mfr in Moldflow Communicator, the mfr-file is unpacked to a temporary storage, such as:
C:\Users\user_id\AppData\Local\Temp\AMCx,
where x is a number.
In that folder the study file .sdy, and resultfiles .o* are temporarily stored, when viewing results.
I have even tried to import that .sdy to Synergy, but it crashed.
So, the Moldflow Communicator viewer files are locked for import to Synergy.
Even if your own files, they are locked.
This hard coded security probably has their reasons.
Regards,
Berndt
Hi,
from what I know this is not possible to import .mfr file to Synergy.
It contains the study file .sdy, and resultfiles .o* , and aimed for Moldflow Communicator only.
When opening the .mfr in Moldflow Communicator, the mfr-file is unpacked to a temporary storage, such as:
C:\Users\user_id\AppData\Local\Temp\AMCx,
where x is a number.
In that folder the study file .sdy, and resultfiles .o* are temporarily stored, when viewing results.
I have even tried to import that .sdy to Synergy, but it crashed.
So, the Moldflow Communicator viewer files are locked for import to Synergy.
Even if your own files, they are locked.
This hard coded security probably has their reasons.
Regards,
Berndt
Hi simulators,
I agree with Berndt, it's not possible to import a MFR file in Synergy.
This could be also useful to import a mesh made by another person.
I wonder if I won't add a post in Ideas for that...
(no... I'm joking 😉 )
Signature: "Maybe Moldflow does not work properly, but the real world neither" my son...6 years old 😉
Hi simulators,
I agree with Berndt, it's not possible to import a MFR file in Synergy.
This could be also useful to import a mesh made by another person.
I wonder if I won't add a post in Ideas for that...
(no... I'm joking 😉 )
Signature: "Maybe Moldflow does not work properly, but the real world neither" my son...6 years old 😉
Hi Pascal,
I would second that idea and kudos it. 😊
In the world of collaboration today, I find it a bit old-fashion to not having some options here.
Of course protecting data and proprietary information is important.
If having Moldflow Insight this should be possible.
Think of an option to lock or not lock the mfr for import to Synergy could be controlled when exporting from Communicator.
Either a tickbox, and a tickbox and a security code.
Basically as when sending a zip-file, locked by password or not locked.
Regards,
Berndt
Hi Pascal,
I would second that idea and kudos it. 😊
In the world of collaboration today, I find it a bit old-fashion to not having some options here.
Of course protecting data and proprietary information is important.
If having Moldflow Insight this should be possible.
Think of an option to lock or not lock the mfr for import to Synergy could be controlled when exporting from Communicator.
Either a tickbox, and a tickbox and a security code.
Basically as when sending a zip-file, locked by password or not locked.
Regards,
Berndt
hello guys,
to go deeper on that idea, the use of shared views can be higly improved to have a use of shared datas (animation, results, ...) instead of using a software that need to be installed with the risk of version compatibilty, graphic issues,...
As you said Berndt, i would also vote for that 🙂
hello guys,
to go deeper on that idea, the use of shared views can be higly improved to have a use of shared datas (animation, results, ...) instead of using a software that need to be installed with the risk of version compatibilty, graphic issues,...
As you said Berndt, i would also vote for that 🙂
Thank you everyone for sharing your experience/thoughts!
Hopefully we can have an option to make communicator files compatible with Synergy in the future update...
Thank you everyone for sharing your experience/thoughts!
Hopefully we can have an option to make communicator files compatible with Synergy in the future update...
Can't find what you're looking for? Ask the community or share your knowledge.