Quote:
|
Originally Posted by Laffs
Yes it would have to default unspecified values, as for the exact defaults and values, Kos has made an extensive list of all values and it is unfair to point you to that and work out the defaults yourself and add to your work on this,
So Kos could you please make up a list of the "missing" defaults for Ger to work with here please bud, As you know know them far better than I do.
Thanks for your help with this Ger, it is appreciated  |
Yeah, I saw the list. Been playing with how this works a bit, which is why I asked about defaulting. The problem as I see it is that we don't know what quality level the user generally runs at. For me, the defaults would be the Extreme Performance settings. For another they might be Balanced, or High Performance, or whatever. So I guess the question is, how do we decide? I'd personally go with whatever the UI defaults to, with a possible option to include the default quality as a command line variable. The problem with that is it'd require someone to map the defaults for every command for every quality level, and that's no small task.
One other thing I need to know before I get the skeleton of the parser coded, what do you all intend to call the mod XML file? I intend to have the program determine the location of the mod and install the parsed file in any and all directories where it's present, but to do that I need to know what it's going to be called.