Hi there - I can compile my project fine (both normally and with nativisation), but when nativising, even exclusively one simple blueprint, I get the following error when attempting to run the packaged game:
Hi , thanks for the reply! I am packaging for Win64, using Exclusive nativisation.
The easiest way to reproduce it is to nativise the BP_PlayerCharacter blueprint from the Generic Shooter marketplace addon. I have not tried to nativise level or macro blueprints.
Looking forward to hearing from you again, best of luck trying to find the cause! if you need any more info dont hesitate to get in touch.
Lawrence
It took a while to coordinate getting the Generic Shooter authorized to check out for testing nativisation. My results following your repro steps were (Following steps for Exclusive Nativization):
UATHelper: Packaging (Windows (64-bit)): UE4Editor-Cmd: [2017.03.07-19.55.54:467][ 0]LogInit:Display: LogBlueprintCodeGen:Error: BP /Game/GenericShooter/BlueprintLogic/BP_PlayerCharacter.BP_PlayerCharacter is selected for nativization, but BP interface class /Game/GenericShooter/BlueprintLogic/Interfaces/BPI_CanOverrideDamage.BPI_CanOverrideDamage_C is not
When I nativised that file, it would not successfully compile due to other erros so I attempted to repro the issue by nativising the ThirdPersonCharacter Blueprint from the Third Person Blueprint project template. (Note that the Generic Shooter is currently not tested/approved for UE4.15 so this may be the cause of the issue.)
This compiled successfully with the nativised asset, so the issue does not appear to be with a bug with nativisition per se, but something that needs to be adjusted in the Generic Shooter file to work with nativization.
If you can reproduce the issue with a project that is meant to work with UE4.15 specifically, we will continue to investigate the issue.
I have the same error when running a nativized project. I have tried to reproduce it on a new project but failed, it may have to do that I run a converted old project (Started building my game with version 4.7).
I could give you access to our current project that shows this behavior when trying to nativize but it is currently close to 10GB uncompressed. If that’s the case then how do I get in contact with you directly? As I don’t want to add a link here for everyone to download.
Hi , thanks for your attempt, but you seem to have missed the issue - I was able to compile and nativize without errors. the errors occurred when the successfully packaged build was run.
Also - what do you mean by designed for 4.15 specifically? there is no guidelines for nativisation regarding what is and isnt supported per se, so if my project which runs perfectly in all aspects in 4.15 apart from nativisation, errors when running the nativised build it sounds like its an issue with the engine. If not, please can you point me to any documentation regarding what is, or isnt, supported by nativisation.
Judging by the other comments I am not the only person who is having the issue so being told to try to reproduce it by recoding my entire project from scratch in 4.15 with no documentation as per what to look out for while aiming for nativisation still leaves us up the proverbial creek with no paddle.
Regards,
Lawrence
2sneaky: I think means that the Generic Shooter template does not work in 4.15 without changes, so he wonders if you can convert the Generic Shooter to a 4.15 build that stills shows the error. That would at least be a bit smaller than my 10GB project to work with.
My guess is that it has something to do with convertion of enums from an old project ( < 4.15 ) to a 4.15 project and then nativizing it. But that’s just pure speculation on my part.
If it wasn’t clear, I did run my packaged test after nativizing the 3rd Person Blueprint without errors or crashing. I was not, however, able to package the Generic Shooter due to a large number of errors, so I could not test the packaged results.
Since I’m assuming that when you don’t nativise you are not getting the error when attempting to run your packaged game, the best way to resolve this is to compare apples to apples so to speak.
To that end, if you would be willing to send a copy of your project for testing, you can send a link to your zipped file on Dropbox, Google drive, etc in a private message to me on our . This would help get to the root of the problem significantly faster.
Hey guys, I’m running into this problem as well. Project builds fine with exclusive blueprint nativization. I’m on 4.18.2. Running the packaged game gives the LowLevelFatalError, AsyncLoading.cpp, FAsyncPackage::FindExistingImport class mismatch ByteProperty != EnumProperty error.
Disabling nativisation fixes the issue and the packaged game runs fine.
By changing from exclusive to inclusive it seemed to fix this error. I am running into some different errors on some machines with blueprint nativization, seems to be a pretty buggy feature sadly.
