Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.
Need help? 1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first. 2) Start a journal and post to it daily with the trades you made to show your strengths and weaknesses. 3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make. 4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance. 5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers. 6) Help using the forum? Watch this video to learn general tips on using the site.
If you want to support our community, become an Elite Member.
The following 2 users say Thank You to Big Mike for this post:
Here are some answers for the last questions in this thread. Thanks to @Silvester17 for answering some questions along the way and @futuretrader for providing the PAS with a swing histogram.
@typer77, the swing is first fix and will not change anymore if there is a new swing. Otherwise the indicator would repaint, because we don't know the point when the swing is finished.
@tst1, that's pretty simple just add in the code in the "CalcDnSwing(…)" function in the region "New and update Swing values" in the in first if-statement ("if (!updateLow)") part
where AudioFileName is the name of the audio file and which has to be in the NinjaTrader 7/sound folder. Do the same thing in the "CalcUpSwing(…)" function and you are ready.
@djkiwi, in the newer version I put the "SwingRelation" Dataseries in the PriceActionSwingOscillator to keep the PAS simple. Just change the "PriceActionSwing" to "PriceActionSwingOscillator" and it should work:
@supermht, this isn't possible in this PAS version. You can code it relative easily yourself. In the "Swing calculation" region you have to replace the "High"/"Low" data series with the "Close" series.
@marty73, this isn't possible. But you can code it yourself. Just add a Dataseries variable and in OnBarUpdate save the retracement values in this variable. Then you have to make this Dataseries public and now you can access this Dataseries in the MA.
1. In the source code set the variable "divergenceMode" in the variables region to "DivergenceMode.Custom".
2./3. The Regular Divergence Signal updates (re-prints) with every change in the swing value. The signal is not fix, because at this point it isn't safe to assume, that the swing is finished.
The Regular Divergence Entry occurs if the swing is complete and at this point the divergence signal will not change anymore.
4. You can use in your strategy the Dataseries "AbcSignals" and "DivergenceSignals" and check the values of this data series to know in which state they are.
@jmont1, sorry, but due to several reasons I'll not discuss and share strategy related things. I haven't traded or even looked at the mentioned strategy in a while, so I don't have any idea how the strategy would run this days. But it is relative simple to create such a strategy yourself or with a little help.
The following 10 users say Thank You to dorschden for this post:
Dear fellow members. Could someone let me know what the latest version of Price action Pro is so that I can make sure that I am running it with the most current features. Sometimes updates and tweaks get put into a thread and are available but we do not always know that it has been updated our improvements made to it by diff BM members.
Again thx to Dorschden for sharing a marvelous indicator that I use on every chart I have and would not trade without it. Thx for letting me know and I will check it against the version I am running.
Please add the audio alert (option to turn it on/off) for divergence alert signal since I am not a programmer for Ninja platform. Also, I'm a bit confused about Divergence signal vs Divergence entry where I don't see any separated inputs in my PriceActionSwingPro version for display which one of the divergence to show on the chart. How many bars delay if audio alert added for Divergence signal (alert in next new bar ?) and Divergence entry ( how many bars later ) ? If there is too many bars delay on Divergence entry, then all I need is the Divergence signal because I would take the signal aligned with support and resistance line touch so I don't need to wait the completion of the divergence coming late.