sync dd's wallhack for spectator #817
Conversation
Linear rendering is always enabled by means of either FP16 or sRGB framebuffer (thus making EXT_framebuffer_sRGB mandatory)
It’s safe to do this because entire the rendering pipeline now uses the linear color space.
Note that LimboView.cpp no longer exists in v0.2.0 because it was replaced with LimboWindow.as. # Conflicts: # Sources/Client/Client_Update.cpp # Sources/Client/LimboView.cpp
# Conflicts: # OpenSpades.xcodeproj/project.pbxproj
# Conflicts: # Sources/Client/Client.cpp # Sources/Client/Client_Input.cpp # Sources/Client/Client_NetHandler.cpp # Sources/Client/FTFont.cpp # Sources/Client/LimboView.h # Sources/Gui/StartupScreen.cpp
Currently, the following steps are used: * <90: green * <120: yellow * <200: orange * >200: red It currently looks waaay to colorful. I think a colored bar or something might look best, but for now this works and lets you quickly see how good you can expect the connection to be
Add color coding to ping
# Conflicts: # Resources/Scripts/Gui/ClientUI.as # Resources/Scripts/Gui/MainScreen.as # Resources/Scripts/Gui/StartupScreen.as # Resources/Scripts/Gui/UIControls.as
# Conflicts: # Resources/PackageInfo.json # XSpades/PackageInfo.json
ghost
closed this
|
Sorry, don't know how GitHub works. I didn't mean to interact with master |
|
I suppose it's too late now, but I'd like to say that I am not a fan of spectator wallhack code being publicly released. The skill required to comment out the spectator team check in the source and recompile is much lower than the skill required to patch a binary. |
|
I was just crudely copying and pasting the already public source from DD just the spectator team check section, not the actual wall hack. Within the safety of my fork, I created a pull request thinking that I could sync that branch to my own master. I was really embarrassed to realise this was not the case. |
|
I am facepalming so hard now. References can be seen on the other issue. |
No description provided.