- Newest
- Most votes
- Most comments
I resolved the issue by doing a full compile with
lmbr_waf.bat configure
lmbr_waf.bat build_win_x64_vs2015_profile -p all
Now a new project loads in the editor without any errors with the CryEntityRemoval gem enabled.
I've had this issue since 1.12. For now, disabling the CryEntityRemoval gem in your project (via the Project Configurator) will solve the issue. I also had this issue with the Water gem, so be wary of that one too. Also, don't forget to run "lmbr_waf configure" and "lmbr_waf build_win_x64_vs2015_profile -p game" (assuming your using VS2015 and 64-bit Windows).
Thanks for your reply and help, I had no issues with 1.12, I recreated the projects and removed only the CryEntityRemoval gem, recompiled and the projects did load in the editor, the extra errors I got was from removing the CryLegacy gem.
Please read the answer I posted as it may work for the Water gem. I did a compile with just the gems enabled in a new project, it took 1h50m16.230s so I'm not keen to recompile just yet.
This post is closed: Adding new answers, comments, and votes is disabled.
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 months ago