Unreal Engine 4.7 Preview

KRushin · February 10, 2015, 4:20am

[=;217788]
questions/169489/ue-47-editor-crash.html

Can anyone confirm ? (Editor crashed when attempting to open an animation blueprint - existing ones as well as newly created ones) Happens to me even in latest 4.7 branch commit which should be 9577d435436a1bcd94931e5aa9ca47ca381b53f3 at of post.
[/]

was a bug over weekend and should be fixed in builds from early sunday now

maxzerr · February 10, 2015, 6:08am

Can anyone please let me know how I can go back to Preview 2 from preview 5? We really need audio for our project and sadly, there is none in latest preview. I have git set up but I’m a bit unsure on how I can download and build Preview 2

Michael_Noland · February 10, 2015, 6:20am

[=maxzerr;219275]
Can anyone please let me know how I can go back to Preview 2 from preview 5? We really need audio for our project and sadly, there is none in latest preview. I have git set up but I’m a bit unsure on how I can download and build Preview 2
[/]

If you are stuck on 4.7 then it would probably be better to move forward to head instead of back to preview 2 as there have been a huge number of changes, but it can’t be reiterated enough that you should not be developing a game on preview build. It is made available for testing compatibility, playing around with new features, and catching upgrade bugs on a copy of your project, but it is not expected to be stable for development until it’s released

Preview 6 should be coming down pipe in next few days as well, but I don’t know specific timing.

Cheers,

maxzerr · February 10, 2015, 6:37am

Thanks for quick update, . We need our prototype to be ready by week. Most of work is done, but we only need to add some little things here and there. Preview 3 wouldn’t even load up our project and would crash. Is there anyway I can rollback to a previous version of preview using github? Any help would be greatly appreciated

Edit: will also keep in mind that previews are only for testing from next

Michael_Noland · February 10, 2015, 6:46am

[=maxzerr;219288]
Thanks for quick update, . We need our prototype to be ready by week. Most of work is done, but we only need to add some little things here and there. Preview 3 wouldn’t even load up our project and would crash. Is there anyway I can rollback to a previous version of preview using github? Any help would be greatly appreciated

Edit: will also keep in mind that previews are only for testing from next
[/]

Yeah, you should be able to sync back to any point, but I don’t know labels for each preview build. If you can get P4 CL# from someone who still has preview 2 (in editor About box) then you can look it up on GitHub and convert to an equivalent git commit to sync to. Otherwise you might try syncing to latest in 4.7 or perhapsgithub/EpicGames/UnrealEngine/commit/884a8bfaa89d69c381d938c060cb9ac8619e18e6 from weekend, which mentioned compiled for them a few posts ago.

Cheers,

Michael_Noland · February 10, 2015, 6:50am

Also to clarify, syncing backwards after saving content in a more recent version is not safe in general, but because we lock ObjectVersion.h in release branches, it’s relatively safe in case.

Cheers,

Jmeletou2014 · February 10, 2015, 6:58am

with version 4.7 preview 5, first person template, physics does not work,
projectiles no longer pushes boxes.

maxzerr · February 10, 2015, 7:04am

Thanks, . It says 4.7.0-2388154. So, basically I search for corresponding commit number and then commit to that? commit should have been made in branch, right? Sorry for too many questions but I’m new to git

maxzerr · February 10, 2015, 7:50am

https://github/EpicGames/UnrealEngine/tree/2f251acda8de233efd8fd4941c94e15fbcd2f626

is probably it, if anybody wants it

BPANDREW · February 10, 2015, 12:10pm

[=maxzerr;219309]
https://github/EpicGames/UnrealEngine/tree/2f251acda8de233efd8fd4941c94e15fbcd2f626

is probably it, if anybody wants it
[/]

Thanks didnt think about doing !

Toom · February 10, 2015, 1:44pm

[=;219083]
@ ,

Not offensive . Ive seen descriptions, but that’s not point. 4.7 Preview 5 should be very close to release code as by it’s very name it’s 5th iteration with release expected within weeks. So would be a good starting point for integrating our new code into UE. As 4.7 has new LOD code and instancing code we have to use as a dev base. We have semi working code for client already but need 4.7 to test updated integration.I understand 4.7 branch is basicly a version being updated constantly, that’s my point. Why do we need a branch, a promoted branch which can’t be used for future dev tests as many things could change before that branch gets released, and a preview branch thats constantly updated so is a lottery if will compile. Would make for more sense for coders to have latest stable preview build available through launcher as a downloadable preview build that isnt updated. At least then we can use that as a base for code changes and know it will compile.
[/]

I don’t know maybe more sensable thing for them to do is go back to not showing previews at and just put releases on launcher and thats it? People apparently can not that whole part where it says “Developers should not convert their projects for active development on preview releases.” is a preview release with issues, its not granteed to work, its going to have lots of broken parts to it. Also there has not been an announced release date. They are hoping to have a release in afew weeks but its not announced and can change at any point.

Dark-Veil · February 10, 2015, 1:51pm

[=;219281]
it can’t be reiterated enough that you should not be developing a game on preview build.
[/]

Just to reinforce , please always remember to back up your projects before loading (and especially saving assets) using any Preview release of UE4. We’ll look into adding features to Launcher to help keep your files safe when using Preview releases.

[=;219281]
Preview 6 should be coming down pipe in next few days as well, but I don’t know specific timing.
[/]

Preview 6 should be released today, within next four hours. We’ll be doing at least one more preview release after one, possible a few more, to get additional testing and stability.

–

KITATUS · February 10, 2015, 2:22pm

[= ;219475]

Preview 6 should be released today, within next four hours. We’ll be doing at least one more preview release after one, possible a few more, to get additional testing and stability.

–
[/]

Now THAT gets me excited!

I noticed skimming through thread that some say that preview branches should be removed from Launcher; To those people, I pose theory:

If preview build is in launcher, More people are going to be inclined to download it (As opposed to getting GitHub release and building it everytime. Having it in launcher gets preview to more people… And do you know what that means?

More test subjects! More people to break preview release, find bugs and loopholes. Why is beneficial? more bugs found in preview phase, more that can be fixed pre-release. In theory, should make for most stable release when release comes.

Just because 4.7 is on launcher; Doesn’t mean you should migrate your project straight away. I mean by means, do so, but be wary that crashes may and WILL happen and things are likely to go wrong. In migrating to 4.7 without backing up is silly, you’re most likely going to break something in preview release. However in doing a part of your project (After cloning project) in preview release, you’re doing Epic Games a great service in helping finding bugs and squashing them before release.

4.7 seems to have more bugs then normal as there’s been a huge overhaul in UI and a lot of behind–scenes stuff. It is possible that preview release is a one-off with amount of “Game-breaking” bugs, but Epic have been fantastic with getting bugs dealt with as soon as possible.

Remember when using a preview release, you’re not doing it for your own benefit; You’re doing it to help community and Epic by finding bugs that would normally have gone unnoticed until release.

So next you download a preview release, just be wary that there will most likely be bugs (Hence why it’s a preview release and not a full release) and it’s your choice weather to use it or not. If you use it, you get most recent version of engine and are helping community / Epic a great deal but you’re also using something that could have a bug that will stop you advancing in your project.

I hope helps some people realise point of preview releases (I know it’s pretty darn obvious but some people can get confused sometimes!)

kamrann · February 10, 2015, 2:24pm

[= ;219475]
Preview 6 should be released today, within next four hours.
[/]

. Any related commit can be tagged on github, or is there not a direct correspondence between github commits and preview builds?

Demolition_Man · February 10, 2015, 3:40pm

[= ;219475]

Preview 6 should be released today, within next four hours. We’ll be doing at least one more preview release after one, possible a few more, to get additional testing and stability.

–
[/]

Hi ,
I get feeling that 4.7 has had quite a few changes going on in background in an attempt to make a better and more stable engine. Keep up good work my friend. We want a better engine so take your with it.
:D:D:D

anonymous_user_02360bb5 · February 10, 2015, 5:05pm

[=Demolition Man;219549]
Hi ,
I get feeling that 4.7 has had quite a few changes going on in background in an attempt to make a better and more stable engine. Keep up good work my friend. We want a better engine so take your with it.
:D:D:D
[/]

Yep take your guys, but not valve tho plz

Stephen_Ellis · February 10, 2015, 5:07pm

UPDATE!

We have just released Preview 6 for 4.7! update to preview contains an additional 51 bug fixes. Please view original post on page 1 of thread for updated “Known Issues” list.

update also contains some important known issues which we wish to call particular attention to.

Important Known Issues in 4.7 Preview 6
UE-7353 - Projects launched on from Mac to Android crash upon opening
UE-8635 - Sample games are not working once launched onto Android
UE-8873 - Mac Binary missing files for HTML5
UE-9448 - UAT no longer seems to work with -<platform>, it needs -platform=<platform> ( means that packaging for iOS and HTML5 packages for Windows)

Thank you for your continued help in testing 4.7 build before its official release. As a reminder, Preview builds are for testing only, and should not be used for active development of your project.

anonymous_user_0df12f74 · February 10, 2015, 5:16pm

Looks like 4.7 Preview 6 is on launcher, just downloading it now. Thanks Guys!

Also to reiterate , , , & :

NEVER upgrade only copy of your project to a preview release!! When you open project you will get a popup box how to proceed, ALWAYS select “Open a Copy” to avoid any problems. will keep a copy of your 4.6 project (or other earlier version) and create a duplicate named “ProjectName 4.7”, way you will keep your working version and not lose any data. is also a proven method to prevent headaches…

anonymous_user_f2dd594d · February 10, 2015, 5:17pm

I’ve noticed there’s a highlight with sample games launching on Android in 4.7p5 & 4.7p6.

I’ve not been able to get my current project to launch on Android since P5 (it worked with P1-4) and would like to know if it’s same or not. Is there any way to tell?

anonymous_user_17ec24a01 · February 10, 2015, 5:23pm

[= ;219597]
UPDATE!

…and should not be used for active development of your project.
[/]

you can’t stop me! mwahahahhahaa!!