Did I spend an hour trying to debug a script before I realized I forgot to import the api key? Maybe. But I'd never admit to doing something that dumb.
I figured out how to prevent my Xcode builds from failing all the time on my MBA. It was apparently overheating, so I just have to tilt my laptop so the bottom stays cool. At least it’s quiet without all those pesky fans.
@dan It works quite well on most apps. While it was working on Xcode, it was taking a very long time. I killed the process before it finished, but I'm sure it would've finished at some point.
Did you know that USDA scenes can be opened in a text editor? So if you need to, say, replace 300 instances of a particular 3D model, you can just do a big find & replace and it totally works?
@dan yeah man. The way to do it now is to zip the file and upload. If you leave a logic or Final Cut project in Dropbox it gets terrible on the other end
@dan this is smoke and mirrors by the Dropbox team, we feel. Apple allows for this just fine.
The actual problem is that Dropbox’s file propagation is simply too slow for this to work properly, as FCP libs are a bundle of files which all need to be in sync. It’s the same for an Avid project for instance, and not limited to Apple pro apps.
Dropbox finally forced me to update to the new File Provider API version where it shoves everything into CloudStorage for safety or whatever.
It's been "indexing" for 2 days, all my files have the fun little ☁️ icon, and yet it filled my entire hard drive with files that it’s now unable to remove because it's full and stuck.
It seems like Dropbox's new “Manage Hard Drive Space" tool that's supposed batch-move things to online-only won't work till it finishes indexing...which it can't do.
migrating to the File Provider version of the app on a specific device is irreversible
it's unclear if I'll be able to link my work and personal accounts on this computer again, have to wait until it finishes indexing (he literally said "we'll see” wtf)