Projects that have specifically been abandoned or considered "dead" get moved here, so people will quit bumping them. If your project has wound up here and it should not be, contact a moderator to have it moved back to the land of the living.
Marnetmar wrote:I'm unable to start this, I keep getting the "X has stopped working" error. I know it doesn't have anything to do with slimdx or all that jazz since I already have Doom Builder 2 installed. Little help?
Can you post "GZBuilder.log" file located in: Windows Vista, 7: "C:\Users\{user}\AppData\Local\Doom Builder\" Windows XP: "C:\Documents and Settings\{user}\Local Settings\Application Data\Doom Builder\"
Huh, that's odd. The regular builder log was there but there was no GZbuilder log :S
Odd, I'm getting an error every time I try to go into Visual Mode. I load up the same map in regular Doom Builder and it works fine, but here it gives me an error - Index was outside the bounds of the array. I created a visual mode camera in a basic room, and yet cannot successfully load it in this editor.
Here is what I get when I hit details, perhaps it helps in figuring out what is wrong.
Spoiler:
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text ************** System.IndexOutOfRangeException: Index was outside the bounds of the array. at CodeImp.DoomBuilder.VisualModes.VisualGeometry.CalculateNormalsAndShading() at CodeImp.DoomBuilder.VisualModes.VisualGeometry.SetVertices(ICollection`1 verts) at CodeImp.DoomBuilder.BuilderModes.VisualUpper.Setup() at CodeImp.DoomBuilder.BuilderModes.BaseVisualSector.Rebuild() at CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.CreateVisualSector(Sector s) at CodeImp.DoomBuilder.VisualModes.VisualMode.ProcessSidedefCulling(Sidedef sd) at CodeImp.DoomBuilder.VisualModes.VisualMode.DoCulling() at CodeImp.DoomBuilder.VisualModes.VisualMode.OnProcess(Double deltatime) at CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.OnProcess(Double deltatime) at CodeImp.DoomBuilder.Windows.MainForm.processor_Tick(Object sender, EventArgs e) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
deathstalker666 wrote:Odd, I'm getting an error every time I try to go into Visual Mode. I load up the same map in regular Doom Builder and it works fine, but here it gives me an error - Index was outside the bounds of the array. I created a visual mode camera in a basic room, and yet cannot successfully load it in this editor.
Any ideas what the problem is with the editor?
I was unable to replicate this problem, but try this Builder.exe (added sanity check to CalculateNormalsAndShading() function, let's see if that helps)
Marnetmar wrote:I'm unable to start this, I keep getting the "X has stopped working" error. I know it doesn't have anything to do with slimdx or all that jazz since I already have Doom Builder 2 installed. Little help?
Can you post "GZBuilder.log" file located in: Windows Vista, 7: "C:\Users\{user}\AppData\Local\Doom Builder\" Windows XP: "C:\Documents and Settings\{user}\Local Settings\Application Data\Doom Builder\"
Huh, that's odd. The regular builder log was there but there was no GZbuilder log :S
That's odd indeed, because creating a log file is among the first things Doom Builder 2 does after launch, so either dependencies aren't met (but they are met in you'r case) or GZDoomBuilder files are somehow damaged (what version of GZDoomBuilder do you have? Have you tried downloading newer ones?). And what version of Windows are you using?
deathstalker666 wrote:Odd, I'm getting an error every time I try to go into Visual Mode. I load up the same map in regular Doom Builder and it works fine, but here it gives me an error - Index was outside the bounds of the array. I created a visual mode camera in a basic room, and yet cannot successfully load it in this editor.
Any ideas what the problem is with the editor?
I was unable to replicate this problem, but try this Builder.exe (added sanity check to CalculateNormalsAndShading() function, let's see if that helps)
1. Wouldn't it be better to use a UDMF? I honestly don't see the use of other branches if we have a universal format. The only format we have besides UDMF is Hexen anyway, is there a reason why this one has been left behind?
2. Unix, as this is built for GzDoom, this probably isn't the most compatible builder for Skulltag. That especially applies to the last comment you mentioned. You can only save to the GZDoom port, meaning you are trying to play GzDoom by using Skulltag.
When I am making changes to textures/things in GZDoom Visual Mode, it doesn't apply in-game. I would have to make the changes in regular Visual Mode.
Any fix to this?
I've changed to 1.04a and the problem still happens. But no I can't even use regular Visual Mode.. Something about an Array error.
Also, why can't I use the Skulltag Things?
To use Skulltag things copy "Skulltag_DoomHexen.cfg" from "<GZDoomBuilder>\Configurations\Configs for other games\" to "<GZDoomBuilder>\Configurations\" To fix Array error try replacing Builder.exe with one mentioned in a post previous to your's.
When I am making changes to textures/things in GZDoom Visual Mode, it doesn't apply in-game. I would have to make the changes in regular Visual Mode.
Any fix to this?
I've changed to 1.04a and the problem still happens. But no I can't even use regular Visual Mode.. Something about an Array error.
Also, why can't I use the Skulltag Things?
To use Skulltag things copy "Skulltag_DoomHexen.cfg" from "<GZDoomBuilder>\Configurations\Configs for other games\" to "<GZDoomBuilder>\Configurations\" To fix Array error try replacing Builder.exe with one mentioned in a post previous to your's.
A Linux-only fork can come in handy for people who use Linux that are currently wanting to map for ZDoom without usage of a hex editor and so-called godlike brain processing power and with the ease of Doom Builder aswell. And don't forget to call it GTKBuilder, QtBuilder or even WxDBuilder depending on what user interface API it uses.
gdm413229 wrote:A Linux-only fork can come in handy for people who use Linux that are currently wanting to map for ZDoom without usage of a hex editor and so-called godlike brain processing power and with the ease of Doom Builder aswell. And don't forget to call it GTKBuilder, QtBuilder or even WxDBuilder depending on what user interface API it uses.
It would be one hell of a job, since Doom Builder 2 is written in C# and DirectX... I think Slade 3 has much better chances to be ported to Linux.
by Marnetmar » Wed Apr 25, 2012 6:20 pm 
.
