Autocomplete not fully loading

[izzylys]

Thanks for the extension! It's been working perfectly other than the autocomplete. Code completion works for rhinoscriptsyntax, but not for Rhino.Geometry though they both import just fine. If you have any theories for why this is happening, please let me know!

VS Code: 1.30.2
Rhino 6: 6.10.18311.20531, 07/11/2018
CodeListener: 0.1.7.0

{
    "editor.wordWrap": "on",

    "python.autoComplete.extraPaths": [
        "C:\\Users\\izzy\\AppData\\Roaming\\McNeel\\Rhinoceros\\6.0\\Plug-ins\\CodeListener (8c4235b6-64bc-4508-9166-bef8aa151085)\\0.1.7.0\\AutoComplete",
        "C:\\Users\\izzy\\AppData\\Roaming\\McNeel\\Rhinoceros\\6.0\\Plug-ins\\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\\settings\\lib",
        "C:\\Users\\izzy\\AppData\\Roaming\\McNeel\\Rhinoceros\\6.0\\scripts",
        "C:\\Program Files\\Rhino 6\\Plug-ins\\IronPython\\Lib"

    ],
    // enable new language server. THIS IS EXTREMELY IMPORTANT TO HAVE FAST AUTOCOMPLETE!!
    "python.jediEnabled": false,

    // Enable/Disable rhinopython
    "RhinoPython.Enabled": true,
    // True if you want to reset script engine every time you send code, otherwise False
    "RhinoPython.ResetAndRun": true,

    "markdown.preview.breaks": true,
}

[shwdehaan]

Same for me!

Version: 0.1.9

[jingcheng-chen]

Sorry for late response.

Please check if your Python Interpreter in VS Code is python 2.7.

Also check if under Codelistener plugin foler, in your case "C:\\Users\\izzy\\AppData\\Roaming\\McNeel\\Rhinoceros\\6.0\\Plug-ins\\CodeListener (8c4235b6-64bc-4508-9166-bef8aa151085)\\0.1.7.0\\", there's a folder called AutoComplete.

[shwdehaan]

Thank you for your reply. Switching to python 2.7 breaks intellisense altogether in my case...

The AutoComplete folder is there.

[Krauszi]

Switching to python 2.7.0 x86 solved the issue in my case.

[deKlerk]

In my case, AutoComplete isn't working at all.
All folder paths are correct.

I'm running Python 2.7.15 64-bit, which shouldn't be a problem...

[deKlerk]

Changing Python interpreter to the latest 2.7.18 x86 didn't solve the problem.