When I use OPNET Debugger (ODB), I get different results than when I don't use ODB

When I use OPNET Debugger (ODB), I get different results than when I don't use ODB.  I thought that the same events were supposed to execute whether you were in the debugger or not!

That is correct:  The same events were supposed to execute whether you were in the debugger or not, provided all the simulations were run with identical parameters.

In order to confirm that the parameters were identical, make sure you are passing all the same command-line arguments to the debugger that were used in the non-debug run.

For example, the *minimum* set of arguments to op_runsim are:

op_runsim -net_name project1-scenario1

But look in your <home>/op_admin/session_log file to see that numerous other attributes may be passed in by default.  For example, I pulled the following from my session_log:

D:\PROGRA~1\OPNET\8.1.A\sys\pc_intel_win32\bin\op_runsim -opnet_user_home c:\users\ts -net_name project1-scenario1 -child_id 5 -opnet_port 3456 -noprompt TRUE -ef project1-scenario1 -probe project1-scenario1

Now if you are running the same exact command (with the only difference being the -debug environment attribute), and the results are different, then this is problematic behavior.  That sort of behavior usually indicates memory corruption.

In that situation, I recommend a memory-usage package such as Purify or GreatCircle.  You can also refer to the OPNETWORK presentation 1503: Debugging Simulation Models--Advanced for some additional techniques. See also, S18748

DES Kernel , OPNET Debugger, OPNET Modeling and Simulation, OPNET Modeler