Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Administrator Privilege to install c4d plugin properly #17

Open
eZioPan opened this issue Jul 5, 2017 · 2 comments
Open

Use Administrator Privilege to install c4d plugin properly #17

eZioPan opened this issue Jul 5, 2017 · 2 comments
Assignees
Labels

Comments

@eZioPan
Copy link

eZioPan commented Jul 5, 2017

With release v0.1.6, if we copy C4DDev plugin into c4d plugin directory, we need start c4d with administrator privilege for the first time, to let C4DDev plugin initialize itself. After that we can use c4d and plugin normally.

If we don't use Administrator privilege, then we will get IOError in C4D Script Console

Could this information to https://niklasrosenstein.github.io/c4ddev/getting-started/ to avoid installation problem?

@NiklasRosenstein
Copy link
Collaborator

Hi @eZioPan, thanks for raising this issue! Actually, this is not intended and probably a bug in Node.py. While it will optimize the Python source code to bytecache files on the first run when under an Administrator account, it should not result in an error when it doesn't have write privileges (which I assume is the reason for the error?).

I'll try to reproduce this issue here. I haven't come accross it because I installed C4D on my User's home directory.

@eZioPan
Copy link
Author

eZioPan commented Jul 5, 2017

Yes, I think Node.py causes it. But for most situation, Node.py just does right. Since most python source code will be place in directory that user has privilege to write. But as you know, the default installation directory of C4D is "C:\Program File\MAXON", which exactly need Administrator privilege to write. So just for now, it's better let user know how to fix it.
By the way, since user always has write permission of "C:\Users<UserName>\AppData\Roaming\MAXON", maybe place plugin in this directory is an other workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants