441
you are viewing a single comment's thread
view the rest of the comments
[-] aeharding@vger.social 2 points 1 week ago

Stupid insta360 software >:(

[-] Playgroup_Gristle_360@sh.itjust.works 11 points 1 week ago* (last edited 1 week ago)

Oh boy my time to shine. Took me a while but I finally got Insta360 Studio working smoothly in Bottles on Linux with GPU acceleration. All credit goes to this github repo https://github.com/SveSop/nvidia-libs.

  1. download nvidia-libs-0.8.1.tar.xz from https://github.com/SveSop/nvidia-libs
  2. unzip it
    • the zip includes a bottles_setup.sh script, you can try it and see if it works, but it didn't work for me so I had to use the manual method detailed as follows
  3. copy the extracted nvidia-libs-0.8.1 folder to $HOME/.var/app/com.usebottles.bottles/data/bottles/
    • this is just copying it to a location inside the Bottles flatpak sandbox, so we can access it inside the Flatpak command shell that we use later
  4. go to Bottles > Preferences > Runners
  5. install kron4ek-wine... runner (not the proton one)
  6. create a new Bottle:
    • Name: Insta360
    • Environment: Gaming
    • Runner: soda
  7. after creation, go to Insta360 bottle > Settings:
    • DXVK: Disabled
    • VKD3D: Disabled
    • Discrete Graphics: Enabled
  8. (optional) at this point feel free to close Bottles and disable internet for Bottles if you are really paranoid about privacy and don't want the Insta360 Studio sending telemetry. You can disable internet for Bottles entirely using Flatseal, or use the experimental option inside Bottles to disable internet specifically for the Insta360 bottle
  9. then in terminal, enter a shell inside the Bottles flatpak sandbox: flatpak run --command=bash com.usebottles.bottles
  10. enter the folder you copied from step 3: cd $XDG_DATA_HOME/bottles/nvidia-libs-0.8.1
  11. set variable pointing to the folder corresponding to your Insta360 bottle: export WINEPREFIX=$(realpath ../bottles/Insta360)
  12. set variable pointing to the soda runner: export PATH=$(realpath ../runners/soda-9.0-1/bin):$PATH
    • exact folder name depends on the version of soda you used in step 6
  13. run the installer script ./setup_nvlibs.sh install
  14. back in the Bottles flatpak, go to the Insta360 bottle settings and switch to kron4ek-wine... runner
    • as for why I didn't start with the kron4ek-wine... runner from the start, it's because I had trouble running the setup_nvlibs.sh script in step 13 when I tried to point to the kron4ek-wine... path in step 12, so I started with the soda runner instead
  15. run the Insta360 Studio installer inside the Insta360 bottle
  16. open Insta360 Studio inside the Insta360 bottle, go to Preferences, and if hardware acceleration is enabled by default then everything should be working!

Note: You'll want to put all 360 files in the Bottles Flatpak sandbox at $HOME/.var/app/com.usebottles.bottles/data/bottles/Insta360/. This way Insta360 Studio will be able to see them. Exported files will end up in the sandbox as well.

I actually did this all in a VM with GPU passthrough, and then made a backup of the entire VM. This way I'll always have a working copy of Insta360 Studio, even if newer versions of Linux or Bottles stop supporting it.

Tested on:

  • Fedora Bluefin 42
  • Bottles runner: kron4ek-wine-10.8-amd64
  • nvidia rtx gpu
  • Insta360 Studio version: 5.6.1

References:

[-] imetators@lemmy.dbzer0.com 1 points 6 days ago

Hey, at least they got it to work! Progress has to start somewhere.

load more comments (3 replies)
load more comments (3 replies)
this post was submitted on 18 Oct 2025
441 points (100.0% liked)

Linux

9902 readers
399 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS