impulse | impulse manages a stack of intentions

As the title suggests, I am trying to make a double jump in my Character Controller. The problem is, that using my code the character makes one big jump instead of making a second one.

Here is my code:

To give a bit of context, i am trying to implement in matlab from scratch the following signal diagram, a Feedback Delay Network (FDN). pic: FDN

With an appropriate matrix, indifferent to delay lengths, virtually white noise comes out when fed a dirac impulse.

I've managed to do this in code, but my goal is another and hence my question. I want to apply a filter h(z) after each delay line z^-m. pic: h(z)

More specifically, i want to apply a third-octave cascaded graphic equalizer after each delay line. The purpose is to create frequency dependent attenuation on the whole structure, and consequently delay dependent. I've successfully designed the filter in the form of SOS, but my problem is: how do I apply it within the structure? I assume to use sosfilt() somewhere with what I have, but I'm not sure.

I haven't reduced the order of the system for sake of purpose. The order is 16 (16x16 matrix, 16 delay lines, 31x16 biquad filters)

The first code refers to the lossless FDN, safely runnable which generates white noise. I have commented my failed attempt to introduce the filtering in the loop saying: % Filtering

Unfortunately, I can't post all GEQ entries, but I'll leave 8 in the end corresponding to the first 8 delays.

So, the question is how do I code to filter the white noise, implementing frequency dependent attenuation in the whole FDN structure. Also, although it may be computationally inefficient, I'd prefer to apply this without higher level functions and based on what I already have, i.e: applicable in GNU Octave

Edit: Assuming you have to apply the bandpass 2nd order filtering sample by sample using the difference equation, how would you recursively do it for 31 bands in series? One is shown in the second code section.

I want to create a special case of a room-impulse-response. I am following this implemetation for a room-impulse-response generator. I am also following this tutorial for integrating c++\c with python.

According to the tutorial:

1. You want to speed up a particular section of your Python code by converting a critical section to C. Not only does C have a faster execution speed, but it also allows you to break free from the limitations of the GIL, provided you’re careful.

However, when looking at the MATLAB example, all I see the cpp code segment doing, are regular loops and mathematical computations. In what way will c\cpp be faster than python\MATLAB in this example or any other? Will any general c\cpp code run faster? If so, why? If not, what are the indicators I need to look for, when opting for a c\cpp segment implementation? which operations are faster in c\cpp?

I have the following block diagram and each subsystem, I need to find the overall impulse response for 0<=n<=99.

The individual impulse response for each subsystem was found as shown.

I'm trying to loop through the child object of a JSON array which stores objects. My JSON file is as follows:

I've started to write a physics engine but became stuck on some physics of resolving collisions. Let's say I have this situation:

I.e. body B is going towards body A at the speed of 1 space units/time unit. Both A and B have the same mass of 1 unit. Let's consider a completely elastic collision.

I've read in a book (Game Physics Engine Development) that an impulse-based approach can be used to resolve the collision (i.e. find out the linear and angular velocities of both bodies after the collision). As I understand it, it should work like this:

1. When the bodies collide, I get the point of the collision and the collision normal.
2. At the point of the collision I consider only two points colliding in the direction of the normal (the points at which the bodies are touching, i.e. I ignore the shapes of both bodies) and I compute the new velocities of these two colliding points (this is easy to do, there is a simple formula found e.g. on Wikipedia).
3. I find an impulse such that when applied to both bodies at this point it achieves the computed velocities for these two points.

Now the problem arises when I consider that from a physical point of view both momentum and kinetic energy need to be conserved. With these constraints in mind there is seemingly no solution, because:

When B collides with A, B should come to complete stop and transfer all its momentum and kinetic energy to A, according to elastic collision formula. In order for linear momentum to stay conserved, A then has to start linearly moving left at the same speed as B was before the collision (as they have the same mass). So now A has the same kinetic energy as B had, which however means that A cannot come into rotation because that would add additional kinetic energy to it (as rotating adds kinetic energy as well as linear motion), breaking the conservation of kinetic energy. Nevertheless, the physically correct solution IS for A to both move linearly to the left AND rotate as B colliding at this location exerts torque (and I've also checked real life object behave this way). Note that we cannot take away some energy of A's linear motion and add it to the rotation as that breaks the conservation of linear momentum.

The only "real" solution is that B doesn't come to complete stop and keeps some momentum while A will be both moving left and rotating. But this doesn't seem to be doable with the impulse-based approach that only takes into account the two colliding points, the elastic collision formula simply say the point at B should come to stop and as B cannot receive any torque (the collision happens in its middle), the only way to fulfill this is for B to stop moving.

So is there something I missed? Is the impulse-based approach just not physically correct? I appreciate any insight and suggestions on how to correctly resolve the collision. Thanks!

I have a weird problem and cant seem to fix it

i was creating my first game in unity and i was testing around a bit after creating a movement system and whenever i touch another object (it doesnt matter if it has a rigidbody or not) my player suddenly starts moving on its own.

i have a video showing what exactly happens: https://youtu.be/WGrJ0KNYSr4

i have tried a few different things already and i determined that it has to do something with the physics engine because it only happens when the player isnt kinematic, so i tried to increase the solver iterations for physics in the project settings but the bug was still happening so i looked for answers on the internet yet the only thing i found was to remove Time.deltaTime tho it still didnt work. I have found that it seems to happen less though when the player is moving fast.

i would really appreciate if somebody could help me with this since its my first real game and im creating it for the Seajam thats happening on itch.io.

here is the code for my playercontroller script:

I've been trying to solve an equation for a 2D vector P. But after solve there are still some P on the rhs. Does this mean Maxima can't do it or I've done something wrong?

Here is it:

So i made a player with a rigidbody and a child game object "feet", i also added a layer "floor" to every plateforme my player can jump off so i can use Physics.CheckSphere() to see if my player is actually on the ground and can jump. In this last case i add a force to my rigidbody with a ForceMode.Impulse. Everything work except that sometimes the player do a little jump and sometimes a higher jump. Here is my code :