FX: When creating indicators and EAs, the first thing to consider
Simple Logic FX - Sales Page
Simple Logic FX - Gold Edition - Sales Page
Auto Click - Sales Page
Working on Making the Tool More User-Friendly
For both System A and System B,
many people are using it, so
the environments in which it is used are diverse.
Computer specs and usage,
VPS, mini PC, etc.
It is used in various environments.
If the tool is lightweight,
there is no problem.
However, the tools I create
pack in many features
and tend to become heavy.
In particular, ZigZagH in System B
has become heavy.
The reason is that the amount calculated per tick is large.
ZigZag moves frequently on the latest bars.
We color ZigZag using colors derived from calculations.
Also, the average candlestick I developed
shows the colors of the Heikin-Ashi candles on the candlestick
These are calculated per tick and drawn,
which is why the load is high.
Some users have reported that MT5 becomes heavy and freezes.
Therefore, in the past month or so,
we conducted a thorough investigation
and reviewed internal calculations to lighten the processing.
The most recent modifications are listed below.
（There are other fixes as well, so this version has not yet been uploaded to the member site）
【Operation Improvement Investigation & Fixes】2026.02.11
・Added monitoring descriptions along the ZigZagH_EA and ZigZagH circuits to identify where
stops frequently occur, and implemented changes at locations likely to improve performance.
to implement changes.
・To avoid stopping during repetitive calculations, added a bypass circuit.
・In the circuit that calculates price per pixel, freezes were still observed, so
the specification was changed. (Retrieve information gradually within the timer circuit.)
・In the circuit that deletes old history, freezes were observed, so processing frequency was reduced.
I feel it has become much easier to run now (when testing with intentional PC load).
However, I wondered if there was still more that could be done,
and realized
that perhaps the fundamental calculation timing should be controlled.
So I realized this.
Therefore, I added the following parameters
to ZigZagH and ZigZagH_EA.
Made it possible to separate the calculation timing into “per tick”
and “at bar completion (bar switch).”
Basically use “per tick,”
and if it is too heavy, switch to “at bar completion.”
Naturally, using “at bar completion” reduces the calculation load, so it becomes lighter.
Of course, features that require per-tick calculation
will not be usable.
For example, the pre-signal that appears when the latest bar in ZigZagH is moving.
A signal that informs before the main signal at bar completion.
This will no longer sound.
With this in mind, I considered that using it might be an option.
Thus,
the calculation timing is two types: “per tick” and
“at bar completion (bar switch).”
Knowing this will be useful when you create your own tools in the future.
Please remember this.
Progress of Simple Logic FX
Last Saturday, after sending the newsletter, I received the following feedback from Mr./Ms. O.
――――――――――――――――――――――――――――――――
- 2026.02.07: O
Verification results show graphs that always end with profit, even with drawdowns from losing streaks.
and there were times when capital ran short.
If doing it manually, 2 might be okay too,
as profits recover quickly when winning.
――――――――――――――――――――――――――――――――
There are many features, so not many people may be testing limited martingale,
but please try various things.
System B now includes Gishin Logic in ZigZagH and ZigZagH_EA,
and also
an Moving Average Deviation filter and RSI filter have been added.
We are still adding a few more features,
so uploads to the member site will be next week.
System B continues to evolve.
Please look forward to it.
Simple Logic FX - Sales Page
Simple Logic FX - Gold Edition - Sales Page
Auto Click - Sales Page