godfatherpayne Posted September 3, 2017 (edited) Is there any way to fix that? Edited September 3, 2017 by godfatherpayne : . 0 Share this post Link to post
1 scifista42 Posted September 3, 2017 (edited) You really don't provide us with enough information that would allow us to identify the source of the problem or to fix the problem. Edited September 3, 2017 by scifista42 0 Share this post Link to post
0 everennui Posted September 3, 2017 I think it could be a number of things. Do you have enough ventilation in your case? I THINK you'll have problems if you run a huge bottleneck (I do). What is your display setup? Mine crashes if I use two displays like clockwork. The best thing I can recommend is getting an older build. That might help. Are your drivers up to date? 0 Share this post Link to post
0 DynamiteKaitorn Posted March 7, 2018 When I use GZDB's Visual mode it two will also crash. I'm not sure what causes it so I recommend you save BEFORE entering visual mode. :l 0 Share this post Link to post
0 Kappes Buur Posted March 7, 2018 (edited) I'm not sure if this applies to your dilemna, do you have DirectX 9.0 installed? On the official GZDoom Builder 1.14 page it states under Required Software DirectX 9.0 Runtime. Notice: required even if you already have DirectX 10, 11 or 12 installed. Edited March 7, 2018 by Kappes Buur 0 Share this post Link to post
0 zetsuboupayne Posted May 10, 2019 I have encountered the same problem after (almost) two damn years and losing my account. I'll see if installing DX9 solves it since I formatted my PC recently. 0 Share this post Link to post
0 zetsuboupayne Posted May 10, 2019 This time it gave an error screen. Spoiler ***********SYSTEM INFO*********** OS: Microsoft Windows 7 Ultimate GPU: Intel(R) HD Graphics GZDB: R2787 ********EXCEPTION DETAILS******** Referência de objeto não definida para uma instância de um objeto. em CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.GetSectorData(Sector s) na x:\Source\Plugins\BuilderModes\VisualModes\BaseVisualMode.cs:linha 697 em CodeImp.DoomBuilder.BuilderModes.BaseVisualSector.GetSectorData() na x:\Source\Plugins\BuilderModes\VisualModes\BaseVisualSector.cs:linha 112 em CodeImp.DoomBuilder.BuilderModes.BaseVisualSector.Rebuild() na x:\Source\Plugins\BuilderModes\VisualModes\BaseVisualSector.cs:linha 208 em CodeImp.DoomBuilder.BuilderModes.BaseVisualSector..ctor(BaseVisualMode mode, Sector s) na x:\Source\Plugins\BuilderModes\VisualModes\BaseVisualSector.cs:linha 81 em CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.CreateVisualSector(Sector s) na x:\Source\Plugins\BuilderModes\VisualModes\BaseVisualMode.cs:linha 395 em CodeImp.DoomBuilder.VisualModes.VisualMode.ProcessSidedefCulling(Sidedef sd) na x:\Source\Core\VisualModes\VisualMode.cs:linha 635 em CodeImp.DoomBuilder.VisualModes.VisualMode.DoCulling() na x:\Source\Core\VisualModes\VisualMode.cs:linha 534 em CodeImp.DoomBuilder.VisualModes.VisualMode.OnProcess(Int64 deltatime) na x:\Source\Core\VisualModes\VisualMode.cs:linha 1132 em CodeImp.DoomBuilder.BuilderModes.BaseVisualMode.OnProcess(Int64 deltatime) na x:\Source\Plugins\BuilderModes\VisualModes\BaseVisualMode.cs:linha 1193 em CodeImp.DoomBuilder.Windows.MainForm.processor_Tick(Object sender, EventArgs e) na x:\Source\Core\Windows\MainForm.cs:linha 4241 em System.Windows.Forms.Timer.OnTick(EventArgs e) em System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) em System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) 0 Share this post Link to post
0 zetsuboupayne Posted May 10, 2019 (edited) wait it went back to normal what the fuck edit: IT FUCKING DIDNT WHAT THE HELL IS WRONG WITH THIS GOD DAMN PROGRAM Edited May 10, 2019 by zetsuboupayne 0 Share this post Link to post
Is there any way to fix that?
Edited by godfatherpayne : .Share this post
Link to post