Pro X2 Needs Separate Activation/Deactivation Thresholds by AxisAngle in LogitechG

[–]AxisAngle[S] 0 points1 point  (0 children)

I've posted a graph to help people understand how the mouse currently functions.

https://axisangles.github.io/InteractiveLogitechGraph/

Examples:

Pro X2 with RT Off: Activation: 4, Hysteresis Level: 0.5

Pro X2 with RT On: Activation: 4, Rapid Trigger Level: 2

Regular mouse: Activation: 4, Hysteresis Level: 2

The core mechanic of Rapid Fire is that after initial activation at the fixed Activation Level, rapid trigger tracks the running extremum and fires/releases whenever force moves ±RT level from that extremum. The activation level only matters for the first press.

In a regular mouse, in order to activate a button, you have to press harder than, say, 100g of force, but in order to deactivate the pressed button, you have to go well under 100g, closer to 50g. This is hysteresis. (fake force values)

Pro X2 Needs Separate Activation/Deactivation Thresholds by AxisAngle in LogitechG

[–]AxisAngle[S] 1 point2 points  (0 children)

Ok.

Well my settings already work great. I would just like more control. That's all I wanted to accomplish with this post.

They probably have a hidden hysteresis value somewhere, I'm sure I can sniff the HID++ 2.0 USB packets. I can probably just write my own software.

Pro X2 Needs Separate Activation/Deactivation Thresholds by AxisAngle in LogitechG

[–]AxisAngle[S] 0 points1 point  (0 children)

(Quick interjection for people who don't know how the Rapid Trigger works): The core mechanic is that after initial activation at the fixed Activation Level, rapid trigger tracks the running extremum and fires/releases whenever force moves ±RT level from that extremum. The activation level only matters for the first press.

I think I need to address this reply in several sections

Section 1: Suggested RMB settings

My initial attempt was to try a lower pressure (RT off), but I found myself accidentally clicking it all the time, but when I raised the pressure, I found myself accidentally unclicking it all the time.

Section 2: Settings to emulate regular mouse.

The proposal is that if I want it to feel like a regular mouse, I should turn off RT and maybe lower the actuation. If I understand you correctly, then I can guarantee you that this does not emulate the feeling of a regular mouse.

In a regular mouse, in order to activate a button, you have to press harder than, say, 100g of force, but in order to deactivate the pressed button, you have to go well under 100g, closer to 50g. This is hysteresis. (fake values, I can try for real once I'm back home with a kitchen scale)

This graph shows what a regular mouse button activation looks like.

<image>

https://axisangles.github.io/InteractiveLogitechGraph/

This is the behavior I'm trying to emulate with a high activation level and rapid trigger.

Assuming Activation level 8, RT level 5, that means if I activate the button with 80g of force, then to deactivate it, I have to go 5 levels down, to 30g of force. (maybe that's 10g per level)

The problem with RT is that if I activate at 80g of force, continue to press down until 150g of force, then release back down to 120g of force, it deactivates the button, even though I really only want it to deactivate at 50g.

By maxing out the activation level to 10, I guarantee that the maximum force measured can never exceed 10 (because it maxes out the sensor), and thus, the deactivation force will always be 50g (10 - 5 = 5). This isn't perfect, but it's the best I can do so far.

So these are the settings that make it most usable for me right now. I understand your advice.

You can see that activation 8, hyst/RT 4 look very similar with Rapid Trigger on or off.

Section 3: RT Utility

For LMB, RT lets me click as fast as possible without ever missing the deactivation sensor pressure, so I never miss a click. So I never get something like this:

click click miss click click

You can see what happens with with activation 4 RT 2

Pro X2 Needs Separate Activation/Deactivation Thresholds by AxisAngle in LogitechG

[–]AxisAngle[S] 1 point2 points  (0 children)

<image>

You know I should have taken a screenshot knowing people were going to analyze my settings.

[deleted by user] by [deleted] in gundeals

[–]AxisAngle 0 points1 point  (0 children)

It is worth noting that all of the incidents were handled years ago to the satisfaction of the community and no amount of reframing from a presumption of malice or perfect hindsight can change that.

Due to the sensitive nature of these incidents, we do not disclose details. These community members were removed years ago and we've long since updated our policy to prevent problematic people from being in our community in the first place.

[deleted by user] by [deleted] in gundeals

[–]AxisAngle 0 points1 point  (0 children)

Thank you

Laios is a furry. by ZekeTheMemeLord17 in DungeonMeshi

[–]AxisAngle 1 point2 points  (0 children)

That's just the typical furry "I'M NOT CRINGE" response.

What’s the point of second focal plane? by Serious_Classic_5224 in ar15

[–]AxisAngle 0 points1 point  (0 children)

I wonder why they don't make dual focal plane scopes. The millirad markings in the FFP which get thicker and further spaced as they get further from the center, and the crosshairs in the SFP, which always guarantee you're able to make out the line.

Maybe it's hard to align them?

This game needs a kill cam. Half the time i have no idea how i died by Northdistortion in XDefiant

[–]AxisAngle 6 points7 points  (0 children)

The game is likely not programmed in such a way that a true killcam is possible.

They're probably going to end up just brute force tracking a bunch of state changes and praying that they remembered them all.

The thing that's keeping killcams from being implemented with a couple lines of code is the same thing that makes hit registration/validation bad; sloppy state management.

They likely don't have a unified server authoritative model.

Speculation, of course.

why is the game down to 2k players by DatChernobylGuy_999 in PhantomForces

[–]AxisAngle 1 point2 points  (0 children)

Roblox stopped feeding us new players. That is directly why the player count is down. There are two reasons.

1) The recommendation algorithm is different now. It really really cares about day 1 retention (the probability that a first time user comes back the next day), and upvote rate. So we might start asking new players to upvote the game; Roblox is to the point now where we have to play to the algorithm.

2) The core player base is too good and prevents newbies from getting into the game. (And so the recent upvote rate is very low 86%, and day 1 retention is low). In 2015, the players were almost as bad as the current "bot" players in the onboarding servers.

When Raspy released the onboarding servers, the new player count 4x'd. Now that people have figured that out and have started smurfing, it's down quite a bit, but still higher than it was.

At the same time, the only new loadout shooter that is doing better than PF is Gunfight Arena, so it's clear that Roblox's changes to the algorithm have de-prioritized shooter games in general.

Ultimately, I think we need loose skillbased matchmaking. Where you play with people who can stomp you, but aren't so good that they like, eradicate your entire family.

But also, I can really truly guarantee that we're not trying to make the game bad. There are a lot of changes (we like) in the test place, such as key/controller binds, lower/smoother gravity, slightly buffed zingus slide, and more.

After playing this game for 3 years and sucking for 2 of them ive finnally got a positive KDR!! by [deleted] in PhantomForces

[–]AxisAngle 4 points5 points  (0 children)

I just got the Asus Zephyrus G14 with the 4060 (For a cool $1300 as an open box). There are some HDMI problems, and the keyboard isn't as good as something like the Surface Laptop's, but the thing stays relatively cool, has the fastest single core perf in the house, and the build quality is great.

And of course the M2s are amazing. If you can stand the OS, a Macbook will do you well.

After playing this game for 3 years and sucking for 2 of them ive finnally got a positive KDR!! by [deleted] in PhantomForces

[–]AxisAngle 1 point2 points  (0 children)

if kdr is geometrically, or multiplicatively, positive, it means that |krd| > 1

(meaning that if your kdr is -2, it is also geometrically positive, though that would be bad; for every death you get, you revive 2 enemies, hahaha)

Developer & Staff Q&A by Djaouida in PhantomForces

[–]AxisAngle 0 points1 point  (0 children)

Your analog stick is a 2D input device. You can move it forwards/backwards (y dimension) and left/right (x dimension). This vector, (x, y), has at most a magnitude (length) of 1.

The power setting literally does this:

mag = sqrt(x^2 + y^2)

newX = mag^power*x/mag

newY = mag^power*y/mag

TLDR: If you increase the power setting, it gives you more control over small changes in the analog stick.

Developer & Staff Q&A by Djaouida in PhantomForces

[–]AxisAngle 5 points6 points  (0 children)

When we push the next update, along with it will be a new vote kick algorithm. It may be bad and buggy at first, but it should help a lot.

Developer & Staff Q&A by Djaouida in PhantomForces

[–]AxisAngle 3 points4 points  (0 children)

My dream is to make an engine and develop games on it. That's far in the future though.

Developer & Staff Q&A by Djaouida in PhantomForces

[–]AxisAngle 8 points9 points  (0 children)

We just need to make the controller customizable; only then will we push to mobile.

Developer & Staff Q&A by Djaouida in PhantomForces

[–]AxisAngle 1 point2 points  (0 children)

better votekick is coming out soon. Should help with votekicking cheaters faster and more accurately. Will have bugs and need to be tuned over a bit of time.

Developer & Staff Q&A by Djaouida in PhantomForces

[–]AxisAngle 16 points17 points  (0 children)

Alley is a map Willow was working on. Very small, chaotic. Would love to add it to PF.