VIRA EA Testing & Support Guide: Why the Same SET File Can Produce Different Results

VIRA EA Testing and Support Guide: Why the Same SET File Can Produce Different Results

When two traders use the same Expert Advisor and obtain different results, one of the most common requests is:

“Please send me the SET file.”

A SET file is important, but it is only one part of the testing environment.

The same EA with the same input parameters can produce a different number of trades, different entry prices, different drawdown, and different overall results when the broker, account type, historical data, symbol specification, spread, commission, or Strategy Tester settings are different.

This guide explains what information is required to investigate VIRA results properly, how to prepare an effective support request, and how to evaluate VIRA before purchase without relying on technically invalid comparisons.

The objective is simple:

Make tests reproducible. Make support efficient. Find the real reason behind different results.

1. A SET File Is Not the Complete Trading Environment

A .set file stores the input parameters of the Expert Advisor.

It does not contain your broker's:

• historical tick data;

• price feed;

• spread;

• commission;

• swap conditions;

• symbol specification;

• contract size;

• tick size;

• tick value;

• trading sessions;

• server time;

• liquidity conditions;

• execution behavior;

• slippage;

• account configuration.

It also does not define every parameter of the MetaTrader 5 Strategy Tester.

Therefore:

Same EA + Same SET does not automatically mean Same Result.

A more realistic formula is:

EA Version + SET + Broker + Account Type + Symbol + Historical Data + Tester Settings + Test Period = Comparable Test Environment

If one of these elements is different, the result may also be different.

This is why sending another SET file without understanding the complete environment often does not solve the original problem.

---

2. Before Asking for Support

If your message contains only:

My result is different.

or:

Very few trades.

or:

Send me the SET file.

or:

It does not work.

there is not enough technical information to determine the cause.

A support request becomes much easier to investigate when the necessary information is provided from the beginning.

Whenever possible, please send the complete diagnostic package below in one message.

---

3. Broker

Please provide the exact broker name.

For example:

• IC Markets

• Pepperstone

• Exness

• Vantage

“MetaTrader 5” is not a broker.

The trading platform may be the same while the broker's data feed, spreads, commissions, contract specifications, and execution environment are completely different.

---

4. Account Type

Please provide the exact account type.

Examples may include:

• Standard

• Raw

• Raw Spread

• ECN

• Pro

• Zero

Different account types offered by the same broker may use different spreads, commissions, and execution conditions.

For meaningful comparison, the account type matters.

---

5. Exact Symbol Name

Please provide the symbol exactly as it appears in your MetaTrader 5 terminal.

For example:

• XAUUSD

• XAUUSD.a

• XAUUSDm

• GOLD

• GOLD.pro

A suffix or a different symbol name is not always cosmetic.

Different symbols may have different:

• contract sizes;

• tick sizes;

• tick values;

• spreads;

• commissions;

• trading sessions;

• margin requirements.

If you are testing a result from another account, always verify the symbol specification.

---

6. Timeframe

Please provide the timeframe used for the test.

For example:

• M5

• M15

• M30

• H1

Do not assume that the timeframe is obvious from the equity curve or test report.

If the original test was performed on one timeframe and your test was performed on another, the comparison is not equivalent.

---

7. Exact Testing Period

Please provide both dates:

From: YYYY.MM.DD
To: YYYY.MM.DD

A different testing period can produce a very different number of trades and a completely different equity curve.

If you are comparing your result with one of my published tests, use the same period before comparing the statistics.

Even a relatively small date difference can matter.

---

8. Strategy Tester Modeling Mode

Please specify which modeling mode you used.

For example:

• Every tick based on real ticks

• Every tick

• 1 minute OHLC

• Open prices only

This information is essential.

Two tests performed with different modeling methods should not automatically be treated as equivalent.

For detailed EA analysis, the quality and structure of the historical data matter just as much as the EA parameters.

---

9. Deposit, Account Currency and Leverage

Please provide:

• initial deposit;

• account currency;

• leverage.

These parameters may affect:

• position sizing;

• margin requirements;

• available margin;

• risk calculations;

• drawdown.

A test performed with a $1,000 account and another performed with a $10,000 account may not be comparable if the EA uses money-management or risk-based position sizing.

---

10. VIRA Version

Always provide the exact VIRA version you tested.

If the EA has been updated, results from different versions may not be directly comparable.

Updates can contain:

• logic improvements;

• additional filters;

• bug fixes;

• execution changes;

• risk-management changes;

• compatibility changes.

Before investigating a difference, we first need to confirm that we are comparing the same version.

---

11. VIRA Inputs or SET File

Please attach your .set file or provide clear screenshots of the Inputs tab.

If you changed any parameter manually, mention it.

Do not assume that the parameters currently loaded in your terminal are identical to those used in another test.

Even one changed parameter can significantly alter:

• entry frequency;

• trading sessions;

• filters;

• risk;

• exit behavior;

• trade management.

The SET file is useful.

It is simply not sufficient by itself.

---

12. Full Strategy Tester Settings Screenshot

Please include a screenshot where the important Strategy Tester parameters are visible.

I should be able to identify:

• Expert Advisor;

• Symbol;

• Timeframe;

• Testing period;

• Modeling mode;

• Initial deposit;

• Leverage;

• Forward mode, if used;

• relevant Strategy Tester settings.

A screenshot containing only the equity curve is usually not enough for diagnosis.

The equity curve shows the result.

It does not show the complete environment that produced the result.

---

13. Test Report

Whenever possible, provide the complete Strategy Tester report.

If that is not available, please provide screenshots containing at least:

• number of trades;

• drawdown;

• profit factor;

• expected payoff;

• final result;

• test period;

• modeling/history information.

The report often reveals problems that cannot be identified from the graph alone.

For example, two equity curves may look different simply because one test generated 400 trades while another generated only 80.

The next question is therefore not:

“Which SET file is correct?”

The correct question is:

“Why did the two environments generate a different number of signals?”

---

14. Common Question: “Can You Just Send Me the Same SET File?”

Yes, a SET file can be useful when reproducing a particular configuration.

However, a SET file alone cannot reproduce the broker environment.

If you use the same SET on another broker and obtain different results, the next questions will still be:

• Which broker?

• Which account type?

• Which symbol?

• Which historical data?

• Which test period?

• Which modeling mode?

• Which spread?

• Which commission?

• Which EA version?

That is why I may ask for your testing environment before spending time comparing SET files.

The purpose is not to make support complicated.

The purpose is to avoid comparing two technically different tests as if they were identical.

---

15. “I Used the Same SET but I Have Fewer Trades”

If your test produces significantly fewer trades, check the following:

1. Is the broker the same?

2. Is the account type the same?

3. Is the exact symbol the same?

4. Is the symbol specification comparable?

5. Is the testing period exactly the same?

6. Is the timeframe the same?

7. Is the modeling mode the same?

8. Is the historical data complete?

9. Is the VIRA version the same?

10. Are all Inputs actually identical?

11. Are spread and commission conditions comparable?

A large difference in trade count is an important diagnostic signal.

It does not automatically mean that the SET file is wrong.

In many cases, the trade count is the first indication that the underlying market data or test environment is different.

---

16. “VIRA Does Not Open Trades”

If the EA does not open trades, please provide:

• broker;

• account type;

• exact symbol;

• timeframe;

• VIRA version;

• Inputs or SET file;

• screenshot of the chart;

• Experts tab;

• Journal tab;

• Strategy Tester settings, if the problem occurs during testing.

Also verify:

• Algo Trading is enabled;

• automated trading is allowed for the EA;

• the correct symbol is being used;

• sufficient historical data is available;

• the market/session conditions are valid;

• there are no errors in the Experts tab;

• there are no errors in the Journal.

A message saying only:

EA does not trade.

does not provide enough information for technical diagnosis.

The Experts and Journal tabs are especially important because MetaTrader often already explains the problem there.

---

17. “My Drawdown Is Different”

Drawdown depends on more than entry logic.

It may also be affected by:

• initial deposit;

• position size;

• risk settings;

• leverage;

• spread;

• commission;

• execution;

• historical price sequence;

• broker data.

If you want me to investigate a drawdown difference, please provide the complete Strategy Tester report and your risk settings.

Comparing only the maximum drawdown percentage from two different reports is usually not enough.

---

18. “My Entry Is Different From Yours”

Two brokers do not necessarily produce identical candles.

The same market movement may have slightly different:

• High;

• Low;

• Open;

• Close;

• spread;

• tick sequence;

• server time.

These differences can determine whether a trading condition is triggered.

A signal may therefore appear on one broker and not appear on another.

If you are investigating a specific trade, please provide:

• broker;

• account type;

• exact symbol;

• timeframe;

• date and time;

• chart screenshot;

• relevant Strategy Tester report;

• VIRA version;

• SET file.

Comparing only the entry timestamp is usually insufficient.

---

19. “Your Published Result Is Different From Mine”

A published test represents a result obtained under a specific set of conditions.

It should not be interpreted as a guarantee that every broker, account, or price feed will reproduce identical trades.

To compare your test correctly, match as many conditions as possible:

• EA version;

• configuration;

• broker environment;

• account type;

• symbol;

• timeframe;

• test period;

• modeling mode;

• deposit;

• leverage;

• spread;

• commission;

• historical data.

The objective of a proper comparison is not to force two reports to look identical.

The objective is to understand why they differ.

That information is much more useful when deciding how an EA behaves under your own broker conditions.

---

20. Backtest vs Live Trading

A backtest and a live trading account are not identical environments.

Live trading can include:

• variable spreads;

• slippage;

• execution delays;

• changing liquidity;

• broker-side execution behavior;

• real-time price-feed differences.

Historical testing is therefore a research tool.

It helps evaluate how an algorithm behaves under historical conditions, but previous backtest or live results should not be interpreted as a guarantee of future performance.

VIRA should always be evaluated using realistic risk parameters and trading conditions that are relevant to the broker where you intend to use it.

---

21. Evaluating VIRA Before Purchase

Pre-purchase questions are welcome.

However, the most useful way to evaluate an Expert Advisor is not to rely on one screenshot or one SET file.

If you are considering VIRA, I recommend evaluating the product systematically.

You can:

• review the VIRA product documentation;

• study the published test conditions;

• use the MQL5 Market Demo in Strategy Tester;

• test VIRA using your own broker's historical data;

• use Visual Tester mode to observe its behavior;

• test more than one market period;

• inspect the actual list of trades;

• study the available risk parameters;

• compare different market conditions rather than only one equity curve.

This gives you significantly more information than simply asking:

Can I reproduce exactly the same graph?

The more useful question is:

How does VIRA behave under the conditions where I intend to use it?

That is something you can investigate before making a purchasing decision.

---

22. Why Testing on Your Own Broker Matters

An EA is ultimately going to operate using your broker's:

• prices;

• symbols;

• spreads;

• execution;

• commissions;

• trading sessions.

Therefore, testing on your own broker's data is an important part of evaluation.

A result from another broker can be useful as a reference, but your own testing environment provides information that is more directly relevant to your intended setup.

If VIRA's trading behavior, risk controls, and configuration options are suitable for your requirements after your own testing, you can then decide whether the product is appropriate for you.

---

23. Pre-Purchase Support vs Customer Support

I am happy to answer reasonable technical questions before purchase.

At the same time, detailed troubleshooting can require significant time.

There is an important difference between:

Pre-purchase evaluation

and

Individual technical support for an existing customer.

For that reason, support priority is generally:

1. Existing VIRA users experiencing technical or operational issues.

2. Existing VIRA users requesting assistance with configuration or testing.

3. Pre-purchase users who provide a complete and specific technical question.

4. General pre-purchase enquiries without sufficient diagnostic information.

This helps ensure that users who have already purchased and are actively using VIRA receive timely support.

Pre-purchase users are welcome to ask questions, but repeated broker-specific testing and extensive individual troubleshooting cannot replace the normal customer-support process.

---

24. How to Get a Faster Answer

The fastest support request is not necessarily the shortest message.

The fastest support request is the one containing enough information to reproduce the problem.

Instead of writing:

My backtest is wrong. Send SET.

send something like:

Broker: IC Markets
Account Type: Raw Spread
Symbol: XAUUSD
Timeframe: M15
Test Period: 2025.01.01 – 2025.12.31
Modeling: Every tick based on real ticks
Deposit: 10,000 USD
Leverage: 1:500
VIRA Version: [version]
Number of Trades: 87

Problem: My test produces significantly fewer trades than the published test.

Attached: Strategy Tester settings, SET file, and test report.

Now there is something concrete to investigate.

Instead of spending several messages collecting basic information, I can start comparing the environments immediately.

---

25. Copy and Paste This Support Template

Please use this template when contacting me about testing or technical issues:

VIRA VERSION:
BROKER:
ACCOUNT TYPE:
SYMBOL:
TIMEFRAME:
TEST FROM:
TEST TO:
MODELING MODE:
DEPOSIT:
ACCOUNT CURRENCY:
LEVERAGE:
CONFIGURATION / PRESET:
SET FILE ATTACHED: Yes / No

PROBLEM:

EXPECTED RESULT:

ACTUAL RESULT:

NUMBER OF TRADES:

ATTACHMENTS:

• Strategy Tester settings screenshot

• Test report

• Inputs / SET file

• Experts tab, if relevant

• Journal tab, if relevant

Providing this information from the beginning can significantly reduce the number of messages required to identify the issue.

---

26. What I Am Looking for During Diagnosis

When I compare two VIRA results, I am normally trying to determine which category explains the difference.

1. Configuration Difference

The EA inputs are not actually identical.

This includes:

• different presets;

• manually changed values;

• different risk parameters;

• different module settings.

---

2. Test Environment Difference

The Strategy Tester configuration differs.

Examples:

• test period;

• timeframe;

• modeling mode;

• leverage;

• deposit;

• forward-testing settings.

---

3. Broker Data Difference

The historical price data or tick sequence is different.

This can affect whether specific entry conditions occur.

---

4. Symbol Specification Difference

The broker uses different trading specifications for the instrument.

Examples include:

• contract size;

• tick size;

• tick value;

• session times;

• volume limits;

• minimum stop distance.

---

5. Trading Cost Difference

The environment uses different:

• spreads;

• commissions;

• swaps;

• execution assumptions.

---

6. Software Version Difference

The tests were performed using different VIRA versions or materially different MetaTrader environments.

Once the correct category is identified, the problem usually becomes much easier to investigate.

---

27. Why VIRA Uses This Support Process

VIRA uses multiple trading and trade-management conditions.

When an algorithm evaluates market conditions precisely, relatively small differences in market data may change whether a particular setup is triggered.

This is why reproducible testing matters.

I prefer to determine why two results differ instead of simply sending another SET file and hoping that the next equity curve looks closer.

The process I use is:

Show the conditions.
Compare the conditions.
Then compare the result.

This produces much more useful information for both backtesting and live preparation.

---

28. A Better Way to Evaluate an EA

When evaluating any Expert Advisor, avoid focusing only on the final profit figure.

Look deeper.

Study:

• how often it trades;

• when it trades;

• how it manages risk;

• how sensitive it is to trading costs;

• how it behaves in different historical periods;

• how it responds to different broker data;

• whether the trading logic behaves consistently with your expectations.

A beautiful equity curve does not explain why the algorithm generated those trades.

A proper test does.

The purpose of serious EA testing is not to search for the most attractive screenshot.

It is to understand the behavior of the system.

---

29. If You Are Considering VIRA

If you are currently evaluating VIRA, use the available MQL5 testing tools before making your decision.

Run the Demo.

Test your own broker data.

Use Visual Tester.

Study the trades.

Review the configuration options.

Test different market periods.

Understand the risk settings.

Then decide whether VIRA's behavior is suitable for the way you intend to trade.

This approach gives you much more useful information than trying to reproduce one historical screenshot without matching the environment behind it.

---

30. Final Principle

A SET file is a configuration file.

It is not a broker.

It is not historical data.

It is not a price feed.

It is not an account specification.

It is not a Strategy Tester environment.

Therefore, when comparing two EA results, always think about the complete environment:

VIRA + Configuration + Broker + Account Type + Symbol + Data + Tester Settings + Test Period

Only after these conditions are known does it make sense to compare the results.

If you provide the complete diagnostic information from the beginning, I can spend less time asking basic questions and more time helping you identify the real cause.

Clear inputs lead to faster diagnosis and more useful support.