x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Migrate process doesn't take source files

Another of those bug or feature reports. Currently and I think it was the case of all previous versions, migrate process doesn't take source files with it (fbx, png). It would be great if there could be some checkbox in the migrate tool to turn on that behaviour.

Product Version: UE 4.11
Tags:
more ▼

asked May 26 '16 at 08:23 AM in Bug Reports

avatar image

GiM s.r.o.
11 1 2 3

avatar image Steve Hardister ♦♦ STAFF May 26 '16 at 05:29 PM

Hi GiM s.r.o.,

I'll be happy to enter a feature request but I don't quite understand what you're requesting. For instance, if you import a skeletal mesh into one project and migrate that to another, you can still export the fbx from the project it was migrated to. The same goes with practically all assets, as far as I'm aware.

Also when you import an fbx into a project, a copy of the original does not generate in the project folder unless that is where you chose to save it out of your native application. For example, I typically work in a folder that has all the original files (for backup) and simply import them into the UE4 project. This does not result in a copy of the original being kept in the Unreal Project folder, as mentioned above, and thus will not result in the original being copied to a different project when migrating.

With this understanding, let me know if you still feel there's a valid reason to add this feature.

Thanks,

Steve H.

avatar image GiM s.r.o. May 27 '16 at 01:48 PM

Hi Steve,

I guess my bug report or why I have considered it a bug is a bit different workflow with the engine and the asset pipeline.

We are usually exporting right into the UE project folder structure (fbx, png...) and we are using the autoimport/autoreimport feature. With that in mind, some (maybe all) features in content browser, for example rename operation would rename the fbx/png source files too, delete dialogue when deleting assets has a checkbox "to delete corresponding sourcefiles" too.

So when you are used to that, then it might feel like the migrate function should also take care of the source files. I think it really would be beneficial for this type of workflow/asset pipeline if the migrate dialogue would have a checkbox "migrate corresponding source files".

Thanks for considering this and sorry if shouldn't have been posted as bug.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Hi GiMs s.r.o.

I have entered the Feature Request UE-31405 to migrate corresponding source files along with the converted uassets and included your explanation of why this is beneficial. If this feature is adopted into the engine, we will notify you with an update to this post.

Thanks for the feedback,

Steve H.

more ▼

answered May 27 '16 at 04:45 PM

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question