Correct location for local robot XML files [Bug] <title>

[nickhfoley]

Is there an existing issue for this?

• [X] I have searched the existing issues

What Robots version are you using?

1.6.X

What Rhino version are you using?

Rhino 7 for Windows

Current Behavior

The docs should be updated to reflect that the correct location for custom robots files (at least with Windows 11 / Rhino 7) is actually C:\Users\ username \AppData\Roaming\McNeel\Rhinoceros\packages\7.0\Robots\libraries

Expected Behavior

No response

Steps To Reproduce

No response

Anything else?

No response

[visose]

Hi, if you're manually creating or editing 3dm/xml files, you should place them in your Documents/Robots/ folder as it says in the wiki. The folder you mention is just the cache folder used when installing "online" libraries via the UI. You don't need to know about this folder path, it's an implementation detail which could change.

[nickhfoley]

Interesting - I did that first, but nothing happened and grasshopper did not find the robots. Once I moved the same files to the mentioned folder, everything worked immediately. Thoughts?

Nick

On Sun, Jan 14, 2024 at 10:17 AM visose @.***> wrote:

Hi, if you're manually creating or editing 3dm/xml files, you should place them in your Documents/Robots/ folder as it says in the wiki. The folder you mention is just the cache folder used when installing "online" libraries via the UI. You don't need to know about this folder path, it's an implementation detail which could change.

— Reply to this email directly, view it on GitHub https://github.com/visose/Robots/issues/260#issuecomment-1891023634, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFGTHP4R7KMEUOR6PS4XTS3YOQOMBAVCNFSM6AAAAABB2ICSX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJRGAZDGNRTGQ . You are receiving this because you authored the thread.Message ID: @.***>

[nickhfoley]

It seems like it may be a Windows 11 thing, since I just tried the steps on a Windows 10 machine and things worked as expected.

[visose]

There shouldn't be any difference between Windows 10 and 11. Double check the path for your Documents folder, it might be different. For example, if you are you are using the OneDrive integration, the path might be: C:\Users\user\OneDrive\Documents\

[nickhfoley]

I think that's the root of the issue - Windows 11 pushes OneDrive so persistently that even though I'm not "using" OneDrive, and there already was a Documents folder in the legacy location, it must be looking for the files in the OneDrive folder.

On Sun, Jan 14, 2024 at 1:03 PM visose @.***> wrote:

There shouldn't be any difference between Windows 10 and 11. Double check the path for your Documents folder, it might be different. For example, if you are you are using the OneDrive integration, the path might be: C:\Users\user\OneDrive\Documents\

— Reply to this email directly, view it on GitHub https://github.com/visose/Robots/issues/260#issuecomment-1891071597, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFGTHP573L6C2BBSMXTGI23YORB2TAVCNFSM6AAAAABB2ICSX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJRGA3TCNJZG4 . You are receiving this because you authored the thread.Message ID: @.***>

-- Nick