GiD forum

It seems a problem related to the graphic card or driver Try starting without graphical acceleration with ./gidx instead ./gid In any case, except for special purposes like testing doesn't has much sense to run a Linux version in a virtual machine hosted in a Windows machine, can directly run the Gi...

A 'GiD problemtype' is simply a collection of files in a folder .gid that when is loaded customize GiD for a specific simulation. It is a kind of plugin that is loaded to modify the GiD behaviour and add new features, like allow write calculation files in the format expected by the simulation. see t...

I don't understand well the question
Each file input or output of code_bright or other program is different,
and I don't know its valid syntax.
Simply do a visual inspection as human of text files to guess if looks ok or looks truncated, with 'something strange', or some error message in output files

Yes, the code shown must not be used exactly with in tcl scripting, batchs
e.g.
some Escape of MEscape must be added,
unnecessary commands must be deleted, etc.
-tcl- mean that is a Tcl proc, not a 'GiD process' string
(in batch must use *****tcl )

Our Tohil package include our own version of Python, and is independent or other possible Python versions installed on the system In our package we set (or try to do it at least) the environment variables, etc. to ignore all external copies, just to avoid the related nightmare with other Python vers...

Thanks for the bug report.
This is a known bug of this version 16.1.6d calculating boundary meshes mixing some element types.
It is only a visualization issue.
We have been solved some time ago, but the version 16.1.7d is already not published.

A way to know the process commands used by GiD to do something (require GiD 16.1.6d developer or higher) is to go to the checkbox menu Utilities->Tools->Develop->Show process commands then do the actions you want as user and finally unset the checkbox a Window will show the commands processed, it is...

Sorry, but this question seems not related to GiD at all, but to the calculation of Anura.
Must ask this question to Anura developers,
or maybe some advanced user of this solver of this forum is able to provide an answer...

The problem is that you are defining different result names for each element type, and different 1-gauss points name definitions. Result "someVectors at Hexahedra Center" "root" 0 Vector OnGaussPoints "Hexahedra" Result "someVectors at Tetrahedra Center" "...

Sorry, the link with 'project.gid' is not available now for download.

You can attach zip files directly in this forum