Using a very specific way of importing an FBX will cause a crash assertion that closes the editor without opening crash reporter. Essentially when using the import button in the content browser and ...
REGRESSION: YesWORKING: 3132914 (Dev-Editor merge into Main)BROKEN: 3133983 FBX files referencing external textures via absolute path are no longer resolved correctly. This used to work - as seen w ...
A licensee reported this issue on UDN. They are seeing a discrepancy with animations imported from Maya. In this case, they appear to be off by 1-frame. We've talked about this on Slack and I know ...
This is a regression in behavior between 4.14.1 and 4.14.2! The editor will crash when importing FBX meshes that have multiple material ID assignments. If it's a single material ID it will import w ...
Not all material elements are created and assigned to the static mesh using multiple materials. With the attached mesh, only the first element is created and the other two are left non-existent. I c ...
In UE 4.20 we got a feature that let you import a FBX file that contains cameras with a camereaswitcher to create a "camera cut track" within sequencer. From the release notes of 4.20: https://docs ...
This Jira was created from CrashReports submitted by the public due to the high number of occurrences. Descriptions from users are provided below. Error message: Access violation - code c0000005 ( ...
The reimport process does not respect the new source path. Below is a workaround. UE::Interchange::FAssetImportResultRef FReimportManager::ReimportAsync(UObject* Obj, bool bAskForNewFileIfMissing, ...
Error message: Assertion failed: (Index >= 0) & (Index < ArrayNum) [Link Removed] [Line: 633] Array index out of bounds: 68 from an array of size 68 Source Context: 733 734 Extrac ...
It looks like when reimporting a texture asset into the engine after loading a level, you will be confronted with the File Selection box and not the reimport successful notification. In fact if you ...