Simulation freezes when nodes are close

[ROCHETTE Andy]

Hello,

My simulation freezes when base station and nodes are close, less than 10 meters. It does a step forward when I move the background or when I zoom in or zoom out.

And it works perfectly, it's fluid, when nodes are 10m+ separated.

Any idea please ?

[ROCHETTE Andy]

I forgot to mentioned that the simulation freezes only when run in normal mode, it's fluid in fast and express mode. And it works in 3D, in normal, fast and express mode. I guess the issue come from this red line which represent the data :

[Attila Török]

Could you try to create a minimal example that can reproduce your issue, and send it to me? I'd like to take a look.

--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.

[ROCHETTE Andy]

Sorry i can't reproduce this error with a light example, and i can't send sources to you. I'll work on it later.

[Attila Török]

Understandable. If you can send just a stack trace (only including the frames within omnetpp/qtenv) when the simulation is frozen, that might also help a bit.

[ROCHETTE Andy]

I have some news :

When simtime-resolution = ns, it freezes

when simtime-resolution = ps, i have a simtime_t overflow (don't understand why, my sim-time-limit = 7200s and at the beginning I schedule only at 20s maximum)

when simtime-resolution = us, it works well, no problem.

This is the stack trace after a suspend when it's frozen :

[Attila Török]

We run all our code (qtenv, kernel and model) on Thread #1, the rest is started by Qt internally, so those stack traces are not very useful for us.
And if changing simtime-resolution has this effect, then the culprit indeed could be the message visualization (the red lines).
Which OMNeT++ version are you running? If not 5.4, could you try it with that too? We have fixed some similar issues in recent releases (with the simtime overflow, not sure about the freezing).