open TELEMAC-MASCARET The mathematically superior suite of solvers

Hello BK Community,

I've encountered a bug in BK 3.12.28 related to .2dm import and .t3s export.

• Importing a .2dm file works fine—there are no error messages, and the mesh displays correctly.
• However, after saving it as .t3s and trying to reimport the .t3s file, I get the error: "FileType mismatch."

Additionally, if I try to create a Selafin file from the imported .2dm, one of the mesh nodes loses its coordinates.

When opening this Selafin file in another software (e.g., QGIS), I see NaN values, and the spatial extent is incorrect.

This issue did not occur in BK 3.12.23.

Has anyone else experienced this? Any workarounds?

Thanks for your help!

Confirmed fault. Saving the 2DM object to a single frame ASCII T3S file seems incorrect. I will investigate further...

The released version of Blue Kenue (i.e. 3.3.4) also has this same fault; so I have not introduced a NEW bug (yah me!):

• Import a 2DM file
• Save the loaded object as an ASCII T3S file
• Load the T3S file
• A FileType mismatch dialog box will appear

The next Blue Kenue installer will have this fault fixed.

Kindly... Alan

This happens when dragging a 2DM mesh to a new Selafin object. Internally, a 2DM object is copied into a new 2D T3 Scalar Mesh object. That internal process uses X and the current attribute from the 2DM mesh to create X and Y in the new mesh object.

• You can test this by changing the 2DM object's current attribute to "Y"
• Then copy the 2DM object to the new Selafin object

In any case, I will fix it so that "X" and "Y" will be used instead of "X" and "Current Attribute".

Sorry about that!

Kindly... Alan

I have added fixes for these issues so that the next installer created on or after 18 February 2025 will no longer contain these faults.

Kindly... Alan

Please upgrade to BK 3.12.29 - beta as per post #46275

Kindly... Alan