2 LogCook:Warning: Found unparsable ini setting Windows.EditorPerProjectUserSettings:DetailCategories:FirstPersonCharacter_C.Character Movement: Walking:0 for platform WindowsNoEditor, invalidating cook.
What is this warning and how bad it affects packaging game?
I had this same warning appear for myself as well. Remove the intermediate and saved folders under your project folder. This should clear the invalidating cook warning. The only thing I have noticed though is that it will fix the warning for only so long. In my project it will come back every now and then but the solution is to remove those two folders. Sometimes removing the hidden UnrealEngine folder under your AppData folder will also clear any strange issues.
Correct, I still experience this in my project so this actually might be a bug within the engine itself, I’m hoping an Epic Staff member can chime in on this.
I tried to use Fix Up Redirectors in Folder, nothing changed.
Also “showing all actors using this asset” selects my AI child class that never actually uses it but doesnt select my FirstPersonCharacter that uses it
Well, I cant provide any details since there are no errors in actual gameplay or packaging… Seems like some redirections have been fckd up. Can I check them on my side somehow?
Verified, nothing changed. Btw Im using 4.14.0 version. Didnt find anything what bothers me in hotfixes. Is it safe to upgrade project with hotfixes? If so I can try it and say result.
In most cases it should be safe to upgrade to the latest hotfix. A hotfix is used to add in any major fixes that may have been over looked on the original release.
LogCook:Warning: Found unparsable ini setting Windows.EditorPerProjectUserSettings:DetailCategories:SideScrollerCharacter_C.Character Movement: Walking:0 for platform AllDesktop, invalidating cook.
This is in a side scroller template project with a few changes… I am not sure if it produced this bug in previous versions. I am a noob and accidentally clicked “Launch” for the first time.
It doesn’t impact me for now, I just wondered if I could help replicate this bug more.
After doing a bit of digging I was able to find that this is a known issue. I have provided a link to the public tracker. Please feel free to use the link provided for future updates. Thank you for your time and information.
I will need you to create a new thread for the second question for tracking purposes. After this you can place a link in a reply here and I will be happy to follow up. One test I would like you to try (please post the information gathered on the new thread), is migrating the asset that is not being found to a new project and let me know if the error still occurs.