[OpenFOAM] UI error when loading files .stl and .foam

Max-N · March 2, 2020, 06:48

When trying to open files .stl or .foam, the ui completely breaks down without any error messages :

correct_ui.jpg

broken_ui.jpg

I just started using paraview recently so I am completely clueless on what to do and I didn't manage to find any related topic that might help.

I was thinking paraview might have a problem with the size of my screen or my resolution, but I couldn't confirm it.

Thank you for any help.

thomaslschmidt · March 21, 2020, 08:07

I have encountered exactly the same problem, which makes ParaView unusable. Is there a solution?

Max-N · March 27, 2020, 05:52

After trying out various things to solve the issue, I actually found that the problem didn't occur with some older versions of Paraview.

So I am now working using the 5.6.2 version of Paraview and everything seems to be fine.

March 2, 2020, 06:48	UI error when loading files .stl and .foam	#1
Max-N New Member Join Date: Mar 2020 Posts: 2 Rep Power: 0	When trying to open files .stl or .foam, the ui completely breaks down without any error messages : correct_ui.jpg broken_ui.jpg I just started using paraview recently so I am completely clueless on what to do and I didn't manage to find any related topic that might help. I was thinking paraview might have a problem with the size of my screen or my resolution, but I couldn't confirm it. Thank you for any help.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[OpenFOAM] Paraview: .foam and .OpenFOAM files support	redbullah	ParaView	2	September 4, 2019 06:49

March 21, 2020, 08:07		#2
thomaslschmidt New Member Thomas Schmidt Join Date: Jan 2020 Posts: 1 Rep Power: 0	I have encountered exactly the same problem, which makes ParaView unusable. Is there a solution?

March 27, 2020, 05:52		#3
Max-N New Member Join Date: Mar 2020 Posts: 2 Rep Power: 0	After trying out various things to solve the issue, I actually found that the problem didn't occur with some older versions of Paraview. So I am now working using the 5.6.2 version of Paraview and everything seems to be fine.