If any other information is needed, please let me know.
GPU: ATI Radeon HD 5770 Series
GPU Clocking: 850Mhz
Driver: Catalyst 10.12 (Latest)
CPU: i5 Intel
OS: Win 6.1
Spoiler: Display
Spoiler: INI File = GLOBALSETTINGS
Moderator: Graf Zahl
Spoiler: Display
Spoiler: INI File = GLOBALSETTINGS
That doesn't mean anything. In scenarios, perhaps I could be the only one at this moment that has the specifications above in the topic post, using the latest SVN's. Of course there are many sceneries that can just be thought of.Salad Viking wrote:Since I haven't seen anyone else reporting this error
If the computer itself was a problem than r1152 would also not work.Salad Viking wrote:I'm going to take a guess and say that it's an error with the machine and not GZDoom.
And you did not create a new topic for this bug report, why?Salad Viking wrote:I have, however, found something interesting to report:
Maybe because it's not a new bug report.Tiger wrote:And you did not create a new topic for this bug report, why?
Honestly, you previous post just gives me another impression that highly upsets me. If you reread your entire previous post, I' am sure you will find it.Salad Viking wrote:Umm... if the latest revision of GZDoom was completely unplayable on everyone's computer, I would assume more people would notice than just you and me.
That is the only thing I can think of just by looking at the SVN logs.Salad Viking wrote:Revision 1152 still works because the build is from before the revision which doesn't work on our machines, which is most likely the voxel branch merger.
Of course not, and I have never stated that he did. However, his GPU is different compared to ours. As a result, where it will work on his GPU may not work with ours. Moreover, as GZDoom does not have a programmer that uses ATI, these issues can easily occur.Salad Viking wrote:I highly doubt that Graf Zahl would upload a completely broken build without having checked to see if it worked.
I just retried it again, and still no dice.Gez wrote:I can confirm it works correctly for me.
Spoiler: DisplayAs I have stated, if any more information is needed, please let me know. I' am also willing to try out experimental builds if needed to help get this issue resolved.
Sure.Enjay wrote:Just in case it helps, it might be worth posting a log file of your startup.
Spoiler: Startup Log
Even with a new INI file, this problem still occurs. Infact the recent picture above uses a new INI with no additional WAD's loaded, other than GZDoom.PK3 and Doom2.wad. So I don't think that will be necessary. If you still need it, I'll paste it on this topic.Graf Zahl wrote:Can you also post your .ini file?
That command line worked for me on r1157.Graf Zahl wrote:Can you also try to start GZDoom with the '-sm2' command line option?
Spoiler: Display
ConfirmedNash wrote:ATI 4870 X2, Catalyst 10.12.
Confirmed HOM with r1158.![]()
![]()
gzdoom.exe -sm2 gets rid of the HOM.
I just did a complete rollback to Catalyst 10.10 drivers, and I get the exact same results with Catalyst 10.12 drivers. Of course, the -sm2 command line resolves the HOM effect. Hopefully you wont need any more testing on that older driver, as I' am going to restore back to the latest version. Hopefully this information helps.Graf Zahl wrote:So, someone with older drivers?