Print String of not taking the second line feed

Development Programming & Scripting Blueprint
, , , , ,
1
  1. Add “Print String” block
  2. Enter to field “In String” any symbols and return (SHIFT+ENTER)
  3. Apply entering string (Enter)
  4. Go to field “In String” to edit and append return (SHIFT+ENTER)
  5. Crash.

Regards.

2

Hey -

Can you provide the callstack and log files from the crash? If you’re able to reproduce the crash in a new project, can you also elaborate on your reproduction steps? I tried creating a print string node and then entering a character (%) followed by Return (shift+enter), accept (enter), Return (shift+enter) in the In String field and did not get a crash on my end.

3

Hey

Yes of course.

Try it like this.

  1. Create a new BluePrint
  2. Open, go to EventGraph
  3. Add PrintString block
  4. In the “In String” at the end of the line to press shift + enter
  5. Click outside the box or press enter to save
  6. Once again, go into the field and at the end again press shift + enter

[link text][1]

112519-cr.png
112519-cr.png750×594 53.5 KB

4

Did this reproduce in a new project for you as well? I tried the steps you provided but I am still not getting a crash to occur after the second time using Shift+Enter. Just to make sure I am understanding correctly, you are using the Print String node shown here, correct?

112578-printstring.png

5

Tried to reproduce it but nothing happened.

6

Yes, if try create in a new project – Blank and add new Actor, trouble saved.
I attached video.

7

Try several times, perhaps there is some really random sequence.

8

Hey -

Can you provide your dxdiag to provide additional information? Additionally, can you copy the output of the Crash Report window so that I may add that to the report?

9

Yes of course.

link text
link text

10

Hey -

Thank you for submitting a bug report. I was unable to reproduce the issue locally however I have logged a report for it here Unreal Engine Issues and Bug Tracker (UE-37890) . You can track the report’s status as the issue is reviewed by our development staff.

Cheers