[= ;238363]
So if a bug occurs in one version like 4.7 is it not supposed to get fixed in a hotfix but only in 4.8 except it is causing a crash? If every bug which was introduced in some major update will only get fixed in the next major update there will never be a version where everything works…
So for example UE-9829 broke something which worked in 4.6.1. You say it will probably only get fixed in 4.8. So if someone really needs to work he can’t use 4.7 at all. But 4.8 will have new features and totally new bugs, which may cause the same person to also not be able to use 4.8, because the fixes for the bugs intruduced with 4.8 will only come in 4.9 and so on…
So it’s really gambling whether a major version is usable at all for someone.
[/]
The focus is stability for sure. is the point of the preview releases to help get a more stable version and is why is the method being used on forward. It can be frustrating when bugs happen and I’m sorry for that.
If you have any concerns regarding the stability or release method you can always post a thread in the feedback section.
I think it is nice idea to make version 4.10 special. Imagine that 4.9 and 4.8 will bring new features and there will be no new features in 4.10, whole Epic Games team would be working all time on bugfixes to make 4.10 version super stable. I really like that idea. What do you think ?
[= ;238403]
The focus is stability for sure. is the point of the preview releases to help get a more stable version and is why is the method being used on forward. It can be frustrating when bugs happen and I’m sorry for that.
If you have any concerns regarding the stability or release method you can always post a thread in the feedback section.
[/]
Chuck performance onto that bandwagon and it’ll be the best engine there ever was.
[=pixelvspixel;228501]
Hahaha, I’ve wondered how many other people bugged.
[/]
I think around half or even more. I do dual coding with friend (we swap who is coding every 30min and constantly brainstorm), and i quietly observe him. Every time he is stuck he starts “compressing” blueprint code and moving things to be aligned.
Btw. blueprints redefine term “spaghetti code”, well it takes it to new level of awesome.
I also managed to create cthulu god from blueprint nodes.
I’m not familiar with all the bugs and crashes that have been submitted necessarily. Was there a ticket number for one. I can check and see the status if so.
As a note for anyone else wanting an update, I will not be checking status for every ticket number that is submitted in . I just wanted to do a brief check for some of the ones that are crashing and update.
I know it’s frustrating but thank you for your patience while these are looked into.
[/]
Thanks for the anwer I don’t know the number, but it’s one:
https://.unrealengine/showthread.php?59923-Unreal-Engine-4-7-Released!&p=232709&viewfull=1#post232709
seems quite grave, that’s why I asked you to check.
I’m not familiar with all the bugs and crashes that have been submitted necessarily. Was there a ticket number for one. I can check and see the status if so.
As a note for anyone else wanting an update, I will not be checking status for every ticket number that is submitted in . I just wanted to do a brief check for some of the ones that are crashing and update.
I know it’s frustrating but thank you for your patience while these are looked into.
[/]
[=Monops;239451]
Thanks for the anwer I don’t know the number, but it’s one:
https://.unrealengine/showthread.php?59923-Unreal-Engine-4-7-Released!&p=232709&viewfull=1#post232709
seems quite grave, that’s why I asked you to check.
(thanks to Kenomica for posting that with the repro as well)
I haven’t yet found time to test my proposed workaround for (the idea was to use a proxy object/blutility instead of construction scripts for instanced mesh creation). For now I’ve just migrated to 4.7 and started working on new stuff with empty space adorning the parts of my level where my instanced meshes used to be!
[=Skylonxe;238490]
I think it is nice idea to make version 4.10 special. Imagine that 4.9 and 4.8 will bring new features and there will be no new features in 4.10, whole Epic Games team would be working all time on bugfixes to make 4.10 version super stable. I really like that idea. What do you think ?
[/]
That’s an idea that sounds very logical.
There should be at least one release a year that is designed to be as stable as possible, (even if it’s a fork) with nothing new, just bug fixes and performance improvements, so those developers who are in the final stages can grab it, and stick with it through to release.
Otherwise it’s a recurring loop of - bug - release - - hotfix- bug - release etc.
I’m also stuck in the, cannot upgrade to 4.7.2 boat. I filed a bug 4.7 broke a ui blueprint, and the blueprint editor is also broken when trying to debug it. The step and stop buttons are even broken.
What worries me is the focus on free and features is really making a non-starter as a tool. Every upgrade has broken something we were using and set the team back. Is there paid support anywhere? If so I cannot find it from the website. I have a 100% repro case for the bug. However, since the text indicates anything I upload is a contribution, that’s a non-starter for a repro case that includes bits of the game we are working on.
[=;239868]
I’m also stuck in the, cannot upgrade to 4.7.2 boat. I filed a bug 4.7 broke a ui blueprint, and the blueprint editor is also broken when trying to debug it. The step and stop buttons are even broken.
What worries me is the focus on free and features is really making a non-starter as a tool. Every upgrade has broken something we were using and set the team back. Is there paid support anywhere? If so I cannot find it from the website. I have a 100% repro case for the bug. However, since the text indicates anything I upload is a contribution, that’s a non-starter for a repro case that includes bits of the game we are working on.
[/]
Hi!
I think Epic will be more than happy to help you with your bugs: post on Answerhub, that’s the way
So i just switched from 4.6.1 to 4.7.2(After you awesome guys made UE4 free! <3) and i didnt notice any big bugs until i decided to run my game for the first time, and noticed my Pawn (which is just a simple sprite nothing else) dissapears as soon as i possess it.
I like new in-world component editing a lot, but what annoys me about it is its seeming inability to add existing objects from the level (as opposed to Content Browser) as blueprintable components. That means that even if I already have a compound object created in the level out of attached parts, if I wanted to turn it into a blueprintable component, I’d still have to fully repeat the assembly process by picking every single part of it from Content Browser and then adjusting their relative scale, rotation, and so on. It would be FANTASTIC to have an eyedropper tool functionality added to In-world Component Editing later on, or at least have a contextual menu for attached items that would allow to easily link them to the parent as blueprintable components.
[=Kenomica;237526]
I have done, thanks. Updated the post with all the newly found information to hopefully help fix the.
Glad to hear your problem was fixed
[/]
Kenomica/others - did you discover any workaround for the instanced mesh?
I tested further today and found that using a proxy object/blutility to spawn instances doesn’t work either; the moment you restart the editor any instances spawned outside of a construction script seem to be cleaned up (and to quickly recap the original bug, any instances spawned within a construction script cause the editor to crash on load after lighting is built). Looking at InstancedStaticMesh.cpp I see code specifically to handle lightmaps for instances created in construction scripts (eg: FLightMapInstanceData), further debugging may yield clues on the crash or a workaround. Probably best to have Epic look further though, I’ve bumped your answer hub post for comment from Devs.
To move forward for now I’ve moved all procedural foliage to ‘Begin Play’ and will apply dynamic lighting if feasible.
[=;240102]
How go the UE-11109 ? because bug is making my week, i got problem in all static cameras of topdown
[/]
We encourage bugs to be addressed on the AnswerHub instead vs the so that they can be tracked and updated by one person when complete. I just happened across your post and looked up the report for an update: It is still marked as being worked on but I cannot say when there will be a fix, but likely soon as it is being looked at as major.
Is there a place where I can check when the 4.7.3 release is coming out… there have been a few fixes pushed in there that will help me out a ton… I only ask because I know of the road map and tell of an tracker often but don’t think the tracker is public? and not seeing it in the road map
P.S. i really feel bad about asking …(as a developer I’ve been asked so many times I wanna shout WHEN IT GETS !!! but you guys share so much info every step of the way I figure there really is a good :P)
[=Kenomica;244028]
Sadly not, been stuck using 4.6 until it is resolved. Very disappointing. Epic seem to have stopped replying on my answerhub post, too.
[/]
Unfortunately we haven’t been able to fix yet due to us not being able to reproduce yet. We see that also experiences the and we will try reaching out to them for a reproduction case.
[=Sychris]
Is there a place where I can check when the 4.7.3 release is coming out
[/]
No, we don’t post publicly with intended release dates. These can often change at the last minute due to unforeseen issues cropping up or other circumstances. We are aiming for the 4.7.3 release early next week.
I don’t know the number, but it’s one: