Видео

hello @Robertkuepper4214, which issue are you facing with this video? We hear clearly the speaker from our side, could that be a setting issue from your side? Or is it about the speaker tone/wording/accent?

hello @yvescartier7884, thanks for your honest message. We understand this change can cause some frustration, that should not prevent our frustrated users to contact us and to communicate in a polite and professional manner. If you consider you are loosing efficiency and time , please report it to Altair so that we can support you in this transition and make sure you can not only recover your previous process time but also get some extra gain with time to deliver challenges

hello @andrewrutherford568, please feel free to submit a support request so that we can support you and understand why you are not able to reproduce the steps described in the video

hello @ananthansp, looping over results is not available (yet). With the Python automation we started to introduce with 2023, our plan is to make it available and to offer more flexibility. We still have some milestones before delivering such feature, so stay tuned :)

Hi there, you raise a good point. This appears to be an error, and should be in the X-axis.

Hi there, if you install S-FRAME on the same machine as Revit, the plugin should be installed automatically. If you have tried this, and still have issues, please reach out to our support team here: community.altair.com/csm?id=csm_get_help&sys_id=de45c412c312310015519f2974d3ae1b

Hi there, you can find the full playlist for this tutorial series here: ruclips.net/p/PLGNemB0NFb0D5Uc_9jAryhFQ5wiXd7miA&si=t0BhVgQdzgV8TvVo

Hello @Sunilarkt, thanks for honest and passionate feedback. You are speaking about muscle memory. That is probably one of the single reason that would force a software company (or any company) to keep the way of doing things because "this is the way we've doing it for many years". Point is, no product (either software or hardware) offers the same user experience than 10-15 years ago. Or such product get replaced because other companies propose disruptive (and generally) more efficient methods. We needed these changes for many reasons (consistency across products, most efficient development of cross utilities, competition, AI integration...) and we are always willing to expose to our users why we brought these disruptive changes and the benefit they can bring to our users. If you have some metrics showing you are not able yet to achieve similarly with the new UI the tasks you are performing on a daily basis, please reach us out through regular support channel or your local representative, so that we can support you and expose you the best strategies with our latest versions.

hello @stefanindahouse8458, thanks for reporting us this use case. Does that mean you do not use *CONTACT_AUTOMATIC_GENERAL, or *CONTACT_AUTOMATIC_GENERAL_INTERIOR and that you crete a 1D mesh along all your shell edges?

Hello @gustavoguimaraes7475, thanks for your honest feedback. We have communicated for many versions that panels were going to be removed. In few words, the learning slope for fresh users was complex (any HyperMesh trainer got the same feedbacks at the end of training) and the design of interface lead to unnecessary clicks/mouse travels. Users starting with the new UI can now learn HyperMesh basics more easily. That said, these changes are significant for our historical users and we are supporting them to transition. If you think a web meeting with our teams can help, please feel free to contact us through the support channel

hello @mustafatugberkcakr3364, the Field feature does not allow yet nodal thickness mapping. As a work-around, you can map elemental thickness then switch to nodal thickness: ruclips.net/video/DREssGFSPBU/видео.htmlsi=83mbSTh55uqPkBQN If you are interested by this feature, please create a support request so that we can track your demand properly. Also, if you have access to the orignal CAD, you can use the Map Thickness method directly, which proposes the different mapping method: ruclips.net/video/RRfn_GqUELk/видео.htmlsi=5KRYUWCUy6GzredW

hello @sanjaip.s8429, we have integrated from the first release of the new interface a search tool top right which allows to fill in any legacy command (such as equivalence, ...), and to get as output the equivalent command/location in the new interface. Also, the different tools you are mentioning are related to model validation, and are now available from a unique ribbon Validation. For instance, duplicate elements will now be under Model Checker. Hope that helps!

hello @Ferdy1979, the extension file and Notepad++ template should be released i the coming days. The VS Code extension is already available on the marketplace HyperWorksPyAPI - Visual Studio Marketplace: marketplace.visualstudio.com/items?itemName=AltairEngineering.hwapi-python

Hello @anon3181, we would need extra information in order to help you: which solver profile, which version? the best for such cases is to open a support request, or to post a thread on our forums

@@altairhowto version is 2023.1 and solver is Optistruct

@@altairhowto HyperMesh version is 2023.1 and OptiStruct is the solver

@@anon3181 we don't reproduce. Please submit a support request or ask in the forum so that we can investigate further. Feel freed to share a screen recording regarding your issue, that will help us to understand what goes wrong

hello @anon3181, we were not able to reproduce. For such case, as we suggested earlier, please report either a support request or send a post on Altair forum, if possible with a screen recording, so that we can investigate further

Yes interesting. And why is Inspire 2023 Used instead of 2024?

Hello @Vimvigour3327, some features are available in core, you can for instance define pressure with equations with no need to use such script. Convection cards are less usual and thus does not offer such core feature yet. If we get a significant number of requests for it, we can for sure evaluate for future versions the possibility to propose it as a core feature. That said, this RUclips channel is a repository for promoting not only core features, but also automation tips, whether with tcl or in the future with Python. Obviously we want to expose automation tips only for situations where core features are not available (yet).

Hello @muhammadaliabid5793, the intent of this video iss to explain that even if the panels are definitely gone with version 2023, all the functions that were in the panels have been moved to other locations, and the new interface also offers new capabilities/workflows.

Hello @rahulzambre8906, managing rigid as simple elements, especially if you have thousands of them, should not be discussion here, as it becomes a significant time consuming task. Why not using HyperMesh connectors, for such cases? They allow to deal with different type of 1D elements (absorb them as connectors, re-realize them after mesh update) and have been designed on purpose for such scenarii. So for sure you can do it "by hand", and then you have to review carefully your thousands of rigids every time you replace a part or remesh it. Or you use manage your rigids through connectors, which should prevent you to check such a number of rigids

@@altairhowto fe absorb is good option. but in some cases like in IP (instrument panel). fe absorb may not work ,because of complicated modeling of connections (clip connections, snap connections). in that case we have to equivalence the free rigids to the new mesh. and this practice i have used many times. many companies use the same method . when nothing works ,this method will work. that's why I am asking for this feature. thanks.

hello @@rahulzambre8906 , we know that connectors are not suited for certain use cases, but we also know that some of our users don't rely on connectors for use cases they have been designed for. That said, your cases are relevant, and we should re-introduce in the next version (2024.1) the highlight of free nodes in the Model Checker. By the way, equivalence is still available so you should still be able to use it on any kind of mesh.

hello @rahulzambre8906, detecting rigid element free node(s) is now part of the Model Checker. There is an automated fix proposed, which deletes the detected free nodes. Is it what you are looking for?

hello @vimvigour3327, for OptiStruct profile, you have access from 1D ribbon to Member mesh and Stiffener mesh, which allow to create 1D elements along 2Dor 3D elements, with the control of density. This reduces the risk of getting 1D elements not being connected to 2D mesh

hello @user-ri9ti4eh2u, please visit the learning section of altairone.com in order to get access to our training modules. If your request deals with Abaqus model set up, right now you can review the playlist in our channel dedicated to Abaqus model set up. We are working on a dedicated e-learning which should be available later this year.

@@altairhowto is it possible to contact an operator or to have private lessons ?