| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
Use Vertex Depth Range when zRange Exceeds farZ
|
|
detected in places other than VertexShaderManager
|
|
When the inverted depth range is unsupported and zRange is greater than farZ then min_depth becomes a negative value and far_depth will then exceed a depth of 1.0 (which is outside the scope of most backends and greater than GX_MAX_DEPTH of the console).
This happens when the backend supports depth clamping the min_depth is not clamped to zero.
|
|
|
|
|
|
|
|
|
|
There wasn't really a good place for it, but this will do
|
|
|
|
|
|
|
|
|
|
|
|
|
|
removing parameters with less code overhead
|
|
|
|
|
|
This normalization was added in 02ac5e95c84a1d9a46df1dc4102342fb653e36ee, and changed to use floats in 4bf031c0646e91b35777f1ba4e2b0328063bb666. The conversion to floats means that sometimes there is insufficient precision for the normalization process, which results in values of NaN or infinity. Performing the whole process with doubles prevents that, but games also sometimes set the values to NaN or infinity directly (possibly accidentally due to the values not being initialized due to them not being used in the current configuration?).
The version of Mesa currently in use on FifoCI (20.3.5) has issues with NaN. Although this bug has been fixed (https://gitlab.freedesktop.org/mesa/mesa/-/commit/b3f3287eac066eae16dce0e47aad3229dcff8257 in 21.2.0), FifoCI is stuck with the older version.
This change may or may not be incorrect, but it should result in the same behavior as already present in Dolphin, while working around the Mesa bug.
|
|
draw call
|
|
VertexManagerBase (draw calls), and VertexShaderManager (projection calls)
|
|
|
|
This is mainly for debugging, and is only exposed by manually editing the configuration.
|
|
This increases accuracy, fixing the white rendering in Major Minor's Majestic March. However, the hardware backends can only have one viewport and scissor rectangle at a time, while sometimes multiple are needed to accurately emulate what is happening. If possible, this will need to be fixed later.
|
|
I think this is a relic of D3D9. D3D11 and D3D12 seem to work fine without it. Plus, ViewportCorrectionMatrix just didn't work correctly (at least with the viewports being generated by the new scissor code).
|
|
|
|
|
|
'FieldOfViewMultiplier' to better reflect usage
|
|
controller handle all the logic (field-of-view, movement, etc)
|
|
SPDX standardizes how source code conveys its copyright and licensing
information. See https://spdx.github.io/spdx-spec/1-rationale/ . SPDX
tags are adopted in many large projects, including things like the Linux
kernel.
|
|
... while not breaking other games.
|
|
Additionally a new ClipDisable union has been added (though it is not currently used by Dolphin).
|
|
Additionally, VCacheEnhance has been added to UVAT_group1. According to YAGCD, this field is always 1.
TVtxDesc also now has separate low and high fields whose hex values correspond with the proper registers, instead of having one 33-bit value. This change was made in a way that should be backwards-compatible.
|
|
add multiple cameras
|
|
|
|
Cel-damage depends on lighting being calculated for the first channel
even though there is no color in the vertex format (defaults to the
material color). If lighting for the channel is not enabled, the vertex
will use the default color as before.
The default value of the color is determined by the number of elements in
the vertex format. This fixes the grey cubes in Super Mario Sunshine.
If the color channel count is zero, we set the color to black before the
end of the vertex shader. It's possible that this would be undefined
behavior on hardware if a vertex color index that was greater than the
channel count was used within TEV.
|
|
Migrates off the printf-based formatting where applicable.
|
|
VertexShaderManager: Only look for freelook config changes if we're using freelook
|
|
each call which caused a performance hit, move check to RenderBase where it is checked when config changes
|
|
|
|
|
|
direct freelook camera methods
|
|
Makes the global variable follow our convention of prefixing g_ on
global variables to make it obvious in surrounding code that it's not a
local variable.
|
|
We can use this to shorten up the initialization code a little bit.
Despite being saved to savestates, this is a non-breaking change.
|
|
Makes the members within the interface much nicer to look at, and also
makes copying them over much nicer too.
|
|
Since C++17, non-member std::size() is present in the standard library
which also operates on regular C arrays. Given that, we can just replace
usages of ArraySize with that where applicable.
In many cases, we can just change the actual C array ArraySize() was
called on into a std::array and just use its .size() member function
instead.
In some other cases, we can collapse the loops they were used in, into a
ranged-for loop, eliminating the need for en explicit bounds query.
|
|
|
