I have the following parser mapping for Unreal log files:

[%d{yyyy.MM.dd-HH.mm.ss:fff}][%3t]%c: %p: %m%n
[%d{yyyy.MM.dd-HH.mm.ss:fff}][%3t]%c: %m%n
%c: %m%n
%m%n

It used to work very well, until recently where (one of) the update broke the Level such that some logs without a Level are parsed as having a Level. If I were to guess, it looks like LogViewPlus is searching for the Level with wildcards in between each character e.g., "e*r*r*o*r". Just a guess.

In the following screenshot, you can see that the log is clearly not 'Severe'. All the letters (underlined red by me) are present though (and I found that to be the case with all the logs that have incorrect Level.

Okay, great thank you.

Looking forward to a solution for this issue with Unreal logs.

Hi Samaursa,

I just wanted to let you know that we have now released LogViewPlus v3.0.1 as a BETA release.  This release allows you to define the priority levels in the parser explicitly.  This gives the parser a chance to fail if one of the specified priorities is not detected.  This failure will allow your second patten (which does not have a priority) to be used.  Log entries without a priority will still be displayed as None. 

To specify the priority levels, you need to use the new -expectedValues parameter with a comma separated list of priorities.  Values are case sensitive.  For example:

%p{-expectedValues:info,warn,error}

Hope that helps.  Thanks again for bringing this issue to our attention.

Toby

Thanks for adding the feature! I'll try it out.