Just a basic rclone config with my api, and crypted google drive.
Basically I get an error saying OBS doesn't have the rights to write to the path (the rclone mount) because:
There could be no space available
Other problem I encountered, was while creating and saving .mkv files they were getting corrupted (or at least they are playable but don't get the last bit of the mkv file that tells the "time" of the video file, basically an infinite mkv file)
check the windows folder/file permissions, not rclone permissions.
when you run rclone, the command prompt, are you running it in a standard privileges or elevated privileges.
make sure to use the same for OBS and rclone.
or use a folder, not drive letter, something like
Unless execute permissions on files are relevant (which I think not, when just saving files from the application), this should not be any different from the default --file-perms 0666 --dir-perms 0777 and could be omitted. But related to that, I've found that with the default permissions, and when using the --file-perms/--dir-perms options, you get a set of ACLs that are a bit "messy", as it tries to emulate the corresponding Unix permissions. This may not be that useful for Windows users, and setting a specific ACL can give you "cleaner" permissions. E.g. -o FileSecurity="D:P(A;;FRFW;;;WD)" sets file read (FR) and file
write (FW) to everyone (WD), and nothing else. If file execute (FX) is also needed, then change
to -o FileSecurity="D:P(A;;FRFWFX;;;WD)", or if delete is needed then set all access (FA) with -o FileSecurity="D:P(A;;FA;;;WD)". There are some notes about this in the mount docs, and the beta version at tip.rclone.org contains even more. I don't see how this would solve @Magno's problem though, but might be worth a test after checking/answering @asdffdsa's questions...