joe-ilya Posted August 30, 2014 It keeps crashing it when I grab it. Do I miss a file or something? 0 Share this post Link to post
DaniJ Posted August 30, 2014 Er, probably? With absolutely zero information about your set up, theres very little anyone can do to help. Which version of Doomsday are you using? Wheres your doomsday.out log file? Which add-ons are you running? 0 Share this post Link to post
joe-ilya Posted September 12, 2014 I just got into the website, downloaded the final version and that's it. 0 Share this post Link to post
entryway Posted September 12, 2014 I've installed new doomsday_1.14.5.exe and got this I tried on win7x64+core2+8800gts (with outdated drivers 320.49) 0 Share this post Link to post
DaniJ Posted September 13, 2014 Its running perfectly fine for me on win7x64 i7 gtx275 (driver ver 340.52). In fact I've never seen that dialog before on any system I've tried Doomsday on. 0 Share this post Link to post
entryway Posted September 13, 2014 Yes, this dialog is strange. I never saw it before too. 0 Share this post Link to post
entryway Posted September 13, 2014 The latest version I can run is doomsday_1.11.2.exe from 2013-08-29. Starting from 1.12 I get that message. P.S. Ok, now I can start the latest 1.14.5 too. By default it trying to start at fullscreen and I get that message. After checking "[x] Always start in windowed mode" it works fine. 0 Share this post Link to post
DaniJ Posted September 13, 2014 I've tested every driver option in the NVIDIA control panel on my Windows dev system to see if there is perhaps some incompatible configuration. Thus far I've found no configuration resulting in such a dialog. Can you try disabling fullscreen anitaliasing (-nofsaa on the command line)? 0 Share this post Link to post
entryway Posted September 13, 2014 DaniJ said:Can you try disabling fullscreen anitaliasing (-nofsaa on the command line)? Yes, it helps. Message about unsupported hardware: doomsday.exe -iwad D:\games\Doom2\DOOM2.WAD Works fine: doomsday.exe -iwad D:\games\Doom2\DOOM2.WAD -nofsaa My native resolution is 2560x1440. 0 Share this post Link to post
DaniJ Posted September 13, 2014 Thanks for the info. I'll run some tests on Doomsday's custom framebuffer and frame compositor to see if there are any issues... 0 Share this post Link to post
DaniJ Posted September 13, 2014 I've tested Doomsday's framebuffer and on my system at least, rendering to such a large canvas appears to be working fine. Although I can't test such a canvas in fullscreen mode as my monitor's max resolution is 1920x1200. Can you run Doomsday in fullscreen with antialiasing enabled and following the fatal error, post the contents of your doomsday.out (I'm hoping to find a warning or two indicating at what point the display mode change is failing). 0 Share this post Link to post
entryway Posted September 13, 2014 http://pastebin.com/gh6iYYdC P.S. prboom+ works fine with 8x multisampling if it does matter 0 Share this post Link to post
entryway Posted September 13, 2014 If I start with "[x] Always start in window", but without "[ ] Force a safe (640x480) resolution" I get this: http://pastebin.com/LJAWiUyM It opens 1920x1080 or so black window and fails with that message. 0 Share this post Link to post
DaniJ Posted September 13, 2014 entryway said:http://pastebin.com/gh6iYYdCSadly that doesn't help me much as it would appear the display mode change is failing after control is handed off to Qt (no warnings are being logged, indicating that everything appears fine from Doomsday's perspective). P.S. prboom+ works fine with 8x multisampling if it does matterDoomsday will use the NVidia specific CSAA method of antialiasing with a custom framebuffer. I suspect that the coverage-sampled framebuffer Doomsday is requesting isn't supported by your hardware. Can you try forcing 16x CSAA on from the NVidia control panel and see if PrBoom+ behaves the same as Doomsday? 0 Share this post Link to post
entryway Posted September 13, 2014 DaniJ said:Can you try forcing 16x CSAA on from the NVidia control panel and see if PrBoom+ behaves the same as Doomsday? Looks like forcing AA from NVidia control panel does nothing for me. Neither plain 8x, nor 16x CSAA. It does not crash, it just does nothing. Only forcing FXAA gives effect. https://dl.dropboxusercontent.com/u/235592644/clip/2014-09-13_22.03.10.png Ok, probably I should try to update my drivers. Again. I stuck with old version, because all new versions (within a year, I think) cause system crash from time to time if hardware acceleration is enabled in Firefox. But it happened with 560Ti. Now I use old 8800. There are many similar reports on NVidia forums: https://forums.geforce.com/default/topic/625051/r331-drivers-still-crash-nvidia-are-you-listening-/?offset=30 0 Share this post Link to post
entryway Posted September 13, 2014 entryway said:Ok, probably I should try to update my drivers. Done. I've installed 340.52-desktop-win8-win7-winvista-64bit-english-whql.exe. Unfortunately it does not help. Doomsday can't start with default settings. 0 Share this post Link to post