[ghost82]

Hi!
I have problems with ensight 10.1.2b.
I cannot create rigid body motion: after opening the encas file,s electing the wall I want to rotate opening user defined tools-->rigid body motion a popup says "FAILED: input file suffix is not .case nor .encas!".
I remember I successfully created in the past with an older version of ensight the rbm with the same encas file; what's going on?

Thanks

[Marina G]

Hi,

When you are creating a Rigid Body Motion, make sure that in the "Existing Case file" field you select the input file, so the file that you have open at the moment, complete of the ".encas" ending.

If this doesn't explain the issue you are having, would it be possible for you to send us your dataset, so we can test what is happening and solve the issue?

Thank you.
Best Regards,

Marina Galvagni
CEI Software Support Engineer

[ghost82]

Hi Marina,
I cannot open the rigid body motion window, the error comes up before, as soon as I click on the "rigid body motion" icon, in user defined tools.
The dataset is quite big to upload for me, let's see if I can setup a small sample case with same error.

Thank you Marina, I will update this post.

[ghost82]

Ok, after investigating a bit I found what causes the error.
I created a small model and opened as usual at university: same error.
University has a hpc network license.
I installed the free version on my laptop and I was able to open and create the rigid body motion.
So all is ok with the free version, but not with the hpc.
Tell me if you need the license file, as I need to ask it to the network admin.

The error message comes up with a title "Requires: Case Gold".

If you need it I can upload the sample file if needed for test.

[Marina G]

Sounds like there are two possibilities here:
- the rigid body motion tool in your installation is buggy (maybe a wrong version, or something went wrong in the installation)
- something got stuck in the cache and is giving you this error message
We can address both these possibilities in the following way.

Go into your hpc machine, and delete the rbm.py file that you find in the installation directory $CEI_HOME/ensight101/site_preferences/extensions/user_defined/Tools/Visualize

Download the file here in attachment, change its name from rbm.txt to rbm.py, and place it in the same directory
$CEI_HOME/ensight101/site_preferences/extensions/user_defined/Tools/Visualize

This will take care of changing the rigid body motion tool to the newest version.
Now, open EnSight with the -no_prefs flag:
ensight101 -no_prefs
This will clean the cache. Close and re-open EnSight normally. Try to use the Rigid Body Motion tool.
Does it work correctly now?

Let me know.
Bests,

Marina

[ghost82]

Thanks Marina, but both solutions didn't work
I also uninstalled and reinstalled ensight (and deleted C:\users\myuser\.ensight101), but error is the same..

I'm repeating that it should be related only to the hpc version as also in that workstation all is fine with the free version.

[Marina G]

Can you please send me only the .encas file - the file that you are loading in EnSight? It could be that you have some characters in the file that are "forbidden" for EnSight, and that will give you problems only with some OS.

If you wish to send me the .encas file in private, send an email to support@ensight.com and we'll take this on a private email exchange.

Thanks,
Marina

[ghost82]

Sure, here the small test encas file.

Thank you

[Marina G]

Everything looks fine in the .encas file.
Can you please do a search for all the rbm.py and rbm.pyc files in the machine, delete all the ones you find, and re-install the rbm.py file that I've sent you? Just trying to make sure EnSight isn't picking up a bad version of the tool.

You said you have this problem only on the university machine, but not on the home machine. Can you give me OS and version of EnSight for both machines?

Thanks,
Marina

[ghost82]

Hi Marina,
What you suggested did not work.
I think it's not machine related because on the workstation at university I backup the license network, uninstalled and reinstalled all without license and rigid body motion worked well with ensight free.
Then I copied back the network license and started the hpc version with the -sos flag and the error was back again.
However, that workstation has win 7 sp1 64 bit.
Ensight is 10.1.2b.

Can you check if the rigid body motion works as expected with the hpc version?

Thanks for your help!

[Marina G]

You are correct,

The rigid body tool doesn't work with SOS (even if you use sos on only one server). I've submitted this as bug 4741 into our bug track system.
The only work-around for you is to use this tool without the -sos flag (you can still force EnSight to open in hpc configuration with the -gold flag, but you won't have distributed data with this option).
Apologies for the inconvenience this bug creates.

Best Regards,
Marina

[ghost82]

Thanks Marina,
no problems at all, important thing is that the cause of the error was identified!

Have a good day!

Daniele