4.8.3 -> 4.10.4 conversion: 300 errors/warnings

Hello,

we have a rather large project that we developed in 4.8.3 and tested now the conversion to 4.10.4.
We get a very large amount of errors and warning, which do not seem to have effect on the running game PIE.
Everything seems to be running fine apart form some minor material issues and other minor things.
Please find a list attached.

Our question is:

Can we ignore the warnings and

errors and just go on, or do we have to solve them somehow? In other words, are they really bad or are they the kind of errors that ‘can just be ignored’? If they are ‘to be ignored errors’, can we switch them off somehow to not show up everytime we open the project?

Before converting the project, have you tried fixing up redirectors in your content browser? To do so, RMB the “Contents” folder and press “Fix up redirectors”. Does this cause the errors to go away?

We just tried a few times. Unfortunately fix up redirectors does not help. We never did it before because all was fine in 4.8.3, and therefore it took quite long now, but it went through. It threw one message though. We forced delete here.
Is there a feature planned that fixes the redirectors automatically and takes it off the users head?

when you look through the errors, then there are also things in there that are not content brought in by the user. Engine specific things like World Info, Sensing component etc…Things we do not even know what they mean tbh.

There are more post about this. It is a know problem and it seems to have made it into 4.10.4.

There seem to be workarounds. Although a fix would be better, as those workarounds touch config files and ini files, which instantly makes one feel uncomfortable that this might backfire at some other end, which you might not even notice immediately but only weeks or months later. The work arounds are not really suited for larger projects, but only for smaller projects. They contain an inherent risk.

Hi BlueBudgie,

I’ve entered a new bug report for this, UE-28509, to be assessed by the development staff.