Re: GZDoomBuilder 1.06: GZDoom features in Doom Builder 2
Posted: Sun May 20, 2012 3:44 am
by Tormentor667
Didn't solve it unfortunately.
Spoiler:
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
System.FormatException: Die Eingabezeichenfolge hat das falsche Format.
bei System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
bei System.Number.ParseSingle(String value, NumberStyles options, NumberFormatInfo numfmt)
bei System.Single.Parse(String s, NumberStyles style, NumberFormatInfo info)
bei CodeImp.DoomBuilder.GZBuilder.IO.ModelDefParser.parseModelDef(Dictionary`2 modelDefEntriesByName, String path, String modelDef)
bei CodeImp.DoomBuilder.GZBuilder.IO.ModelDefParser.Parse(Dictionary`2 modelDefEntriesByName, String path, String fileName)
bei CodeImp.DoomBuilder.GZBuilder.IO.ModelDefParser.ParseFolder(Dictionary`2 modelDefEntriesByName, String path)
bei CodeImp.DoomBuilder.GZBuilder.GZGeneral.loadModelDefs()
bei CodeImp.DoomBuilder.GZBuilder.GZGeneral.OnMapOpenEnd()
bei CodeImp.DoomBuilder.MapManager.InitializeOpenMap(String filepathname, MapOptions options)
bei CodeImp.DoomBuilder.General.OpenMapFileWithOptions(String filename, MapOptions options)
bei CodeImp.DoomBuilder.General.OpenMapFile(String filename, MapOptions options)
bei CodeImp.DoomBuilder.General.OpenMap()
bei CodeImp.DoomBuilder.Actions.Action.Begin()
bei CodeImp.DoomBuilder.Actions.ActionManager.InvokeAction(String actionname)
bei CodeImp.DoomBuilder.Windows.MainForm.InvokeTaggedAction(Object sender, EventArgs e)
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
When opening the map, I do get the map 2D view for a short moment but then immediately the error message pops up. It's directly when parsing the MODELDEF, though it happens only once and when hitting "Continue" I actually can work in 2D mode. But when launching the 3D mode, I get this error: (D3ERR_INVALIDCALL: Invalid call (-2005540516),
Spoiler:
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
SlimDX.Direct3D9.Direct3D9Exception: D3DERR_INVALIDCALL: Invalid call (-2005530516)
bei SlimDX.Result.Throw[T](Object dataKey, Object dataValue)
bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
bei SlimDX.Direct3D9.Device.BeginScene()
bei CodeImp.DoomBuilder.Rendering.D3DDevice.StartRendering(Boolean clear, Color4 backcolor, Surface target, Surface depthbuffer)
bei CodeImp.DoomBuilder.Rendering.Renderer3D.Start()
bei CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.OnRedrawDisplay()
bei CodeImp.DoomBuilder.Windows.MainForm.RedrawDisplay()
bei CodeImp.DoomBuilder.VisualModes.VisualMode.OnProcess(Double deltatime)
bei CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.OnProcess(Double 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)
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
...and the only thing I can do then is shutting down GZDB Hope this helps with tracking down the issue.
Re: GZDoomBuilder 1.06: GZDoom features in Doom Builder 2
Posted: Sun May 20, 2012 6:29 am
by MaxED
Tormentor667 wrote:Didn't solve it unfortunately.
Spoiler:
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
System.FormatException: Die Eingabezeichenfolge hat das falsche Format.
bei System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
bei System.Number.ParseSingle(String value, NumberStyles options, NumberFormatInfo numfmt)
bei System.Single.Parse(String s, NumberStyles style, NumberFormatInfo info)
bei CodeImp.DoomBuilder.GZBuilder.IO.ModelDefParser.parseModelDef(Dictionary`2 modelDefEntriesByName, String path, String modelDef)
bei CodeImp.DoomBuilder.GZBuilder.IO.ModelDefParser.Parse(Dictionary`2 modelDefEntriesByName, String path, String fileName)
bei CodeImp.DoomBuilder.GZBuilder.IO.ModelDefParser.ParseFolder(Dictionary`2 modelDefEntriesByName, String path)
bei CodeImp.DoomBuilder.GZBuilder.GZGeneral.loadModelDefs()
bei CodeImp.DoomBuilder.GZBuilder.GZGeneral.OnMapOpenEnd()
bei CodeImp.DoomBuilder.MapManager.InitializeOpenMap(String filepathname, MapOptions options)
bei CodeImp.DoomBuilder.General.OpenMapFileWithOptions(String filename, MapOptions options)
bei CodeImp.DoomBuilder.General.OpenMapFile(String filename, MapOptions options)
bei CodeImp.DoomBuilder.General.OpenMap()
bei CodeImp.DoomBuilder.Actions.Action.Begin()
bei CodeImp.DoomBuilder.Actions.ActionManager.InvokeAction(String actionname)
bei CodeImp.DoomBuilder.Windows.MainForm.InvokeTaggedAction(Object sender, EventArgs e)
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
When opening the map, I do get the map 2D view for a short moment but then immediately the error message pops up. It's directly when parsing the MODELDEF, though it happens only once and when hitting "Continue" I actually can work in 2D mode. But when launching the 3D mode, I get this error: (D3ERR_INVALIDCALL: Invalid call (-2005540516),
Spoiler:
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
SlimDX.Direct3D9.Direct3D9Exception: D3DERR_INVALIDCALL: Invalid call (-2005530516)
bei SlimDX.Result.Throw[T](Object dataKey, Object dataValue)
bei SlimDX.Result.Record[T](Int32 hr, Boolean failed, Object dataKey, Object dataValue)
bei SlimDX.Direct3D9.Device.BeginScene()
bei CodeImp.DoomBuilder.Rendering.D3DDevice.StartRendering(Boolean clear, Color4 backcolor, Surface target, Surface depthbuffer)
bei CodeImp.DoomBuilder.Rendering.Renderer3D.Start()
bei CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.OnRedrawDisplay()
bei CodeImp.DoomBuilder.Windows.MainForm.RedrawDisplay()
bei CodeImp.DoomBuilder.VisualModes.VisualMode.OnProcess(Double deltatime)
bei CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.OnProcess(Double 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)
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
...and the only thing I can do then is shutting down GZDB Hope this helps with tracking down the issue.
Hmm... Check that decimal separator is point, not comma on your OS (it should be somewhere under Control Pannel - Regional standards).
Re: GZDoomBuilder 1.06: GZDoom features in Doom Builder 2
Posted: Sun May 20, 2012 8:44 am
by Tormentor667
I have a german Windows 7 and in Germany it's usual to have a comma as seperator, not a point. You should take this into consideration as Germany isn't the only country where this is usual.
Re: GZDoomBuilder 1.06: GZDoom features in Doom Builder 2
Posted: Sun May 20, 2012 8:54 am
by MaxED
Tormentor667 wrote:I have a german Windows 7 and in Germany it's usual to have a comma as seperator, not a point. You should take this into consideration as Germany isn't the only country where this is usual.
Well, it's also usual in Russia, but I haven't had any problems with it when I changed it to point in Russian versions of Windows XP and 7...
Anyway, currently I'm going to rewrite my modeldef parsing code in a way other Doom Builder 2 parsers work (it should also allow me to load MODELDEFs and models from wads and pk3s), so this problem should be gone in one of 1.06 updates.
Re: GZDoomBuilder 1.06: GZDoom features in Doom Builder 2
Posted: Mon May 21, 2012 4:50 am
by Tormentor667
Glad to hear, so I am just being a bit patient now
Re: GZDoomBuilder 1.06: GZDoom features in Doom Builder 2
Posted: Tue May 22, 2012 2:20 am
by MaxED
Tormentor667 wrote:Glad to hear, so I am just being a bit patient now
Check out 1.06a
Re: GZDoomBuilder 1.06a: GZDoom features in Doom Builder 2
Posted: Tue May 22, 2012 1:16 pm
by Tormentor667
Pretty nice, I was able to use 3D Mode without any further crashes Though there are some problems with some models though. The first 2 attached shots show a distortion with some models. They work fine ingame but look strange in GZDoomBuilder. On the other hand, as in shot 3, transparent textures will be displayed as white instead of transparent.
Other than that very well done in terms of bugfixing
Re: GZDoomBuilder 1.06a: GZDoom features in Doom Builder 2
Posted: Tue May 22, 2012 2:57 pm
by MaxED
Tormentor667 wrote:Pretty nice, I was able to use 3D Mode without any further crashes Though there are some problems with some models though. The first 2 attached shots show a distortion with some models. They work fine ingame but look strange in GZDoomBuilder. On the other hand, as in shot 3, transparent textures will be displayed as white instead of transparent.
Other than that very well done in terms of bugfixing
Oh wow...
I completely forgot that models can have transparent textures (that'll be easy to fix fixed in 1.06b).
But I haven't seen such distortions while I tested the editor (I noticed that some of MD2 models have their UVs messed up, but hasn't seen any problems with geometry)... Looks like vertex order gets messed in some cases.
Can you send me one of such distorted models for testing?..
Re: GZDoomBuilder 1.06b: GZDoom features in Doom Builder 2
Posted: Wed May 23, 2012 12:35 am
by Tormentor667
I am currently at work, but I will check for an example model this evening.
Re: GZDoomBuilder 1.06b: GZDoom features in Doom Builder 2
Posted: Thu May 24, 2012 1:02 pm
by Tormentor667
Just writing a pm
Re: GZDoomBuilder 1.06b: GZDoom features in Doom Builder 2
Posted: Fri May 25, 2012 5:15 am
by MaxED
Tormentor667 wrote:Just writing a pm
Check out 1.06c
Re: GZDoomBuilder 1.06c: GZDoom features in Doom Builder 2
Posted: Fri May 25, 2012 12:27 pm
by cq75
This is very interesting; CodeImp made a post earlier on some UDMF features I commonly use
CodeImp wrote:You may even want to add the features that my GZDoom Editing plugin has (many UDMF stuff such as flat rotation/scaling/offset, individual high/mid/low texture offsets and auto-align, slopes, etc) ...
Has there been any progress on these features? I would definitely switch from DB2 to this editor if it had DB2's GzDoom editing plugin features.
Re: GZDoomBuilder 1.06c: GZDoom features in Doom Builder 2
Posted: Fri May 25, 2012 12:49 pm
by MaxED
cq75 wrote:This is very interesting; CodeImp made a post earlier on some UDMF features I commonly use
CodeImp wrote:You may even want to add the features that my GZDoom Editing plugin has (many UDMF stuff such as flat rotation/scaling/offset, individual high/mid/low texture offsets and auto-align, slopes, etc) ...
Has there been any progress on these features? I would definitely switch from DB2 to this editor if it had DB2's GzDoom editing plugin features.
GZDoom Builder is based on latest Doom Builder 2 SVN version, so it has all features Doom Builder 2 has (including GZDoom Visual mode and UDMF features).
Re: GZDoomBuilder 1.06c: GZDoom features in Doom Builder 2
Posted: Fri May 25, 2012 8:58 pm
by cq75
Great, downloading!
EDIT - Works great, thanks for making this
Re: GZDoomBuilder 1.06c: GZDoom features in Doom Builder 2
Posted: Mon May 28, 2012 8:19 am
by cq75
Double posted to report an odd problem, it works great on one computer but it doesn't work on another, both of them are running Windows 7 Professional x64, the only difference is the graphics card and one of them is newer and possibly has more windows updates.
Hope this helps with tracking down the issue.
