Extremely slow loading of indicators

[aediaz1]

I have some custom-made indicators for NT that takes forever to load (30sec to several minutes) on my computer but not on others. I have a strong computer so thats not the issue. Is there any known issues why this occurs ?

[NinjaTrader_Brett]

Hello,

Thanks for the note.

Are you sure that you haven't manually installed this indicator and it was exported with a previous version of NinjaTrader or you have another third party indicator on this computer that is exported with a remote soft or previous protection technology we used in release 2 and below do you? As if you have one of these installed this could cause the issue you describe.

Any other indicators that you installed that was about the same time this started happening.


Let me know if I can be of further assistance.

[aediaz1]

Hello,

Thanks for the note.

Are you sure that you 1. haven't manually installed this indicator and it was exported with a previous version of NinjaTrader or 2. you have another third party indicator on this computer that is exported with a remote soft or previous protection technology we used in release 2 and below do you? As if you have one of these installed this could cause the issue you describe.

Any other indicators that you installed that was about the same time this started happening.


Let me know if I can be of further assistance.

First, I have always appreciated NT great customer support through this forum and mail, thank you very much.

1. No.
2. I have a indicator that is exported as you say but it should be up to date and I load it in a different workspace so it shouldn't affect in this case (?).

Update: it seems that it worked better when I changed data loading from days to periods. Strange

[NinjaTrader_Brett]

Hello,

If your up and going , great and thanks for the comments.

Otherwise. I would suggest removing all other indicators as a quick test to see if it in fact this indicators causing the issues(Indicators that run in background workspaces will be loaded in the current namespace). If it is then I can take a look at the code of this specific issue to tell where the error is would be our next steps.