Change Details

Make sure this doesn't break the gcc debug build. Verify the behavior is the same as before and intended. How do I test this in Profiler2 https://trac.wildfiregames.com/wiki/Profiler2 ?

Make sure this doesn't break the gcc debug build. Verify the behavior is the same as before and intended. That the correct string is processed can be tested by adding a `Engine.ProfileAttribute("hello");` to a system simulation component init, running a non-visual replay, and searching in the `profile2.jsonp` for `hello`. One can add a string > the max length in JS and see that it will be truncated with three dots rather than trigger the ENSURE.

Make sure this doesn't break the gcc debug build. Verify the behavior is the same as before and intended. That the correct string is processed can be tested by adding a `Engine.ProfileAttribute("hello");` to a system simulation component init, running a non-visual replay, How do I test this in Profiler2 https://trac.wildfiregames.com/wiki/Profiler2 ?and searching in the `profile2.jsonp` for `hello`. One can add a string > the max length in JS and see that it will be truncated with three dots rather than trigger the ENSURE.