Unreal Engine 4.10 Preview

I can see it being a lot of extra work for you (I manage the sprints at work…) but I hope it becomes a thing :slight_smile:

I’m using 4.9.2.

Were there some changes in the foliage tool? -> the culling of the meshes is totally messed up now :slight_smile:

No, it requires runtime libraries as well of course, and will either use the runtime you installed or install a newer version alongside, as did VS2013 and before.

Thanks for the clarification :slight_smile:

Is anyone else getting this? When I try to create a blank c++ project with 4.10 then I get the message that it can’t be compiled and when I open visual studio then and see whats the error, I get this:

The project is called “PluginProject10” and it’s just a new blank c++ project with nothing inside.

Is there a list of all the fixed bugs?

I am really liking that you are focusing on stability and bug fixes for this build, stability is a bit issue with all the major game engines right now. I’d love to see the “new” features previously added fixed up and taken out of experimental as well as blueprint optimizations and/or a blueprint to c++ converter (if such a thing is even possible)

Blueprint to cpp converter would be cool but that sounds tedious and almost counter productive. I’d like to see more paper2d optimizations and completion. I’m well aware UE4 is more or less a 3D engine but a ton of individuals without a large studio or experience start out with 2D. Paper2d in itself isn’t that bad but the tilemaps could use a lot of work. I’d love to make a local player co-op game similar to Zelda Four Swords but the engine just can’t pull it off right now without going through a hail storm of bugs and tacky work arounds.

But as far as stability and bug fixes I’d say they’re doing pretty well. From 4.6 when I first started to now the engine is way more stable. My mobile game has less issues and the engine went from crashing many times a session to virtually never.

I’m getting similar error
Error 1 error C3859: virtual memory range for PCH exceeded; please recompile with a command line option of ‘-Zm23’ or greater c:\ue4.10.0p1\engine\source\runtime\core\public\delegates\DelegateSignatureImpl_Variadics.inl 272 1 UE4
Error 2 error C1076: compiler limit : internal heap limit reached; use /Zm to specify a higher limit c:\ue4.10.0p1\engine\source\runtime\core\public\delegates\DelegateSignatureImpl_Variadics.inl 272 1 UE4
Error 3 error : Failed to produce item: C:\UE4.10.0p1\Engine\Plugins\ScriptGeneratorPlugin\Binaries\Win64\UnrealHeaderTool-ScriptGeneratorPlugin.dll C:\UE4.10.0p1\Engine\Intermediate\ProjectFiles\ERROR UE4
Error 4 error MSB3073: The command “…\Build\BatchFiles\Build.bat UE4Editor Win64 Development -waitmutex” exited with code -1. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.MakeFile.Targets 38 5 UE4

That’s when I try to compile the PS4 version. Any idea what that is?

I’d love to see Paper2D (or any 2D solution) be polished and better-implemented. I feel that UE4’s ease of accessibility (especially with BluePrint) is at odds with its relatively significant difficulty in dealing with 2D games, and it really could (and should) be better at it. 2D games give beginners a much easier starting point than an engine saying “I guess you could technically do 2D but look, between you and me… maybe don’t”.

I know the Paper2D stuff still isn’t fully integrated the way it should be, but I’m really looking forward to better tools for 2D games, and I’m hoping it’s still on the to-do list!

Yeah, I’d rather see the focus on fixing all the little annoying bugs, rather than new features…

It doesn’t seem to be an issue that 2D currently uses 3D space, physics and what not. It’s really not that hard to work with. The problem is that some of the Paper2D components act wonky under certain conditions.

It would be super awesome too if you could make an entire layer have a collision type in tilemaps instead of making individual tiles have collision. This would speed up work considerably and I feel make a huge contribution to tilemaps.

Collision layers with navmesh on tilemaps would pretty much be the best thing ever. I suppose if it were me I’d make the navmesh calculate around all layers but ignore collisions.

Yeah, I’m more referring to things like Paper2D skeletal systems and dynamic animation of that sort (without resorting to a 3d model comprised of a bunch of flat images), P2D flipbooks being integrated with and recognized by other tools (can’t be used in UMG or with some other aspects of the engine that would save lots of time), et cetera. It’d just be nice if it could be brought up to speed with the 3D tools and other engines’ 2D support, since the BluePrints feature would gel incredibly well with learning 2D games.

BP -> C++ is actually in the works, they said earlier in this thread that it’s estimated around 4.12 I think. ( Trello )

I’m a little curious about will the gpu particles be available in ios metal in 4.10?Since it has been postponed from 4.7…

Perhaps I am a little on the confused side. I don’t use code anymore, just blueprints. So WHY do I need to upgrade to VS2015?

And to answer your question, no, I don’t have VS2015 installed. I appear to have a copy of VS2013 installed.

Because lightmass (apparently) was updated to use the 2015 extension libraries a.k.a. windows api, instead of the older 2013 ones.

All you need to do is download the redistributable from MS pointed out in the post you quoted.

with 4.10 does it mean we can uninstall VS2013 now?

i hope

gonna be fixed and i finally move from 4.8


So far 4.10 worked fine, if used with the BP templates. Now I tried to create a new project based on C++.
Upon creating the project in the launcher, I get an error messagethat some sort of SDK ismissing…
My windows is up to date, so what am I missing and how can I fix this?

AnswerHub reference:

Thanks for checking :slight_smile: