ZDoom

NeuralStunner wrote:

DOOMERO-21 wrote:nice, i have a question for play gzdoom or zdoom online use the sistem peer to peer or client/server?

Either one. For 2 players it doesn't really matter, for 3 or more Client/Server will generally perform better.

but when are only 2 players, peer to peer is the dominant? is possible change to client/server?

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 [wiki=Command_line_parameters#Multiplayer_options]the Wiki says[/wiki]..)

The "Always Add These Parameters Field" is not saved in the qZDL.ini.

For example I have my game with my mods added.



Then I go to the Settings tab and on the "Always Add These Parameters Field" I enter : -TURBO 200 +logfile C:/WADS/QZDL/zdl-log2.txt



And I check them on C:\Users\(my user)\AppData\Roaming\Vectec Software\qZDL.ini and see that in fact they are written under the entry :

alwaysadd=-TURBO 200 +logfile C:/WADS/QZDL/zdl-log2.txt

Spoiler:

---

Code: Select all

[zdl.general]
autoclose=1
engine=qZDL
version=3.0.5.5 beta (windows/2012-04-18_14-54-01)
importedfrom=C:/WADS/QZDL/zdl.ini
isimported=1
importdate=2012-04-18T07:02:55
quotefiles=enabled
zdllaunch=0
alwaysadd=-TURBO 200 +logfile C:/WADS/QZDL/zdl-log2.txt
[zdl.save]
port=GZDoom
iwad=Doom2
warp=MAP32
skill=4
dlgmode=closed
gametype=0
players=0
file0=C:/WADS/QZDL/ecaweapGZ.zip
file1=C:/WADS/QZDL/asgarden.wad
[zdl.iwads]
i0n=Doom2
i0f=C:/Zdoom2100/DOOM2.WAD
i1n=Doom1
i1f=C:/DOOM/DOOM.WAD
i2n=Heretic
i2f=C:/Heretic13/HERETIC.WAD
i3n=Hexen
i3f=C:/HEXEN/HEXEN.WAD
i4n=TNT
i4f=C:/WADS/Final/tnt.wad
i5n=Plutonia
i5f=C:/WADS/Final/plutonia.wad
[zdl.ports]
p0n=GZDoom
p0f=C:/Zdoom2100/gzdoom.exe
p1n=SkullTag
p1f=C:/Program Files (x86)/Skulltag/skulltag.exe

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.

Spoiler:

---

Code: Select all

[zdl.general]
autoclose=1
engine=qZDL
version=3.0.5.5 beta (windows/2012-04-18_14-54-01)
importedfrom=C:/WADS/QZDL/zdl.ini
isimported=1
importdate=2012-04-18T07:02:55
quotefiles=enabled
zdllaunch=0
[zdl.save]
port=GZDoom
iwad=Doom2
warp=MAP32
skill=4
dlgmode=closed
gametype=0
players=0
file0=C:/WADS/QZDL/ecaweapGZ.zip
file1=C:/WADS/QZDL/asgarden.wad
[zdl.iwads]
i0n=Doom2
i0f=C:/Zdoom2100/DOOM2.WAD
i1n=Doom1
i1f=C:/DOOM/DOOM.WAD
i2n=Heretic
i2f=C:/Heretic13/HERETIC.WAD
i3n=Hexen
i3f=C:/HEXEN/HEXEN.WAD
i4n=TNT
i4f=C:/WADS/Final/tnt.wad
i5n=Plutonia
i5f=C:/WADS/Final/plutonia.wad
[zdl.ports]
p0n=GZDoom
p0f=C:/Zdoom2100/gzdoom.exe
p1n=SkullTag
p1f=C:/Program Files (x86)/Skulltag/skulltag.exe

Could you please take a look at this issue ?

Thanks

Nevermind, I can reproduce it here, I'll have a look. For the sake of others, this is my standard diagnostic guide:

Spoiler:

---

Can you do the following steps for me?

Open qZDL and add the always add arguments and close, such that they get saved in qZDL.ini

Then, can you create the following .bat file (In the same dir as qzdl), such as qzdl-logger.bat:

Code: Select all

qzdl.exe --enable-logger

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.

OK, just in case this helps something :

qzdl log first run - When I enter the values in the "Always Add These Parameters Field" box.

http://pastebin.com/A2RhUxh4

qzdl log second run - When I re-start immediately after finishing a game and discovering that the aforementioned parameters have disappeared.

http://pastebin.com/5Yj27xHZ

lzvk25 wrote:OK, just in case this helps something :

qzdl log first run - When I enter the values in the "Always Add These Parameters Field" box.

http://pastebin.com/A2RhUxh4

qzdl log second run - When I re-start immediately after finishing a game and discovering that the aforementioned parameters have disappeared.

http://pastebin.com/5Yj27xHZ

I've updated to 3.0.5.6, it should fix this issue. Please update and let me know

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.

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.

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.

You (or anybody else) may want to try the latest pre-release at http://zdl.vectec.net/builds/qzdl-win32 ... -02-43.zip. Of course, it's pre-release, so there may be bigger bugs. You can still report them here, though.

QBasicer wrote: You (or anybody else) may want to try the latest pre-release at http://zdl.vectec.net/builds/qzdl-win32 ... -02-43.zip. Of course, it's pre-release, so there may be bigger bugs. You can still report them here, though.

Sorry, I didn't notice the PM

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

Seems to work now QBasicer, thanks for the info and the fix

So, when do you think are you going to add the wad library?

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.