Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Mario

  1. Hello flyforever, Try the following: Open in the menu Preferences->Options Go to Lighting Here you can change direction, specular color, flat/smooth or use multiple lights I hope I could help you. Best Regards, Mario
  2. Hello, I have another problem in V2020. In both Step 3 and Step 4 the function "Align to Curve" crashes the program. In step 3, when I take the node on the plane of symmetry. In step 4 already the first projection. Very frustrating. Best Regards, Mario
  3. Hello carcagiu, You can do it by Page Window Layout, see picture. Best Regards, Mario
  4. Hello, For me it works well with the Curves-> Intersect command. If the curves are not in one plane, I have to define the direction of projection using Visual Intersection. Best Regards, Mario
  5. Hello, The body is not a closed solid. You can check this using Analysis-> Tolerance Check (see picture). If you correct that, it works. Best Regards, Mario
  6. Hello, It's not working for me either. Try this: Select the two surfaces for the bridge Enter the edge mode, instead of face mode Right click, bridge... For me it will work now. But anyway, it seems to be a bug. Best Regards, Mario
  7. Hello, If your elastic modulus is 2e5, the error message is correct. Since for the first plastic slope 100/0.0005 = 2e5, exact same slope and this is not allowed. The strain in the table starts at plastification, means 0,0 is end of elastic range. Best Regards, Mario
  8. Hello, Most commands supporting the catch error handling. if { [ catch {command_name...} ] } { # Handle error } e.g. error handling if already a panel is open, it is not allowed in HW to stack panels: if { [catch {*createmarkpanel lines 1 "Select first line ..."}] } { set Info01Label "Warning: Can't Stack Panels" update return } Best Regards, Mario
  9. Hi, It is of course the ID of the load, not the ID of the load collector... I don't know a direct way to show this. Best Regards, Mario
  10. Hello, I only know the possibility to do it in the mass panel by the review function (except of course what Koushik said). 1D->masses switch to update press review and select CONM2 element See attached picture Best Regards, Mario
  11. Hello, You can do it via the nodes panel: press F8, or Geom->nodes, or Menu Mesh->Create->Nodes Don't forget to zoom to the model dimensions (press F or Ctrl+middle mouse button) See attached picture. Best Regards, Mario
  12. Hello, Wait for support from Altair Use another graphics card Switch to a desktop model (Max-Q is laptop) Ignore it Best Regards, Mario
  13. Hello FBa, You can edit the element RBE3->Update->dofs and switch "select to type" into "set individual". Now you can set the dofs and update the independent node. See picture. Best Regards, Mario
  14. Thank you very much for your answer. (... see update ...I understand that now, but I can't reproduce this. In all cases the selectbox "Constraint" always remains grey and cannot be changed. This also happens if I want to select Rails (like in your video).) Update: It works only, if I finishing the Profile selection by right click. Any other action (manualy switch to rail, close and reopen the Control Panel) will not work. It seems it switch to an "add vertices" mode. Best Regards, Mario
  15. Hello, You have to request the corner stresses (see pic. 1) and then you must switch on the "Use corner data" in Hyperview (see yellow marker). Best Regards, Mario
  16. Hello, EVOLVE had a great "Blend Surface" tool, I can't find it in Inspire Studio either. I can't understand your hint "use loft", can you please explain that? Best Regards, Mario
  17. Hello, You have to request the GLSTAT option in *DATABASE keyword. (*DATABASE_GLSTAT) This will includes the following: Normally it is included in the binout file, which you can read into Hypergraph. Best Regards, Mario
  18. Hello, You can use MATS1 in Optistruct. You can define stress train curves (in TABLE entity) or bilinear (slope). See Optistruct manual: MATS1 Bulk Data Entry Specifies stress-dependent and temperature-dependent material properties for use in applications involving nonlinear materials. This entry is used if a MAT1 entry is specified with the same MID in a nonlinear subcase. Comments For nonlinear elastic material, the stress-strain data given in the TABLES1 or TABLEG entry will be used to determine the stress for a given value of strain. The values H, YF, HR, and LIMIT1 will not be used in this case. Nonlinear elastic material is only available in EXPDYN subcases. For elastoplastic materials, the elastic stress-strain matrix is computed from a MAT1 entry, and the isotropic plasticity theory is used to perform the plastic analysis. In this case, either the table identification TID or the work hardening slope HH may be specified, but not both. If the TID is omitted, the work hardening slope HH must be specified, unless the material is perfectly plastic. The plasticity modulus ( HH ) is related to the tangential modulus ( ETET ) by: (1) H=ET1−ETEH=ET1−ETE Where, EE is the elastic modulus and ET=dY/dεET=dY/dε is the slope of the uniaxial stress-strain curve in the plastic region. Figure 1. If TID is given, TABLES1 or TABLEG entries (Xi,Yi) of stress-strain data ( εε x,Yx) must conform to the following rules: If TYPE=PLASTIC, the curve must be defined in the first quadrant. The data points must be in ascending order. If the table is defined in terms of total strain (TYPSTRN=0), the first point must be at the origin (X1=0, Y1=0) and the second point (X2, Y2) must be at the initial yield point (Y1) specified on the MATS1 entry. The slope of the line joining the origin to the yield stress must be equal to the value of E. If the table is defined in terms of plastic strain (TYPSTRN=1), the first point (X1, Y1), corresponding to yield point (Y1), must be at X1=0. TID may reference a TABLEST entry. In this case, the above rules apply to all TABLES1 tables pointed to by TABLEST. If TYPE=NLELAST, the full stress-strain curve may be defined in the first and third quadrants to accommodate different uniaxial compression data. If the curve is defined only in the first quadrant, then the curve must start at the origin (X1=0.0, Y1=0.0). For analysis where small deformations are assumed, there should be little or no difference between the true stress-strain curve and the engineering stress-strain curve, so either of them may be used in the TABLES1 definition. For analyses where small deformations are not assumed, the true stress-strain curve should be used. If the deformations go past the values defined in the table, the curve is extrapolated linearly. Best Regards, Mario
  19. Hi, try to switch in the property panel (right click HV icon) -> Compatibility -> DPI scaling to system. This helps for me in other applications, i can't try it in the moment for HV. Best Regards, Mario
  20. Hello Tommy, Ah, OK. The only known solution would be the Hotspot Finder from the MVP Toolbar. See attached picture (the text boxes are generated automatically by 1 click). But you have to get it from your local Altair service. Very useful tool. From Altair, but not supported. Best Regards, Mario
  21. Hello Tommy, Yes, you can do it. Instead of selecting all components, select only the requested elements. The measure tool Static MinMax Result will also work. See my attached picture. For same legend pin the max and min values (manual entries). Best Regards Mario
  22. Hello Imre, Wished since years, not possible until today. Best Regards, Mario
  23. Hello, see my comment above. Try to use AUTOSPC=YES. Best Regards, Mario
  24. Hello, Normally Hypermesh converts directional vectors into orientation nodes. This is not a problem. In Hyperview these then appear as "Orphan Nodes". You can just turn it off. Orphan Nodes have nothing to do with rigid modes. Normally these should be "auto-constraint" in any case. Icon "Entity Attributes"-> select "Orphan-Grids-> Display: Off Best Regards, Mario
  25. Hello, Normally, the connection should be mapped correctly with "shared" edges (green lines, mixed visualization) at geometry level. See first picture. If you are using the automesher, then all lines are shared and you will see only one density value / shared edge. If you are meshing the surfaces step by step they will be also connected. See picture 2. You can check the connection by: Tools->edges->Find edges and correct it by equivalence, if there are nodes not connected. See picture 3: Best Regards, Mario
  • Create New...