TUFLOW crashing: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 13:45, 6 August 2025 view source Abigail.lillo (talk \| contribs) Bureaucrats, Administrators 539 edits →How to keep simulation console window open ← Older edit		Latest revision as of 09:25, 22 January 2026 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,385 edits →Console window lists all licences and model doesn't run
(4 intermediate revisions by 2 users not shown)
Line 21: pause * :The simulation console window is the one that displays the TUFLOW build (e.g. "TUFLOW Build: 2025.0.3-iSP-w64") in the top-left corner of the window header, as shown in the image below. :[[File:TUFLOW Simulation Console with Build Info Displayed.png\|frameless\|600x600px]]▼ ~~<ol>~~ ▲[[File:TUFLOW Simulation Console with Build Info Displayed.png\|frameless\|600x600px]] * :If start "TUFLOW" is included in the batch file, the console window will instead show "C:\WINDOWS\system32\cmd.exe" in the window header and will not display the desired simulation output, as shown below.▼ ~~</ol>~~ :[[File:Batch File Console Showing CMD Header Only.png\|frameless\|600x600px]]▼ ▲* If start "TUFLOW" is included in the batch file, the console window will instead show "C:\WINDOWS\system32\cmd.exe" in the window header and will not display the desired simulation output, as shown below. ~~<ol>~~ ▲[[File:Batch File Console Showing CMD Header Only.png\|frameless\|600x600px]] ~~</ol>~~ * Or, let the console window be written to a text file. This will redirect console output messages as well as the standard error stream to the “dump.txt” file, and it will likely record more error information than the usual .tlf file. <pre>"C:\TUFLOW\Releases\2020-10-AD\TUFLOW_iSP_w64.exe" "M01_5m_001.tcf" > dump.txt</pre> Line 87 ⟶ 85: =TUFLOW crashes at the end of the simulation before writing out maximum results= The output drive might not have enough free space to write out the full results. If multiple TUFLOW simulations run in parallel, the free space might be filling up faster than expected. There can also be other processes filling up the drive, e.g. other software, backups, other users copying data. The target drive should never ~~be planned to~~ be filled to the brim, as performance will suffer for all processes.<br> '''Suggestions:''' * Ensure storage locations that outputs are written to have enough free space. Depending on the infrastructure, reported free space may not be accurate, or performance of storage may substantially degrade as it nears being full. Line 121 ⟶ 119: * Insert the full required text (example line below) into Notepad++ Run function text box. See <u>[[NotepadPlusPlus_Run_TUFLOW \| Running TUFLOW from Notepad++]]</u> for further guidance. <ol> "C:\TUFLOW\2025.0.3\TUFLOW_iSP_w64.exe" "$(FULL_CURRENT_PATH)" </ol> * See detailed steps on how to run a TUFLOW model in the <u>[[Tutorial_M01#Running_the_Simulation \| Tutorial model]]</u>. ==Running very old TUFLOW releases== Line 127 ⟶ 126: ==No TUFLOW dongle and licence settings files found (.lcf and .dcf)== Some users might mistake this sentence in the .tlf file as there is an issue with the licence. The "No TUFLOW licence settings files found" sentence is followed by "Default settings applied" and the default settings are listed on the next three lines, e.g. WIBU Retry Time, WIBU Retry Count, WIBU Dongles Only. Only if these settings are required to be different, the licence control file (.lcf) or dongle control file (.dcf) would be ~~created~~required. Not having these licence files doesn't prevent TUFLOW from running, it would automatically use the default licence settings. The .tlf should continue past these lines and if there is an error, it would be written as the bottom of the .tlf. ==Technical licence issues== Line 161 ⟶ 160: ) pause</pre> {{Tips Navigation \|uplink=[[TUFLOW_Modelling_Guidance \| Back to TUFLOW Modelling Guidance]] }}