Fatal Error! 4.7 when player trigger blueprint event
I have moved up from 4.4 to 4.7, and after packageing the game (win32 shipping build) the game will fatal error crash when the player triggers a blueprint event on a character blueprint. The project uses unmodified 4.7 Shooter Game code as base.
This crash would not happen in the past, and I cant see why it is happening? Any advice would be appreciated! The blueprint the player triggers is a Mixamo character blueprint, player can trigger an event by proximity. I also currently have problems hosting multiplayer games, wich also worked great in the past. Clients will find the hosted servers, but never be able to connect to them. Thanks for any help!
asked Mar 18 '15 at 09:09 PM in Bug Reports
I talked with one of our coding support guys about this. Basically, our recommendation is usually that people don't try to prototype in Shootergame (or any of our other more complex code samples).
That being said, I'd like to try something that might...MIGHT be a workaround for this, but the only way to know is for you to try it. I don't know if you've done any code changes or what parent classes you're using for your blueprints, but if you haven't, try this (try it anyways if you have):
I have some doubts that this will work, but worth a shot.
In the future we DO NOT recommend prototyping or developing based off of a code sample if you aren't intimately familiar with the code for that project.
answered Mar 30 '15 at 06:30 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here