11-24-2021 09:19 AM
The known issue with Rosetta 2 is that LabVIEW is getting erroneous results from some file operations.
So using LabVIEW on M1 with Rosetta 2 is going to result in intermittent failures and sometimes crashes of LabVIEW.
NI is considering supporting M1 natively with a future release of LabVIEW.
11-25-2021 02:30 AM
hi !
very very glad to read that there is a m1 support on the way (i wonder when of course 🙂
but isn't there a work around before this ?
the weird thing is that it worked well until I re-installed LV for being able to create applications
I could at least work before this re-installation .. now I nearly can't (which as you can imagine is really problematic)
what could be the add-on installed (which was not copied with the apple tool for getting all the settings of an old mac) which cause problem ?
11-25-2021 10:48 AM
Well, good to hear that NI does consider to provide continued LV support for the future Apple chipset technology which was recently initiated with the contemporary M1 Macs! Some kind of hardware driver possibilities should make it back to the Mac as well!
In any case, that application builder issue is quirky and sometimes it works, sometimes it does not. I was so far not able to locate a possible underlying mechanism due to a lack of consistency and time to go thru more extensive testing. I however did also try to erase the cacheDB.vidb file in the LabVIEW Data/AppBuilderCache folder but without any obvious effect.
Anyway, it's like most of the time nowadays with these monumental software environments that are constantly patched to perform better... sometimes it works and sometimes it doesn't!
Anyway, let's keep on hanging in there while crossing our fingers for LabVIEW to stay natively on the Mac;-)
Happy wireworks indeed
Urs