NQ4K by aesrude on Windows 10
category: general [glöplog]
http://www.pouet.net/prod.php?which=62374
Has anyone had any luck getting this one to work on a modern system? All the 'tricks' I know don't work. People sometimes suggest I post directly on the demo's page but nobody's written a message there in three years, which makes sense what with the problems I'm having on WinOS X. And the safe compile doesn't count!
Has anyone had any luck getting this one to work on a modern system? All the 'tricks' I know don't work. People sometimes suggest I post directly on the demo's page but nobody's written a message there in three years, which makes sense what with the problems I'm having on WinOS X. And the safe compile doesn't count!
recompress didn't work? that's strange, maybe he had used some more experimental features of clinkster?!
you can read more info on this topic on this thread aswell
you should still mail the creator and ask him for a more stable final version imho.
you can read more info on this topic on this thread aswell
you should still mail the creator and ask him for a more stable final version imho.
I just downloaded it and ran the nq4k_fs_1366x768_msaa file from windows explorer and it worked fine, showed gfx and played music.
I'm on Win10 ver 10.0.16288.1 if that helps. AMD radeon something or other video card.
I'm on Win10 ver 10.0.16288.1 if that helps. AMD radeon something or other video card.
Crashes here on GTX 1080. I investigated it a bit and saw that the D3D10CreateDeviceAndSwapChain call fails. The differences to the "safe" version (which works) are that the safe version runs windowed whereas the others run fullscreen, and the safe version requests multisample count 1 quality 0 where the others request multisample count 8 quality 8.
My guess is that the multisample count/quality combination is rejected by the driver.
My guess is that the multisample count/quality combination is rejected by the driver.
Not sure what "modern system" is supposed to be, but the prod works fine on a i3/7100 with gf660 under win7x64... I´d suspect a driver issue...
Thanks for your responses guys. Usually AMD cards are a problem but not this time it would seem. I wonder what changed over the years. Oh and by modern system I pretty much meant Windows 10. It seems to handle things slightly differently now. I tried enabling my shitty onboard AMD graphics alongside my regular nVidia card but it still crashes with the onboard set to main display. Maybe I'll get to see it run as intended eventually, one day...