The 4.10.4 Hotfix is now live! This Hotfix corrects an issue that was unintentionally caused by the previous update. We apologize for any difficulties this may have caused.
Fixed in 4.10.4- CL#2872498
Fixed! UE-27124 Switching levels via blueprints crashes editor
[=Kanizitas;479021]
Ok! One change, lets see how much GB it is worth :,D
[FONT=Arial Black]1.9 GB
[/]
You do realize how inheritance works right?
I had no issues with it maybe I didnt try any BP level loads but thanks for fixing what would’ve caused huge headaches for so fast. I wasnt even aware. Epic = awesome.
I might be over my head , I’m entirely new to this. I’m an artist during the day, trying to figure the rest out by night. My goal is to build a project to share with some friends and I’m somewhat stuck…
It is my understanding that I should be building 10.3? I have tried to build 10.3 by choosing it under releases, but I keep ending up with 4.11 when I launch the editor. Tonight I changed my default branch to 10 and when I build in Vis and launched the editor it popped up 10.4. I’m a bit lost.
How do I ensure the build I am going to fork and clone will be 10.3? How do I check it before running bats and building Vis ? Is 10.4 ok to use at this point or do I really need to be using 10.3… Or is it 10.0 that is most stable…
Thanks in advance! Any help sorting this out would be greatly appreciated.
Quick question about 4.10.4 release
If I look at github, the following change is included in 4.10.2,4.10.3,4.10.4.
but if I look in the source code with 4.10.4 (launcher), I can’t find ListenForInputAction function and this function is also not “callable” from a UserWidget in the BP UMG Editor.
Could you please tell me what’s wrong with this? Do the GitHub tags are not good? Is it a release build failure ? Should I raise an Answerhub for this?
I’m really looking at this function at it will solved some case that I was facing recently in UMG.
[=SpacemanChuck;484357]
I have tried to build 10.3 by choosing it under releases, but I keep ending up with 4.11 when I launch the editor.
[/]
This is probably because of an issue on GitHub where the Releases branch unintentionally has the 4.11 Preview code on it. There is a note regarding this on the ReadMe. https://github.com/EpicGames/UnrealEngine
“Important: The Release branch has unintentionally been overwritten with code from the 4.11 Previews, and is not currently the latest and stable release. Please use Tags to grab the latest 4.10 release for our most stable version. This message will be removed when this matter has been resolved.”
[=SpacemanChuck;484357]
Is 10.4 ok to use at this point or do I really need to be using 10.3… Or is it 10.0 that is most stable…
[/]
As I discussed elsewhere, 4.10.3 had a rather bad crash in it that was fixed in 4.10.4. You definitely want to be on 4.10.4 (and as a general rule, users should always update to the latest Hotfix version, since hotfixes are almost exclusively just filled with bug fixes)
[=]
Quick question about 4.10.4 release
If I look at github, the following change is included in 4.10.2,4.10.3,4.10.4.
but if I look in the source code with 4.10.4 (launcher), I can’t find ListenForInputAction function and this function is also not “callable” from a UserWidget in the BP UMG Editor.
[/]
[=;484391]
Quick question about 4.10.4 release
If I look at github, the following change is included in 4.10.2,4.10.3,4.10.4.
but if I look in the source code with 4.10.4 (launcher), I can’t find ListenForInputAction function and this function is also not “callable” from a UserWidget in the BP UMG Editor.
Could you please tell me what’s wrong with this? Do the GitHub tags are not good? Is it a release build failure ? Should I raise an Answerhub for this?
I’m really looking at this function at it will solved some case that I was facing recently in UMG.
thanks,
[/]
Hi ,
I did some checking on this with the help of , and we were able to confirm that this function is present in the 4.11 preview, but not in any of the released versions of 4.10. I suspect what happened was due to our mistakenly including 4.11 previews in the Release branch. That messed up the history of the Release branch a little bit, and it would appear that in this case (and I’m sure there are probably others as well), it caused GitHub’s automated systems to assume that the change was put into both 4.10 as well as the 4.11 preview builds.
So, just to confirm. The function you asked about is NOT in 4.10, but IS present in 4.11. Sorry for any confusion this caused.