Messages

That being said, it does say the X-Input API (Which I assume is what GPB Uses seeing as its all bound as "X-Input") is not compatible. However you're more qualified to judge that than me 

I had a quick look at some doc, it's the usual Micrsoft API mess.
They have only one API that support this, but in principle it's only for UWP apps.
If you want to use it in non-UWP apps there're some workarounds.
Also (if I understood it correctly), it only works from certain versions of windows 10 on (not sure how big a problem that is).

One day, maybe

Loving the vibration, Now I've figured out the ini file and can set the maps up individually its amazing.

Yeah, the setup of HUDRumble (vie the .ini file) is a bit cumbersome but it allows you to configure a lot of stuff. 

One thing that would love, is the ability to use the "Trigger Motors" as an option as well as "Heavy" and "Light". A lot of modern controllers have vibration motors in the actual triggers themselves, as well as the 2 main ones, having the ability to use them, for wheelspin for instance, would be amazing.

Hmm interesting, I may want to have a look into this.
And maybe get one of those joypads with "Trigger Motors": do you (or anybody else) have one ? Which one ? How good it  is compared to others (sticks, triggers etc) ?

I've fixed it in my code. Can it wait until the next plugin release ?

I'll have a look asap.

Holy mother that's a fast one. NICE!      

Lucky combo: I stumbled on the forum and I had some free time

P.S.
Thanks to the donors !

[V2.7 out (2023/08/18)]

V2.7 out (2023/08/18)

• Updates for GPB beta21 (only, no changes for GPB, WRS and KRP).

I've added a PayPal donate button in the 1st post

[V2.7 out (2023/08/18)]

V2.7 out (2023/08/18)

• Updates for GPB beta21 (only, no changes for GPB, WRS and KRP).

I've added a PayPal donate button in the 1st post

[V2.2.7 out (2023/08/18)]

V2.2.7 out (2023/08/18)

• Updates for GPB beta21 (nothing visible, only internals). No changes for MXB, KRP, WRS.

I've added a PayPal donate button in the 1st post

[V2.2.7 out (2023/08/18)]

V2.2.7 out (2023/08/18)

• Updates for GPB beta21 (nothing visible, only internals). No changes for MXB, KRP, WRS.

I've added a PayPal donate button in the 1st post

Would it Be possible to get an update to MaxHUD where these options are basically "duplicated" for the Front Over/Underrun and Rear Over/Underrun (4 Pages). I really like the feel I had on this version on the rear, but I struggle with the 2.2.6 rear, however I enjoy having the front feeling.

Or is it possible to change the "Maps" in a cfg somewhere?

I'm not sure I understand what you want to do exactly.
If your goal is to have what you show in your screen shot (from 2.2.5) in 2.2.6, that's definitely possible: in 2.2.6, "CoG Acc destination" set to "Light rumble" and "Rear overrun destination" to "Heavy rumble" (all the others off). Then you need to check the maps in the .ini and set the values you like.
For your screnshot above, one of the cogacc maps should be set at {0.2, 0.5, 0.2, 0.4} and one of the tireslip maps should be set at {0.03, 0.20, 0.2, 0.5}.

If you mess up, just delete the lines from the .ini, they will be recreated with default values.

Hi David, looks like your pad is not seen as an xinput pad, so no joy.
A quick search on the web (Logitech Rumble Pad 2 xinput) brings up a lot of results of people with troubles using that pad in xinput games. There may be a solution via x360ce (e.g. here), but it may be a bit messy.

But why would you want the rumble active on a pad mounted on your steering wheel ? Just curious ...

As for my issue I think the actual zip archive seems corrupted ( "MaXHUD - v2.2.6.zip" on the Mega site ). Any of the downloads I tried last weeks ended with a 0 bytes zip result. Would be great if you could check that out.

Seems to work fine here for me, I can download 2.2.6 without any problem. Can you try with a different browser ?

BTW, 2.2.6beta should not be used.

EDIT: I re-uploaded the archive just in case.

Not cheap, but not terribly expensive either.
Hall sensors on sticks and triggers should make a lot of difference.

Too bad I just purchased a random pad, would have tried this one for sure.

[EDIT: doh, you told me about that in your DM, sorry.]

hey Max, we've just recently discovered that by using MaxHud on a specific MXB track, the game crashes with a C++ Runtime error. PiBoSo figured it was due to MaxHud, I tried it as well and can confirm that it only crashes with MaxHud enabled.
I'll send you a DM with the track link, would be awesome if you'd got the time to debug and fix this We appreciate it big time!

Hi,

what do you mean exactly with "it crashes" ? At startup ? When you go to track ? After riding a few meters ? Always at the same spot ? Randomly after a few secs/minutes ? Context, plz

Also:

• I don't understand what you want to show with the screen capture above.
• The .pkz is named "Jones_AX2.pkz" but the folder inside is "Jones AX2" (OK I can fix that by myself, just FYI). EDIT: doh, you told me about that in your DM, sorry.
• In your racedata (.rdf) you have finishline, holeshot, split1 & split2 all at the same place. Maybe this screws MaxHUD (or even MXB). Not sure it's good practice.

_Edit: The lack of MaxHUD and ReShade out of the box is problematic, too.

Not that I think PiBoSo needs my help on anything even loosely related to coding, but if he wants he can have the source code of MaxHUD. Anytime, for free. Same applies to the other tools I've created (MaxTM, MaxTyre, MaxSCL).

Again, not sure it will help a lot, but if it does and he can stomach reading what probably qualifies as poor code, then he can have all of them in a nice bundle