Program crashes

[Mushad]

After a Windows 10 update, I've opened the program and it showed in my two monitors, but the mouse was visualized only in one monitor, and the menus was running in the other one. It was difficult to imagin where the mouse was actived because it was showed in the monitor where it did'nt work.

Now the program doesn't open, and I get the following message:

Much to our regret we must report the program has encountered an error.

Please let us know at ​http://trac.wildfiregames.com/ and attach the crashlog.txt and crashlog.dmp files.

Details: unhandled exception (Access violation reading 0x00000004)

Location: unknown:0 (?)

Call stack:

(error while dumping stack: No stack frames found) errno = 2 (Error during IO) OS error = 0 (no error code was set)

[Stan]

According to the crashlog you uploaded you have an issue with the Prefer GLSL option in the game, try disabling it.

Thanks for the report.

>	pyrogenesis.exe!CShaderTechnique::BeginPass(int pass=0) Line 134	C++	Symbols loaded.
 	pyrogenesis.exe!CLogger::Render() Line 215	C++	Symbols loaded.
 	pyrogenesis.exe!Render() Line 264	C++	Symbols loaded.
 	pyrogenesis.exe!Frame() Line 416	C++	Symbols loaded.
 	pyrogenesis.exe!RunGameOrAtlas(int argc=1, const char * * argv=0x00e70008) Line 634	C++	Symbols loaded.
 	pyrogenesis.exe!SDL_main(int argc=1, char * * argv=0x00e70008) Line 680	C++	Symbols loaded.
 	pyrogenesis.exe!main_utf8(int argc=1, char * * argv=0x00e70008) Line 126	C	Symbols loaded.
 	pyrogenesis.exe!wmain(int argc=1, unsigned short * * wargv=0x008da898, unsigned short * wenvp=0x008cee88) Line 151	C	Symbols loaded.
 	pyrogenesis.exe!__tmainCRTStartup() Line 623	C	Non-user code. Symbols loaded.
 	pyrogenesis.exe!CallStartupWithinTryBlock() Line 364	C++	Symbols loaded.
 	kernel32.dll!76ef6359()	Unknown	Non-user code. No matching binary found.

[Mushad]

Thanks for your time and the answer. It has worked. And exiting the application and enabling again the GLSL option, continues working.

[Stan]

The underlying issue will be fixed in the next version, so I'm closing this ticket; Thanks for the report.