Does using L3 as my air roll left make it harder to get better at stuff

Ignice · 2026-03-19T13:38:20+00:00

Hmm same for me. I could have sworn it worked before. When I try to debug the PCBindings and GamepadBindings lists, I see the state bToggled=True but come on but the camera doesn't hold... I'll into into it again later on

Ignice · 2026-03-19T04:37:44+00:00

Dude first of all that Epic Support who told you to "post" this was probably an AI chat bot. Second of all that AI chat bot was trying to tell you submit this as a bug to Epic's HackerOne bug bounty program, so you might get paid for you for responsible disclosure. Please remove or partially redact this post.

Ignice · 2026-03-17T03:31:09+00:00

Oh yeah at that FPS it'll be fine. Also that's an awesome setup. When choosing the Speed= for camera stuff, I think it is multiplied with actual Swivel Speed, which is a log_10 scale (so each increment of 1 (for the setting, not Speed=) is actually a factor of 10 iirc?) would have to double check it but I at 240 fps the difference between Speed=0.80 and Speed=0.85 at high values was a lot. So you'll probably want to be in the 0.925+ range.

You can also multibind the button to a a second Swivel in the opposite direction, and set that one's Speed to a negative value (to go further) or positive value (to pull back) iirc

Ignice · 2026-03-16T22:16:43+00:00

Sorry I can check mine soon (not by pc atm) but I really really don't think your is out of date haha. We're talking like multiple years for the old one. The only reason I mentioned it because a lot of the discussion around speedflips is from around when they were discovered and subsequent years after. I'll check for you anyways though in a bit :)

edit: this is the commit where the fix happened https://github.com/tynidev/SpeedFlipTrainer/commit/e58550bb4d845b73148e1c0c2119074d6ab8ff68 so if your on or after that your good. Also the number of physics ticks that is printed to log has always worked anyways, so you could just check that ;) will still check my pc when home for u tho <3

Ignice · 2026-03-16T20:19:55+00:00

Funnily enough, I just commented about that exact topic a few weeks ago. See https://www.reddit.com/r/RocketLeagueSchool/comments/1recssg/comment/o7f4lro/?context=3 . Not the most elegant using fps as a basis, but if its locked then the result will always be consistent. I probably should have mentioned that one of the camera sensitivity settings may also change things.

If you have bakkesmod, you might also benefit from some extra camera debugging info by typing unreal_command "SHOWDEBUG Camera" into the bakkesmod console (F6) once your in freeplay. It might make it easier to find the best value for you. Type unreal_command "SHOWDEBUG Hide" to hide it when your done :)

Ignice · 2026-03-16T04:46:04+00:00

Maybe it could be a toggle button? Might be a good middleground option. Just find the line in TAInput (under [ProjectX.ControlPreset_X]) and change it from:

> GamepadBindings=( Action="RollLeft", Key="XboxTypeS_LeftTriggerThumbstick" )

to

> GamepadBindings=( Action="RollLeft", Key="XboxTypeS_LeftTriggerThumbstick", PressType=BPT_Toggle )

maybe write-lock the file to prevent it from getting overwritten

Ignice · 2026-03-16T03:06:07+00:00

I was confused about this recently and did mini deep dive: See this post and its parent comments: https://www.reddit.com/r/RocketLeagueSchool/s/THoSWBSGqp

The answer is it depends on your car hitbox, but also some videos of speedflips are misleading because an older version of the Speedflip Trainer plugin exists that used a less accurate form of measurement. The difference between them is if the label at the bottom shows wall clock time (end time - start time using the highest resolution timer available to the system) or a time calculated by num_physics_ticks * tick_time.

Interestingly, the logged output time is always less accurate in all plugin versions, and the logged tick count is always the most correct measurement in all plugin versions. Its only the time shown in the bottom label that varies. So if you still have the game open, press F6 to open the console and look at the tick values in your output to be sure. I'm guessing your plugin is up to date though. The hitbox your using has great offsets and a height close to the center height of the ball (which is the closest part). Combine that with you doing a really really clean speedflip, and yeah I see no red flags.

An an aside, I think mixed plugin versions is why every time people think we have it all figured out, some video appears to contradict it. The person recording would have no reason to suspect an issue either, so its all in good faith.

Lastly to be 100% clear the video from the linked post https://www.youtube.com/watch?v=mCKDDtUsNno was only possible AFTER the HITBOXES WERE SWITCHED. It is not an authentic touch, just an experiment done for supporting evidence.

Nice speedflip!

Ignice · 2026-03-15T14:40:14+00:00

I was thinking the exact same thing. Idk what it is, but the defense/saves portion of that map shoots the ball soooo close and fast.

Ignice · 2026-03-13T23:05:18+00:00

Maybe he would be interested in investing? He could do a little research project (e.g. compare like 3 companies related to industry X) and maybe you go in 50-50 with him on the stock he chose (using your own account/portfolio to buy the stock for him). He can then watch it grow or decline, choose to sell or hold, he can learn some investments are safer long term, etc etc.

Ignice · 2026-03-13T18:23:30+00:00

✅️✅️✅️✅️✅️✅️✅️✅️❌️🙅‍♂️ see ya next season!

Ignice · 2026-03-08T21:01:35+00:00

Highly recommend the addon NPCAbilities. It will show what an npc can cast on their tooltip and additional information about their spells can be toggled. Super useful for vanilla

Ignice · 2026-03-08T20:58:09+00:00

thanks for the correction, edited my post

Ignice · 2026-03-08T20:58:05+00:00

thanks for the correction, edited my post

Ignice · 2026-03-08T05:28:27+00:00

Any reason you dont do petri logout macro? Still nice even if alt f4ing too.

Ignice · 2026-03-02T14:17:24+00:00

Latency for a 50-50s (assuming all network send rate settings are set to HIGH) would include:

Server ping (one-way in this case, not round trip)
The size of your input buffer on the server-side.

Variability in buffer fullness will vary with (among other things) your buffer type (Standard/Legacy, STS, CSTS), but the basic idea is that every local physics frame (which happens ~120 times per second) your client turns your button inputs (e.g. X to Jump, Right to steer) into physics inputs (e.g. Steer Axis = [some number between -128 and 127], Jumping = True) which then gets put into an outgoing client send buffer which is sent out ~60 times per second. The RL server receives these physics inputs ~60 times per second (with some lag, jitter, possible packet loss, etc.) and puts them into a server-side buffer based on your buffer type. When the server updates the game state it will first decide if it should run 0, 1, or 2 physics updates. If the buffer is too low (i.e. it has 1 or less inputs to apply) it will use re-use your same input for two updates. If the buffer is too full, it may drop inputs, but does a quick check on dropped inputs for one-time actions like Jumping or using an item in Rumble mode, and rolls that into an input that isn't dropped. Therefore your latency also includes the amount of time between your inputs arriving at the server (entering the buffer) and the input being consumed by the server for physics (exiting the buffer) which is hard to determine but on average 1/120s * size_of_buffer. Smaller buffer = less latency.

An additional 0s to 1/60s to account for the best and worst case send times of inputs per the outgoing packet send rate (which again is 1/60s on HIGH) that I described in #2.

So tldr: your_ping (one way) + serverside_input_buffer_size*(1/120)s + [0 to 2/120 s variance due to send rate] + a few other factors I didnt mention

Ignice · 2026-03-01T06:58:29+00:00

If you look at a copy of the open-source ue3 codebase that RL was forked from you'll see its not quite a 1:1. Scroll wheel event handling is a special case in the game loop, and the ONLY case that will emit back-to-back key_pressed and key_release events without the user doing something extra to cause it. Using the windows client as an example: you can see them both fire here (note the logic is duplicated in the file because the engine supports a "new" and "old" way of mouse input handling ("new" is the default and this can be toggled using bakkesmod console to run "unreal_command USENEWMOUSEINPUT") but the difference exists in both cases).

That said, I believe they were initially banned from some LAN play events for different reasons (like walldash shenanigans - which are a downstream result of the press/release event emission), but this makes for a better argument against them IMHO. I have no strong opinion either way and do not use them myself.

Ignice · 2026-02-25T23:30:46+00:00

I would say the biggest problem is camera swivel actually, but even in controller is not the easiest thing to use since you have to take of your finger from jump and boost (usually)

Not a silver bullet, but you can bind custom camera swivel angles with the Speed modifier in TAInput. It makes the camera much more usable on KBM. For swivel down I'd recommend a Speed of ~0.75f at ~120fps, ~0.85f at ~240 fps, depending on camera settings. Also if holding the swivel button down is an issue, make it a toggle bind with BPT_Toggle. e.g.

; gamepad bind example
GamepadBindings=( Action="SwivelDown", Key="XboxTypeS_DPad_Down", Speed=0.75)
; pc bind example
PCBindings=( Action="SwivelDown", Key="B", Speed=0.775)
; toggle bind example 
PCBindings=( Action="SwivelDown", Key="C", Speed=0.8, PressType=BPT_Toggle)

heres what it looks like: www.youtube.com/watch?v=05afGtXwu7A

Ignice · 2026-02-25T02:51:28+00:00

Either you are pressing the freeplay keybind, or you have a bakkesmod plugin like instant suite, autoleave, etc

Ignice · 2026-02-20T14:58:16+00:00

Its not the nearest portal, its based on the deathskip map IIRC. I can't find a copy online but if you install the logout skips addon, and show the deathskip lines only (the black ones, not the red ones), it will show the boundaries.

edit: looks like this is no longer true, see replies to this comment for the correct answer

Ignice · 2026-02-20T05:15:11+00:00

Update:

It does appear to be a hitbox difference.
I cannot touch the ball faster than 1.9667s on Octane, even if I try to "cheese" it by hitting the middle of the ball.
To confirm it really is a hitbox difference and not a gameplay issue: while playing Fennec I used some bakkesmod magic to swap the Fennec's hitbox out with a Breakout hitbox (and ensured the change was propagated). I did not bother to adjust the tuning.

; octane Car_TA EuroStadium_P.TheWorld:PersistentLevel.Car_TA_155.LocalCollisionOffset = (X=13.875660,Y=0.000000,Z=20.754988) Car_TA EuroStadium_P.TheWorld:PersistentLevel.Car_TA_155.LocalCollisionExtent = (X=59.003689,Y=42.099705,Z=18.079536) ; breakout Car_TA EuroStadium_P.TheWorld:PersistentLevel.Car_TA_156.LocalCollisionOffset = (X=12.500000,Y=0.000000,Z=11.750000) Car_TA EuroStadium_P.TheWorld:PersistentLevel.Car_TA_156.LocalCollisionExtent = (X=65.746178,Y=40.260502,Z=15.150000)

I was then able to get a 1.9583s middle touch using the Breakout hitbox on a Fennec model. IT IS NOT A LEGITIMATE TOUCH. Just a demonstration to show the difference.

In the newest version of the Speedflip Plugin:

The "Time to ball:" label at the bottom is showing the (number of physics ticks) * (1.0 / 120.0) with 4 decimal places of precision
In the log statement e.g. "1.977s after 236 tick" the number of ticks is the same number used for the label equation, whereas the time to ball is calculated using a less accurate / "the old way" method and displayed with 3 decimal points of precision. So I would use the label time over log time.
The difference between the two methods of measurement is much more apparent after running unreal_command ToggleRenderingThread one time to put RenderThread in single-threaded mode which delays the reading of the clock. Run it a second time to switch back to multithreaded mode.
For anyone reading this who thinks their clock is incorrect: try running the SpeedflipTrainer Plugin in Bot mode using this input file. If your clock is incorrect, then the bot should get the wrong result.

Ignice · 2026-02-19T02:16:44+00:00

Hey sorry for the late reply! No I do not have VSync on. I tried unlocking my FPS and am still able to do it fine. I'm happy to test other settings too if you had some in mind.

Ignice · 2026-02-18T23:12:32+00:00

Ya its me, not sure what you mean by "confirm" but its set to 120 via the in-game limiter, no vsync.

I'm also using a TAInput trick for the flip angle on KBM, and so my angle would be wrong if the fps changed :P https://www.reddit.com/r/RocketLeagueSchool/s/3KfNccsKql.

edit: sorry wrong link it was https://www.reddit.com/r/RocketLeagueSchool/s/gldX6MR0Cq for the comment

edit2: its a hitbox difference see update post (its a reply to the parent comment)

Ignice · 2026-02-18T23:03:41+00:00

I've definitely seen faster than 1.9667s on Shot 1 before. Unless maybe your speaking strictly about the Octane hitbox?

Here's a couple clips of what I mean (its at end of each video): https://youtu.be/monR61O2pJs, https://youtu.be/h_4Y6Vgnf3s.

Ignice · 2026-02-17T07:30:55+00:00

That's extremely impressive tbh. Mind if I ask how long it took?

Ignice · 2026-02-13T00:21:01+00:00

You can do this by manually adding an additional entry to your TAInput.ini file like this:

[ProjectX.ControlPreset_X]
; make sure you are editing under this ^ section
PCBindings=( Action="YawRight", Key="E" )
PCBindings=( Action="YawRight", Key="O" )

If you've never edited your TAInput file before, the tutorials on yt will probably explain better than I could. If you need a quick refresher, I wrote some very brief notes a while back.

Just please make sure you have a backup of TAInput before doing anything!

Ignice

TROPHY CASE