Messages

[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

MaX.. Do you have any plans to make a VR version? 

No.

Sorry for dumb question (I don't have VR hardware): what's the problem with VR ? Stuff doesn't show up ?
At all ? Or is it just in a fixed position (hence not kept in visual range when head moves) ?
It could be something that PiBoSo should do and not really the plugin.

Never heard about anybody having troubles using MaxHUD and playing online.
The problem is likely elsewhere.

So I tried installing Max Hud into my Plugins folder but It didnt work...
I figuered the problem was the other two files which were already in there: one of them was called something with x input....
So I delete those two files which was very dumb because now my controller isnt working anymor ((
Any tips what i should do??

Did you read how to install it properly ? Including MSVC redist stuff ?

Bad idea to delete random files when you don't know what they are for. Reinstall MXB ?

[EDIT]

EDIT: the pdf had a wrong explanation of how rumble profiles work (thx to Saemon No Jyo for spotting that). I've ninja-updated the 2.2.6 zip with the corrected pdf. The relevant part is this:

• _cogacc_rumble_map0/1/2, _tireslip_rumble_map0/1/2: each map is composed of 4 floats representing the two interpolation points translating the source value into a rumble value: [min driving value, max driving value, min rumble strength, max rumble strength]. E.g. for tire slip "{0.04,0.10,0.20,1.00}" means that at 4% slip rumble will be at 20% and at 10% slip rumble will be at 100%. You can modify the maps in the .ini file manually.
  

[V2.6 out (2022/02/06)]

V2.6 out (2022/02/06)

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

[V2.2.6 out (2022/02/06)]

V2.2.6 out (2022/02/06)

• Updates for MXB beta17.
• New HUDRumble: this will overwrite your previous rumble settings. You need to reconfigure the settings (at least associate the right XInput device). Read the .pdf help for explanations.

EDIT: the pdf had a wrong explanation of how rumble profiles work (thx to Saemon No Jyo for spotting that). I've ninja-updated the 2.2.6 zip with the corrected pdf. The relevant part is this:

• _cogacc_rumble_map0/1/2, _tireslip_rumble_map0/1/2: each map is composed of 4 floats representing the two interpolation points translating the source value into a rumble value: [min driving value, max driving value, min rumble strength, max rumble strength]. E.g. for tire slip "{0.04,0.10,0.20,1.00}" means that at 4% slip rumble will be at 20% and at 10% slip rumble will be at 100%. You can modify the maps in the .ini file manually.
  

[V2.5 out (2021/12/19)]

V2.5 out (2021/12/19)

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

[V2.2.5 out (2021/12/19)]

V2.2.5 out (2021/12/19)

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

Thx tfc. warning, it's probably crap for MXB, too many big jumps and the previous rumble is likely more useful.
It may make more sense in GPB, just as a "powerslide" warning.

[V2.2.4 out (2021/09/27)]

V2.2.4 out (2021/09/27)

• .ini file version change: will lose all settings. You'll have to manually redo them. Sorry. That's life.
• Minor cosmetic changes: widgets options with fixed font and better aligned.
• HUDRumble rework:
  
  • 2 possible sources: CoG acceleration (norm filtered by highpass) or rear tyre overrun (how much faster is the rear tyre spinning compared to CoG velocity norm). Overrun is only for GPB and MXB. In MXB it may not make sense at all.
  • Each source has 2 extreme points between which the values are interpolated.
  • Each source can be associated with each rumble motor.

If you test the two rumbles, I'm interested in your feedback, including what default settings could make sense.

[v2.4 out:]

v2.4 out:

• In the viewer, the displayed track width is now in actual meters.
• Fix for GPB: logging of TC/EB/AW flags was wrong.
• For GPB & MXB only: added some data about tire slip (from wheelspeed and CoG speed).

[v2.3 out:]

v2.3 out:

• Updates for GPB beta19 (tyre temps are logged).

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

[V2.2.4 out (2020/12/30)]

V2.2.4 out (2020/12/30)

• Removed fixed font AsapBold as not truly fixed.
• GPB only: ECU widget now also shows tyres temperatures (when bike allows it).