After "Push Verse Changes" Print messages no longer appear in Output Log

Summary

Start a UEFN session and Launch Session. Print messages from Verse will appear in Output log. End game then make a verse change and “Build Verse Code” and then “Push Verse Changes” Print messages no longer appear in Output Log.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Other

Steps to Reproduce

Start a UEFN session and Launch Session. Print messages from Verse will appear in Output log. End game then make a verse change and “Build Verse Code” and then “Push Verse Changes” Print messages no longer appear in Output Log.

Expected Result

Print messages should appear in Output Log

Observed Result

No messages appear in output log

Platform(s)

PC

Anyone else seeing this? Still an issue for me

1 Like

Just tested for you for extra support and it doesnt show after you push the first change.

It only shows

LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.
LogVerse: File path did not pass sanitization check.

Instead of the correct prints

3 Likes

FORT-867814 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

2 Likes

Thank you for doing this!

2 Likes

The messages do appear on screen and in the Creative 1.0 log section, just not in output log.

2 Likes

Yea but the log is good you can use the window/message log/verse section but it should show in the output log as it always has

1 Like

Window, message log, verse section doesnt seem to show messages all the time. Am I the only one who uses the output log? Wasnt fixed in 34.10