Since I started with 4.1 and created a new Landscape Map with some of the Textures of the newly added Elemental Demo, I kind get Errors when I submit to Perforce. When I look at it it wants to add Engine Content to Depot. Now evidently it isn’t under my workspace and shouldn’t be as far as I am concerned.
Can someone help me to understand what happened or am I just facing some kind of bug?
During the sculpting, import and materials creation it wasn’t any issue, it occurred after I uploaded my Landscape Map for the third time.
The log doesn’t look like its trying to add engine content - those ‘errors’ usually come from fstats and are usually just a warning when you view engine content in the content browser, as the editor ends up querying the source control status of those files.
Could you post a full text log (found in /Saved/Logs) from when you experienced the issue?
From the log you posted, it looks like the checkin succeeded with no issues.
The benign output you are seeing is coming from the Editor checking all the assets it knows about before displaying the “submit to source control” dialog. We need to check engine content in this process because internally we do change engine content & submit it to Perforce.
FWIW, previous to 4.1 the dialog would have displayed the engine content, requiring you to manually uncheck all the files.
Yeah I saw it was successful, but I will get still that error output than regularly that Engine isn’t within the workspace? So basically this is how it should suppose to be? Because I get it now every time I submit.
Oki after I tested it again the Error is gone and they are just now warnings. And that’s fine. Just the error made me uneasy. Thanks a lot for the help!
What you see now is how it is supposed to be now when using the “submit to source control” option.
The fact that the first log entry of that kind is reported as an error in the log is odd (they are all reported as warnings). There may be a bug in the message log somewhere.
I see now - that first error is reported on initial connection, rather than when you go to check in. Safe to ignore, although I should strip that error out too, like the others.
