Hello again all,
I was here last week asking if anyone can help with my UnrealBuildTool not working when trying to create the needed project files after running “GenerateProjectFile.bat”.
The error says: "Could not resolve this reference. Could not locate the assembly “Windows”.
I have no idea why this is only happening on my station as others who have been helping me can generate the files with no problem. Thank you very much to @ for all of you assistance in the past week but we are both doing the same exact steps yet I get this error.
Its been a frustrating 2 weeks troubleshooting but I do not want to give up now especially when I am so close.
any help would be super greatly appreciated.
Discovering modules, targets and source code for project…
ERROR: Targets with a unique build environment cannot be built an installed engine.
Even if the official version is released, I still have to download it from github？. The learning classification in EpicLauncher can’t be opened with the official version of .423.
The 4.23 release notes states that Chaos still needs to be build from source if you want to test it. The 1st post in this thread was updated with the steps to make it work. You will need to compile the Chaos Demo project aswel with the compiled engine. To run it you will need to use Visual Studio or double click the .uproject file for the Chaos Demo after it was compiled (in my case I could only run it inside Visual Studio, the other option didn’t work).
When I run GenerateProjectFiles.bat I get “GenerateProjectFiles ERROR: It looks like you’re missing some files that are required in order to generate projects. Please check that you’ve downloaded and unpacked the engine source code, binaries, content and third-party dependencies before running this script.”
FYI - Some of the maps in the Chaos Demo Content Example take a looong time to load the first time. Just wait it out… dont cancel or interrupt. I hard stopped one and think I corrupted some of the fracture files in it. Also, for whatever reason, after switching the project to the compiled 4.23, it has to rebuild the engine again to launch the first time… gah
This is the page where you can go and pick the releases (the one which goes to the Epic Launcher), there you will choose the .zip for the release you want. If you went there then the UnrealEngine-4.23.0-release.zip is the correct one.
Also - Worth mentioning the last example (1.F) in ChaosExamples_05_Gameplay has a shooting example. Looks like the spawn a field at the impact location of the projectile
Does the standard LineTrace work only against the PhysX scene?
Do Chaos objects exist in both PhysX and Chaos?
Thanks in advance for any insight
[UPDATE]
Here are a few more assumptions/observations ( NOTE: they could be incorrect - feel free to correct)
Looks like the initial collision shape is in PhysX and remains event after being broken in Chaos. The Chaos broken pieces are not in PhysX.
Hence, LineTraces work in the PhysX scene against teh initial unbroken shape.
Note: Each time you create Field System Actor Blueprint, it will need its own unique Field System asset to contain the data for the Field System being created.
This means if you alt-drag an anchor it wont work till you create a new FieldSystem asset for it
When i compiled the over 3000 shaders for the 4.23 Chaos VS says:
Error C1083 File (Include) cannot be opened: “metahost.h”: No such file or directory UE4 C:\Users\jan-e\Documents\UnrealEngine-4.23\UnrealEngine-4.23\Engine\Source\Editor\SwarmInterface\Private\SwarmInterface.cpp 21
Error MSB3075 The command “…\Build\BatchFiles\Build.bat -Target=“UE4Editor Win64 Development” -Target=“ShaderCompileWorker Win64 Development” -WaitMutex -FromMsBuild” was terminated with code 5. Make sure that you are authorized to execute this command. UE4 C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.MakeFile.Targets 44
Yes, I have been running the Setup.bat file successfully without any problems. Its the next step when running “GenerateProjectFiles.bat” that is kicking my butt. :eek:
I am enabling all Windows SDK options in my Visual Studio 2017 Installer currently.
With a 8 core 16 threads processor at 3.7GHz in a NVMe SSD in raid (which I use just for that) takes around 55-65min to compile, then you can duplicate the folder after that just in case you need the build from source without Chaos and in the copy you setup Chaos and takes another 20-25min if you include the Demo. The difference is because I try to do something in parallel, like seeing a video because waiting sucks.
IT GENERATED THE PROJECT FILES!!! WOOOOOO!!!
So two things… I enabled all Windows SDKs which after running again gave me a new error… It was at least running UnrealBuildTool now though except it was failing to create the project files still. Progress…
Then I noticed that in the example given by Epic where they say to modify your “UE4Editor.Target.cs” they do not include two lines that I had to leave in at the very top.
using UnrealBuildTool;
using System.Collections.Generic;
I added these back in and then ran “CreateProjectFiles.bat” and it finally worked! It created the project files and the needed UE4.sln file. I opened it in VS and it has finished compiling successfully. I am currently building the ChaosDestructionDemo from VS and everything is working going good so far… just taking for ever.
