Skip to content
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

Update FileSystem.cpp #79

Closed
wants to merge 1 commit into from
Closed

Update FileSystem.cpp #79

wants to merge 1 commit into from

Conversation

BielBdeLuna
Copy link
Member

defaulted fs_resourceLoadPriority to 0 so it is easier to develop with the engine

defaulted fs_resourceLoadPriority to 0 so it is easier to develop with the engine
@kortemik
Copy link
Member

does this mean that specified path will be prioritised instead of normal lookup. Normal lookup meaning first in base/ then in mod path?

In that case I am against this because base/ should contain only stuff that will be extended in mods, not something that will be used only in case nothing else is there.

We should fix base instead.

@DanielGibson
Copy link
Member

If I understood correctly in the idtechforums, this is only relevant if the assets are in .resources files, right?
This is currently not the case for OTE and possibly never will be (I wanna bring back .pk4).

However, I haven't looked up what this option really does, if the descrption("if 1, open requests will be honored from resource files first; if 0, the resource files are checked after normal search paths") is right defaulting to 0 indeed makes sense when not using resource files.

@BielBdeLuna
Copy link
Member Author

yes this is only for the resources,

in OTE makes not sense to keep this at 1 unless we end up building resources, but then it's up to us to bring it back to 1, I don't think we will ever really use the resources, but the option should remain there. so only changing it to 0 we keep it there but it doesn't interfere with the development of OTE.

@BielBdeLuna BielBdeLuna deleted the patch-2 branch December 29, 2015 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants