I see what you mean. The "Process Physical Memory" got consumed and is not part of the Message column.

It would be great to have the option similar to what you suggested "require an exact match"

Thanks for the feedback.  

It would be great to handle this scenario better.  LogViewPlus is close to achieving what you want without custom code, but the last 5% is still needed.  I will try and think of a way that this can be done without complicating the configuration.  

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.