Hi all,
this plugin allows to put on screen a variety of widgets as show in the below images.
EACH WIDGET CAN BE CONFIGURED AND HIDDEN, YOU DO NOT HAVE TO USE THEM ALL.For install instructions, plugin configuration, changes in versions and so on,
please read the .pdf file in the .zip. PLEASE. READ. IT. DOWNLOAD v2.2.7: (https://mega.nz/#F!dRsyARjI!ceFbX0UW01KgB93KY83hZA) <<-- THIS if for
GPB beta21,
WRS beta14,
KRP rel13 and
MXB beta18 Love this stuff and you want to show that ? Have too much money at hand and don't knowe what to do with it ? Donations are welcome 8)
PM me when donations are done, so that I can keep a donors list
HERE (http://forum.piboso.com/index.php?topic=6059.0).
(http://i.imgur.com/8qEORV3.png) (https://www.paypal.me/HornetMaX)
| (https://i.imgur.com/sVqoL5N.jpg) (https://i.imgur.com/sVqoL5N.jpg) | (https://i.imgur.com/vTGLNhk.jpg) (https://i.imgur.com/vTGLNhk.jpg) |
| (https://i.imgur.com/WJTUxOX.jpg) (https://i.imgur.com/WJTUxOX.jpg) | (https://i.imgur.com/cXxuJKA.jpg) (https://i.imgur.com/cXxuJKA.jpg) |
IMPORTANT: If you get a warning/error about missing dlls, or if nothing shows up once on track, install:
- Microsoft Visual C++ 2015,2017,2019 Redistributable Package (x64) (https://aka.ms/vs/16/release/vc_redist.x64.exe)
Thank you very much MaX, at least for me it's the KRP plugin of the year. :)
Finaly realtime live-timing is back. All plugins of NOP (random) stopped working with the changed data format of KRP beta11.
I don't see temperature. Can it be added? This would be useful for me because I need all the fps I can get so I hve to hide the driver and hud.
There also to view with the helmet ?
Quote from: EVO on May 30, 2014, 08:19:43 PM
I don't see temperature. Can it be added? This would be useful for me because I need all the fps I can get so I hve to hide the driver and hud.
There's no temperature because that's normally shown on the HUD. Just show the HUD, no ? I doubt it makes you lose a lot of FPS.
Quote from: Tmax94 on May 31, 2014, 03:11:10 PM
There also to view with the helmet ?
What do you mean exactly ?
There's an option to show/hide the helmet inside (and you can also make it vibrate a bit and put its top and bottom section at different height).
MaX.
The plugin is great!! Can you add temperature though?
how to instal
Quote from: EVO on June 02, 2014, 06:22:30 PM
The plugin is great!! Can you add temperature though?
Temperature is on the dash ? Why don't you activate the dash to get it ?
Quote from: Top-Kart 92 on June 02, 2014, 07:51:46 PM
how to instal
Oh man, what about reading the 1st message ?
Quote from: HornetMaX on May 29, 2014, 10:40:42 PM
For install instructions, plugin configuration, changes in versions and so on, please read the .pdf file in the .zip. PLEASE. READ. IT.
MaX.
CONGRATULATIONS!!!!!!! Very Cool!
***PIBOSO***
Now just need to have support for TrackIR
Quote from: HornetMaX on June 02, 2014, 08:30:20 PM
Quote from: EVO on June 02, 2014, 06:22:30 PM
The plugin is great!! Can you add temperature though?
Temperature is on the dash ? Why don't you activate the dash to get it ?
Quote from: Top-Kart 92 on June 02, 2014, 07:51:46 PM
how to instal
Oh man, what about reading the 1st message ?
Quote from: HornetMaX on May 29, 2014, 10:40:42 PM
For install instructions, plugin configuration, changes in versions and so on, please read the .pdf file in the .zip. PLEASE. READ. IT.
MaX.
No sense in showing redundant information. Less distractions. For example I only need temp light (not even the value just a light) an rpm light and splits.
Quote from: EVO on June 03, 2014, 04:02:31 PM
No sense in showing redundant information. Less distractions.
Well, that's why there's no temp in the plugin, it's already in the dash.
Quote from: EVO on June 03, 2014, 04:02:31 PM
For example I only need temp light (not even the value just a light) an rpm light and splits.
RPM light is in the speed/gear indication: it changes color depending on the RPMs.
Splits are already there in the plugin.
What's missing ?
I can't customize the whole thing to fit anyone's needs (well, except my own ones :) ), it has to be a sort of trade-off.
MaX.
Is your telemetry working for KRP?
Quote from: LauZzZn on June 03, 2014, 04:53:41 PM
Is your telemetry working for KRP?
As replied on GPB forum:
Quote
Not the version currently out (v1.1), but I have one almost ready and it is working with KRP too. So it's gonna come soon ...
MaX.
What software do you use to make this?
Quote from: EVO on June 03, 2014, 05:38:09 PM
What software do you use to make this?
You can use any language you want, provided it has a C interface. I use C++.
MaX.
how long did it take you to make it? How difficult was it to manipulate random's code for PiBoSo's sims? May inquire to acquire the code so that I can have a shot at a personal hud design?
Quote from: EVO on June 05, 2014, 11:09:42 PM
how long did it take you to make it?
I didn't count the time spent on it and I've been adding features for a long time.
Despite being a comp. science engineer, I was a bit rusty on development as I no longer work in this field, so I lost quite some time at start.
Right now, when I have to add a new feature it'a matter of a minutes to hours (unless it's something very complex).
Quote from: EVO on June 05, 2014, 11:09:42 PM
How difficult was it to manipulate random's code for PiBoSo's sims?
As always with other's code, it's a bit hard to understand. Random's code was also with very few comments and in a strange language (strange to me at least, not even sure if it was hungarian or something like that).
After having understood it, I've essentially rewritten everything, not sure there's a single line left in.
Quote from: EVO on June 05, 2014, 11:09:42 PM
May inquire to acquire the code so that I can have a shot at a personal hud design?
Random's code no, I cannot send it to you.
My one yes (send me a PM with your email), but I can warn you from now that if you're not proficient in C++, then you're entering a world of pain: it's 4000+ lines of messy code (without counting blank lines, comments and not even some preprocessor stuff), overcomplicated by the fact it can be compiled for GPB, WRS and KRP.
MaX.
Is this possible to run this on beta 10b, As at the moment we are running SimVibe and that is not able to run with beta 11.
Quote from: maxrod on June 06, 2014, 09:12:44 AM
Is this possible to run this on beta 10b, As at the moment we are running SimVibe and that is not able to run with beta 11.
I would have to make a dedicated builld for this, which in turns implies I'd have to fetch piboso's plugin interface for beta10b (I don't have it, maybe somebody has it around or Piboso can fetch it) and adapt some code.
I'd be really happy to avoid doing that as it could become a maintenace nightmare. In any case, one day or the other you'l have to move forward so ...
What's the problem with SimVibe and beta11 ?
MaX.
Thanks for the reply, It is not for me it is for some one else I will have to get in touch with the person to find out, As you would think if SimVib works with 10b sooner or later it has to work with beta 11, But then again are people going to keep updating software plugins tracks ect with every beta, as there has now been over 11.
Quote from: maxrod on June 06, 2014, 12:59:55 PM
But then again are people going to keep updating software plugins tracks ect with every beta, as there has now been over 11.
Plugins and tracks may not need to be updated every single beta. For plugins it's only if the plugin interface changes (which has been the case from 10 to 11, but not on many other betas).
Anyway, for my plugins and stuff, I'll keep updating them: usually it's just a 2 hours job as most of the time the changes are done by Piboso in order to minimize impact on the plugins.
MaX.
v1.8.0 out:
- Updated for GPB beta5 (no changes for KRP and WRS).
MaX.
v1.8.1 out:
- Updated for WRS beta5 (no changes for GPB and KRP).
MaX.
v1.9.0 out:
- LiveGapBar replaces LiveGap (Klax75 suggestion, similar to iRacing indicator).
- Plugin rate bumped at 50Hz (from 20Hz): shouldn't be a problem and makes everything smoother.
- Widgets cannot be moved out of the screen.
- Widgets cannot be moved if they are not enabled.
- Interpolated colors in HUDInputs (just eye candy).
- Some default sizes are slightly changed.
- .ini file structure modified (one section per widget + global section).
- .ini file version bumped to 7: you will lose your plugin settings as they will be reset to defaults.
MaX.
v1.9.1 out:
- Fix a bunch of bugs in LiveGapBar (I must have been very drunk).
MaX.
v1.9.2 out:
- Now works for MXB too (no changes for other versions).
MaX.
v1.9.3 out:
- Bug fixed: MXB has only 2 sector times, not 3. Doh !
MaX.
I just get it !
very nice thank you.
As already said the MaxHud plugin is still the plugin of the year for me.:)
Max, I've noticed a time difference between -0.2 and -0.9 seconds at the splits between your tool and PiBoSo's time in the dash. Do you know what's the reason?
Quote from: dibu on November 28, 2014, 09:30:04 PM
As already said the MaxHud plugin is still the plugin of the year for me.:)
Way too generous. And I stil lowe you a beer :)
Quote from: dibu on November 28, 2014, 09:30:04 PM
Max, I've noticed a time difference between -0.2 and -0.9 seconds at the splits between your tool and PiBoBo's time in the dash. Do you know what's the reason?
I guess you mean the live-gap line in the timing widget, right ? From the manual:
QuoteLine 4 is for LiveGap: it's the time difference at (roughly) the same spot on the track between your current lap and your best lap. Kind of a ghost for the poors. You'll notice two values: the 1st one is compute with GPB/WRS/KRP timing info (_fTime), the second with Windows accurate timer. Normally GPB/WRS/KRP info should be enough, but for some unexplained reasons GPB/WRS/KRP''s _fTime sometimes drifts off (I've seen errors of 0.7s on a single lap). Once the issue is sorted out I'll keep only one value.
Honestly, I asked Piboso at least 3 times to have a look at why the game time passed to the plugin (_fTime) drifts off like this, but I never got any answer.
I'm making one last attempt here: http://forum.piboso.com/index.php?topic=1769.0 (http://forum.piboso.com/index.php?topic=1769.0)
MaX.
update for KRP beta 12? thanks
Quote from: VELOCIPEDE on January 02, 2015, 07:44:41 PM
update for KRP beta 12? thanks
Gee, give me at least the time to download beta12 ... it hasn't even been out for 48hrs and, to be honest, I was relatively busy on Jan 1st :)
MaX.
v1.9.5 out:
- Update for KRP beta12 (no changes for GPB, MXB and WRS).
MaX.
v1.9.6 out:
- New helmet for MXB, thanks to TheFatController (MXB forum).
- When pit limiter is used (GPB and WRS only), the gear indicator now turns into a 'L' and the input bar for throttle changes shape (davidboda46 suggestion).
- Fixed the documentation.
MaX.
v1.9.7 out:
- Changes for WRS beta6 (no changes for GPB, KRP and MXB).
MaX.
v1.9.8 out:
- Shows steering in Inputs widget.
- New widget to show joypad output.
- Other minor changes.
IMPORTANT:
- It will erase your current config for the plugin: you'll have to manually reconfigure it (options and widget positions).
- To use the steering and the new widget showing the joypad output you have to select the input device and the appropriate axes. Read the .pdf manual.
- The joypad widget shows the triggers as combined (even if you're using XInput). I know, it sucks a bit, bit I'm not going to spend too much time on that.
MaX.
v1.9.9 out:
- Added HUDRumble to enable rumble on XInput devices.
- For GPB/MXB, HUDInputs now show the "lean input" and the steering angle.
IMPORTANT: the rumble stuff has been tested on GPB only (and very briefly). Read the manual for the details (it saves you asking here and me replying "It's in the manual").
MaX.
don't work with the last beta 14, please update, thanks
v1.9.9c out:
- Updated for KRP beta14.
- Fix bug: MaxHUD.log was never erased (hence growing over time). Now it's erased at startup.
- Fix bug: starting the game and exiting right after (i.e. without going to track) was messing up the MaxHUD.ini file (possible loss of parameters).
MaX.
Thank you MaX, nice that you don't forget KRP. :)
thank you :)
v1.9.9d out:
- Sort out some issues with saving options in .ini file (hopefully).
MaX.
v1.9.9e out:
- Updated for WRS beta7.
- HUDSpeed has option to show background (color in .ini file).
MaX.
v1.9.9g out:
- Fix bug leading to crash (when going to replay immediately after connecting).
MaX.
v2.0.0 out:
- Updates for GPB b8, WRS b8, MXB b4, KRP b14
- Track map widget now shows also other vehicles (up to 20) and the race numbers.
- New radar widget: can show a radar and/or "flying markers" (around the screen). Should help people using 1st person view to be more aware of nearby vehicles.
- Helmet now has an option to rotate with the bike lean (with a factor specifying how much it will rotate). @ddcc: Play around with that and let me know. The manual has a few extra details about how this works.
v2.0.1 (2016/07/13):
- NEW HUDStandings: show current standings and gaps. Doesn't work for WRS beta8 and KRP beta14 (sims bug ?)
- HUDHelment: option to inverse rotation.
- HUDRadar:
- Markers are shown only if distance is within range and track-distance (distance along track) is in range too.
- Option to fade flying markers when in FOV (configurable FOV).
- Maximum 4 simultaneous markers shown (the 4 closest ones).
- HUDSupsensions: option to show raw values (and reference point height).
- HUDLean: simplified, removed steering angle indicators.
- Minor changes to default colors, sizes and positions.
Thank you as always MaX, also for the WRS version :)
Quote from: dibu on July 14, 2016, 07:11:40 PM
Thank you as always MaX, also for the WRS version :)
Pleasure ! Unfortunately there seems to be be a bug in KRP and WRS, so the standings widget doesn't work for them :(
V2.0.3 (2016/10/06) out:
- Does not work with MXB beta4, use v2.0.2b for it.
- Update to KRP beta15, WRS beta9, GPB beta9.
- HUDMap: better centerline approximation (more segments when needed).
- HUDMap now available also in replay and spectating mode.
- HUDStandings now available also in spectating mode.
- HUDStandings option to show player race number, name or alternate between the two.
- HUDInputs: minor changes.
- HUDSpeed showing throttle, brake and gear also in replays: now works in GPB (but gear not yet passed by KRP/ MXB).
- Various improvements to HUDStandings (session type/time, etc).
[/quote]
Thank you very much MaX, I was already missing it. :)
The new feature list makes MaXHUD even more interesting.
V2.0.4 (2016/10/08) out:
- Does not work with MXB beta4, use v2.0.2b for it.
- Fix HUDRadar bug (likely introduced with v2.0.3).
- Workaround for GPB/WRS bug (SessionState not going to in-progress after semaphore).
thanks for this :D
V2.0.5 (2016/12/29) out:
- Updated for MXB beta5.
- Allow to change the fonts used by the plugin (2 fixed and 3 variable are provided, more can be added, read the .pdf manual for infos).
- Use fixed font (monospaced) where it makes sense (e.g. HUDTiming).
- Better looking HUDMenu.
v2.05b (2016/12/30) out:
- HUDLean not showing in menu :-[ (reported by philiaN).
v2.0.6 out (2017/02/16):
- Notify when .ini is recreated (due to new version of .ini format).
- v2.0.6 will recreate your .ini, you'll have to redo all the HUD settings. Sorry :)
- Introduce profiles: you can set widget on/off status, position and options for each profile independently. Click on the small helmet button (top right of the menu) to change the current profile. For example, you could set:
- profile 1: all widgets off
- profile 2: HUDMap an HUDHelmet on, HUDMap rotation off
- profile 3: HUDMap an HUDHelmet on, HUDMap rotation on
By default, the position of each widget is the same across the profiles. If you need a per profile position, click on the "pin" icon of the widget. - Improved LiveGap: should give more precise timing.
- Changes in HUDRumble (to better suit to MXB): on top of the rumble strength and threshold, now you can specify a rumble range.
- When the magnitude of the (high-pass filtered) CoG acceleration vector is below or equal to the threshold, the rumble speed is zero (i.e. no rumble).
- When it's equal to (threshold + range) then the rumble speed is maximal.
- In between the two points, it's linear interpolation.
Said otherwise:
- A lower threshold will make the rumble happen earlier (more often).
- A lover range will make the rumble become stronger earlier.
- The max strength is still controlled by the strength option.
v2.0.6a out (2017/02/17):
- Changes for GPB beta11 and WRS beta11.
- No changes for KRP and MXB.
v2.0.6b out (2017/02/19):
- Fixed a bug (some widgets not saving position). Reported by PeterV.
Doesn't work for beta 16?
Quote from: AidenKempf on March 14, 2017, 03:57:45 AM
Doesn't work for beta 16?
it has to be updated bro.... the game changed things dont work for it anymore
Yeah figured I hope it gets updated :)
v2.0.7 out (2017/03/16):
- Updated for KRP beta16 and MXB beta6.
- Show "Rumble if crashed" option in HUDRumbe only for GPB and MXB.
v2.0.7b out (2017/03/17):
- Fix for invalid laps (KRP and MXB only, no change for GPB and WRS).
Wow you are one of the best mod makers thanks <3
v2.0.8 out (2017/06/19):
- HUDSuspensions: warning sign when suspension is bottoming out + configurable threshold (not for KRP of course).
- HUDMap: cosmetic changes (lines for finish/trap/split points, plus arrow for track direction).
- HUDJoypad: cosmetic changes.
- HUDRadar: cosmetic changes (flying markers are now triangular).
- HUDHelmet: rotation factor has now finer settings (10deg steps). You'll need to redo all the settings of this widget.
Quote from: HornetMaX on June 19, 2017, 11:34:58 PM
v2.0.8 out (2017/06/19):
Thank you MaX, I still love your plugins. :)
Quote from: dibu on June 20, 2017, 06:38:58 PM
Quote from: HornetMaX on June 19, 2017, 11:34:58 PM
v2.0.8 out (2017/06/19):
Thank you MaX, I still love your plugins. :)
Cheers dibu !
BTW, it seems to work fine with rel1/2.
V2.0.9 (2018/01/23) out:
- Updated for GPB beta13 (no changes for MXB, KRN and WRS).
- New HUDECU: shows when TC, EB and AW kicks in (GPB only).
V2.1.0 out(2018/06/16)
- Updated for MXB beta 8: first x64 release of PiBoSo sims !!
- Files renamed to:
- MaxHUD_GPB32.dlo
- MaxHUD_MXB64.dlo
- MaxHUD_WRS32.dlo
- MaxHUD_KRP32.dlo
No changes for GPB, WRS and KRP.
V2.1.1 out(2018/07/16)
- Updated for GPB beta14 and WRS beta13 (both are now x64).
- Files renamed to:
- MaxHUD_GPB64.dlo
- MaxHUD_MXB64.dlo
- MaxHUD_WRS64.dlo
- MaxHUD_KRP32.dlo
No changes for MXB and KRP.I've added a PayPal donate button in the 1st post 8)
Thank you MaX, donation button found :).
V2.1.2 out(2018/08/29)No changes for GPB, WRS and KRP.
V2.1.3 out (2019/04/11)- Update for KRP release 8: it's not an x64 app !
- Try to prevent rumble staying on in some conditions (thanks to TFC for reporting).
- Fix names of Session & SessionState (was very broken in MXB).
V2.1.4 out (2019/05/08)- Improved HUDECU (GPB only) on suggestion from Myst1cPrun3
- No chenages for MXB, KRP and WRS
V2.1.5 out (2019/08/18)- Changes for MXB beta11 (reference UI is now 16:9).
- Avoid widgets outside the screen (when loading .ini)
- Change default background color for HUDSpeed.
V2.1.7 out (2020/01/03)- Changes for KRP beta10 (reference UI is now 16:9).
- GPB only: option in HUDInputs to show either "throttle" or "engine throttle": "throttle" is what comes out of your input device, "engine throttle" is what goes into the engine (i.e. corrected buy the ECU with idle control, traction control, anti wheeling and rev limiter).
Happy New year all !
V2.1.8 out (2020/01/23)- HUDTiming: LiveGap now shows only one livegap (the one from Windows timer, as the game's own timing passed to the output plugins drifts away over laps).
- Change LiveTiming due to a bug discovered in MXB (see http://forum.mx-bikes.com/index.php?topic=3143.0). Should have no impact (aside mitigating the MXB bug).
V2.2.0 out (2020/05/06)- Important: there are new files in the MaxHUD_data fodler: please copy the whole folder.
- All the widgets that had the option to show or not a background can now also use a .tga file as background. Click on the menu option to know the file name each widget is expecting (in MaxHUD_data folder).
- HUDMap: Improved track drawing. Now plots a border along the track. Width and color of track and border can be
configured. Track width and track border width have a "fixed screen size" option. Warning: widget configuration will be
reset. - HUDStandings: some cosmetic rework. Warning: widget configuration will be reset.
- Fixed some scaling/aspect ratio bugs.
- Some cosmetic changes all around.
V2.2.1 out (2020/08/11)- Reduced by 50% the number of quads used by HUDMap: fps impact of MaxHUD should be lowered (especially on long tracks / low-spec systems).
- All timings can now display longer times / gaps.
- HUDLiveGapBar has now more options for its scale (can be longer, for veeery long tracks).
V2.2.2 out (2020/12/26)- Changes for GPB beta19.
- Widgets in menu are now sorted alphabetically.
- Changed default track & border width in HUDMap to "fixed screen size".
Hello,
I just logged into KRP and the menu's that normally appear when I click on the thumbtacks are not opening? I can't manipulate the individual attributes of each function? (map, speed, timing, etc)
I am on version 2.2.1
THANKS!
All the thumbtacks only show this information:
You cannot see attachments on this board.
Quote from: Overdue on December 26, 2020, 07:38:16 PMHello,
I just logged into KRP and the menu's that normally appear when I click on the thumbtacks are not opening? I can't manipulate the individual attributes of each function? (map, speed, timing, etc)
Click on thge widget name (e.g. "Helmet", "Timing" etc).
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).
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.2.5 out (2021/12/19)- Updates for GPB beta20 (only, no changes for MXB, WRS and KRP).
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.
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.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 8)