Alias running on M1 Pro! - Just a few problems

[malte.wohlfahrt]

Hey there, 

I’ve been desperately looking for an answer for the ever lasting question of “can I still BUY a Mac after the introduction of Apple’s M1 and STILL use Alias”.

Last week, I finally got my hands on my friend’s 2021 MacBook Pro (M1 Pro).

Within 15-20 min I had installed Parallels (Virtual Machine) which automatically installed Win 11 ARM as well.

Windows worked very well and therefore, the installation of Alias wasn’t a problem either.
I launched Alias and everything was how it’s supposed to be. I then opened a file and could perfectly use the view keys and tools, as well as the different shading modes. I also projected a few curves on the surfaces and built a few SUBDs  cubes. 
Everything was working fine and I was minutes away from buying a MacBook on the Apple website…

Problem 1)

Until I tried using the “marking menu” of the left mouse button because the menu simply wouldn’t open.

Instead, it seamed as the selection rectangle was activated by this key combination.

I connected another mouse and another keyboard to see if those were the source of the problem - but no luck with that either.

Every other marking menu worked fine except from the most important one for me. 

Problem 2)

I thought I’d might be able to find a workaround for this first problem by changing the shortcuts for the marking menus and thereby still be able to get to use the M1 Pro’s power, but that was only until I discovered the second problem:

I wanted to save the project but when I clicked on “Save”, “Save as”, “rapid prototype” or any other kind of saving/export option nothing happened. The icon on the upper left corner flashed real quick every time I clicked on one of the mentioned above options.

Also, importing a User Preference Set wasn’t working either.

Then, I updated 2022.1 to 2022.2 and also tried the 2021 version of Alias but ended up with the same problem.

@AnonymousTeam

I know there is no real support for MacOS anymore and that running Windows on a Virtual Machine can cause problems. 
But because the VM + Win worked so well and Windows 11 ARM perfectly emulated the X64 architecture that Alias needs, I can’t believe that this is a MacOS but rather an ARM-processor problem in general.

Assuming that ARM processor are the future of CPUs, I think this might be worth looking into for you.

Thanks in advance and stay safe

Malte Wohlfahrt

———————————

malte.wohlfahrt@hotmail.com

[82068042]

Only modeling looks fine. Seems still have problems on shading. And VRED is not working as well.

[82068042]

Problem solved! The usetex, clay, including Zebra etc. diagnostic shading problems seem caused by the surface oritation setting. choose "Surface edit/Orientation/Set Geometric Surface Orientation",  use the mouse left key click the surface to make sure the surface upper side to be in BLUE color (rather then RED). And redo the diagnostic, everthing should goes fine then.

[systembolaget]

Has someone got a current list of what does NOT work properly?

That would be important to make a decision whether to purchase new macOS computers with M1 or M2 chip. Thanks!

[Fausto_Brevi]

You're right, it seems that it's no possible to manage canvas images: Alias allows to get the image but when I try to use Pick->Object to select canvas,  I can't select it.

I found two workarounds for this problem:

1. it works fine if you select the canvas from the Object Lister window;

2. it works fine (I mean, you can pick object a canvas from the graphic window) it you have at least two canvas images. 

[Fausto_Brevi]

Currently I have found, as an unsolved problem, that I cannot select any "green" object. But...

1. Some "green" objects, such as light sources, texture projectors, camera components, can be selected from the Object List window.

2. Another very important group of "green" objects, namely locators, currently has no solution.

Has anyone found a solution or, at least, a workaround for these types of selections?

[designlabor]

Hi malte, my old PowerBook Witz bootcamp just crashed. So i like to Buy a new MacBook with M2 Chip. As a Prof. In the design Area, i need to work with Autostudio. After looking around in the net, i thing you have, quite a lot Knowledge. Do you have some information if Autostudio (2024) will work an a M2 Max with Paralells 18 and Win 11? 
Regards Achim

[dee2]

Hi, I tested Alias 2024 on Parallels 18 running Win11 on M1 pro (that I borrowed). I see the same problem with the "green objects" beeing unable to select - I agree, lights etc can be selected from the object lister, but it's not full there yet.
Regards

Regards

[systembolaget]

So, are selecting Canvas images and green Locator objects the only problems not solved?

I must transition a whole group of users to macOS laptops and desktops, so it would be great if someone from Autodesk could chip in!

[dee2]

The not able to select the green objects is not a M1 problem, it's a Parallels problem as it does also not work when running on the Intel macbook pro - just saying.

[systembolaget]

Thanks, so if that's really the only thing, one can already safely switch over to macOS.

[dee2]

Please don't quote me for that 🙂 I just want to use the modeling tools, and I think that will be okay.

I will return to this thread again, I am getting my M2 next week then I will be able to do further testing.

Regards

[systembolaget]

Of course not, the responsibility of the macOS shift will be entirely on my side. It is just encouraging to know that, as far as modelling is concerned, we can now take the plunge.

[dee2]

Hi,

I just got my M2 max and have Alias running on it now, if there is something specific you want me to try let me know.

Regards

[systembolaget]

Thanks, much appreciated. As long as the interface works for all modelling tasks, and the various diagnostic shading and CV/hull/etc. display methods, too, I have nothing specific.

[dee2]

Hi all,

Just tried 2024 learning edition on the M2. I am able to select the green objects, ie. lights with no workaround and also able to edit the locators.

Vred is a no-go though.

Regards

[systembolaget]

Interesting!

Since we're not using VRED, if only that ain't working, it's no big deal. Which version of Parallels have you installed?

[dee2]

Hi,

Version 18.13.2 (53621)

Regards

[eortizGSAYD]

Hey, i'm not running the M1 chip (intel machine) but I had the same issue with the shaders in previous versions of Alias running parallels.

I solved it by checking the "shade by vertex" option box in the HW shade options pane.

The default is the "shade by pixel" the vertex shading is not as high quality but doesn't cause the non uniform shader look issue.  Give it a shot in the older versions of Alias. That said with the 2024 update they removed that option box and i have the same shader problem again (Autodesk wtf!!!).   Diagnostic shaders work correctly tho.