July 2013 UDK Available Now

[Aasmund]

Whoo Hoo!!.... Thanks for letting us know Aasmund!!! New Build Hurray!!!

Haha, I have been into CryEngine for a while and came back to Unreal Engine, due to CryEngine`s craches.
So I got happy when I saw that they have realesed the feb. build Hope they fixed the terrain-editor crash.

[President]

Whoo Hoo!!.... Thanks for letting us know Aasmund!!! New Build Hurray!!!

[Aasmund]

Finally a new build!

[Slcark52210]

Okay I there are a lot of people having some problems with the Swarm Agent too and it looks like there is no help for it. So I am going to tell you my problem. When I am putting my lighting my level and then Build All a error pops up saying, Failed to connect to Swarm. SwarmAgent has stopped working, A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. Then a tap for Close program, then other message comes up and says, The lighting build Failed! See the log for more information! If there is anyone out there that can help please let me know for this for a class I am taking.

Thank you very much,

[KnightChatX]

In Appreciation:
Thank you for bringing out the July 2013 version and for giving us the tools to be creative and make our passions a reality, I'm starting to have fun now with this stuff as I am also serious about developing using these tools and am in this for the long haul, the tools and licensing model is perfect for my work. Also, the youtube previews of the Unreal 4 editor looks awesome and it does look very improved and simplified in many ways and looking forward to using that system in the near future.

Now for the bugs, several bugs I've noticed which are probably already reported are these:
Minimizing the editor after you've used editactor command makes the recently opened Actor Properties window disappear, when you reuse the command it increments window count with a number and opens multiple property window copies behind placing the newly opened property window in the foreground.

Sometimes the Fracture Tool or Unreal PHAT crashes the editor.

If editor crashes while adjusting Physics Asset the Physics Asset may not load the Unreal PHAT and might not be able to forcefully delete the Physics Asset as if it's locked into memory or something, I took several attempts to finally get the Physics Asset deleted and editor re-opened, and then the Unreal PHAT would open again once I was able to delete the Physics Asset.

Sometimes I make a change to Physics Asset and the Physics Asset already shows in the Content Browser as if the change was already saved to package, it isn't reflected in the main editor, and then when I close and re-open UDK it shows the change in physics, this is very rare though.

Sometimes editing a field in any of the tools such as updating a number when changing a field or editing a field in Actor Properties after the editactor command has been used crashes UDK.

Other Thoughts:
And from bug fixes and a future UDK4, I'd like to see documentation covering more such as space based environment elements such as space based vehicles since alot of focus has been on land based and foliage filled environments, and more documentation covering building and importing of assets from other programs than just the most common ones, as the steps do somewhat vary a bit, especially with skeletal meshes even if the desired end result is the same, I think that would help accelerate the development process further as personally I'm finding and experimenting with things that are not fully covered on those topics using different brand asset creation tools and at the moment that's where the development slow down has been coming from.

Possibly some more youtube video's covering basic ways components could be used in form of just a few minute video's representing even some of the advanced variables and displaying the affects visually in a different graphical form than the webpages with text and pictures, there's alot of helpful video's out there already from people, but UDK does have alot of variables that do alot of different things, and even going through textual documentation you can get a bit lost starting out.

[cube2222]

http://forums.epicgames.com/threads/...-2014-Deadline , also, they re working on ue4.

[Keiyentai]

Would be nice to know if there will be an update soon since this one has been going on for a pretty decent stretch compared to other releases it seems.

[daimaku]

as far as i know there is a new build on the way, to fix the ios7 update for the app store.

[HangingBunny]

Is there going to be a new build anytime soon, or have UDK builds been pushed back until UE4 is deployed?

[Aasmund]

Hello and happy new year! Does anyone know if there is any status on the UDK that we see in the Unreal Engine 4 demo video? Will it be out this year?

[BurstStream]

I waited for this update for a long time.Thanks you so much.That's the best news for today

[BurstStream]

Thank you, Epic! It's really great news!

[Sythenz]

It depends on what you were doing at the time of the error. List your specs too.

[Trooper1]

Hello all, this is my first time on here and need some help. I downloaded 2013 UDK and tried to start up to make a level. Then I get this error message..
" Built with UDK has stopped working. A problem caused program to stop working correctly. Windows will close program & notify you if a solution is available."
Never received a solution. Has anyone ever had this happen? I am running windows 7 and my computer meets all the required specs.
Any help would be awesome.

Thanks.

[DemoMan2]

Sorry I didn't update this thread with some additional findings.

I originally thought that the "installation" problem was caused by a memory issue. One machine that we tried to install my game on had 6G of ram and the install died on that machine. The next machine had 8G and installed fine. Both had Nvidia cards so I thought we had some sort of memory issue. After looking into the problem in more detail, my game should run in a 2G memory model without any problems. So my current theory is that the Nvidia graphics drivers where causing the problem. The machine where it died on had the 320.49 drivers. I still need to confirm which Nvidia driver set was on the 8G machine. Since many people on the net have mentioned that the 320.xx drivers have been giving them trouble with their games, I think this might be the cause of my problems. Please note that this is just a theory at present. I am still trying to determine exactly what happen that caused the problem. I will post some more info when I have a chance to work on this in more detail.