I boost like a mad thing towards where I think the Titan is. When I hear the build-up for a pulse, I put 4 power blips into Systems, then wait..... until I see the pulse bubble coming, then immediately hold down the neutraliser. Seems to work fairly well, for me.
Yep, that's exactly what I do. I already have 4 pips to SYS, as anything above 2 for ENG at that point is largely pointless, as it doesn't allow me to boost more frequently. I watch the bubble expand for, well, it feels like several seconds but it's likely not that long, and hold the button
just as it's about to reach me. I then let go of the button moments later after it's passed. SYS usually still has come capacity left, but it's close to empty. I do the same thing each time, and hadn't overheated from it previously. One time I was caught out as the counter simply did not work, yet I timed it perfectly. That was a particularly buggy PG instance though.
I do suspect that, for whatever reason, sometimes what the client (aka my game) is showing me is different to what the server thinks is happening. Basically, there's a slight timing difference or some data isn't getting through. My internet is really, good, best it's ever been, so I don't think it's me. It's like how, sometimes, you can be approaching a planet (to dock at the orbiting station) and it's counting down slowly, 12, 11, 10 seconds quite slowly, then
suddenly it's showing 5 second - aka, you're going to over-shoot, yet you're at 50% throttle so it shouldn't happen. A momentary sync thing. I've had situations where a count-down timer has jumped before, most recently - and the cause of my last death - I'd lost the canopy, but had a little over a minute remaining just as I was about to enter the station instance to dock. I entered the instance, and the timer dropped to like 10 seconds, I not enough time to synth more O2. I
could have synthed earlier of course, but the timer suggested there was no need, so I wasn't worried. Use to lose the canopy all the time in certain ships, so sorta got used to returning to dock within a time limit. Of course, since we gained the ability to synth O2, it became even less of a concern.
If I was on a dodgy internet connection - especially if wireless - or my PC was old and struggling, I'd 100% assume the issue were my side. However, neither of those things are true. Other who are sharing some of my issues, what are you system specs out of interest? I'll list mine:
- CPU: 5800X3d - darn good cpu, water-cooled so it's running at its best
- GPU: 3070 - perhaps feeling a bit old for a GPU now, but it's working well. Also water-cooled so running as well as it possibly can.
- RAM: 32GB DDR4 3600 - two sticks, dual rank. Currently at stock CL18, not not the quickest. However, since going 3900X to 5800X3d, running the RAM at lower latencies make very little difference.
- Drives: 2x M.2 in RAID0, doubling of peak transfer speeds, while retaining low-latency. Working well. Slower than a pair of newer PCIe 5.0 drive I'm sure, but certainly no slouch.
- OS: Windows 10 Pro. Not felt the need to go W11 thus far, but I expect I will eventually. Build is quite lean, with various spurious services set to manual rather than automatically launching. As such, I regularly only have 70 or so processes running as it's not launching any it doesn't actually need.
- Game: Running at 2560x1440p, fairly high settings, can't remember exactly what. vSync limited to 60fps, which is good enough for me.
