-
Notifications
You must be signed in to change notification settings - Fork 14
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
Not able to use "Mandatory" flags #39
Comments
Where is the flags file for this program? The code seems to indicate a list somewhere, but I don't see it, and it doesn't seem to be within the application itself, based on the error I received above. |
The flags file is included as part of the creation kit, so you'll need to install that somewhere first, or else grab the flags file for fallout from one of the earlier releases of Caprica. The flags file is game-specific, but does not change between versions of the game or versions of Caprica. |
I did find the flag file, but Caprica seems to have a problem with something called "ObjectReference.psc", which does seem to be a core script:
I get this regardless of the script I try to compile, and I've checked the flags file, and I've checked my caprica command:
|
As a quick and dirty workaround, rename |
The problem seems to be that "struct ConnectPoint" has an item called "string parent". From what I understand, Caprica has a long list of issues with FO4SE. Is there a complete list on how to make them compatible? I've been working a while on finding a simple way to work on Fallout 4 scripting, and so far, that seems more and more infeasible. |
I'm using the GOG version of Fallout 4, pre-Next-Gen version, so I do not have the Creation Kit installed. I am getting these errors:
Is there a way to setup Caprica where it can use these kinds of flags? Please keep in mind that I am new to scripting for Fallout 4 and FO4SE.
EDIT: I've looked, and it seems that there are other files besides the main executable, but Caprica.exe is all there is in Caprica.v0.3.0.7z. This should be fixed.
The text was updated successfully, but these errors were encountered: