Jump to content
  • Advertisement
Sign in to follow this  
  • entries
    54
  • comments
    70
  • views
    39617

My woes while trying to build UE4 from source

Sign in to follow this  
ryan20fun

984 views

Welcome to this special entry,

[Monday] I have tried compiling UE4 from GitHub, But I am getting (semi) random ICE errors.
Right now, When I see an ICE; I go Argggg
This is really frustrating!
I have also run into more then 6 BSOD's (PFN_LIST_CORRUPT, MEMORY_MANAGEMENT x2, NTFS_FILE_SYSTEM, CRITICAL_STRUCTURE_CORRUPTION (This happend after turning off the page file) )
I am updating the VC++ compiler to see if that helps.
Maybe I really do have some kinda hardware/software mismatch problem or fault somewhere <_<

The VC++ compiler update used ~35MiB.
Aaaand, Bam ICE error.
I am just about to give up on building from source,

[Today] I get ICE errors with a new Win8 VM with VS2015.

I have tried different combos of Unity compilation(I believe it combines different source files together for compilation), PCH's to no avail.

Unless anybody has suggestions, I am going to use the Launcher build from Epic when hotfix two is released.

/Rant
Have a good day :)

Sign in to follow this  


2 Comments


Recommended Comments

Try a stable source release rather than HEAD first, also make sure you have any prerequisites installed.

 

All of those errors sounds like your drive file system however PFN_LIST_CORRUPT reminds me of a Windows 10 upgrade problem - usually a bad driver that hasn't had an update https://msdn.microsoft.com/en-gb/library/windows/hardware/ff559014(v=vs.85).aspx

 

You're correct about the Unity builds, they lump source files into a bunch of bigger clumps for optimal build times.

Share this comment


Link to comment

Thanks for the comment.

Do you use UE4?

 

Try a stable source release rather than HEAD first, also make sure you have any prerequisites installed.

I used the default release branch if that is what you mean.

I made a post on there answer hub, So I am going to try the 4.11 branch instead of release.

I found ~3 simple syntax errors in some files, so there may be some kinda bad syntax/code causing the compiler to crash.

I even tried in a VM that has only been used to test cloning software.

 

VS2013 compiler crashed shortly after the build started, So the VS2015.2 C++ compiler lasted longer.

 

All of those errors sounds like your drive file system however PFN_LIST_CORRUPT reminds me of a Windows 10 upgrade problem - usually a bad driver that hasn't had an update https://msdn.microsoft.com/en-gb/library/windows/hardware/ff559014(v=vs.85).aspx

I have been getting random BSoD's since installing a 8GiB RAM stick(had two 4GiBs), Mostly MEMORY_MANAGEMENT.

So I may have some kinda hardware/software conflict or fault.

I have rearanged the RAM placements.

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!