Age | Commit message (Collapse) | Author |
|
No functional changes.
- add `override' everywhere where missing
- almost pass clang's `-Wweak-vtables'
- avoid some float/double conversions
- remove unused private members
- make signedness conversions explicit
- put stuff in right namespaces to aid analysis
|
|
|
|
This is possibly related to a livelock where several threads do const
removal in their respective code paths.
Use the `mutable' specifier for the mutexes and spline's cached data.
Now using the `mutable' specifier, get rid of <optional> in
compat/mutex.
|
|
|
|
|
|
It assumed that all values were of the same type when packing into an
initializer list.
|
|
|
|
This is incorrect but people like it.
|
|
|
|
While we're keeping 250 Hz in the tracker pipeline, the
frame variance isn't optimal, as per `backlog_time'
values. Try a different magic number.
|
|
Calling QThread::setPriority twice in a succession
means:
1. if you can, set high priority
a) if not allowed, highest won't work either
b) if allowed, see below
2. if you can, set highest priority
a) if highest is allowed, happy happy joy joy
b) if not, at least high priority is successful
Note that we don't have any return value from
QThread::setPriority().
|
|
|
|
|
|
Issue: #726
|
|
|
|
|
|
|
|
v2: fix comments
v3: fix reltrans
|
|
|
|
|
|
|
|
No visible changes (hopefully).
|
|
use `cc_xx' rather than awkward synonyms.
|
|
|
|
Use more C++17 features where this helps any.
|
|
No functional changes.
Don't perform any atomic reads before compare-and-swap.
The value read by CAS needs to go outside the loop.
That's how CAS works.
|
|
|
|
The actual order is (xyz, ypr). This was broken since
forever. This February's refactor merely preserved the
order of things.
|
|
|
|
|
|
|
|
|
|
Also fix faulty xor logic
Issue: #777
Requested-by: @r8d
|
|
|
|
Add additional RC value for fast convergence.
|
|
Change `reltrans_not_aiming' threshold values
|
|
Also remove the license in header. It's stale.
|
|
Requested by: CAHEK on the Russian IL-2 Sturmovik forum
|
|
|
|
Requested by: HOPPING_PONY on the Russian IL-2 Sturmovik forum.
|
|
|
|
|
|
|
|
|
|
The `scaled_rotation' gimbal lock "fix" didn't take
into account sign changes, making center close to +-180
useless. remove the "fix".
This leaves with a gimbal lock problem at +-90 yaw. Fix
in another commit.
|
|
The pipeline code is hard to understand for programmers due to the
practice of putting all logic into a single function.
Split it up into logical components.
This needs more testing and bug reports. It's a big change with possibly
many regressions all over the place.
Issue: #688
|
|
- use `static constexpr inline' to avoid requiring
explicit declarations in object code
- use `const Foo* const' to maybe put into readonly
binary segment (at least for ELF DSOs)
- `constexpr' in function scope has storage, avoid
`static'
- don't use `constexpr' where there's no advantage,
like arrays
We'd like to avoid overhead of atomic initialization
for each function call. No idea how `static constexpr'
requiring storage in the standard plays with atomic
initialization requirement. Hearsay points that
`constexpr' without `static' in block scope behaves
more to our liking. It's all hazy though.
I'm not 100% sure if `static inline constexpr' has any
storage. Hopefully none, like a #define, and stuff
bigger than registers gets coalesced within the same
module, with small stuff being immediates.
|
|
|
|
|
|
We must keep a certain leeway here for people aiming in WW2 sims.
|