at home ill.Īutomatic access to the stuff of another user is an unwanted effect.įurther to this, per user settings can change, and one may want to have a super quick library loading 256 px samples, while another may want the samples to be 2k res.
It will still allow for an easy way to share the parts one wants, but will crucially stay private for the content one creates for themselves, or has otherwise no express intention of sharing.Īs a practical example, It's common enough in a studio to swap out places, and workstations, with someone f.e. Instead, putting it in a folder accessible only by the user renders it private by default. It's rather yours the assumption that the library should be public to all accessing the computer. I have argumented my point before showing it's a standard (which, granted, you call "following the confused herd".): i have admin rights on my machine, meaning my stuff is mine alone. This should say something like "Unable to find the Material Library at C:\Users\Public\Documents" In other words it should include the directory it is looking for so the user knows why things have failed. I would also encourage you to add an error message to the vrayShowAssetBrowser() function such that it displays an error when it cannot find the MatLib directory path. Also, they are put into a per-user directory, even though these are system wide files that belong in a system wide (public) directory. When you install as as admin user, but run as an underprivileged user (like everyone should) the files get put in the wrong place. Rather than putting these files into the Documents directory of the current user running the install.
HOWEVER, I would STRONGLY encourage you to consider the correct placement for system wide files to be: I ran mtllib.exe as my local non-admin user, and it copied the files to my own user's Documents directory.
0 kommentar(er)
