Thanks so much for taking the time to look into this! This feature has been a real game changer for my team and I, so we’re really excited to see how it progresses
Hopefully I can provide some helpful context. I am fairly confident it’s an issue with my editor + the networked drive, but I don’t know exactly what since it works with other editors like VSCode or Sublime Text.
Yeah as far as I’m aware the file shouldn’t be getting deleted/moved/renamed, at least not by me… When I show the synced file location it takes me to where I would expect, with the Windows explorer selecting the correct file. Opening the file shows the expected changes.
Very valid question… My setup is a bit unconventional and complicated:
I have a Windows PC that I use only for gaming + running Roblox Studio, and a Macbook that I use for everything else. Running Studio on an entirely separate computer and then using Parsec (low-latency remote desktop) leaves my Macbook—which runs everything else like my browser, chat apps, music, etc—with enough resources to basically never lag. I normally have multiple Studio instances open at once, so this separation makes my workflow really snappy since all of my other programs are unaffected by whatever I’m doing in Studio, and Studio is unaffected by other programs.
For the networked drive: it’s very useful with this setup, since it’s common for me to need to transfer files between the two computers (e.g. I make something in Photoshop on my Macbook, then upload it directly from Studio on my PC). Normally when working on projects I serve Rojo from my Macbook over the network (e.g. rojo serve --address 192.168.0.2
) and connect to that IP with the plugin from Studio. In this case, I’m trying to recreate that workflow by syncing the files from Studio to a folder on the networked drive from my PC, and then edit them from my editor on my Macbook.
The editor I use is Neovim. I tested this with Neovim, VSCode, and Sublime Text and was able to consistently trigger the “File not found” error by saving the file with Neovim to the networked drive (add comment in VSCode → save & check Studio → remove comment in Neovim → save & check → sync breaks). Saving to the networked drive with VSC/Sublime both seemed to work consistently.
This seems to be reproducible with a default Neovim (and Vim) configuration (nvim --clean
or vim --clean
).
Another reason I believe it makes sense that it’s my editor because this was happening to me when trying to save directly to the disk. I was having this problem around December when I was travelling with my Macbook (also using Neovim), however I could not reproduce it today and it seems to be stable.
Last thing, while testing I noticed that Studio would only crash if I attempted to stop syncing broken and working files at the same time. If I individually stopped syncing/delete the broken ones only it wouldn’t crash. I must have ran into this since it was faster to select all children → sync to disk.
Sent! Thank you again!