Hunter_5E Posted March 1, 2020 Posted March 1, 2020 We're told in "graphics_readme.txt" not to edit "Graphics.lua" file directly but rather to use "autoexec.cfg" in \User\Saved Games\DCS\Config. The statsColor command (FPS counter) doesn't work in autoexec.cfg though and only works in Graphics.lua. Is this supposed to work in the autoexec file? Also, there's hardly any info available for using the autoexec. It would be nice if we could have some clear documentation on what is possible with this file.
Worrazen Posted March 2, 2020 Posted March 2, 2020 (edited) That's because various variables are grouped to subitems in a tree-like structure, autoexec starts from the programs root level, so you have to specify the path, unless the variable is a general/global one. options.graphics.statsColor = {nnn,nnn,nnn} This should be the case for all graphics options. For other things you can get clues about this by just looking at the folder structure but this may not be a sure way for all cases. It can take a bit of trial and error. Edited March 2, 2020 by Worrazen Modules: A-10C I/II, F/A-18C, Mig-21Bis, M-2000C, AJS-37, Spitfire LF Mk. IX, P-47, FC3, SC, CA, WW2AP, CE2. Terrains: NTTR, Normandy, Persian Gulf, Syria
Hunter_5E Posted March 2, 2020 Author Posted March 2, 2020 Thanks for that answer, much appreciated - got it working now. Again though, it would be very nice to have some documentation on how to use the autoexec to it's best advantage. Why tell us to use the autoexec.cfg file then not tell us HOW to use it? Why must we use trial and error to figure it out? If I were a trainee bomb squaddie, would you send me to a live bomb and say "Figure it out yourself, you'll be ok!" (Extreme example but same concept) Not all of us are that familiar with the nuts and bolts of DCS and even though we try to learn, it's a lot harder to do so if we can't find any clear documentation and have to rely on random snippets from scattered posts on the forum. Come on ED, how hard would it be to knock up a quick text file outlining the use and syntax of the autoexec.cfg file? It would save us a lot of frustration and wasted time.
Worrazen Posted March 3, 2020 Posted March 3, 2020 Well, there's lot of these small tricks that are documented across the forum and the modding guys who dig deeper know about it so you'll at least get help when you ask most likely, but also search the forum. Modules: A-10C I/II, F/A-18C, Mig-21Bis, M-2000C, AJS-37, Spitfire LF Mk. IX, P-47, FC3, SC, CA, WW2AP, CE2. Terrains: NTTR, Normandy, Persian Gulf, Syria
Hunter_5E Posted March 3, 2020 Author Posted March 3, 2020 That's exactly what I'm on about - small snippets of advice, scattered across the forum and we have to search for ages to find them, then trawl through often lengthy threads to find the bits we need. There can't be a huge list of functions available in the autoexec.cfg file, but from what I can make out, they can be very useful for a number of things. So, why make us search and use trial and error when it would take them literally just minutes to outline them in a simple text file? I don't get it. Far too often we get the standard "search the forum" answer for stuff that could and should be easily documented.
Worrazen Posted March 4, 2020 Posted March 4, 2020 I know I know, it takes someone from the community to do that kind of a list, the staff is busy with development so you can't blame them right. Modules: A-10C I/II, F/A-18C, Mig-21Bis, M-2000C, AJS-37, Spitfire LF Mk. IX, P-47, FC3, SC, CA, WW2AP, CE2. Terrains: NTTR, Normandy, Persian Gulf, Syria
JG14_Smil Posted March 4, 2020 Posted March 4, 2020 That's exactly what I'm on about - small snippets of advice, scattered across the forum and we have to search for ages to find them, then trawl through often lengthy threads to find the bits we need. There can't be a huge list of functions available in the autoexec.cfg file, but from what I can make out, they can be very useful for a number of things. So, why make us search and use trial and error when it would take them literally just minutes to outline them in a simple text file? I don't get it. Far too often we get the standard "search the forum" answer for stuff that could and should be easily documented. If it is so easy, you better get started doing it You *should* have no trouble fitting it into your schedule. DCS has always been this way. New user's, new issue's all the time. If someone wrote the document you ask for, it would soon be outdated. Best wishes and enjoy,
Hunter_5E Posted March 5, 2020 Author Posted March 5, 2020 If it is so easy, you better get started doing it You *should* have no trouble fitting it into your schedule. DCS has always been this way. New user's, new issue's all the time. If someone wrote the document you ask for, it would soon be outdated. Best wishes and enjoy, I would do it myself but... without access to the full list of functions and their proper usage, all I would end up with is a half baked and inaccurate document and I'd get even more grief for posting garbage. What is scattered on the forum is incomplete and unconcise, so not a good source to compile a list from. I'd have to ask ED to provide me with a list of functions so I could make the document - which is what this post is about to begin with. A simple request for information. It's not like I'm asking for a complete manual on all the editable files in DCS - just for one file which they told us to use. It would literally take them just minutes to post a short text document listing the functions (which will already exist somewhere anyway). Sure, there are functions that are for in house testing only. So leave them out and just list the ones they want us to use. Simples. If that's too much to ask then fair enough, slap me down and rain on my parade. I'll just humbly keep quiet and accept the status quo.
Recommended Posts