Issue with fstring Function Not Correctly Handling Certain String Formats

[chendongde310]

Hello [Author/Developer Team],

I've encountered an issue with the fstring function in the ReaderUasset prototype, where it seems to incorrectly handle or interpret certain string formats, particularly strings containing underscores followed by numbers. For example, a string like M_dviz_Plants_a_x_2 is unexpectedly read as M_dviz_Plants_a_x, omitting the trailing digit.

Expected Behavior:
The expected behavior is for the fstring function to accurately read and return the full string as it appears in the data, including any numbers or special characters following an underscore.

Actual Behavior:
When reading strings formatted with an underscore followed by numbers, the numbers are ignored, and the string is truncated at the underscore. This behavior is consistent across multiple tests and seems unrelated to the specific data set.

Possible Issues:
Upon reviewing the provided fstring function code, there doesn't seem to be explicit logic that would cause this behavior. The issue might stem from how the string lengths are calculated or how bytes are read and interpreted in the presence of special characters.

Suggested Next Steps:
I am unsure if this behavior is intended or if it's a bug. It would be greatly appreciated if you could provide some insight into this issue, and whether there's a workaround or fix that I can apply.

Thank you for your time and assistance. Looking forward to your response.

[rancoud]

Hello, do you have an uasset with that problem as an example to share here?
Maybe I can find a pattern on how/why it failed.