OMNeT++ 5.0 with cmdenv:
Is there a way to stop a running simulation, which consists of multiple repetitions?
The Terminate-Button only terminates the current iteration, but not the whole simulation.
That is an issue with the Eclipse version OMNeT++ 5.0 is built on (Eclipse 4.4). OMNeT++ 5.1 will be based on Eclipse 4.6 and it will handle the batch cancellation correctly. OMNeT++ 5.1 pre 2 version should also work.
Related
I am working on a IddCx indirect Display Driver. I have run into a bug that I cant find any reason to blame my own code on. Every two seconds or so IddCxSwapChainReleaseAndAcquireBuffer takes over 100ms, up to 8000ms to complete. It normally takes below 16ms to complete (depends on your frame rate).
I even added timestamps to the IddCx Sample code from Microsoft. It still has this issue, so it cant be a fault with my own code. I have exhausted most of my debugging options.
Changing IddCx versions I am compiling with (1.4 to 1.8) by targeting the libs, the headers, and defining the macros (IDDCX_VERSION_MAJOR, IDDCX_VERSION_MINOR, IDDCX_MINIMUM_VERSION_REQUIRED). 1.9 btw doesnt seem to run well, IddCxDeviceInitConfig() fails with Invalid Parameter if I choose version 1.9.
Changing which UMDF version I am compiling with (2.25 to 2.33).
Changing the Windows SDK version I am using (10.0.19041.0, 10.0.20348.0, 10.0.22000.0, 10.0.22572.0).
Swapping my OS to the Insider Program preview version of win11 (currently 22000.588 co_release).
Things I think may be solutions that I need help on.
When I am running the Driver, within dxdiag, the display says its using WDDM version 1.3, while my other displays use WDDM version 3.0. WDDM 1.3 is old, so maybe this could be causing issues? How do I tell visual studio to compile my driver to compile with WDDM version 3.0? Does my driver need to WHQL Logo'd first?
IddCxGetVersion() returns with version 1801 or 1803 no matter what I change (SDK, IDDCx version, etc), which is from 2018! So what am I doing wrong here to get the OS to choose to use a newer version of IddCx? This may be related to the WDDM version being 1.3 instead of 3.0.
Swapping back to Windows 10. I originally swapped to Windows 11 because the WDK dev environment is completely unstable, with the samples sometimes not creating functional drivers, that fail to call into 'EVT_IDD_CX_ADAPTER_INIT_FINISHED', I have confirmed its being compiled incorrectly (sometimes) on windows 10, and the old dlls from earlier that day will still work, but the new dlls will not. So thats why I am staying with Windows 11, I also need to swap to Windows 11 anyways since we should be moving forwards, not backwards.
forgot to close this.
Realized the issue was that the monitor desktop simply wasnt updating. So the OS was just rendering the desktop less often, resulting in less frames being pushed to the swapchain for me to grab
I have recently started Flutter development and on my machine, and the gradle build seemingly takes forever when completely restarting the app or running it for the first time, at times it gets quite frustrating. I am using an Ubuntu 20.04 (KDE Plasma env) with 8 GB RAM/ 240 GB SSD and using VS Code for running the app. Is there any way to optimize this? Would appreciate any suggestion on the same. Thanks in advance.
According to this documentation by developer.android.com there is a way to optimize gradle build by using JVM Garbage collector.
Add this parameter to your gradle.properties in your android folder you can find it on /{your-project}/android/:
org.gradle.jvmargs=-XX:+UseParallelGC
and if there are already value set in this field, just add a new option:
org.gradle.jvmargs=-Xmx1536m -XX:+UseParallelGC
I was running my simulation in OMNeT++ 3 months ago, and now that I've tried to launch it, it says initializing and it's stuck. The only "error" I get is the java.lang.runtimeError which doesn't really say much. Even that error doesn't pop up, you need to bring it up by clicking inside the OMNeT IDE. I am using OMNeT++ 5.4.1, SUMO 0.32.0, and Veins 4.7.1.
Sumo was checked with the gui, and it runs normally. I don't know which java version needs to be installed..
Picture attached,
Simulation stuck
Please if any1 could offer a solution?
The .metadata directory in your workspace contains a detailed log of the IDE. I would try to upgrade to OMNeT++ 5.6.2 though, to use a later version of the IDE (and Eclipse which the IDE is based on)
I'm running with OMNET 5.0 veins 4.4 and SUMO 0.25.0 ...
Everything works fine until the last time when I tried to run my code the simulation window does not appear but its icon exists in the taskbar and the simulation crashes with this error
I have all reinstaller but the problem persists (I have read in other topics that I have to verify the versions but my version is countable according to http://veins.car2x.org/download/)
Can you help me please ?!
I know only OMNeT++ Version 5.0 with INET 3.4 and Versions before ...
In OMNeT++ is Language C++ used, you have to take about nullptr or
garbarge in memory.
The first step is to run GDB in OMNeT++ this graphical user interface
in eclipse editor is quite enough to get neccessary information.
If it don't run after simple checking memory, objects, nullptr, exceptions and so on. See working with valgrind http://www.eclipse.org/linuxtools/projectPages/valgrind/
But usally it is enough to workout with GDB, try to initialize everything, check exception and it works sthhow ...
I tried running my project in Xcode Version 6.0 (6A313) and received Error creating LLDB target at path '/path' - using an empty LLDB target which can cause slow memory reads from remote devices. But it runs perfectly on xcode 5.1. I think the problem with architecture of iOS 8. Is this is a serious problem i should take care of ? Anyone help me with some suggestions.