Hi all:
I'm trying to get 3ds max 2015 working with Intellisense in PTVS. I have VS 2013 installed.
I configured the python interpreter to use the same paths that I do in PyCharm, and set the project search paths the same way, along with also setting the project references to a _MaxPlus.pyd file as well. When I first open my python project using the default Python interpreter and then open my 3ds max project, initially I am able to actually get intellisense working for the MaxPlus module and other built-in modules such as sys, os etc, and able to even get auto-completions working. However, after a few seconds, suddenly all auto-completions will stop, and I will get the No completions dialog, along with everything, even builtins such as sys and os showing unknown type.
Clearly, things are working before something happens in the background that breaks everything related to Intellisense, so could anyone point me as to how I might resolve/narrow down what's causing this issue? I have tried refreshing the db as well, but that has not helped.
How I have my Python Project set up:
http://i.imgur.com/hokUFi2.png
How I have the 3ds max python interpreter configured:
http://i.imgur.com/HySEXjs.png
I should point out here that I have used the same paths and .pyd file to get 3ds max auto-completion working in both PyCharm and Wing IDE flawlessly; this is my first time trying to use PTVS with 3ds max however, so if anyone spots me doing something incorrect in the setup here, I'd appreciate some pointers.
UPDATE: I attempted the workaround as detailed here: https://pytools.codeplex.com/workitem/3005 by setting HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\PythonTools\Options\Advanced@CrossModuleAnalysisLimit
to 10000. I also tried installing the latest development release of PTVS. The odd thing is that sometimes I do get intellisense working on certain modules such as MaxPlus, sometimes not. Additionally, I have issues with modules that say they have been indexed in the database such as PySide, but when I do an import statement such as import PySide
, they show themselves as unknown type again as well. Builtins such as sys, os, ctypes etc. seem to work now though.
The last thing is that I tried adding one of my current production 3ds max projects to PTVS, but for some reason, even though the PYTHONPATH and search paths are set up exactly the same way as I have them in PyCharm, my modules seem to be incorrectly trying to reference a folder level that they shouldn't be when determining the module root folder, and this is using a virtualenv as well.
A screenshot of that project and its search paths is as shown here:
http://i.imgur.com/9QReX5i.png
I'm expecting to be able to do a import stkToolkit_3dsmax
and have the module have Intellisense on it, but somehow it seems to be taking scripts
(the solution's parent folder) as the top-level module for some reason.
Anyone got any idea on what might be causing this issue, I'd love to have your input (on top of the general slowdown in PTVS, such as almost-hanging when right clicking on items in my solution explorer as well)
Thanks!