by Graf Zahl » Wed Oct 22, 2014 4:17 am
Not only that, the report is lacking any information about hardware/drivers whatsoever.
This problem seems to be limited to a subset of AMD users but with 3 people reporting so far it's nearly impossible to narrow down, what is the cause. The first advice would always be to check if you got the most recent driver - in any case I need GZDoom's startup log and preferably a DxDiag log, too.
Not only that, the report is lacking any information about hardware/drivers whatsoever.
This problem seems to be limited to a subset of AMD users but with 3 people reporting so far it's nearly impossible to narrow down, what is the cause. The first advice would always be to check if you got the most recent driver - in any case I need GZDoom's startup log and preferably a DxDiag log, too.