Revision as of 13:25, 9 May 2022 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,395 edits →How to keep simulation console window open ← Older edit		Revision as of 13:29, 9 May 2022 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,395 edits →How to keep simulation console window open Newer edit →
Line 17: =How to keep simulation console window open= Simulation console window can display errors not written in the .tlf file and provide more information for troubleshooting: * Insert "pause" at the end of the batch file and remove any Start "TUFLOW", -b and/or -t switch. The simulation console window is the one stating for example "TUFLOW Build: 2020-10-AD-iSP-w64" in the header's top left corner. If the only console window that remains open states "C:\\WINDOWS\system32\cmd.exe" that is the batch file console window which won't provide desired information. Simple batch file as below should be used if more complex looping batch file doesn't keep the console window open even with the suggested changes. The simulation console window is the one stating with the TUFLOW build, for example "TUFLOW Build: 2020-10-AD-iSP-w64" in the header's top left corner. The batch file console window stating "C:\\WINDOWS\system32\cmd.exe" in the header's top left corner won't provide desired information. <pre>"C:\TUFLOW\Releases\2020-10-AD\TUFLOW_iSP_w64.exe" "M01_5m_001.tcf"</pre> * Or, let the console window be written to a text file, e.g. “TUFLOW.exe my_model.tcf > dump.txt”. This will redirect console output messages as well as the standard error stream to the “dump.log” file, and it will likely record more error information than the usual .tlf file.

TUFLOW crashing: Difference between revisions