- #AMD CONTROL PANEL DUAL GRAPHICS UPDATE#
- #AMD CONTROL PANEL DUAL GRAPHICS ARCHIVE#
- #AMD CONTROL PANEL DUAL GRAPHICS WINDOWS#
Performance improvements: Upgraded graphics engines can provide better performance and efficiency.There are actually several good reasons for these updates:
#AMD CONTROL PANEL DUAL GRAPHICS UPDATE#
I can understand why they made these changes, as it's common for software companies to update their graphics engines from time to time. I noticed your comments about the updated graphics engine in Alibre. This complex structure example with shell plate bending inf. I don't have the money for the last version. That is an example of superb engineering.
#AMD CONTROL PANEL DUAL GRAPHICS ARCHIVE#
The company is NOT CONCENTRATE IN GRAPHIC VISUALIZATION is concentrate only in features and this features increasing the weight of the archive if them are UTILIZED.If not the archive is light. Here is a software that is 15 years old where I am doing the flooding study of one model for a customer builder (and the new version has the same render graphic) and cost 20 times than alibre and the presentation render is same to the ADV11 with little kb. The other "Effect" like ambient occlusion etc. If the software are most powerful must to have "at the same features" less kb.Ģ.-Regarding to the visualization I don't need more that I described above for my task. So between V14 and V23 the archive is increased in 160 kb useless for me. How you explain to me that the same model that I show above with the "same features": I hope that AD comes to its senses and does not dilute the great opportunity it has to position itself as a good Mechanical Software of the immediate and mediate future.Ĭlick to expand.Thanks very much Serenity for your answer.ġ.-Regarding to you comment. It is a question of strategy in the face of an increasingly fierce competition between CAD programs.
If we compare the weight of a file of a model of the same complexity made in Alibre D V11 and a recent version, we have that the file of the ADV11 version is much lighter. It is an engineering program where perfection is the important thing. I think that alibre's turn in this direction interrupted a beautiful tradition and potentiality. Only hoops should have improved this chart by making it more robust and acquiring the dynamic section features for inspection. The historical graph was superb, for its line fineness in Sketch mode and the visualization in part Workspace and assembly workspace mode. My opinion is that, the graphic issue is a very big mistake of Alibre Design. Is this a thing that happens on someone else's laptop too? Is this a known issue? Can anyone guess what's going on? However, this behaviour does not happen on any other software on my system so it would seem there is a way around it.
#AMD CONTROL PANEL DUAL GRAPHICS WINDOWS#
I am guessing this is a complex issue that has to do with my system's firmware, Windows and Alibre itself.
I did that and it had the same behaviour as when I did it through the Windows Graphics Performance preferences. On that other thread, Ralf suggested I handle the assignment through the NVidia control panel. However, the performance is great and the task manager reports the NVidia GPU being used. If I let Windows select, the system options in Alibre are set as per the attached image (AMD APU selected). When I go to the Windows Graphics Performance preference settings and set Alibre to start with the NVidia GPU the performance degrades significantly, almost a slideshow on larger models, and the task manager reports that the AMD APU is being used. My system has a Ryzen 7 5800h with an APU (AMD Radeon Graphics) and a mobile RTX3060. Performance was terrible and in the system options, it showed the discrete GPU being used. The problem started when I upgraded from v24 to v25. To my knowledge, this does not impact the performance of the software, in the sense that you can set it so it performs well, but it could create confusion for some users as it did for me. I have mentioned this on another thread but the issue was not resolved.
0 kommentar(er)
