lawnjelly

Some performance timings of different release compiles of `PoolVector`, in milliseconds, smaller times is therefore faster. These are in gdscript so not super gold standard, because there will be a...

> I guess an over-simplication could just be, is PoolVector thread-safe or not? It seems to attempt to be thread-safe as ` PoolVector::operator[]` uses 'read' access, `PoolVector::set` uses a 'write'...

> The `Alloc` is already locked on all accesses, if you take a look at `Access`, which is inherited by `Read` and `Write` in `pool_vector.h`. What that basically means is...

It occurred to me that for the version where we lock the `Alloc` when creating `Access`, we can move almost all the functionality of the `PoolVector` (push_backs etc) into the...

@dedm0zaj I haven't used it myself for VR, but the principles inside the plugin are very simple, most of it is housekeeping. If you have a look at the source,...

As I'm currently having a go at implementing this (3D to start with) in two draft PRs (#52771 and #52846) I thought here would be as good a place as...

> Have you seen any issues with allowing the follow target to be the parent in 4.0? You may be able to do it sensibly in combination with a call...

> I modified the your plugin by adding it to the ready function. Just like you described. That's great. We should probably have a look at putting this in the...

> My suspicion is that whatever jitter_fix does is it introduces error into the time step and fraction. Jitter fix should be set to 0.0 when doing anything involving physics...

Fixed by #92152.