TUFLOW crashing - Revision history

Teegan.Burke at 05:30, 1 April 2026

2026-04-01T05:30:34Z

← Older revision		Revision as of 15:30, 1 April 2026
Line 52:		Line 52:
	</ol>		</ol>
	<br>		<br>

			=TUFLOW pauses at any time during simulation=
			'''Causes''':
			*Ctrl+S shortcut has been activated.
			*Windows 10 Quick Edit Mode is active.
			'''Suggestions:'''<br>
			See <u>[[Console_Window_Simulation_Paused]]</u> for further guidance.


	=TUFLOW crashes during model initialisation=		=TUFLOW crashes during model initialisation=

Pavlina Monhartova: /* Console window lists all licences and model doesn't run */

2026-01-21T23:25:58Z

Console window lists all licences and model doesn't run

← Older revision		Revision as of 09:25, 22 January 2026
Line 119:		Line 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.		* 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>		<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==		==Running very old TUFLOW releases==

Pavlina Monhartova: /* TUFLOW crashes at the end of the simulation before writing out maximum results */

2025-09-03T07:30:00Z

TUFLOW crashes at the end of the simulation before writing out maximum results

← Older revision		Revision as of 17:30, 3 September 2025
Line 85:		Line 85:

	=TUFLOW crashes at the end of the simulation before writing out maximum results=		=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>		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 filled to the brim, as performance will suffer for all processes.<br>
	'''Suggestions:'''		'''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.		* 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.

Abigail.lillo at 05:09, 22 August 2025

2025-08-22T05:09:21Z

← Older revision		Revision as of 15:09, 22 August 2025
Line 159:		Line 159:
	)		)
	pause</pre>		pause</pre>


			{{Tips Navigation
			\|uplink=[[TUFLOW_Modelling_Guidance \| Back to TUFLOW Modelling Guidance]]
			}}

Pavlina Monhartova: /* No TUFLOW dongle and licence settings files found (.lcf and .dcf) */

2025-08-11T04:26:14Z

No TUFLOW dongle and licence settings files found (.lcf and .dcf)

← Older revision		Revision as of 14:26, 11 August 2025
Line 125:		Line 125:

	==No TUFLOW dongle and licence settings files found (.lcf and .dcf)==		==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~~. Not having these files doesn't prevent TUFLOW from running, the .tlf should continue past these lines and if there is an error, it would be written as the bottom of the .tlf.		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 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==		==Technical licence issues==

Abigail.lillo: /* How to keep simulation console window open */

2025-08-06T03:52:26Z

How to keep simulation console window open

@@ Line 21: / 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.
+: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.
 * 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>

Abigail.lillo: /* How to keep simulation console window open */

2025-08-06T03:45:46Z

How to keep simulation console window open

← Older revision		Revision as of 13:45, 6 August 2025
Line 22:		Line 22:

	* 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.		* 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.
			<ol>

	[[File:TUFLOW Simulation Console with Build Info Displayed.png\|frameless\|600x600px]]		[[File:TUFLOW Simulation Console with Build Info Displayed.png\|frameless\|600x600px]]
			</ol>

	* ~~The~~ batch file console window, ~~which~~ ~~shows~~ "C:\WINDOWS\system32\cmd.exe" in the ~~top-left~~ ~~corner,~~ ~~does~~ not display the desired simulation output, as shown ~~in the image~~ below.		* 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]]		[[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.		* 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>		<pre>"C:\TUFLOW\Releases\2020-10-AD\TUFLOW_iSP_w64.exe" "M01_5m_001.tcf" > dump.txt</pre>

	=Simulation console window flashes and disappears=		=Simulation console window flashes and disappears=
	When batch file is double clicked and the simulation DOW window flashes and disappears the problem might be in the filepath of the TUFLOW executable or incorrect syntax.<br>		When batch file is double clicked and the simulation DOW window flashes and disappears the problem might be in the filepath of the TUFLOW executable or incorrect syntax.<br>

Pavlina Monhartova: /* Console window lists all licences and model doesn't run */

2025-06-11T01:31:52Z

Console window lists all licences and model doesn't run

← Older revision		Revision as of 11:31, 11 June 2025
Line 110:		Line 110:
	During the licence check, one licence from each available module is temporarily reserved. These are released either immediately by pressing Enter, or automatically after a few minutes when the console window is closed.		During the licence check, one licence from each available module is temporarily reserved. These are released either immediately by pressing Enter, or automatically after a few minutes when the console window is closed.

	Once the licences are released by pressing Enter, the console window displays "Not licenced or no local licence free". This confirms that the licences are no longer reserved and are available for running TUFLOW models.<ol> [[File: Licence_Check_2.png \| 600px]]</ol>		Once the licences are released by pressing Enter, the console window displays "Not licenced or no local licence free". This confirms that the licences are no longer reserved by the licence check and are available for running TUFLOW models.<ol> [[File: Licence_Check_2.png \| 600px]]</ol>
	The licence check is performed in the following situations:		The licence check is performed in the following situations:
	* Double clicking a TUFLOW executable.		* Double clicking a TUFLOW executable.

Abrar.Alttahir: /* How to keep simulation console window open */

2025-05-15T01:05:02Z

How to keep simulation console window open

← Older revision		Revision as of 11:05, 15 May 2025
Line 14:		Line 14:

	=How to keep simulation console window open=		=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:		The simulation console window can display errors not written to the .tlf file and often provides additional information useful for troubleshooting:

	* Insert "pause" at the end of the batch file and remove any Start "TUFLOW", -b and/or -t switch. Simple batch file as below should be used if current batch file doesn't keep the console window open even with the suggested changes.
			* To ensure the console window remains open, add pause at the end of the batch file and remove any Start "TUFLOW", -b, or -t switches. If the console window still closes, use a simplified batch file like the example below.
⚫	**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"		"C:\TUFLOW\Releases\2020-10-AD\TUFLOW_iSP_w64.exe" "M01_5m_001.tcf"
	pause~~</pre>~~		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]]

		⚫	* The batch file console window, which shows "C:\WINDOWS\system32\cmd.exe" in the top-left corner, does not display the desired simulation output, as shown in the image below.

			[[File:Batch File Console Showing CMD Header Only.png\|frameless\|600x600px]]
	* 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.		* 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>		<pre>"C:\TUFLOW\Releases\2020-10-AD\TUFLOW_iSP_w64.exe" "M01_5m_001.tcf" > dump.txt</pre>
	<br>

	=Simulation console window flashes and disappears=		=Simulation console window flashes and disappears=
	When batch file is double clicked and the simulation DOW window flashes and disappears the problem might be in the filepath of the TUFLOW executable or incorrect syntax.<br>		When batch file is double clicked and the simulation DOW window flashes and disappears the problem might be in the filepath of the TUFLOW executable or incorrect syntax.<br>

Abrar.Alttahir: /* Console window lists all licences and model doesn't run */

2025-04-24T04:48:11Z

Console window lists all licences and model doesn't run

← Older revision		Revision as of 14:48, 24 April 2025
Line 100:		Line 100:

	==Console window lists all licences and model doesn't run==		==Console window lists all licences and model doesn't run==
	If the console window ~~looks~~ ~~like~~ ~~the picture~~ below, ~~ending~~ with ~~last~~ line "Press ENTER to Release WIBU Licences", a licence check was performed. ~~TUFLOW~~ ~~model does not run when~~ licence check is ~~performed~~ ~~and~~ a ~~a .tlf file~~ does not ~~get~~ produced. Licence check temporarily takes one licence from every available module until the licences are released by pressing Enter (released immediately) or by closing the console window (released after a ~~couple of minutes)~~. ~~Once~~ ~~licenses~~ ~~are~~ ~~released by pressing Enter, the console window shows “Not licenced or no local licence free”~~. ~~This means the licences are no longer taken by the licence check and can be used for running TUFLOW models. <br>~~		If the console window appears as shown below and ends with the line "Press ENTER to Release WIBU Licences", this indicates a licence check was performed. When a licence check is run, the TUFLOW model does not execute, and a .tlf file is not produced.

	<ol> [[File: Licence_Check_2.png \| 600px]]</ol>
			During the licence check, one licence from each available module is temporarily reserved. These are released either immediately by pressing Enter, or automatically after a few minutes when the console window is closed.

			Once the licences are released by pressing Enter, the console window displays "Not licenced or no local licence free". This confirms that the licences are no longer reserved and are available for running TUFLOW models.<ol> [[File: Licence_Check_2.png \| 600px]]</ol>
	The licence check is performed in the following situations:		The licence check is performed in the following situations:
	* Double clicking a TUFLOW executable.		* Double clicking a TUFLOW executable.
	* Running a batch file ~~with~~ only TUFLOW executable ~~specified~~.		* Running a batch file that only specifies the TUFLOW executable.
	* Running TUFLOW from Notepad++, ~~when inserting~~ only the TUFLOW executable into the Run function text box.~~<br>~~		* Running TUFLOW from Notepad++ with only the TUFLOW executable inserted into the Run function text box.
	Suggestions to run a TUFLOW model:		Suggestions to run a TUFLOW model:
	* Include the model .tcf name in the batch file. See <u>[[Running_TUFLOW \| Running TUFLOW model]]</u> for further guidance.		* Include the model .tcf name in the batch file. See <u>[[Running_TUFLOW \| Running TUFLOW model]]</u> for further guidance.