Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge v0.2.0 branch #838

Draft
wants to merge 63 commits into
base: master
Choose a base branch
from
Draft

Merge v0.2.0 branch #838

wants to merge 63 commits into from

Conversation

yvt
Copy link
Owner

@yvt yvt commented Jun 9, 2019

Changes

Requirements

The GPU requirement for the OpenGL renderer was raised:

  • Video card supporting OpenGL 2.1 and following extensions:
    • EXT_framebuffer_object (part of OpenGL 3.0)
    • NEW: EXT_framebuffer_sRGB (part of OpenGL 3.0)

Highlights

  • Rewrite LimboView in AngelScript
  • Temporal antialiasing
  • Ping in the server list (17b4100)
  • Rendering Scale (feature to change the 3D rendering resolution independently from 2D to improve the performance while keeping 2D rendering sharp) (3cd32b5)
  • GUI now supports DPI scaling (ff3af0f)
  • GUI redesign
  • etc.

Miscellaneous

  • All rendering, including GUI, is done in the linear colorspace. This simplifies the code base.
    • r_srgb and r_srgb2d were removed. (cf3e187)
    • LINEAR_FRAMEBUFFER was removed. (af35e30)
  • The legacy setting importer was removed. (daf3732)
  • GUI: Blur effect
  • GUI: Rectangular clipping (4c8e9b2), which is useful for smooth scrolling

Issues

  • The non-HDR (r_hdr 0) rendering path is broken
  • r_fogShadow is broken (maybe remove it?)
  • Not sure if it's okay to drop support for GPUs without EXT_framebuffer_sRGB.

yvt added 30 commits January 9, 2017 23:53
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
yvt and others added 25 commits September 5, 2017 01:03
# 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
# 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
This commit fixes the issue by explicitly requesting a sRGB-capable
default framebuffer.

Fixes #827.
@yvt yvt added the enhancement request/proposal to add a new feature label Jun 9, 2019
@yvt yvt self-assigned this Jun 9, 2019
@sudodouuuuuu
Copy link

I understand you are looking forward to merging these branches, is v0.2.0 the one us testers should use?

@yvt
Copy link
Owner Author

yvt commented Nov 26, 2020

I understand you are looking forward to merging these branches, is v0.2.0 the one us testers should use?

I'm sorry I haven't been able to answer your question for a while. No, master or #844 is what you might want to use. The v0.2.0 branch won't be merged anytime soon because of many incomplete features and its stricter system requirements, which I'm not sure users are okay with.

The current plan is as follows:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement request/proposal to add a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants