[FEA REQUEST] more info on hack detect

Advanced OpenGL source port fork from ZDoom, picking up where ZDoomGL left off.
[Home] [Download] [Git builds (Win)] [Git builds (Mac)] [Wiki] [Repo] [Bugs&Suggestions]

Moderator: Graf Zahl

Locked
User avatar
nwbeeman
Posts: 146
Joined: Mon Oct 17, 2005 1:18
Location: Tampa

[FEA REQUEST] more info on hack detect

Post by nwbeeman »

I know its not worth your time, but would it be possible to print out

Code: Select all

HACK DETECTED (x,y)
Hack: whatever the hack is
to the console? I would find it entertaining. Something you may be able to add once you get all the important stuff done, or a feature you could add just as an excuse to up the version number by a letter if you haven't thought of anything new in a while. (I doubt that, because you seem to have taken ZDOOM over and added every feature that makes it kickass). Wonder if anyone still plays ZDOOM? :?:

Also, I envy you. You are one of the few people on this planet that can actually look at a crash log and figure it out

Keep up the damn good work.
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Post by Graf Zahl »

That line is just some debug output I forget to comment out. It merely means the engine found some open sectors. It doesn't have any direct implications which can be determined only during rendering.
nwbeeman wrote: Also, I envy you. You are one of the few people on this planet that can actually look at a crash log and figure it out
That isn't really that hard if you have a .map file with all the addresses of the functions and a complete assembly output of the code. All you have to do is look which function is represented by an address and then look up the code that is there.

Considering that, a ZDoom crash log is as useless to me as to anybody else except Randy.
Locked

Return to “GZDoom”