@Basem another usefull feature that could be implemented in the program, is the possibility of changing units. Some preprocessors works with visible engineering units, but behaind curtains they use a fixed unit set for the input and frd results (for example meters and Pa), and then could be interesting for the user open those results and transform/change the visualization of results to mm and MPa or inches and psi
1 Like
Thanks Sergio, that was exactly the check I needed. Mecway reports the maximum along the path, ccxview showed both ends. In all nine cases the Mecway value is one of the two ends. Two changes are now in: a third column “max on line”, and the ASME 5-A.4.1.2 rule that bending is taken only from the components normal to the line ( Mecway “Exclude sxx, sxy, szx from bending” box, which was off in your screenshots). It is on by default in ccxview since that is what the code asks for; a checkbox turns it off to compare with Mecway’s default.
2 Likes
many thanks for light theme and added new colormaps. Maybe gizmo best placed at left similar with CGX and option to hide as available for legend. Another curious me is in CCXview work with Fbd files, can it give some brief in using this feature and currently limitation compared with CGX.
There is some example of stress linearization here: FreeCAD FEM results in Fatlab – fatigue.pro
But it uses the tool available in FreeCAD which may provide unexpected results.
Hi Basem,
Amazing work. Thank you very much
Is it mandatory to pass the results in global coordinates. What happens if ccx results where requested with GLOBAL=NO?
1 Like
Hi Disla,
Thanks! I’m glad you like it.
Oh, that’s something I did not consider; GLOBAL=NO would not work correctly for now.
I’ll be working on this soon.
Good that you asked this!
1 Like
@Basem Could you consider supporting contact element display (some transparency setting would be needed for that too) ? GraphiX is not so good at this: How to properly visualize contact elements in GraphiX?
CalculiX stores them in jobname.cel files.
And it would be awesome to display tie constraints like in Abaqus (to check where the constraints are actually applied in the analysis):
CalculiX generates the jobname_WarnNodeMissMasterIntersect.nam files for disconnected nodes and supporting that could even suffice for now, but inverting it to show connected nodes would be even better.
1 Like
Yes, this should be doable.
Can you post this on GitHub as an issue:
I think it is better that we get the bugs and features in one place.
Also, it would be nice if you share a sample model with these files so I can test it.
Sure, I will. Thanks.
Right, GitHub issues are the best way to organize bug reports and feature requests. The ones for CalculiX used to get lost on the forum until the official repo was shared.
Sure, I will include a simple example for both cases.
2 Likes
Actual version 0.1.14 with some closed issues.
See releases at Releases · BasemRajjoub/ccxview · GitHub
ccxview 0.1.10 now shows contact elements, ties with master/slave surfaces and the untied slave nodes from the nam warning file (or only the tied ones), and a see-through model.
Could you try it on a real model?
If you find bugs or anything odd, please open an issue on GitHub: Issues · BasemRajjoub/ccxview · GitHub
5 Likes
when displaying normal modes calculated with *FREQUENCY the scale sometimes has to be a very small number, and that’s not possible in the interface (see picture, example test problem achtel2.inp modified from static to frequency analysis) so it’s very difficult to see the mode shape at an appropriate scale.
Congratulations for the application 
3 Likes
yes, it will be improved in the next release; thanks for mentioning this and I’m glad you like the software.
If you have any suggestions, feature requests or bugs found, please let me know.
You can also use github issues for easier communication.
3 Likes
It would be cool if you could join our Discord server too: PrePoMax & CalculiX
We can add a channel for ccxview.
2 Likes