Software projects like source ports (EDGE, Eternity, etc), launchers like ZDL, and other useful utilities belong in this forum.
Forum rules The Projects forums are ONLY for YOUR PROJECTS! If you are asking questions about a project, either find that project's thread, or start a thread in the General section instead.
As far as I know there's no practical difference between the two for 2P games. (Aside from C/S perhaps causing fewer headaches when firewalls are involved, from what the Wiki says..)
So, I start my game and when I finish, I go back, I see that on the Settings screen, the parameters have disappeared.
The funny thing is that in the qZDL.ini the entry is still there, but if I don't re-enter the parameters, the entry will disappear and my game will start without the parameters.
Then open that bat file, this will turn on qZDL's logging facility and save it to the directory qzdl is located in called "zdl.log". Can you go to the settings tab and verify that the always add arguments box is empty. Then close ZDL, and copy and paste the zdl.log file into a pastebin (such as http://pastebin.com/), you can't use Notepad for this, you must use either Wordpad or Notepad++.
I've seen this bug before but thought I fixed it prior to 3.0.5.4.
QBasicer wrote:I've updated to 3.0.5.6, it should fix this issue. Please update and let me know
Sorry, the error still remains. The values in the "Always Add These Parameters Field" box are still dissapearing like I said before.
Are you sure you are not confusing them with the "Extra Command Line Arguments" box or the extra=... entry in the qZDL.ini file ? Those are being saved properly.
Tormentor667 wrote:For some strange reason, it doesn't save my settings (IWADs, Sourceports), why?!
*EDIT* I could import the ZDL.INI but I guess thats not a solution if I use qZDL for the first time for example.
That's a bug I fixed for 3.0.5.7 (I dropped a prerelease to lzvk25 to see if that fixes their problem, I haven't heard back yet).
The basic problem was that the internal configuration state couldn't get written to the file if the "%APPDATA%/Vectec Software" folder doesn't exist. I've modified the writeINI to create any parent directories required to write the .ini file.
I just tried the version you sent me, as well as this one, and they are working normally.
The only thing is that in my case the "%APPDATA%/Vectec Software" folder or C:\Users\(my computer id)\AppData\Roaming\Vectec Software folder already existed, in fact, it was created from the start when I imported my ZDL.INI settings from the very first time and just like Tormentor said, we need to test it from scratch.
Cool, I can compose a real release tomorrow then. Unfortunately the release date for 3.0.6.0 has slid back, for a few reasons, such as the complexity around reading map names.
I can confirm Tormentor's suspicions, and I think it is even worst, if the "%APPDATA%/Vectec Software" folder does not exist, the settings will NEVER be saved regardless of from where you got your initial settings.
And if it is a first time installation, you better do your settings via the old ZDL and import them because otherwise for some reason the settings will NEVER be saved.
And finally, I think that the inclusion of the entry "nouserconf=1" makes matters worse for first time installations.
I don't know but wouldn't be simpler just to include a "base" ini file, always save it in the same folder as the application itself and never rely on crazy windows folders like "%APPDATA%" which changes from location to location, just like the old ZDL ? I say this because in my profession I also get nasty surprises from time to time because of this reason.
lzvk25 wrote:I can confirm Tormentor's suspicions, and I think it is even worst, if the "%APPDATA%/Vectec Software" folder does not exist, the settings will NEVER be saved regardless of from where you got your initial settings.
And if it is a first time installation, you better do your settings via the old ZDL and import them because otherwise for some reason the settings will NEVER be saved.
Did you try that with 3.0.5.7 pre-release or with the current release? .7 should automatically create the folder, I tested that and it worked for me, so if it doesnt I need to fix it
Tormentor667 wrote:Seems to work now QBasicer, thanks for the info and the fix
Great, I've had a couple of nasty little bugs, I'm glad to get them fixed.
Tormentor667 wrote:So, when do you think are you going to add the wad library?
It's in the pipes, while I haven't started on it directly, I've been working on and planning the changes that have to happen underneath. One of the things that needs to be done is make sure the code is thread safe, which it very much is not at the moment. I think when you see my plans, some people will be very interested.