8x Multicolour Market States

Forums › ProRealTime English forum › ProBuilder support › 8x Multicolour Market States

  • This topic has 28 replies, 5 voices, and was last updated 3 years ago by avatarBard.

Tagged: , , ,

Viewing 14 posts - 16 through 29 (of 29 total)
1 2
  • 05/11/2020 at 8:50 PM #131204
    Bard

    Hi @Nicolas, it’d be nice to add this indicator directly above (it’s on daily TF) to the library, but the colours extend beyond the Bollinger bands when on timeframes like 3 and 10 mins. Pls see images. When on 4 hours its all grey between the Bollinger bands? Any ideas? Cheers!

    05/12/2020 at 8:23 AM #131233
    Nicolas

    No problem for me with GBPUSD on 3min or 4-hours timeframe with the last version you posted in the previous page.

    05/12/2020 at 12:03 PM #131278
    Bard

    Oh? Thanks Nicolas. I had this grey Bollinger colour appear sometimes on the daily when I was developing it too. It would appear when I was adjusting, eg, the Damiani settings. I thought it was the settings alterations causing the grey to suddenly appear? Apparently not…

    When the 4 hour produced that grey colour I logged out and back in because that can resolve issues I have, like missing indicators, but in this case it was still grey, until I changed the TF back to daily. It’s still grey now today.

    May I send you the indicator itf? Perhaps there is a difference, something in the code because tbh, I’m getting all kinds of time consuming issues, exactly like this one. It’s been ongoing with my account ever since last October 2019, issues with code producing different results, issues with saving systems/indicators (they don’t save and are are either completely missing or reappear on the next log in). Do you know of any other Macbook users having these kind of issues?

    I think, thanks to your prompting, I received an email the from Gregoire and they say they are looking into, but it’s been a nightmare though, I almost quit PRT last week.

    05/12/2020 at 2:46 PM #131319
    Nicolas

    That color problem is probably due to your settings, make sure you have sufficient bars loaded on the chart. I used your last version posted here without any problem on many different instrument.

    1 user thanked author for this post.
    avatar Bard
    05/12/2020 at 3:12 PM #131328
    Bard

    Cool, but mine is still grey on the 4 hour after doubling my units from 1,500 to 3,000?
    How many have you got? Shouldn’t be an issue? The Williams Vix Fix is only looking back over 365 periods for the high/low. I’m not aware of a longer period setting in the code.
    It went grey a few times during development on the daily TF too.

    Edit: But it now works okay on 4 hour on 1,000 units. Why can’t it work on 1,500 or 3,000?

    05/12/2020 at 5:38 PM #131351
    Bard

    Hi Nicolas, the solution to colours appearing above the Bollinger Bands was to remove colour zones that were on the chart associated with Pivot Points.
    I can tell you I didn’t even know you could add colour zones to the Pivot Points! But there they were… besides I used another chart to “set as template” that didn’t have any Pivot Points colour zones on it to launch a new chart with which to build these multicolour indicators on… Just more of the same unusual things I experience everyday loggin into this platform.

    Update to prior post:

    The grey only appears on the 4 hour 1,000 unit £/$ chart if DEFPARAM CalculateOnLastBars = 1,500 and less, but not 1,550 bars and above.
    Experimenting with lots of different chart units and CalculateOnLastBars amounts it ‘s hard to figure out the logic?

    1,000 chart units and 2,000 last bars works but 500 chart units and 1,000 last bars doesn’t?

    Could you please explain the relationship and why does it need 1,500 last bars if the max lookback in only 365 bars for the Vix Fix? Thanks.

    05/12/2020 at 5:52 PM #131354
    Vonasi
    Bard wrote:

    Just more of the same unusual things I experience everyday using this platform.

    I don’t think the platform can be blamed for displaying colour zones that you must have added to the chart at some point or added as part of an indicator at some point. I believe we can put the grey zones down to what is technically classified as operator error.

    …..another Bard case is closed! 🙂

    05/12/2020 at 6:52 PM #131364
    Bard

    Okay Vonasi, don’t accept my word, yes it was me, I added two Pivot point colour zones even though I never knew they existed or you could do that or have ever seen them on my charts before (because I would have posted about it), or, that they weren’t on the charts at any time during the development of the multi colour indicator as the dozens of dozens of screenshots I took during development show (I just looked). As for “included in an indicator,” no, sorry I have no such indicator (although I’m already getting an idea where that could be useful), and if you’d seen the dogs dinner that has greeted me some days (pls see image) when opening my platform you’d become suspicious too that it’s a template/PRT /Save issue. You’d also started making have triple back ups as I have. My platform just crashed an hour ago… using my “light” template (no heavy Ehler’s multiple indicator MESA math). It’s been a nightmare since last October.

    As for the other case I still don’t regard that closed. How can it be? GraHal posted an indent image that wasn’t relevant to my point or prior images or code and you made a comment about endif’s that also wasn’t relevant to the code or my screenshots of the problem. Please feel free to double check, but there are no “indents” that were in the code screenshots that I posted (yes I appreciate they were too small to see). As of yet, I haven’t heard any logical explanation for this: https://www.prorealcode.com/topic/why-does-removing-one-line-of-unused-space-cause-profits-to-reappear/page/2/#post-131321

    I wish I had filmed it… it would stop yours or anyone else’s doubts.

    So then I removed one line of unused space between the “DEFPARAM…” (line 2) and the “//Conditions to go long” (line 5) and NOW the profits are the same.

    https://www.prorealcode.com/topic/why-does-removing-one-line-of-unused-space-cause-profits-to-reappear/#post-130880

    That is exactly what happened and I simply have no idea why you find that so hard to accept? Why, because code can’t become corrupted? Because code works 100% of the time every time? It happened. It’s still unresolved.

    05/12/2020 at 7:09 PM #131366
    Vonasi

    I can’t see a thing in that image except some clouds due to the same screen shot capture issue as before.

    You seem to be missing my attempt to raise your spirits with some light-hearted humour. The smiley face was meant to be a clue.

    Whenever something odd happens or something does not work as I expect it to (in life in general and while writing code or using the platform) then my first question to myself is ‘OK – what did I f**k up?’ Only after I have exhausted searching for my own f**k up and failed to find it will I resort to asking someone else to look and see where I might have f**ked up. By this time I will have gathered a whole load of evidence to prove why I don’t think it is my f**k up and to maybe help them in their search for the reason…. and still nine times out of ten they then show me how and where I f**ked up. The one out of ten will turn out to be some one else’s f**k up.

    05/21/2020 at 5:22 PM #132647
    Bard

    Cheers for the feedback, I’d have written sooner, but compressed/bruised a nerve in my lower back and have taken time off.
    The support is really appreciated, as mentioned in one of my comments on my original PRT issues thread: https://www.prorealcode.com/topic/why-does-removing-one-line-of-unused-space-cause-profits-to-reappear/page/2/#post-131321

    The image above shows a PRT template on launch that instead of being two neat rows of charts top and bottom of my desktop, was missing data/charts/windows.

    I also experience missing indicators and code that doesn’t save properly from the last session, or a template that I regularly save during a work session doesn’t re-launch up to date (i.e. it appears most of my saves during the session were not saved). I have emailed PRT about issues like this, they’ve invited me to send more examples via the PRT help.

    The platform is not stable for me so I can try GraHal’s option and clear out tons of indicators and systems from the list in case it’s some kind of indexing/save problem, or try on Window’s XP on this Mac. It may even be network issue?

    As for the odd behaviour of code as described on that thread above I have no explanation, but my description of events is accurate.

    05/21/2020 at 5:48 PM #132660
    Bard
    Vonasi wrote:

    The one out of ten will turn out to be some one else’s f**k up.

    Just logged in to extend the demo and the Pivot Zones colour zones are back.

    I’d already deleted them and got the indicator looking correct and saved the platform during the session and on quitting… but here they are again and they weren’t re-added by me. (Pls see Screen 1). EDIT: Wrong image. Here is image “1” now labelled image 1b as I don’t see a way of deleting image 1 in Edit?

    Also do you know where the modify/amend indicator tab has gone in settings after I click on the price chart settings spanner — which shows me the indicators listed for this chart? (Pls see Screen 2). Cheers.

    05/21/2020 at 6:05 PM #132670
    Bard

    Please ignore amend question, I was clicking in the wrong place.

    I also thought PRT  launched the last template of the platform used?

    Could it be with all the save issues I have that I am not being returned to my last used template? (I have 3 versions of this template, the original and two identical backups).

    Therefore the colour zone is showing now because PRT have launched another backup template I use? (Even though that backup also should have a “saved” 4x multi colour indicator without pivot colour zones because once I fix an issue I save all three templates — the original and the two backups) and surely once an indicator is fixed and the pivot colour zone is deleted it should load in it’s new “non pivot colour zone” state?

    05/21/2020 at 8:23 PM #132693
    Vonasi

    I’m no template expert. When I shut down my platform I save the template on exit because I want the platform to launch and look the same when I next open it. I have various stuff on test or in development that I want to be there the next time I launch the platform and during that next session I will delete some indicators, some charts and some strategies and create some new ones. I am only interested in what I am currently interested in so I have one template and I save it on exit and it all looks the same when I relaunch.

    1 user thanked author for this post.
    avatar Bard
    05/22/2020 at 1:18 PM #132812
    Bard
    Bard wrote:

    surely once an indicator is fixed and the pivot colour zone is deleted it should load in it’s new “non pivot colour zone” state?

    Cheers Vonasi, the quote above, that holds true right?

    I still don’t know why deleted pivot colour zones would reappear in an indicator if it’s been “saved” without them? All very strange.

    Since Oct 2019 when the save issues started I’ve been constantly second guessing the PRT platfrom, like, “did that something happen  because of something I’ve done?” or because the platform isn’t behaving right… (which clearly it hasn’t been).

     

     

     

  • Author
    Posts
Viewing 14 posts - 16 through 29 (of 29 total)
1 2

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
🚀 experience the power of ws3m v1.5 – rent for free for 1 month! 🚀
🚀 experience the power of ws3m v1.7 – rent for free for 1 month! 🚀
4x developer separate the buy side
code trailing stop like “set stop ptrailing x”
highlight a “x” trading” day or fixed time regression
minimum distance for this market is x
which is a priority, set stop price and sell at x stop
x max trade per day

Create your free account now and post your request to benefit from the help of the community
Register or Login