Just found a new bug which let’s the engine crash Of course already written a post on the answerhub. A day where I find less than 3 bugs or get less than 30 crashes a day would be a special day…
Err… No UE-9829 fix yet;
://img.4plebs.org/boards/tv/image/1370/09/1370096830629.jpg
[=Kenomica;249838]
Sadly the instanced static mesh from construction script bug fix missed the deadline for 4.7.3 - but they’ve fixed it internally (fix available via github commit) and Epic have said the fix will be in either 4.7.4, if one comes to pass, or 4.8 if not.
So I’m definitely pleased that the is at least fixed internally and will make it to us soon
[/]
If you are in hurry, you can cherry-pick the fix(es) from github and compile the source yourself…
[=;250241]
If you are in hurry, you can cherry-pick the fix(es) from github and compile the source yourself…
[/]
Thanks, I definitely thought about it.
The Epic Staff who I was communicating with on Answerhub linked me to the exact fix, actually - but I have no experience with it, however. But It’s probably something worth learning
Hi,
I just wanted to thank you for your hard work, but also tell you that I agree with the general feeling that making a regular “stable” version from time to time would be a really great thing.
For example, look at how Canonical makes regular Ubuntu updates, but has a LTS (Long-Term Support) every 2 years.
Basically, UE4 on OS X is super unstable. I can expect a crash roughly every 30 minutes.
[=Monops;239997]
Hi!
Yes, there’s a paid support: I use it, actually. Contact epic, they will tell you everything about it.
Cheers,
[/]
DUDE how the hell do you even contact epic. There isn’t any contact information anywhere.
[= Barnette;250975]
DUDE how the hell do you even contact epic. There isn’t any contact information anywhere.
[/]
For support agreements, etc…, is the best place to start: https://www.unrealengine/custom-licensing
Cheers,
Well that was quick stupid ue4 bugs swiftly my hopes oh well
Guys shouldnt release anything until its stable coz its really irritating
[=ThomasN;251608]
Well that was quick stupid ue4 bugs swiftly my hopes oh well
[/]
[=ThomasN;251618]
Guys shouldnt release anything until its stable coz its really irritating
[/]
Hi there,
It would be helpful if you could let us know what bug or issues you are encountering. Could you please provide us a link to your post on the so we can try and help? There may be a workaround available.
Thanks!
Hoping UE-11324 will soon be fixed (crash when exiting immersive mode after having opened content). I’ve crashed so many times now because I use immersive mode so much. I’m just wondering, is specific for certain people or does have ? If you want to try it, restart the editor and go into immersive mode (make a viewport large, then press F11), open the content browser (CTRL + Shift + F) and open some content (static mesh etc.). It shouldn’t open the content and when you press F11 to exit immersive mode it should crash the editor.
[=Logithx;252046]
Hoping UE-11324 will soon be fixed (crash when exiting immersive mode after having opened content).
[/]
Hi Logithx.
UE-11324 ended up being a duplicate of another report, UE-11204. The has been fixed internally. At the moment it is slated to be included in the 4.8 release, but I’m going to start a discussion and see if it is safe to include in an earlier Hotfix.
[= ;252335]
Hi Logithx.
UE-11324 ended up being a duplicate of another report, UE-11204. The has been fixed internally. At the moment it is slated to be included in the 4.8 release, but I’m going to start a discussion and see if it is safe to include in an earlier Hotfix.
[/]
Thanks for the update, that is great news.
when we see a fix to actor child component(always disappeared when i start editor first time or build game) i see bug in 4.7 and now in 4.7.3 i don’t see a fix…
for example is one of the many posts from answerhubanswers.unrealengine/questions/193892/modifications-to-child-blueprint-actors-not-saving.html
UE-10524 Icon reports failure to add if creating a project with source control enabled
is from the 4.7.1 update but it is not fixed. After excluding the Build folder from the perforce stream, I get error when trying to compile the project files on another machine after synching. I excluded the build folder because the documentation recommends it.
Some staff marked my answerhub thread as solved but it is not, as tried with 4.7.2 and 4.7.3 and still getting errors about missing icons in the build folder. It would be nice to get some information about problem.
[= ;250058]
Err… No UE-9829 fix yet;
://img.4plebs.org/boards/tv/image/1370/09/1370096830629.jpg
[/]
I really hope for you that Epic will get a fix for in 4.7.4 Do you have an answerhub post for bug?
Some staff marked my answerhub thread as solved but it is not, as tried with 4.7.2 and 4.7.3 and still getting errors about missing icons in the build folder. It would be nice to get some information about problem.
[/]
Hi ,
The AnswerHub post was probably marked ‘resolved’ because you suggested that it be closed in your Answer. You can go ahead and un-accept that answer and post a new comment on it that it is still occurring in 4.7.3. Once opened again, Support staff will look into it as soon as possible.
Cheers
Unfortunately, I cannot the “accepted” status, it says "You don’t have permission to do action. Please Login as another ". (And I am logged in with my account). If you could help with that, would be nice.
[=;255971]
Unfortunately, I cannot the “accepted” status, it says "You don’t have permission to do action. Please Login as another ". (And I am logged in with my account). If you could help with that, would be nice.
[/]
Hmm, that’s strange. You should always be able to mark the status of your own question. We’ll do some tests on functionality. The post is “un-accepted” now (I did not do it), so maybe the server was just being weird.
Someone will be responding to the post soon.
Cheers
[= ;255295]
I really hope for you that Epic will get a fix for in 4.7.4 Do you have an answerhub post for bug?
[/]
They already marked the bug as critical, bug nobody managed to fix it yet.