Page 56 of 97

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Sun Apr 29, 2018 9:22 am
by ZZYZX

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Mon Apr 30, 2018 4:30 pm
by Bridgeburner56
No change unfortunately. x64 still doesn't work and the crash is still ocurring

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Sat May 05, 2018 12:05 am
by Kappes Buur
Bridgeburner56 wrote:No change unfortunately. x64 still doesn't work and the crash is still ocurring
In times of yore, running the DB2 installer would install all necessary software to have a working editor.
That was with Windows 7, but from what others have mentioned this also works with Windows 10.
After that you can install GZDBBF.r3012 and it should work.

[edit]
If you have .NET Framework 4.6 installed then installing the x86 version of r3018 shouild also work.
And if you have a 64 bit system, the same goes for the x64 version of r3018.

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Sat May 05, 2018 11:55 pm
by Bridgeburner56
Kappes Buur wrote:
Bridgeburner56 wrote:No change unfortunately. x64 still doesn't work and the crash is still ocurring
In times of yore, running the DB2 installer would install all necessary software to have a working editor.
That was with Windows 7, but from what others have mentioned this also works with Windows 10.
After that you can install GZDBBF.r3018 and it should work.

If you have .NET Framework 4.6 installed then installing the x64 version shouild also work.
Thanks for that, I'll give it a shot

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Mon May 07, 2018 6:05 am
by Batandy
To fix my black screen issue, i simply deleted everything from the GZDB's install folder and dropped in version 2.3.0.3012 (0a5a2e8) which should be this one if i'm not mistaken: https://devbuilds.drdteam.org/gzdbbf/GZ ... x-r3012.7z

After this it works even if i don't have the latest version, but it's better than nothing.

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Mon May 07, 2018 9:25 pm
by Kappes Buur
Batandy wrote:To fix my black screen issue, i simply deleted everything from the GZDB's install folder and dropped in version 2.3.0.3012 (0a5a2e8) which should be this one if i'm not mistaken: https://devbuilds.drdteam.org/gzdbbf/GZ ... x-r3012.7z

After this it works even if i don't have the latest version, but it's better than nothing.
The r3018 versions are build against .NET Framework 4.6.x.
Do you have that installed on your system ?

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Tue May 08, 2018 1:50 am
by Batandy
Kappes Buur wrote:
Batandy wrote:To fix my black screen issue, i simply deleted everything from the GZDB's install folder and dropped in version 2.3.0.3012 (0a5a2e8) which should be this one if i'm not mistaken: https://devbuilds.drdteam.org/gzdbbf/GZ ... x-r3012.7z

After this it works even if i don't have the latest version, but it's better than nothing.
The r3018 versions are build against .NET Framework 4.6.x.
Do you have that installed on your system ?
Just checked in regedit, i do have 4.6.1 (DWORD: 394271), Windows 7 user

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Tue May 08, 2018 11:15 am
by Kappes Buur
Batandy wrote: Just checked in regedit, i do have 4.6.1 (DWORD: 394271), Windows 7 user
Okay, so 4.6.1 seems to be installed.

When you run r3018, what does the generated GZBuilder.log logfile say ?
Perhaps that could provide a clue. Upload its contents for someone to look at.

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Wed May 09, 2018 4:25 am
by Batandy
Kappes Buur wrote:
Batandy wrote: Just checked in regedit, i do have 4.6.1 (DWORD: 394271), Windows 7 user
Okay, so 4.6.1 seems to be installed.

When you run r3018, what does the generated GZBuilder.log logfile say ?
Perhaps that could provide a clue. Upload its contents for someone to look at.
Nevermind, i've just tried updating again after one week of using the outdated ver. and did manage to get it working for some reason. I've clean reinstalled everything and that did it apparently.

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Thu May 10, 2018 5:03 am
by ZZYZX
Looks like SlimDX version change issue. I honestly still don't know how GZDB interacts with SlimDX — it clearly has it bundled, but it won't work without also installing it system-wide, so I don't understand why bundle it then..?
But this is done ever since CodeImp's very first DB2, so idk. Should make sense, probably.

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Sat May 12, 2018 7:11 am
by boris
There seems to be something wrong with the acc.exe that's included in 3018 (in fact with the one that came with 3012). It won't compile scripts for me, telling me that it can't find zcommon.acs. Apparently it won't look for include files in the folder where the .exe is. Also, the acc.exe versioned 1.56 that comes with GZDB-BF isn't the official 1.56 (why?).

Here's a test I made. My script file is pretty simple:

Code: Select all

#include "zcommon.acs"

script 1 open
{
	Print(s:"Hello, world!");
}
So my test directory strucute looks like this:

d:\test
d:\test\hello.acs
d:\test\acc156 (with acc.exe, zcommon.acs etc)
d:\test\acc-gzdbbf-3018 (with acc.exe, zcommon.acs etc)


Content of folder with official ACC 1.56

Code: Select all

D:\test>dir acc156
 Datenträger in Laufwerk D: ist Daten
 Volumeseriennummer: 5C81-92DF

 Verzeichnis von D:\test\acc156

12.05.2018  14:30    <DIR>          .
12.05.2018  14:30    <DIR>          ..
24.10.2017  09:25            76.800 acc.exe
05.12.2016  00:32               480 zcommon.acs
23.10.2017  03:03            34.855 zdefs.acs
23.10.2017  03:03            12.159 zspecial.acs
05.12.2016  00:32               240 zwvars.acs

Content of folder with ACC 1.56 that comes with GZDB-BF 3018

Code: Select all

D:\test>dir acc-gzdbbf-3018
 Datenträger in Laufwerk D: ist Daten
 Volumeseriennummer: 5C81-92DF

 Verzeichnis von D:\test\acc-gzdbbf-3018

12.05.2018  14:37    <DIR>          .
12.05.2018  14:37    <DIR>          ..
10.04.2018  20:05            75.776 acc.exe
10.04.2018  20:04               480 zcommon.acs
10.04.2018  20:04            34.855 zdefs.acs
10.04.2018  20:04            12.185 zspecial.acs
10.04.2018  20:04               240 zwvars.acs
               5 Datei(en),        123.536 Bytes

Compiling hello.acs from d:\test, with calling d:\test\acc156\acc.exe:

Code: Select all

D:\test>acc156\acc.exe hello.acs

Original ACC Version 1.10 by Ben Gokey
Copyright (c) 1995 Raven Software, Corp.

This is version 1.56 (Oct 24 2017)
This software is not supported by Raven Software or Activision
ZDoom changes and language extensions by Randy Heit
Further changes by Brad Carney
Even more changes by James Bentler
Some additions by Michael "Necromage" Weber
Error reporting improvements and limit expansion by Ty Halderman
Include paths added by Pascal vd Heiden
Host byte order: LITTLE endian

"hello.acs":
  6 lines (1588 included)
  0 functions
  1 script
    1 open
  0 global variables
  0 world variables
  0 map variables
  0 global arrays
  0 world arrays
  object "hello.o": 104 bytes
All fine and well.


Compiling hello.acs from d:\test, with calling d:\test\acc-gzdbbf-3018\acc.exe:

Code: Select all

D:\test>acc-gzdbbf-3018\acc.exe hello.acs

Original ACC Version 1.10 by Ben Gokey
Copyright (c) 1995 Raven Software, Corp.

This is version 1.56 (Apr 10 2018)
This software is not supported by Raven Software or Activision
ZDoom changes and language extensions by Randy Heit
Further changes by Brad Carney
Even more changes by James Bentler
Some additions by Michael "Necromage" Weber
Error reporting improvements and limit expansion by Ty Halderman
Include paths added by Pascal vd Heiden
Host byte order: LITTLE endian

**** ERROR ****
Line 1 in file "hello.acs" ...
hello.acs:1: Couldn't find include file "zcommon.acs".
As expected, replacing the acc.exe that comes with GZDB-BF with the official one also lets me compile the scripts from the script editor.

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Mon May 14, 2018 5:04 am
by Tormentor667
Permanently getting an error in visual mode when editing the map, but it only happens if things are displayed (version R3018 64bit)

Code: Select all

***********SYSTEM INFO***********
OS: Microsoft Windows 7 Ultimate 
GPU: VNC Mirror Driver
GZDB: R3018

********EXCEPTION DETAILS********
Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei CodeImp.DoomBuilder.Rendering.Renderer3D.RenderModels(Boolean lightpass, Boolean trans)
   bei CodeImp.DoomBuilder.Rendering.Renderer3D.FinishGeometry()
   bei CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.OnRedrawDisplay()
   bei CodeImp.DoomBuilder.Windows.MainForm.RedrawDisplay()
   bei CodeImp.DoomBuilder.VisualModes.VisualMode.OnProcess(Int64 deltatime)
   bei CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.OnProcess(Int64 deltatime)
   bei CodeImp.DoomBuilder.Windows.MainForm.processor_Tick(Object sender, EventArgs e)
   bei System.Windows.Forms.Timer.OnTick(EventArgs e)
   bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Mon May 14, 2018 5:40 am
by ZZYZX
Odd. Will check.

As for acc: this acc was given to me by someone... I forgot who honestly, but someone with pink nickname on ZDoom Discord ;P
Because "devbuilds are too old and this is the latest-latest build".
edit: actually I built it myself, but yea, it's one of the devbuilds.

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Mon May 14, 2018 5:16 pm
by Kappes Buur
Hmmm, I wonder what the difference is between the two
  • This is version 1.56 (Oct 24 2017)
  • This is version 1.56 (Apr 10 2018)
since acc.exe on the github page had not been updated since Oct 2017.

Re: GZDoomBuilder-Bugfix, a maintenance fork of GZDB

Posted: Mon May 21, 2018 4:31 pm
by Xabis
Looks like the Apr 10 version is no longer including its base directory as a search path, so its no longer finding the zcommon.acs

A quick fix is to update the acc script params to pass the compiler dir in as an include.

I have attached a quick patch as a workaround.