4.7_P8 - Externally Referenced Warnings
This was being investigated on the forums in the 4.7 Preview thread, moving the relevant information here for clarity.
I tested out my project with preview 8 and am happy to report that the issue I was having with DynamicMaterialInstance's not being created through the Construction Script, which was preventing those materials from being applied, has been fixed in the new release.
However I am still receiving the "Externally Referenced" warnings I mentioned to Eric above. They are still being shown in the Map Check section of the Message Log, and I get a warning when I try to save the level about the externally referenced assets (which are not actually externally referenced).
I checked this with an already upgraded copy of the project, and also converted another new copy from 4.6.1 to make sure, and both of them show the warnings. It's not a big deal really but it could be confusing if left as is.
I just uploaded the newly converted copy of the project in case it will help you guys, you can download the project here: https://drive.google.com/file/d/0B3u_RPl4K60iOHIxVHpLSGsxbDg/view?usp=sharing
Eric Ketchum Replied:
Hey DotCam -
I am not finding any errors on loading your project in 4.7p8. I also spent a good amount of time trying to convert a project created in 4.6.1 to 4.7p8, both a C++ GitHub build/C++ project and a launcher variety with no success? Can you let me know if you are doing anything in C++ that would or does alter the components that are throwing the errors for you?
Let me know -
I replied back with more info:
The code is fairly straightforward, it is just a BuoyancyMovementComponent that can be attached to actors (such as the Buoy's in scene) and an OceanManager class that is the base class for the BP_Ocean blueprint. All it does is perform the calculations required for buoyancy when requested by the BuoyancyMovementComponent.
Neither of those classes affect the appearance of the ocean, they only calculate the wave height for Buoyancy. The Skydome itself is 100% blueprint. Nothing there that should be causing the warnings in editor
I deleted some files from the upload in the Intermediate, Saved, and Build folders to reduce the download size, so to make sure I just tested a fresh copy from the upload just now. When first opening the project, there are no Map Errors/Warnings, however if I go to the build button's dropdown box and select "Map Check" all of the warnings re-appear, and if I attempt to save I receive a warning dialog related to the external references error.
Would you guys prefer I create an issue on AnswerHub for this? I don't mind posting it all here, either way is fine by me. Thanks for looking into it Eric!
Upon request I have moved this over to AnswerHub, with my last post above being the latest info.
asked Feb 18 '15 at 08:32 PM in Bug Reports
Hi, I've made the the shift to v4.7 P8 from v4.6.1. I'm getting these warnings as well. But only when I open a new map in the editor. I can go between the levels in-game without any issue. I do not get any warning after quitting the level nor while loading the editor. The warning only appears when I load a new map in the editor.
Edit: Alright, I got it fixed based on a suggestion from another post with a similar issue: https://answers.unrealengine.com/questions/152144/ue461-externally-referenced-on-basic-map.html
Changing the project and folder name and then reopening it did the trick.
Bad new, the Externally Referenced Warnings problem is not fixed in Mac version 4.7.4 Good new, the rename dir tips is always fixing the problem
answered Apr 05 '15 at 07:44 PM
I was having the same issue going from 4.8 to 4.9. If you have a folder name with a "." in the name, just moving the "dot" seems to work. Hope that works for you.
answered Sep 27 '15 at 10:10 PM
I got this when converting a project from 4.8 to 4.9 and I think I found the source of the problem.
At the same time, I was looking up how to properly rename projects. I noticed that using the proper 'Create a Copy' method for making a new, updated version of an old project places everything in a folder with the same name expect for an appended version number. However, the config and project name entries were left as they were. By renaming the old project and making sure that the folder name matches the project file name, all the warnings stopped appearing.
answered Oct 12 '15 at 11:36 AM
Had the same problem switching form 4.11 to 4.12 (on Mac). To solve I had to deleted the Saved folder AND rename my project file (the yourprojectname.uproject file inside the project folder) After doing it, no more warnings at all. Hope it helps.
answered Jan 22 '17 at 11:30 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here