^
Great to hear 4.7.3 is on the cards.
, will the child actor reset issue (which I’m told has already been fixed in internal builds) be part of 4.7.3? To recap, bug forces you to redo setup for all child actor component nodes each time the editor restarts, so given the fix is already available would be a huge time saver for affected users.
For the other (instanced mesh) I’ll work with on the AnswerHub thread to get a repro going.
[= ;246133]
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.
[/]
Totally understand 
thanks for the info. grabbed a build off github that should work till than to keep the wheels turning. thanks for all the resources you guys keep available there are always lots of options 
Another hotfix on the way, coolio! Thanks Epic
[=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 ?
[/]
I’m going to be the pedantic jerk and just point out. There will never be a new version 4.10. Numerically, it is the same as 4.1. After 4.9 comes 5.0 - which either will need to be adopted into the Unreal 4 numerical version system…or smaller and smaller decimals and sub-decimals will have to follow for other things, like 4.9.9.9.9.9.4 etc.
[=conan_thanoz02;246990]
I’m going to be the pedantic jerk and just point out. There will never be a new version 4.10. Numerically, it is the same as 4.1. After 4.9 comes 5.0 - which either will need to be adopted into the Unreal 4 numerical version system…or smaller and smaller decimals and sub-decimals will have to follow for other things, like 4.9.9.9.9.9.4 etc.
[/]
Epic already said there will be 4.10 and 4.11 and so on 
[=conan_thanoz02;246990]
I’m going to be the pedantic jerk and just point out. There will never be a new version 4.10. Numerically, it is the same as 4.1. After 4.9 comes 5.0 - which either will need to be adopted into the Unreal 4 numerical version system…or smaller and smaller decimals and sub-decimals will have to follow for other things, like 4.9.9.9.9.9.4 etc.
[/]
The thing to keep in mind are that version numbers are not decimals. So after 4.9 will be 4.10 and eventually we’ll have 4.100 (probably a totally different engine by then and also hoverboards will be around). In fact, the numbering is kind of arbitrary in itself and it is a common joke that we could be using “4. and 4.Panda”, but then we may forget what order the animals come in.
EDIT: Insert 4.Chicken and 4.Egg joke . Also, there is a great explanation on software version on Wikipedia I found: ://en.wikipedia.org/wiki/Software_versioning
4.xx 4.xxx are very good numbers and gives feeling to lot of people that it is rock stable and in reality i hope too. It is even now stable.
: Dont forget Graphene CPU-s in future
UPDATE!
The 4.7.3 Hotfix is now live! It contains a number of fixes for our latest release, including many crash fixes, all listed below.
If you experience a bug with the 4.7.3 Hotfix, please remember to log a bug report for the on the UE4 AnswerHub to the Bug Reports section.
Fixed in 4.7.3
UE-11029 Crash after converting to 4.7.0 from 4.6.1
UE-11404 Second player is not affecting by any gamepad input.
UE-11402 Editor will not build if you have code, and ONLY SDK 2.0
UE-11485 Compiling the engine with Xcode 6.3 beta generates errors
UE-10128 Preview Static mesh does not translate with socket
UE-11315 Bugg 38187: SIGSEGV: invalid attempt to access memory at address 0x1010102
UE-10569 Crash when opening maps and blueprints in ‘s project
UE-10708 Build failing for users project with all platforms
UE-11312 Mac Bugg 38298: SIGSEGV: invalid attempt to access memory at address 0x3
UE-11369 Crash when clicking on a “Two Bone IK” node
UE-11185 A function in a Blueprint Function Library that references another function in that library cannot be saved after closing and reopening the project
UE-11322 Crash when refreshing/moving/deleting BP nodes
UE-11743 4.7 does not support Morpheus under SDK 2.0
UE-11302 Cannot deploy to iPad
UE-11692 Crash when rendering hit proxies
UE-11304 Can’t compile CrossCompilerTools due to missing file
UE-11484 Fix Xcode 6.3 beta clang issues.
UE-11393 Tiled landscape import’ creates overlapped landscape components
UE-11017 GitHub 857 : Fixed native enum support in blackboard component.
UE-10697 Crash when opening Post Process Material with Live Data Preview running in Profiler
UE-11225 Closing Chunk Parameters tabs with chunk selected and reopening Destructible will cause crash
UE-10149 Project crashes on load after modifying Parent Blueprints
UE-11244 Crash when renaming assets from the Persona asset browser
UE-11272 Blueprint compile error when upgrading project
UE-11319 Crash on project open (Assertion Failed)
UE-11401 Need more logging in the Deployment Server
UE-11292 Editor Crashes when clicking on Transform(Modify) Bone node in Content Examples
UE-10900 Crash in FBatchingSPDI::DrawMesh in stand alone game
UE-11505 Crash launching Blueprint Office standalone
UE-10856 Crash on dragging static meshes into the scene
UE-11298 Crash with Distance Fields while using World Composition
UE-11422 GitHub 894 : wrong parsing of the return of adb cmd: device
UE-11447 Player Character does not collide with landscape
UE-11638 GetActorsPerception useless in 4.7
UE-11589 GitHub 909 : Update .gitignore
UE-11605 Overridden components are broken in static Actors in cooked build
UE-11666 UberGraphFunction should be preloaded in Class::Link
UE-11711 Severe log spam when particles collide with static objects
UE-11640 AI Move To issues in 4.7
UE-11360 Placing a ’ - ’ in theproject name will cause the Android build to fail
UE-11647 Denver Tegra K1 (Nexus 9) disables rendering thread causing bad performance
UE-11383 Screen orientation is ignored on Android devices.
UE-11460 A level will not save if a Blueprint that uses a Blueprint Component with an Event Dispatcher is placed in it
UE-11600 Performing a hot reload on a project that contains an FStringAssetReference will crash the Editor.
UE-11707 Implement workaround for Localization being broken for a number of editor strings
UE-11592 Cook on the fly Android projects crash after launching on the device.
UE-11739 In some circumstances CrowdManager doesn’t get created.
UE-11321 Crash when creating landscape
UE-11777 BP-implemented BT decorators end up thinking they’re not on active branch
UE-11826 MediaPlayer14 class lookup crash with distribution builds
UE-11840 Launch on Nexus 9 fails due to unknown arm64-v8a architecture
UE-11893 Editor crashes when dragging a docked window
Yaaaaay, updating! Thanks so much
Thank you & Epic for update , i hope , will fix my Android problem.
UE-11840 Launch on Nexus 9 fails due to unknown arm64-v8a architecture
UE-11647 Denver Tegra K1 (Nexus 9) disables rendering thread causing bad performance
UE-11592 Cook on the fly Android projects crash after launching on the device.
UE-11360 Placing a ' - ' in theproject name will cause the Android build to fail
UE-11302 Cannot deploy to iPad
I don’t see nothing about JavaLibs / play-services_lib_rev19, I have serious problems with it, probably because of my custom Win7 paths, I don’t know.
update of 2go 
, i need to wait 2h and see…
Thank
UE-11460 A level will not save if a Blueprint that uses a Blueprint Component with an Event Dispatcher is placed in it
Thank you so much for fixing . It was driving me trying to figure out what caused it. I wanted to file a bug report but couldn’t figure out how to replicate it. I really appreciate the work you guys have been putting towards bug-fixes since 4.7 came out. Keep up the great work!
Thanks Epic! I just ported my 4.6.1 project over to the new version, and everything just works, at least at first glance. Thumbs up!
Unfortunately still many bugs in 4.7.3 so I really hope there will be a 4.7.4 :rolleyes:
[= ;249810]
Unfortunately still many bugs in 4.7.3 so I really hope there will be a 4.7.4 :rolleyes:
[/]
://www.makesomelol/wp-content/uploads/2012/09/chat-se-mord-la-queue.jpg
[= ;249810]
Unfortunately still many bugs in 4.7.3 so I really hope there will be a 4.7.4 :rolleyes:
[/]
You are way too specific… please stop it
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
[=;249830]
You are way too specific… please stop it
[/]
The specific stuff you can find on the answerhub 
I would like to have ****](https://answers.unrealengine/questions/193800/engine-crashes-on-compile-of-one-blueprint-only-if.html), most importantly ****](https://answers.unrealengine/questions/190159/struct-default-values-get-reset-after-closing-proj.html), and less importantly ****](https://answers.unrealengine/questions/190264/473-engine-crashes-when-hitting-play-navmesh-error.html) and ** **](https://answers.unrealengine/questions/193721/unresolved-compile-error.html) and ****](https://answers.unrealengine/questions/189943/set-navmodifier-mobility-in-blueprint.html) and ****](https://answers.unrealengine/questions/194566/473-engine-crashes-on-compile-of-one-blueprint.html) and of course ** **](https://answers.unrealengine/questions/166911/bp-function-library-gives-randomly-transient-reins.html)fixed for 4.7.4.
Specific enough?
The good thing is, with 4.7.3 now I can actually use 4.7 because I don’t get too many crashes. I can’t play the game properly because of the missing default values and I can not use some features because of the bugs, but I can at least use 4.7 at all now.
[= ;249862]
I can’t play the game properly because of the missing default values
[/]
That’s still an for you? It was the thing that stopped me using 4.7.2, but it seems to be gone in 4.7.3 for me - my problem was answerhub post. Maybe we’re talking about different things though.
[=MkII;249930]
That’s still an for you? It was the thing that stopped me using 4.7.2, but it seems to be gone in 4.7.3 for me - my problem was answerhub post. Maybe we’re talking about different things though.
[/]
[]
Unfortunately still many bugs in 4.7.3 so I really hope there will be a 4.7.4
[/]
Finaly ,your comment is legitime, you have a lot of bugs too.