We are running FME Server 2016 on Windows Server 2008 SP2 and have found that the RealDWG writer is not supported by this. We use this for outputting data to CAD due to the basic ACAD writer having issues with block attributes. I am investigating this but if anyone knows of a workaround that would be helpful. Thanks.
Question
RealDWG not supported in 2016 - workarounds?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+59- Safer
Hi @chrisw84
I notice that article says "Windows Server 2008 and earlier" - and the information I have seen suggests it should work on 2012 or later.
However, if it's a 64-bit operating system, you would probably need to use FME 64-bit. Apparently RealDWG is insistent on that. (See point #6 in this list).
You don't mention which FME type you are using. If it's 32-bit, then that could be a reason for any problems.
Hope this helps. If not, as Itay says, contacting the support team is a good way forward.
Mark
+21- Safer
I'm curious what the RealDWG writer can do with block attributes, that the ACAD writer cannot.
+15- Contributor
i create a template containing all the blocks,
Using fme to create them from the symboldefining dwg's.
The only problem btw with blockwriting wich the acad writer has is rotation (afaik).
It refuses to use offered angles.
+21- Safer
@gio The behavior of ACAD and REALDWG are expected to be the same. ACAD should provide an alternative to REALDWG when REALDWG is not available, such as on non-Windows platforms.
If there is an issue with ACAD that does not exist in REALDWG, please contact support@safe.com with a workspace and sample data to reproduce the issue, so that ACAD may be fixed. Thanks.
+21- Enthusiast
Hi @chrisw84
I notice that article says "Windows Server 2008 and earlier" - and the information I have seen suggests it should work on 2012 or later.
However, if it's a 64-bit operating system, you would probably need to use FME 64-bit. Apparently RealDWG is insistent on that. (See point #6 in this list).
You don't mention which FME type you are using. If it's 32-bit, then that could be a reason for any problems.
Hope this helps. If not, as Itay says, contacting the support team is a good way forward.
Mark
It seems the issue has temporarily gone away so it may be ok, but from my reading of that article I might expect it to pop up again.
+21- Enthusiast
Contacting Safe for support is always a good option.
+21- Enthusiast
@gio The behavior of ACAD and REALDWG are expected to be the same. ACAD should provide an alternative to REALDWG when REALDWG is not available, such as on non-Windows platforms.
If there is an issue with ACAD that does not exist in REALDWG, please contact support@safe.com with a workspace and sample data to reproduce the issue, so that ACAD may be fixed. Thanks.