Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unreal Engine 4.11 port. #19

Closed
15 tasks done
ttvd opened this issue Jan 28, 2016 · 6 comments
Closed
15 tasks done

Unreal Engine 4.11 port. #19

ttvd opened this issue Jan 28, 2016 · 6 comments
Assignees
Labels

Comments

@ttvd
Copy link

ttvd commented Jan 28, 2016

  • Branch 4.10 code into 4.11 .
  • Create GitHub branch.
  • Deprecate 4.9 branch.
  • Fix API differences and fix deprecations in 4.11 .
  • Internal build system integration.
  • Houdini Installer integration.
  • Change of hashing for Houdini Geo Object Part (name based).
  • Change of unreal_face_material attribute to unreal_material attribute.
    • Adding fallback to unreal_face_material for compatibility reasons.
  • Look into building Game modules for Win and Mac OS X (right now we are building Editor modules only).
  • Set default scale in preferences to 100 (instead of current 50).
  • Update plugin category. At the moment it is Rendering.Components . Move to a category of its own?
  • Update Engine and MinEngineVersion versions in .uplugin file.
  • GeoPartObject refactoring.
    • GeoPartObject serialization versioning.

Filed as RFE # 73549 : HAPI: Unreal: UE4 4.11 port.

@ttvd ttvd added the rfe label Jan 28, 2016
@ttvd ttvd assigned ttvd and Yelmond and unassigned ttvd Jan 28, 2016
@ttvd ttvd assigned ttvd and Yelmond and unassigned Yelmond and ttvd Feb 7, 2016
@ttvd ttvd changed the title Unreal 4.11 port. Unreal Engine 4.11 port. Feb 18, 2016
@ttvd ttvd added the 4.11 label Feb 24, 2016
@robeastham
Copy link

I've manged to build this from source with the current UE4 branch for 4.11 and after quite a number of false starts it now appears to be functioning correctly.

Should I be using it yet or are there some gotchas I'm likely to run into?

@ttvd
Copy link
Author

ttvd commented Mar 22, 2016

Hello!

No, I believe it should be on par with the other branches. We need to do some internal work to integrate it with our build tools, but this should not affect you in any way. We also will be deprecating 4.9 in the few upcoming days.

Thank you!

@robeastham
Copy link

Any update on this? Still looks like a way to go?

Keen to use with 4.11.1 if possible, ideally don;t want to compile from source again and just use vanilla 4.11.1 downloaded from Epic.

@Yelmond
Copy link
Contributor

Yelmond commented Apr 22, 2016

4.11 support should now be in the Windows installers. Mac is taking a bit longer.

@robeastham
Copy link

robeastham commented Apr 28, 2016

Thanks! Can confirm that I have it working with 4.11.2 on Windows now :-)

@Yelmond
Copy link
Contributor

Yelmond commented Jun 24, 2016

Mac should have 4.11 as well now. 4.12 too.

@Yelmond Yelmond closed this as completed Jun 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants