Hi all,
At this moment I’m making a project for the HTC Vive. When I package(windows 64) the project it fails. Common Tools for Visual C++ 2015 is installed as described in this thread.
I dont know if it has anything to do with it, but I am using the Steam VR Template in this thread.
When I package a empty project (FPS Template) I have no issues. I hope anyone can help me. Thank you very much. Enclosed is my export log:
Andre
Hello Andre,
There seem to be quite a few errors/warnings in your log. I’ll try to break down the different types for you.
LogBlueprint:Warning: [compiler FirstPersonCharacter] Warning Input Axis Event references unknown Axis 'LookUpRate' for InputAxis LookUpRate
There are quite a few warnings like this one. It mentions that there are Axis variables being used in your blueprints or code without actually being defined. You can fix these by removing these references or by adding the axis in the Project Settings under Input.
LogBlueprint:Error: [compiler Sphere_Blueprint] Error Dependency cycle detected, preventing node Set Simulate Physics from being scheduled
There are a few of these too. These are pointing out Dependency Cycles, also known as Circular Dependencies. This means that there are two objects/blueprints/otherwise that are both referring to each other and require something from each other to compile correctly. This causes issues as the compiler doesn’t know which to compile first.
LogBlueprint:Error: [compiler Sphere_Blueprint] Error The property associated with Control could not be found
A missing variable, either the reference needs to be removed or the variable needs to be added. Due to the placement, this could be caused by the circular dependencies.
You should be able to find all of the individual messages by pressing ctrl+F and searching for either Warning or Error.
Let me know of any progress you make.
Hi ,
Great you took the time to help me out! I have to work today, so I will work on it more this weekend. Thank you very much for your help, it’s much appreciated. I let you know how this all works out.
We haven’t heard from you in a while, VRVisuals. Are you still experiencing this issue? If so, have you tried fixing the errors I pointed out? What were the results? In the meantime, I’ll be marking this issue as resolved for tracking purposes. Please leave a comment when you’re available and the post will reopen.
Hi . Sorry. I am reworking the whole project, so it wont be till next week till I give it another try. A lot of things you said made perfect sense, so this issue can be marked as resolved. (I will save it in a document for later reference). Thanks!