• 0 Posts
  • 19 Comments
Joined 2 years ago
cake
Cake day: July 4th, 2023

help-circle
  • I collaborate with other people who are also on DRS. Before I had teammates on DRS, I tried using Blender, Openshot, Shotcut, KDenLive. Those NLEs are just not there yet.

    I actually started my solid modeling/parametric journey on FreeCAD, and I prefer the parametric workflow. I switched to Inventor when FreeCAD kept crashing when the object tree was ~60 primitives even on my monstrous workstation. I would love to go back to FreeCAD, because fuck AutoDesk in its ear, so hopefully they get the stability + complexity under control.


  • Rant on, bruddah! I am also in the “must use it for work” group, and I despise my work laptop with the fury of 1000 suns. In my personal work and prior to this new job, I was staying on Win 10 for Inventor, AutoCAD, FL Studio (and a bunch of VST synths I bought), and DaVinci Resolve Studio. My experience with my work laptop has spurred my nearly-complete jump to Linux.

    FL Studio has been replaced by Bitwig, new learning curve and loss of the VSTs just being the cost I have to eat. I almost have DRS running in perfectly in Aurora Linux. And my two Win 10 machines will just go into an isolated network until I can figure out workarounds/replacements for the Autodesk garbage.


  • Sure, this applies most of the time. My big rendering workstation and Asus laptop run Mint so flawlessly, I was kicking myself for not trying this sooner. My brand new Dell G16 7630 has been a special kind of hell with over two months of forum diving. The keyboard backlight is being a crackhead. The video drivers are a chaotic mess that I’m wary of updating lest my machine completely freezes/bricks for the ~20th time, necessitating a Timeshift.

    So, yeah, Linux is great, but that is not everyone’s experience. For me, it’s only fully usable 66% of the time. I’m still going at it, but those are shitty numbers. We FOSS evangelists need to acknowledge that usability, end-user support, and compatibility are an utter shitshow for the average schmuck. Also, this meme is glowing radioactive evidence of the toxicity undermining the FOSS movement.

    When we start taking ownership of all that AND fixing the experience, then we can finally have the Year of Linux on the Desktop. Or we can sit here, say “hurr durr, look at stupid end-user,” and wonder why normies refuse to switch to Linux.








  • Oh, right! I forgot about all of the LIDAR-equipped planes in maritime communities! Those are way more economical to fly than any sUAS. /s in case that wasn’t obvious.

    In case you, or anyone else, were vaguely interested in learning:

    -kelp extent mapping needs to be done in repeatable fashion, specifically at low tide; we can put up an sUAS any time

    -the communities most in need of monitoring absolutely cannot afford to send planes up monthly

    -many of the kelp beds in the PacNW are in restricted airspace; it is much easier to get an FAA clearance to perform low-altitude surveys using sUAS

    -that restricted airspace I mentioned? Some of these kelp beds are on approach paths for the airspace. Even if a plane were the preferred choice for surveying, the planes are unable to fly in the pattern we need

    -(drifting a touch off your point of LIDAR-equipped planes) satellite imagery with the required resolution is prohibitively expensive

    -most construction projects wouldn’t use a plane for tasks such as volumetric or area analysis

    Consumer drones are quickly becoming the preferred, economical means for kelp health analysis, especially for communities that can’t afford planes or purchasing satellite imagery.


  • This “lonely adult” uses drones for aerial mapping and survey. This Summer’s huge project is a workflow I developed to map the extent of PacNW bull kelp forests in order to provide year-over-year health metrics. Using sUAS for this is way more automated, economical, repeatable, and granular than using airplanes and satellites, therefore within reach of those communities monitoring kelp health.

    DJI hits the sweet spot of capabilities, compatibility, and cost. Skydio (go USA!) has abandoned the consumer/enthusiast market that built their business. And even before they turned their back on the consumer market, Skydio couldn’t come close to DJI’s hardware. Additionally, Skydio, in true capitalist fashion, locked capabilities away behind software licenses, capabilities that are already built into the drone.

    It’s important for countries to have domestic drone manufacturing in the current conditions. But the USA’s actions here smack of protecting companies that just can’t hang.