Anyone able to make a Custom Bar Type?

[HandsFreeTrader]

I've been trying to convert over a custom bar type I use and so far haven't been able to get it to show up in the data series list for selection

Upon restarting NT if I have a custom bar type compiled I get this error popup: http://puu.sh/hCyDH/b748867aa7.png

Steps I took

1. Open existing bar type such as renko
2. save as with new name
3. go through and change existing name fields to new strings
4. at this point there are no compile errors but I can't seem to get it to show up as an option in the bar types. When I restart it will cause the error mentioned above which makes me think there is something else I need to renamed. Or there is a way to set the index somewhere that I'm missing.

If anyone has an example cs file of something that isn't stock I'd appreciate it.

[NinjaTrader_Matthew]

I would suggest using the Bar Type wizard to generate all the required code (right click on the BarTypes folder and select new...) which would generate everything you need to get started.

I believe I can reproduce as you may not have updated the BarsPeriod identifier

If you have:

BarsPeriod = new BarsPeriod { BarsPeriodType = BarsPeriodType.Renko };

replace with something like

BarsPeriod = new BarsPeriod { BarsPeriodType = (BarsPeriodType) 14, BarsPeriodTypeName = "MyCustomBarsType", Value = 1 };

There are 14 registered bars period types (0-13), you'll need to cast an int as the BarsPeriodType enum to register your own, which is why I used 14.

edit: skin and bones attached as requested

[HandsFreeTrader]

Awesome thanks. I thought it might have something to do with that line but didn't know what to change it to. Works great now

[NinjaTrader_Matthew]

Cool, glad that worked. We're looking at handling that situation a little more gracefully in the next beta build.

[NinjaTrader_Matthew]

NTEIGHT-8159 scheduled for B2 removes the assertion message that you mentioned in the first place. It also adds some more logging for when a user creates a new BarsType but hasn't configured it properly, which could cause errors.