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)
Yesssssss. I was waiting for this.
Also, do you know of any way to have an icon of some sort pop up on screen when you're sitting? I started to code one and just couldn't get it to work.
Quote from: onlyonetone on October 01, 2014, 11:07:03 PM
Yesssssss. I was waiting for this.
Not waited for too long I'd say :)
Quote from: onlyonetone on October 01, 2014, 11:07:03 PM
Also, do you know of any way to have an icon of some sort pop up on screen when you're sitting? I started to code one and just couldn't get it to work.
As far as I can see, MXB does not pass this info to the plugin, so I can't display it. Same goes for other inputs (like rider lean l/r and f/b, lean).
MaX.
Thank you !
v1.9.3 out:
- Bug fixed: MXB has only 2 sector times, not 3. Doh !
MaX.
Just an example of Max HUD plugin in action :)
Thank you again Max for this plugin :)
https://www.youtube.com/v/ce4HP2Lj4C4
Thanks MaX! but is there any way to just use it with the helmet interior?
Quote from: kmracing99 on October 07, 2014, 09:53:57 PM
Thanks MaX! but is there any way to just use it with the helmet interior?
Yes there is a way. All the individual widgets can be moved and switched on/off (most of them have a bunch of other options).
Out of curiosiy, did you se that line in the top post ?
Quote from: HornetMaX on October 01, 2014, 11:02:44 PM
For install instructions, plugin configuration, changes in versions and so on, please read the .pdf file in the .zip. PLEASE. READ. IT.
I'm starting to think all the MX riders are red-blind maybe :)
MaX.
I really like having some info on the screen but is there a way to toggle the entire plugin off and on?
And is there any possibility of being able to not have the helmet show up in 3rd person?
Thanks for this great little tool btw.
Caps lock! Press caps lock.. Then you can switch on/off whatever you want..
I'm aware of Capslock. I mean to toggle the entire plugin off and on once you have the things you want. I have only a few things but I'd still like to toggle them off or on quickly while in the game. (for when you want to go back to full immersion with no HUD)
I see what you mean now! Im not so sure, I think u have to drag the menu up.. I only use the split times in the corner..
MaX will tell you.. Unless he tells you to read the pdf file first lol :P
Quote from: ExistentialEgg on October 08, 2014, 05:49:18 AM
I'm aware of Capslock. I mean to toggle the entire plugin off and on once you have the things you want. I have only a few things but I'd still like to toggle them off or on quickly while in the game. (for when you want to go back to full immersion with no HUD)
Can you provide a concrete example on how you'd use this ?
MaX.
I was wearing concrete sunglasses at the time, sorry! :-[
Quote from: kmracing99 on October 08, 2014, 09:35:58 AM
I was wearing concrete sunglasses at the time, sorry! :-[
;D
MaX.
Quote from: HornetMaX on October 08, 2014, 08:41:41 AM
Can you provide a concrete example on how you'd use this ?
MaX.
Anytime I switch to 3rd person (in lieu of the helmet issue I mentioned). Caps Lock feels more like the configuration screen so it wouldn't be ideal if you merely wanted to disable the things you had chosen to be on the screen quickly. I was just curious if it would be possible to push Scroll Lock (as an example) and it toggles off and on the widgets you had configured via Caps Lock.
Or sometimes I want to know where I am on the track as far as the finish line but I don't want all that info on the screen the whole time because I enjoy the full immersion of an empty hud. So, I could tap Scroll Lock to get a quick peek at the track map.
And also if I wanted to take a quick screenshot. Instead of needing to go in and toggle each element off I could hit one key that hides my plugin layout.
I guess I'm the only person who would like that feature, idk. If possible I would definitely love if there was a way for the helmet to not show up in 3rd person (not sure if that info gets passed to the plugin).
Quote from: ExistentialEgg on October 08, 2014, 04:04:24 PM
Anytime I switch to 3rd person (in lieu of the helmet issue I mentioned). Caps Lock feels more like the configuration screen so it wouldn't be ideal if you merely wanted to disable the things you had chosen to be on the screen quickly. I was just curious if it would be possible to push Scroll Lock (as an example) and it toggles off and on the widgets you had configured via Caps Lock.
Or sometimes I want to know where I am on the track as far as the finish line but I don't want all that info on the screen the whole time because I enjoy the full immersion of an empty hud. So, I could tap Scroll Lock to get a quick peek at the track map.
And also if I wanted to take a quick screenshot. Instead of needing to go in and toggle each element off I could hit one key that hides my plugin layout.
I guess I'm the only person who would like that feature, idk. If possible I would definitely love if there was a way for the helmet to not show up in 3rd person (not sure if that info gets passed to the plugin).
Well, switching view (rider view --> 3rd person) is not something you're supposed to do frequently, so I don't see the justification there (and no, the plugin does not know if you're using rider view as the info is not passed).
The other use case (quick glance at some info) may make more sense, but I may have to figure out something smarter than the "scroll lock" trick.
I note this down somewhere in my todo list, in case.
MaX.
Yeah its a pretty good idea actually.. Being able to toggle on/off each widget quickly.. Especially online!
Quote from: BOBR6 84 on October 08, 2014, 09:55:28 PM
Yeah its a pretty good idea actually.. Being able to toggle on/off each widget quickly.. Especially online!
The problem is that you'd need a bunch of keys for that (and possibly keys that do not interfere with keys typically used for MXB/GPB/WRS/KRP).
MaX.
Thats true.. I only tend to use the split sector times so its not a problem for me to be honest..
Does your telemetry work for mxbikes?
Quote from: BOBR6 84 on October 08, 2014, 10:56:40 PM
Does your telemetry work for mxbikes?
It's not hard to make it work for MXB, but I was wondering if there's a real audience for that. Already in GPB it has few users, here in MXB it's likely to have even less. And to be honest I don't even know if you have telemetry on real MX bikes.
MaX.
This is a fantastic plugin :)
Makes hotlapping, so much more enjoyable being able to see proper time readouts.
v1.9.5 out:
- Update for KRP beta12 (no changes for GPB, MXB and WRS).
MaX.
This pukka plugin still works well in beta3, cheers for it Max.
Quote from: teeds on May 05, 2015, 12:06:49 PM
This pukka plugin still works well in beta3, cheers for it Max.
That's thanks to the exceptionally smart design of my code. And to the fact that there was no plugin interface change between beta2 and beta3, too :)
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.
Thanks MaX, and thanks for adding the helmet :)
Quote from: TheFatController on July 04, 2015, 07:13:12 PM
Thanks MaX, and thanks for adding the helmet :)
Thanks to you for sharing it with us all !
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.
v1.9.9b out:
- Improved HUDRumble: acceleration-based rumble, no need for "fake" gear shift rumble.
- Improved handling of settings file (MaxHUD.ini): sorry, but it will overwrite your current one (will have to reconfigure everything). In the future, it will happen less often thanks to the improvements in this release.
- Logging to MaxHUD.log is always now on (tiny file, no impact).
IMPORTANT:
- It will erase your current config for the plugin: you'll have to manually reconfigure it (options and widget positions).
MaX.
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.
v1.9.9d out:
- Sort out some issues with saving options in .ini file (hopefully).
MaX.
MaX, I took a break from MXB but recently tried out your latest version and it's great. Absolutely love the rumble! Good job and thanks. ;D
Quote from: TheFatController on August 25, 2015, 01:24:28 AM
MaX, I took a break from MXB but recently tried out your latest version and it's great. Absolutely love the rumble! Good job and thanks. ;D
To be honest I barely tried it with MXB (and WRS, KRP), but I'm happy to hear it seems to work fine.
If you/others here have any suggestion on how to better adapt the rumble to MXB, do not hesitate to put it forward.
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.
Salut Max y aura t-il une mise a jour de ton plugin pour la beta4 mx bikes ??
Quote from: franckyto94 on March 01, 2016, 11:35:45 PM
Salut Max y aura t-il une mise a jour de ton plugin pour la beta4 mx bikes ??
Yes, it will be updated for MXB beta4.
I'm working on a couple of features that have been requested by GPB people: dots for other bikes on the track map (so that you can see where others are, with race numbers) and a kind of "radar" that shows bikes nearby your one.
I was waiting for GPB beta8 and MXB beta4 to come out to finish it up so that it will work with them (and with WRS beta8, not really with KRP, until KRP beta15).
Can't wait MaX..
Miss my rumble lol..
ok thanks man good job ;D
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.
Awesome, thanks Max :D
Never gave this a proper chance, i'll try it today, thanks Max :)
Thanks MaX, have felt naked without it!
thanks men ;D ;D ;D
MaX.. Before you tell me to read the damn PDF!
I can't get it to show up. I've put the right files in my mxb plugins folder (MaxHUD_MXB.dlo and MaxHUD_Data) but pressing Caps-lock in game does nothing. It's also not created the .ini in my PiBoSo folder which is in the usual place..
I've downloaded the vcredist_x86 but it just offers me repair or remove as I already have it. Tried repair and no luck. Side note, that the link you have in the documentation for the C++ redist doesn't work.
This was also a clean install of MXB, including the PiBoSo folder in documents.
Edit: after a good look around I think I'm the only one with this problem so it's obviously a local issue, just lost for ideas!
Any ideas?
Hi Fatty, my fault actually, I forgot to update that in the .pdf :-[
You actually need Microsoft Visual C++ 2013 Redistributable Package (x86) (https://www.microsoft.com/en-us/download/details.aspx?id=40784): once you press Download, select the x86 version "vcredist_x86.exe".
Can you tell me if it works with that ? I'll ninja-update the documentation.
Oh awesome, didn't try the 2013 update so will try later and let you know. Busy day as mothers day and 3 mothers about including the Mrs so will check this evening.
Thanks MaX!
Managed to sneak away. All working great, thanks.
Hey MaX, have you guys over on gpb came up with anytype of replay overlay like you'd see in moto GP or motocross? A live run in order with track position,rider names and lap times etc? I wouldn't know where to even begin with this sort of thing, just wondered if you guys have brushed over this in the past and what your thoughts and problems with it were. Cheers mate.
Quote from: gdubmx on April 08, 2016, 12:15:53 PM
Hey MaX, have you guys over on gpb came up with anytype of replay overlay like you'd see in moto GP or motocross? A live run in order with track position,rider names and lap times etc? I wouldn't know where to even begin with this sort of thing, just wondered if you guys have brushed over this in the past and what your thoughts and problems with it were. Cheers mate.
You mean an overlay while spectating or an overlay while watching a saved replay ?
If it's the 1st one (overlay while spectating) it is surely doable thanks to changes PiBoSo has done to the plugin interface (after we requested the changes to do exactly this kind of things). So yes, it's in my todo list, likely the next thing I'll tackle. To be honest I'd like to wait for the next release of KRP to come out, as my plugin deals with all sims (GPB, MXB, WRS, KRP) and having the sims aligned interms of plugin interface makes my life a tad easier.
About where to start for this kind of things: you need to speak C/C++ and have some basic knowledge about programming. Nothing more.
This sounds great.
Quote from: HornetMaX on April 08, 2016, 12:38:09 PM
Quote from: gdubmx on April 08, 2016, 12:15:53 PM
Hey MaX, have you guys over on gpb came up with anytype of replay overlay like you'd see in moto GP or motocross? A live run in order with track position,rider names and lap times etc? I wouldn't know where to even begin with this sort of thing, just wondered if you guys have brushed over this in the past and what your thoughts and problems with it were. Cheers mate.
You mean an overlay while spectating or an overlay while watching a saved replay ?
If it's the 1st one (overlay while spectating) it is surely doable thanks to changes PiBoSo has done to the plugin interface (after we requested the changes to do exactly this kind of things). So yes, it's in my todo list, likely the next thing I'll tackle. To be honest I'd like to wait for the next release of KRP to come out, as my plugin deals with all sims (GPB, MXB, WRS, KRP) and having the sims aligned interms of plugin interface makes my life a tad easier.
About where to start for this kind of things: you need to speak C/C++ and have some basic knowledge about programming. Nothing more.
Plugins should receive data even with a loaded replay.
Quote from: PiBoSo on April 08, 2016, 01:59:54 PM
Plugins should receive data even with a loaded replay.
I know, just not all the data.
Last time I checked at least, some callbacks were not effective during "offline" replay (e.g. EventInit, TrackCenterline, etc).
To be honest, I didn't check in the very latest betas (GPB b8 and MXB b4), as I don't really see the need for this kind of overlay in "offline" replay mode. But if it supported, I'll do it.
Quote from: HornetMaX on April 08, 2016, 12:38:09 PM
Quote from: gdubmx on April 08, 2016, 12:15:53 PM
Hey MaX, have you guys over on gpb came up with anytype of replay overlay like you'd see in moto GP or motocross? A live run in order with track position,rider names and lap times etc? I wouldn't know where to even begin with this sort of thing, just wondered if you guys have brushed over this in the past and what your thoughts and problems with it were. Cheers mate.
You mean an overlay while spectating or an overlay while watching a saved replay ?
If it's the 1st one (overlay while spectating) it is surely doable thanks to changes PiBoSo has done to the plugin interface (after we requested the changes to do exactly this kind of things). So yes, it's in my todo list, likely the next thing I'll tackle. To be honest I'd like to wait for the next release of KRP to come out, as my plugin deals with all sims (GPB, MXB, WRS, KRP) and having the sims aligned interms of plugin interface makes my life a tad easier.
About where to start for this kind of things: you need to speak C/C++ and have some basic knowledge about programming. Nothing more.
Thanks mate the spectator overlay is exactly what I was on about, sounds brilliant. Is it something that could be attached to replays also? I have no idea at all when It comes to programming or code, I can however make some mean enchiladas :)
Edit. My post was a bit delayed with the 4g area I'm in, that sounds promising Max. Look forward to tracking your progression mate.
Quote from: gdubmx on April 08, 2016, 02:38:46 PM
Thanks mate the spectator overlay is exactly what I was on about, sounds brilliant. Is it something that could be attached to replays also? I have no idea at all when It comes to programming or code, I can however make some mean enchiladas :)
I've coded for less and I happen to like enchiladas, so a deal is definitely possible :)
I'll take some of those enchiladas please :D
Haha man I love enchiladas, with fresh lime and the BEST hot sauce in the world..Cholula. mmm, well fats and Max if you guys are ever in my part of the world you are more the welcome to stop by for an ice cold corona with lime and enchiladas :) but back to the replay/spectator overlay, ive seen this is several games, more noticeably though was on a vrc pro live race on YouTube. Nice colours and animations just like a real TV broadcast. I'd love to help in anyway just let me know what I could do, whether it be colour scheming or sitting and typing a load of names and numbers out. Really look forward to this, this would take our sims to another level.
@gdubmix: I'll skip the corona (gosh guys, how can you drink that stuff ? I can't figure out how they are even allowed to call it beer) but I'm all in for the enchiladas. Offer noted down, even if my stint in Scotland has not impressed me too much so chances I'll fly by your place are thin. But who knows :)
More seriously, if you have a video that showcases what you'd like in terms of overlay, please send.
haha man i bet your an ale drinker eh?;) will look forward to it mate, yeah scotland... :-X
here's the classic running order, not like todays one. which is fine but i think the pre 14' one is better myself.
(https://i.gyazo.com/0032e03b2ff4bfd3b37cd210422cc104.png)
check your pm's Max. :D
@gdubmx: OK, I see. I'd like to start with something simpler. A static display with positions and time gaps for the first 3 riders + yourself and the one immediately before/after you.
Then I coul dmove to rolling strings but I'd need some info from Piboso about font creation (http://forum.piboso.com/index.php?topic=3161.0 (http://forum.piboso.com/index.php?topic=3161.0)) in order to have proper rolling strings.
I'm seeing big black bars everywhere...
Nevermind, my fault.
Quote from: HornetMaX on April 09, 2016, 06:48:59 PM
@gdubmx: OK, I see. I'd like to start with something simpler. A static display with positions and time gaps for the first 3 riders + yourself and the one immediately before/after you.
Then I coul dmove to rolling strings but I'd need some info from Piboso about font creation (http://forum.piboso.com/index.php?topic=3161.0 (http://forum.piboso.com/index.php?topic=3161.0)) in order to have proper rolling strings.
sounds awesome MaX, look forward to seeing it mate.
First time I've used maxhud and what a great little feature this is. Thanks Max. Nice work
Quote from: gdubmx on June 01, 2016, 12:54:33 PM
First time I've used maxhud and what a great little feature this is. Thanks Max. Nice work
First time? Wow I thought you had it all along. When I reinstalled MXB I felt naked without it. Can't live without my rumble, or timing, or speedo, or radar online.. And occasionally helmet.. It adds so much. ;D
Yeah man, a virgin! What exactly does the radar do? Also so I need xinput to gdt rumble to work? I would love a sit/stand indicator though. I know you can tell but a small visual hud like the gear counter would be cool. How's things coming along with the replay overlay Max?
Quote from: gdubmx on June 01, 2016, 01:44:09 PM
Yeah man, a virgin! What exactly does the radar do?
It shows the riders that are close to you (like in the blind spot). Mostly useful when riding in 1st person POV.
Quote from: gdubmx on June 01, 2016, 01:44:09 PM
Also so I need xinput to gdt rumble to work? I would love a sit/stand indicator though.
Yes, xinput needed (better to have it anyway, for other reasons). I even think it will come by default with GPB/MXB/WRS/KRP in the future releases.
I don't have the sit/stand info passed by MXB, so I can't show it.
Quote from: gdubmx on June 01, 2016, 01:44:09 PM
How's things coming along with the replay overlay Max?
In progress. The track map now works also when spectating (useful when live-streaming for example) and I've almost finished a small widget showing the standings and gaps (both while riding and while spectating).
Sounds great!
Sounds great MaX!
The radar is perfect when racing, especially the edge of screen indicators.
awesome max! are we able to see a preview of the overlay in action? also so you have made a sit/stand indicator, just needs to be approved by Piboso? thanks mate
Quote from: gdubmx on June 02, 2016, 08:46:49 PM
awesome max! are we able to see a preview of the overlay in action?
Nope. But I'll ship something soon (I'd say in 2 weeks).
Quote from: gdubmx on June 02, 2016, 08:46:49 PM
also so you have made a sit/stand indicator, just needs to be approved by Piboso? thanks mate
No: as the game does not pass the sit/stand status to the plugin, I can't do it.
awesome thanks mate. look forward to it.
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.
Great job MaX thank you! Looking forward to trying this out next race :)
V2.0.2 (2016/08/22) out:
- HUDLean: steering line added back again.
- Added option to hide/show background to widgets that were missing it.
- Fixed nasty bug in HUDMap.
- HUDSpeed now also work sin replay (both live and saved).
- HUDSpeed now also shows throttle and brake (brake won't show in live/saved replays as not passed by the sim).
- Random fixes here and there.
Thanks for all the hard work as always MaX!
IMPORTANT: v2.0.2 has a bug that will make MXB crash when you load saved replays straight after having started MXB (thank sto Midbeck fo rfinding tis: http://forum.mx-bikes.com/index.php?topic=1269.msg18647#msg18647 (http://forum.mx-bikes.com/index.php?topic=1269.msg18647#msg18647)).
I've made a quick patch (v2.0.2b-MXB_ONLY) available at the usual Mega download link: loading a replay right after having started MXB should no longer crash (but you won't have any widget on screen). It still suffer from an MXb bug (that should be fixed in beta5): if you go to track (testing/racing) then back to main menu and load a saved replay, you'll have 3 widgets. HUDSpeed (ok) but also HUDStandings and HUDMap (with wrong track).
All should be fine once MXB b5 is out.
Great quick fix Max! Thanks for all the work :)
just to clarify Fats, this is not the tv overlay mate. its just a live delta.
Ah crap.. Yeah MaX just posted in the other thread. Sorry!
Quote from: gdubmx on September 22, 2016, 09:16:14 PM
just to clarify Fats, this is not the tv overlay mate. its just a live delta.
What do you mean exactly with tv overlay ?
I was under the impression it displayed who is in what position and what the gaps are, but as I've said I've not tried it out yet..
Maybe gdub is referring to the formatting?
Yeah I mean a TV overlay like we discussed earlier on this year Max. Remember I sent you some sample pics and you were going to have a go at coding a live TV overlay.
Hey Max, got a problem with my max hud mate.
I reformatted my comp and installed mxb, and the maxhud. (updated all drivers so far and downloaded the c++ pack ) but it still doesnt work when i press caps.
it worked before i formatted? any ideas mate? cheers
Quote from: gdubmx on September 30, 2016, 12:04:55 AM
Hey Max, got a problem with my max hud mate.
I reformatted my comp and installed mxb, and the maxhud. (updated all drivers so far and downloaded the c++ pack ) but it still doesnt work when i press caps.
it worked before i formatted? any ideas mate? cheers
Check the 1st message of the thread (or the .pdf manual): most likely you miss the MS Visual C++ 2015 x86 Redistributable, just install it.
haha stupid mistake!!! i kept choosing the 64 bit version! works perfect now. cheers mate
This is amazing. :D I downloadeed it so I could have gear indicator in first person but i don't even use it. Fell in love with the helmet and rumble! Thanks Max!
Quote from: osmeralda on November 26, 2016, 01:07:31 PM
This is amazing. :D I downloadeed it so I could have gear indicator in first person but i don't even use it. Fell in love with the helmet and rumble! Thanks Max!
FYI you can enable the gear indicator in first person via Settings>Simulation>Cockpit View section>Show HUD :)
Hey MaX, I know it's the holidays so not trying to pester, but have you got plans to release a compatible MaXhud for b5? Really missing it :)
Quote from: TFC on December 28, 2016, 10:19:47 PM
Hey MaX, I know it's the holidays so not trying to pester, but have you got plans to release a compatible MaXhud for b5? Really missing it :)
It's baking :)
Slowly, as I was up in the mountains (back now) and as I have one annoying Heisenbug (https://en.wikipedia.org/wiki/Heisenbug (https://en.wikipedia.org/wiki/Heisenbug)).
Awesome ;) well good luck, I did see the posts on the pib board about the fonts, looking forward to it :)
Quote from: geofanatec on December 29, 2016, 03:11:00 AM
Hope you made a more suitable seat/stand indicator :)
I can't (the plugin doesn't know when the rider is sitting/standing) and I wouldn't anyway, now that the indicator is implemented in MXB. Just a matter of fixing the MXB one (shouldn't be hard to find the appropriate .tga files and recolor them).
Quote from: TFC on December 29, 2016, 09:10:31 AM
Awesome ;) well good luck, I did see the posts on the pib board about the fonts, looking forward to it :)
Yeah, I've made the fonts used by the plugin configurable.
Now that I can use a monospaced font, I can eventually think about having "rolling text" on screen. Low-priority though.
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.
Thanks MaX, looking forward to trying this later!
like always well done Max, but there is a little bug. :/ There is no option to turn off the Lean Indicator
v2.05b (2016/12/30) out:
- HUDLean not showing in menu :-[ (reported by philiaN).
one more :/ i cant turn off/(on) the general (complete hud)
**can someone check this too?
Quote from: philiaN on December 30, 2016, 08:59:35 PM
one more :/ i cant turn off/(on) the general (complete hud)
That's normal, albeit admittedly a bit surprising. I will avoid displaying the on/off button, to make this clear.
There's no option to turn it off completely, but I was pondering having an option (under "General) to switch between two configurations: one configuration would be the entire set of parameters of each widget (on/off status, position, all the other options).
This could be useful (for example) to have a setup for 3rd person view and one for 1st person, or one for riding and one for spectating/streaming, or one for joking around and one for racing etc.
it wasnt a big deal for me, just thought that it was possible in b4 :)
btw. what do you need to improve the standings? more updates are needed for this. is it possible to get these informations by the checkpoints?
Quote from: philiaN on December 30, 2016, 09:41:07 PM
it wasnt a big deal for me, just thought that it was possible in b4 :)
In beta4 there was no "General" option in the plugin, so it definitely was not possible :)
Quote from: philiaN on December 30, 2016, 09:41:07 PM
btw. what do you need to improve the standings? more updates are needed for this. is it possible to get these informations by the checkpoints?
They are updated when a rider crosses the finish line. That's decided by MXB.
I could put in place something that updates it in a more timely fashion (i.e. when a rider overtakes another), but it's a bit messy and I'd need to drop the gaps (time between riders).
Quote from: HornetMaX on December 29, 2016, 10:03:05 AM
Quote from: geofanatec on December 29, 2016, 03:11:00 AM
Hope you made a more suitable seat/stand indicator :)
I can't (the plugin doesn't know when the rider is sitting/standing) and I wouldn't anyway, now that the indicator is implemented in MXB. Just a matter of fixing the MXB one (shouldn't be hard to find the appropriate .tga files and recolor them).
If you look into misc.pkz you'll find "helpers/riderstand.tga", that's the .tga for the seat/stand indicator.
So basically go into your MXB folder, create a "misc/helpers" folder and put your own riderstand.tga in it.
Actually tried this for the first time, great tool. I'll keep it on for the Rumble and the Map, and use suspension Tools to help with setups.
If I may suggest two things:
- Rumble: could we get higher values for the min g force to trigger the rumble? 0.5g is low for MXB, i'd like to see this extended (like0.5; 0.75; 1; 1.5; 2 or Something).
- Suspensions: I'm guessing we can't get that in Replay otherwise you'd have it in already. So to make it flashier to read during gameplay, think you could add color codes (possibly with settings alongside?) Like first 50% is green background, 50-80 yellow; 80-100 red for each side?
Thanks a lot :)
Quote from: Asdrael on January 24, 2017, 11:31:43 AM
Actually tried this for the first time, great tool.
Took you a while ;)
Quote from: Asdrael on January 24, 2017, 11:31:43 AM
If I may suggest two things:
- Rumble: could we get higher values for the min g force to trigger the rumble? 0.5g is low for MXB, i'd like to see this extended (like0.5; 0.75; 1; 1.5; 2 or Something).
Let me explain how it works: you take the acceleration vector of the bike, pass it into a high-pass filter (i.e. each component of the 3d vector is low-pass filtered, at 1Hz) and then you take the magnitude of what comes out, let's call this M. Now you have to transform this scalar into a rotational speed signal for the rumble actuator of the joypad (I only use one of the two that are typically present), let's call this S.
The way it's done is that if M is equal to the threshold (e.g. 0.5g) then S is 0 (no rumble), if M is equal (or greater) to 1g then S = 1 (max rotation speed). Anything in between is linear interpolation.
If I allow you to crank the threshold up to 2g, what can I use as high point for the linear interpolation ?
Quote from: Asdrael on January 24, 2017, 11:31:43 AM
- Suspensions: I'm guessing we can't get that in Replay otherwise you'd have it in already. So to make it flashier to read during gameplay, think you could add color codes (possibly with settings alongside?) Like first 50% is green background, 50-80 yellow; 80-100 red for each side?
Hmm ... would it be really usefull ? it will change color very often in MXB, a bit of xmas tree effect.
What about just showing (somehow) when you're bottoming out (or close to) ?
Quote from: HornetMaX on January 24, 2017, 10:03:34 PM
If I allow you to crank the threshold up to 2g, what can I use as high point for the linear interpolation ?
Well, instead of scaling it [threshold - 1g] you could scale it [threshold - X times threshold]. I was under the impression that it was like this already, but tbh I quickly changed to the max threshold.
QuoteHmm ... would it be really usefull ? it will change color very often in MXB, a bit of xmas tree effect.
What about just showing (somehow) when you're bottoming out (or close to) ?
I'd be fine with simply a color when at 10% or less. Just to explain: I was trying to figure out when and how hard I was bottoming out on a track. Watching image per image replay gets tiring fast, and riding hard and trying to watch the indicator at the same time is difficult. I should try your telemetry tool, but I feel that's overkill :p
Quote from: Asdrael on January 24, 2017, 10:14:26 PM
Quote from: HornetMaX on January 24, 2017, 10:03:34 PM
If I allow you to crank the threshold up to 2g, what can I use as high point for the linear interpolation ?
Well, instead of scaling it [threshold - 1g] you could scale it [threshold - X times threshold]. I was under the impression that it was like this already, but tbh I quickly changed to the max threshold.
Honestly, I didn't do any tuning for MXB so yeah, it may not be very good.
I had a 2min test and with the threshold at 0.5g it already vibrates not that much ... if I put it at 2g it will vibrate extremely rarely (just a guesstimate, I'll try).
Quote from: Asdrael on January 24, 2017, 10:14:26 PM
I'd be fine with simply a color when at 10% or less. Just to explain: I was trying to figure out when and how hard I was bottoming out on a track. Watching image per image replay gets tiring fast, and riding hard and trying to watch the indicator at the same time is difficult. I should try your telemetry tool, but I feel that's overkill :p
I'll try to do something to highlight when bottoming.
That's great thanks.
The 0.5g setting is fine (albeit still a bit sensitive) for MX. In SX though, it's vibrating almost non stop, even in the berms. 2g will be too high most likely, buta good way to know when it's bottoming out :p
Thanks for all!
Quote from: Asdrael on January 24, 2017, 10:34:34 PM
That's great thanks.
The 0.5g setting is fine (albeit still a bit sensitive) for MX. In SX though, it's vibrating almost non stop, even in the berms. 2g will be too high most likely, buta good way to know when it's bottoming out :p
Well, knowing when bottoming out is not the intended usage of the rumble.
We've had a similar discussion on GPB when I first put the rumble feature out: some were very willing to have the thing vibrate when you lock the front wheel (or rear wheel).
I don't like the idea: it's some sort of artificial help (even if it compensates partially for the fact you're not sitting on the real bike).
Right now it vibrates "when the bike vibrates".
Which SX track can I test it on ? (I suck at MXB in general and at SX in particular).
To be honest, bottoming out a fork in MX can hurt. A lot. The thing is - when you bottom out hard, the g forces of the landing are transfered into your wrist and stop being dampened by the fork. Which is, imo, different from locking a wheel (which actually feels like a moderate decrease in g forces but that's beside the point).
If you want to test, try JS7 South. It's the most mellow of the SX tracks, yet it vibrates for example on the SX triple and when railing the berm after it.
Quote from: Asdrael on January 25, 2017, 12:31:55 PM
To be honest, bottoming out a fork in MX can hurt. A lot. The thing is - when you bottom out hard, the g forces of the landing are transfered into your wrist and stop being dampened by the fork.
No doubt it can hurt, of course. But no doubt either that you can feel vibrations simply running over 5cm berms.
I would be against alowing it to rumble for one and not for the other.
Quote from: Asdrael on January 25, 2017, 12:31:55 PM
If you want to test, try JS7 South. It's the most mellow of the SX tracks, yet it vibrates for example on the SX triple and when railing the berm after it.
OK will do.
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.
Thanks MaX, looking forward to trying out the new rumble :)
Quote from: TFC on February 16, 2017, 10:04:18 PM
Thanks MaX, looking forward to trying out the new rumble :)
Din't play too much with the new settings. Let me know if they fare better than the previous ones (asdrael in particular had some grievance on SX tracks).
Sounds awesome. I'll give it a proper spin later tonight and let you know, thanks for the work on that !
Awesome work Max. Solves my issues with it. Just need to fiddle around a bit to find my settings but so far I'm enjoying not getting a massive rumble each time I take a berm. Ramps up much better now it seems. Using [0.5-4] x 50% right now as a basis and it's more subtle. Actually gives you a sensory feedback when you are pushing it too. Great! Thanks again!
Cool. Let me know if you think something needs to be tunes (e.g. lower/higher ranges for the parameters).
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.
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.
Quote from: HornetMaX on March 16, 2017, 07:58:33 PM
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.
Much love, very sex.
v2.0.7b out (2017/03/17):
- Fix for invalid laps (KRP and MXB only, no change for GPB and WRS).
Thanks MaX..
Just joined a server and had to quit straight away to download this. I know I've said it before but I can't play MXB without MaxHUD lol :)
Quote from: Asdrael on January 24, 2017, 11:31:43 AM
- Suspensions: I'm guessing we can't get that in Replay otherwise you'd have it in already. So to make it flashier to read during gameplay, think you could add color codes (possibly with settings alongside?) Like first 50% is green background, 50-80 yellow; 80-100 red for each side?
@Asdrael: I gave this a quick try, no joy.
I had something that is green when in range 20% - 80% of suspension length, then quickly turns red outside that range (tanh power !!).
Problem is that when you bottom out, the line I draw is very short (zero length when suspension is fully compressed), so the color-coding has little visual effect (no, really ? :) ).
What I could do is to add an additional symbol (e.g. a red square or circle) at the base of the suspension topping out (and no color coding of the drawn suspension).
As topping out is a short-lived event, I probably need to temporise the warning a bit (e.g. when you bottom out, I can show the warning and let it on screen for let's say 1 sec).
Thoughts ?
Thanks for the update
Your solution sounds good and is pretty intuitive. That's how clipping a track is shown when mixing audio. Clip - red warning that stays on for a bit (or until you click it off). I'd say 2s is plenty in our case.
Quote from: Asdrael on March 19, 2017, 10:38:36 PM
Your solution sounds good and is pretty intuitive. That's how clipping a track is shown when mixing audio. Clip - red warning that stays on for a bit (or until you click it off). I'd say 2s is plenty in our case.
Just did this:
(http://i.imgur.com/wD0NRD7.jpg)
Warning stays on for 2 secs, threshold for warning can be configured 5-10-15-20-25%.
Awesome :) Add a 0% in the mix (or 0.1% if you can't have a 0 in your formula) and it's perfect. Thanks a lot!
Done. Will be in next release.
I have a bug Max if i use the Joypad function the game micro stutters, if i turn it off it stops.
Quote from: GDUBMX on March 26, 2017, 05:11:34 PM
I have a bug Max if i use the Joypad function the game micro stutters, if i turn it off it stops.
Hmm weird, never noticed something similar ... more details ?
That's pretty much it mate to be honest, however I did have Rumble on at the same time. I'll try joypad on its own and see what happens mate.
If I have the joypad hud on the game micro stutters not like screen tearing, more like cpu throttling or something.. It's pretty odd
Windows 10 pro 64bit
Intel i5 4690k at 4.3ghz
16gb ram
Msi gtx 1060 6gb
Asus sabertooth mk2 z97 mobo
Ssd
Water cooled etc
Weird, just tried here (v2.0.7b) no issue.
Also, the code of HUDJoystick hasn't changed in a while, so it's a bit surprising ... at least v2.0.6 had exactly the same code.
Only thing I can try is to send you some sort of beta of the next version and you tell me if the problem is still there (in the next version there are some minor changes to HUDJoystick but they are just cosmetic ones, I don't expect them to make any difference).
Quote from: Asdrael on March 20, 2017, 10:03:28 PM
Awesome :) Add a 0% in the mix (or 0.1% if you can't have a 0 in your formula) and it's perfect. Thanks a lot!
On second thought, I'll make the min threshold equal to 1%. If the value if too small (or exactly 0%) then there's a higher risk to not detecting (due to sampling @50Hz).
@GDUBMX: any news ? Issue still there ? Can anybody else confirm ?
I don't have that particular issue, however, I sometime randomly have stuff not willing to show. I have to turn the panel in question off and on again to usually fix it. I have up to date stuff to, including the redis.
Quote from: HornetMaX on March 28, 2017, 01:30:26 PM
@GDUBMX: any news ? Issue still there ? Can anybody else confirm ?
Yep issue still there mate, every bike, every track with or without other elements. It's definitely a micro stutters like cpu throttling, only ever so slightly. The novice/casual pc user wouldn't even notice I doubt but as an enthusiast and builder it bugs the crap out of me! Haha. Do you want a comparison video mate?
Quote from: Asdrael on March 28, 2017, 01:54:42 PM
I don't have that particular issue, however, I sometime randomly have stuff not willing to show. I have to turn the panel in question off and on again to usually fix it. I have up to date stuff to, including the redis.
When it happens, screenshot and short description and I can have a look.
Quote from: GDUBMX on March 28, 2017, 02:39:23 PM
Yep issue still there mate, every bike, every track with or without other elements. It's definitely a micro stutters like cpu throttling, only ever so slightly. The novice/casual pc user wouldn't even notice I doubt but as an enthusiast and builder it bugs the crap out of me! Haha. Do you want a comparison video mate?
Yes, video if you can (but I don't know if it will be visible in the video). As an alternative, you could use software that logs fps (MSi afterburner allows this, surely others too) and do one lap with/without the offending widget activated. You can also PM/email me your MaxHUD.ini (and MaxHUD.log, if it is created).
Random questions:
- Which widgets do you normaly have ON ?
- Does the micro stuttering happen with other widgets (e.g. HUDMap surely eats up more than HUDJoypad) ? Or is it only HUDJoypad ?
P.S.
Normally I'm pretty sensitive to stuttering: I have a 120Hz screen and literally hate wild fps variations.
I only have Rumble and standings on, as I mentioned above even with the other elements switched off there is still a stutter. And as stated in a previous post this is not a vsync issue and I don't drop and frames. It's not a deal breaker as I don't really use that element anyway I was just testing.
Quote from: GDUBMX on March 28, 2017, 06:40:16 PM
I only have Rumble and standings on, as I mentioned above even with the other elements switched off there is still a stutter. And as stated in a previous post this is not a vsync issue and I don't drop and frames. It's not a deal breaker as I don't really use that element anyway I was just testing.
OK. But I was more after a different info.
You said that standings ON, joypad OFF works fine while standings ON joypad ON stutters.
Question: does it stutter with joypad OFF and any other widget/widget combo ON ?
E.g. Joypad OFF + all other widgets ON = stutter or not ? And setting Joypad ON (so all ON) ?
This is just a try to figure out if the problem is localised in the HUDJoypad widget code or not.
Quote from: HornetMaX on March 28, 2017, 09:29:22 PM
Quote from: GDUBMX on March 28, 2017, 06:40:16 PM
I only have Rumble and standings on, as I mentioned above even with the other elements switched off there is still a stutter. And as stated in a previous post this is not a vsync issue and I don't drop and frames. It's not a deal breaker as I don't really use that element anyway I was just testing.
OK. But I was more after a different info.
You said that standings ON, joypad OFF works fine while standings ON joypad ON stutters.
Question: does it stutter with joypad OFF and any other widget/widget combo ON ?
E.g. Joypad OFF + all other widgets ON = stutter or not ? And setting Joypad ON (so all ON) ?
This is just a try to figure out if the problem is localised in the HUDJoypad widget code or not.
Haha we'll get there mate.. :)
This is what I try to use every session:
Stutters with joypad on
Stutters with joypad on and standings on
Stutters with joypad, standings and Rumble on
Only stutters when joypad is on and that's it. Everything else works fine without joypad on.
If I attempt to use anything with joypad it stutters. Keep everything on and turn joypad off, stutters goes away.
Weird weird weird ... can you send me the .ini and the .log ?
https://www.youtube.com/v/TV7NHye8ggc
Youtubes bad compression may make it difficult but you can see it.
If you look carefully, when joypad is on and im turning if you look at those toyota tough blocks they jolt to the left over and over. Once off, everything is smooth. 60FPS while recording, no drops at all.
log:
MaxHUD v2.0.7b - 29 Mar 2017, 08:54:47
@Startup - 29 Mar 2017, 08:54:47
Game = MXB
szSave path = C:\Users\Tortu\Documents\PiBoSo\MX Bikes\
Save path = C:\Users\Tortu\Documents\PiBoSo\MX Bikes\
Data path = C:\Program Files (x86)\MX Bikes\plugins\MaxHUD_data\
Ini file = C:\Users\Tortu\Documents\PiBoSo\MX Bikes\MaxHUD.ini
Log file = C:\Users\Tortu\Documents\PiBoSo\MX Bikes\MaxHUD.log
Log level = 2
Sprites / Fonts : 21 / 5 (2f + 3v)
Widget creation ...
LiveGapBase done !
LiveGapBase done !
Helmet done !
Timing done !
LiveGapBar done !
Speed done !
Fuel done !
Map done !
Radar done !
Standings done !
Inputs done !
Joypad done !
Rumble done !
Suspensions done !
Lean done !
General done !
@END Startup
@RaceEvent - 08:55:00
@END RaceEvent
@RaceAddEntry - 29 Mar 2017, 08:55:14
@END RaceAddEntry
@EventInit - 29 Mar 2017, 08:55:14
@END EventInit
@TrackCenterLine - 29 Mar 2017, 08:55:14
Segs = 26 (11S + 15A), 914.87m
FL = 11.50, ST = 0.00
S0 = 316.39
S1 = 621.28
HUDMap ACL segs = 101
@END TrackCenterLine
@RaceSession - 29 Mar 2017, 08:55:14
@END RaceSession
@RaceAddEntry - 29 Mar 2017, 08:55:14
@END RaceAddEntry
@RaceCommunication = 29 Mar 2017, 08:55:14
@END RaceCommunication
@RunInit - 29 Mar 2017, 08:59:46
@END RunInit
@RunStart - 29 Mar 2017, 08:59:46
@END RunStart
@RaceVehicleData: new iRaceNum = 84
@Draw: new iDrawState = 0
@RunSplit - 29 Mar 2017, 09:04:32
@END RunSplit
@RunSplit - 29 Mar 2017, 09:04:59
@END RunSplit
@RunLap - 29 Mar 2017, 09:05:31
@END RunLap
@RunStop - 29 Mar 2017, 09:05:38
@END RunStop
@RunStop - 29 Mar 2017, 09:05:43
@END RunStop
@RunStart - 29 Mar 2017, 09:05:44
@END RunStart
@RunStop - 29 Mar 2017, 09:06:20
@END RunStop
@RunStop - 29 Mar 2017, 09:08:05
@END RunStop
@RunDeinit - 29 Mar 2017, 09:08:09
@END RunDeinit
@EventDeinit - 29 Mar 2017, 09:08:11
@END EventDeinit
@RaceDeinit - 09:08:11
@END RaceDeinit
@Shutdown - 29 Mar 2017, 09:08:18
@END Shutdown
.ini
[MaxHUD]
_ini_version=2
active=1
sample_rate=50
notify_events=0
log_level=2
[HUDGeneral]
_ini_version=1
_pos_x={0.200000,0.200000,0.200000}
_pos_Y={0.200000,0.200000,0.200000}
_pos_linked=1
_optlinked=1023
_profile=0
font_fixed={0,0,0}
font_variable={2,2,2}
[HUDHelmet]
_ini_version=1
_enabled={0,1,1}
_optlinked=1023
show_helmet={1,1,1}
top_offset={0,0,0}
bottom_offset={0,0,0}
visor_color={0,0,0}
visor_shade={1,1,1}
vibrate={1,1,1}
helmet_rotation={0,0,0}
helmet_rotation_factor={4,4,4}
helmet_rotation_inverse={0,0,0}
[HUDTiming]
_ini_version=1
_enabled={0,1,1}
_pos_x={-0.157639,-0.157639,-0.157639}
_pos_Y={0.223148,0.223148,0.223148}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
_color_light=[255,230,230,230]
_color_dark=[255,140,140,140]
_color_fast=[255,0,128,0]
_color_slow=[255,0,0,128]
size={1,1,1}
mode={1,1,1}
split_hold={2,2,2}
show_background={1,1,1}
[HUDLiveGapBar]
_ini_version=1
_enabled={0,1,1}
_pos_x={0.233333,0.233333,0.233333}
_pos_Y={0.000000,0.000000,0.000000}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
_color_bar_slow=[150,0,0,128]
_color_bar_neutral=[150,230,230,230]
_color_bar_fast=[150,0,128,0]
_color_text_slow=[255,0,0,128]
_color_text_neutral=[255,230,230,230]
_color_text_fast=[255,0,128,0]
size={1,1,1}
bar_scale={2,2,2}
split_hold={2,2,2}
downsample={0,0,0}
show_background={1,1,1}
[HUDSpeed]
_ini_version=1
_enabled={0,1,1}
_pos_x={0.420000,0.420000,0.420000}
_pos_Y={0.170000,0.170000,0.170000}
_pos_linked=1
_optlinked=1023
_color_lowrpm=[150,0,0,0]
_color_highrpm1=[150,0,128,205]
_color_highrpm2=[150,0,0,128]
_color_back=[255,140,170,180]
size={1,1,1}
use_miles={0,0,0}
hide_speed={0,0,0}
show_thrbrk={1,1,1}
show_background={0,0,0}
[HUDFuel]
_ini_version=1
_enabled={0,1,1}
_pos_x={0.910667,0.910667,0.910667}
_pos_Y={0.050000,0.050000,0.050000}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
_color_light=[255,230,230,230]
_color_dark=[255,140,140,140]
size={1,1,1}
show_background={1,1,1}
[HUDMap]
_ini_version=1
_enabled={0,1,1}
_pos_x={0.866667,0.866667,0.866667}
_pos_Y={0.200000,0.200000,0.200000}
_pos_linked=1
_optlinked=1023
_color_track=[255,128,0,0]
_color_back=[200,0,0,0]
size={1,1,1}
rotate={0,0,0}
range={0,0,0}
show_racenums={1,1,1}
show_range={1,1,1}
show_background={1,1,1}
[HUDRadar]
_ini_version=1
_enabled={0,1,1}
_pos_x={0.033333,0.033333,0.033333}
_pos_Y={0.400000,0.400000,0.400000}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
_color_marker_far=[0,0,200,200]
_color_marker_near=[255,0,0,128]
size={1,1,1}
mode={2,2,2}
range={4,4,4}
markers_size={1,1,1}
markers_fadefov={0,0,0}
show_background={1,1,1}
[HUDStandings]
_ini_version=1
_enabled={0,1,1}
_pos_x={-0.166667,-0.166667,-0.166667}
_pos_Y={0.820000,0.820000,0.820000}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
_color_you=[255,0,200,200]
_color_others=[255,230,230,230]
_color_ahead=[255,0,0,128]
_color_behind=[255,0,128,0]
size={0,0,0}
gaps={0,0,0}
show_names={0,0,0}
show_background={0,0,0}
[HUDInputs]
_ini_version=1
_enabled={0,1,1}
_pos_x={0.033333,0.033333,0.033333}
_pos_Y={0.740000,0.740000,0.740000}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
size={1,1,1}
input_device={0,0,0}
steering_axis={0,0,0}
steering_angle_scale={4,4,4}
show_background={1,1,1}
[HUDJoypad]
_ini_version=1
_enabled={0,1,1}
_pos_x={1.058667,1.058667,1.058667}
_pos_Y={0.928000,0.928000,0.928000}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
_color_front=[150,180,180,180]
_color_dots=[255,128,0,0]
size={0,0,0}
input_device={1,1,1}
stick1_hor={0,0,0}
stick1_ver={3,3,3}
stick2_hor={8,8,8}
stick2_ver={7,7,7}
trigger_1={4,4,4}
trigger_2={5,5,5}
show_values={0,0,0}
show_background={1,1,1}
[HUDRumble]
_ini_version=1
_enabled={0,1,1}
_optlinked=1023
xinput_device={0,0,0}
rumble_strength={4,4,4}
rumble_threshold={2,2,2}
rumble_range={0,0,0}
rumble_crashed={0,0,0}
[HUDSuspensions]
_ini_version=1
_enabled={0,1,1}
_pos_x={-0.166667,-0.166667,-0.166667}
_pos_Y={0.880000,0.880000,0.880000}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
size={1,1,1}
show_infos={0,0,0}
show_background={1,1,1}
[HUDLean]
_ini_version=1
_enabled={0,1,1}
_pos_x={0.300000,0.300000,0.300000}
_pos_Y={0.775000,0.775000,0.775000}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
_steer_scale=1.000000
_slip_scale=1.000000
size={1,1,1}
show_steer={0,0,0}
show_slip={0,0,0}
show_background={1,1,1}
https://mega.nz/#!8gtGSbqT!Ml7JJE07o_RerKQ883TYBs5HvUdRJoDIbSxJVCquvAg < Packaged
Can't see a lot going on in the video but I seem to be bale to download only the 30fps version, I'll check at home.
I even asked a colleague to do a blind test (look the video and tell if there's stuttering or not, without knowing if the HUDJoypas was active or not): he detected some stutternig, but got it wrong on 2 cases out of 5 (saying there was stuttering when HUDJoypad was off)..
One thing: from your .ini I see that you have configured HUDInputs (that you don't use on-screen) to use your first joypad (index 0) while you have configured HUDJoypad to use your second joupad (index 1).
[HUDInputs]
... ... ...
input_device={0,0,0}
[HUDJoypad]
... ... ...
input_device={1,1,1}
[HUDRumble]
... ... ...
xinput_device={0,0,0}
That's weird, normally you should set the same input device for both widgets.
Also, if you use rumble then it means you have an XInput joypad, so you should set that as input device in both HUDInputs and HUDJoypad.
In the options of each widget you typically have 8 DirectInput joypads (1-8), followed by 4 XInput ones (some may be disconnected).
If you only have a XInput joypad conncted to your PC, use the 1st XInput device as input device for HUDInputs and HUDJoypad.
[You are already doing it for HUDRumble, as it can only see XInput devices and not DirectInput ones.]
You can change this from the menu (that should give "input_device={8,8,8}" in the .ini, I guess, for both HUDInputs and HUDJoypad).
Totally not granted it will make any difference but worth a try.
Sorry mate, I thought I had edited this post. Weird is right, I switched my overclock back to stock speed and the stuttering seems to have gone? Weird I know but I must of had some kind of unstable settings although it blitzed through stress tests and benchmarking no troubles. Either way it's gone for now haha. Will check out those inputs though mate for sure. Thanks for this great app and your support Max. Much appreciated mate
Saw that you are using Watercooling on your setup. I'm guessing CPU and/or GPU. Don't forget that WC those units effectively lowers the airflow within the case, resulting in cooling issues for the RAM and possibly MB chipset(s), as they are usually very near the CPU and benefit from its fan(s). WC is great for OCing the CPU, nice for the GPU (if you have a full block covering chip+memory), but can be an issue for OCing the RAM if not compensated by case fans. I gave up on WC once the new copper blocks started appearing (and one tube link broke on my tank scaring the shit out of me).
Cool. I was about to send you an early version of the next reelase of theplugin just for testing, now you'll have to wait like the others :)
Haha you still can mate :) I'm beta testing about 4 different projects for people at the moment why not make it 5!
Quote from: GDUBMX on March 29, 2017, 04:10:11 PM
Haha you still can mate :) I'm beta testing about 4 different projects for people at the moment why not make it 5!
Yeah ... why not. But still not :)
anyway to change font colour of the standings element max?
Quote from: GDUBMX on April 01, 2017, 09:04:31 PM
anyway to change font colour of the standings element max?
Look in the MaxHUD.ini file, the _color_* stuff.
If you find a nice combo let me know :)
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.
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).
woould this work on beta 8 yet max?
edit: no it didnt
Quote from: GDUBMX on June 16, 2018, 09:09:24 PM
woould this work on beta 8 yet max?
edit: no it didnt
Even less chances than usual, given that beta8 is the 1st beta (across all PiBoSo sims) that is x84 instead of x86.
Good news, I've recompiled everything as it seems to work just fine with really minor changes.
I may push some stuff out in the next days.
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.
Awesome HornetMaX, thanks very much! As usual MXB wasn't the same without my timings :D
Thank you very much.
The vibration of the controller makes MX Bikes very fun. :)
Thanks again for the update!
Just wondering - and sorry if I missed it - how do you calculate the suspensions travel % ? I'm surprised it shows less than 100% even when in the air, and thus wonder if you can go below 0% or something.
Quote from: Asdrael on July 13, 2018, 03:28:37 PM
Thanks again for the update!
Just wondering - and sorry if I missed it - how do you calculate the suspensions travel % ? I'm surprised it shows less than 100% even when in the air, and thus wonder if you can go below 0% or something.
I just normalize the susp length to the susp max travel, hence it should always be 0-100%. Guess only PiBoSo can answer this (why it doesn't reach 100%).
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)
V2.1.2 out(2018/08/29)No changes for GPB, WRS and KRP.
Thanks a lot!
Thanks MaX..
I'm sure enough people use this it's a shame not many have replied and thanked.
One bug I noticed in this latest build - Not sure if it's MXB or MaX hud - If you're riding with rumble on and the session ends taking you to the pit, the rumble doesn't stop and just runs continuously.
Thanks again, I feel naked without it.
Quote from: тғc on September 05, 2018, 08:53:18 PM
Thanks MaX..
I'm sure enough people use this it's a shame not many have replied and thanked.
Thanks !
I'm a lazy dog myself so I can't complain :)
Quote from: тғc on September 05, 2018, 08:53:18 PM
One bug I noticed in this latest build - Not sure if it's MXB or MaX hud - If you're riding with rumble on and the session ends taking you to the pit, the rumble doesn't stop and just runs continuously.
Hmm that definitely shouldn't happen, I'll have look.
Temporary workarounds (bad ones, I know): go to track again and it should stop, or use the .exe that comes with the plugin to stop the rumble (it's included in case MXB crashes while rumbling, happened to me once with GPB and only solution was reboot, hence the .exe).
Thank you for the Plugin! It's incredible and really improves the racing experience
Haven't tried this yet. I should soon. Thanks for the work HornetMax
I'm using it since i first rode about it and actually never thought about saying anything.
But honestly, thanks for that awesome plugin Max! And for the continous support and updates you're bringing to us to actually make it possible to use your awesome piece of code! :)
It's always the same.
New beta. I'm like woohoo new stuff. Play a while, notice the improvement, the pitfalls. Update the OEM pack, play a while.
"Hmmm something is missing".
"Hoh yay THE plugin."
Thanks Max <3
This time I didn't even need to update anything :)
Gotta say, the Rumble is the best part for me (threshold 1, 4 range). With lean help off, it makes it for a lot of gratification when you hit berms hard as hell :p
Quote from: HornetMaX on December 02, 2018, 04:30:23 PM
This time I didn't even need to update anything :)
just your first post, from MX Bikes beta9 to beta10 :p
Quote from: iNsane | WeekendWarriors on December 02, 2018, 04:38:38 PM
Quote from: HornetMaX on December 02, 2018, 04:30:23 PM
This time I didn't even need to update anything :)
just your first post, from MX Bikes beta9 to beta10 :p
Ah right. No free lunch :)
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
MaX, are you planning on updating MaXHUD to the latest beta? I miss it.. :(
The latest version of the game and maxhud work fine for me.
Unfortunately for me it seems like MaXHUD thinks I'm running a higher resolution than I am. Half of it is off the screen and the rumble doesn't work.
Hi,
I had the same problem as you.
Solution: With your mouse, spam left click on the left and right edges of your screen (the mouse leaves the frame, this is no problem) and brings the various elements of the hud where you want, you just have to catch them.
Everything is working.
Sorry for my English google translation.
Quote from: тғc on August 10, 2019, 05:48:41 PMUnfortunately for me it seems like MaXHUD thinks I'm running a higher resolution than I am. Half of it is off the screen and the rumble doesn't work.
Hi all,
yes an update is needed as PiBoSo has done a change in MXB that impcts the screen coordinates.
Sorry I'm a bit late on this: holidays + I no longer receive notifications from PiBoSo forums.
And my adsl box at home has been fried by a storm so it may take another week or two.
Quote from: 74med on August 12, 2019, 08:03:25 PMSolution: With your mouse, spam left click on the left and right edges of your screen (the mouse leaves the frame, this is no problem) and brings the various elements of the hud where you want, you just have to catch them.
Alternative (but annoying) solution: manually editing the MaxHUD.ini file you can see the X and Y position of each widget.
Good to know MaX. Thanks 👍
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.
Thanks MaX :)
its this working for Beta 12 ?
Yes...
Hi Max
1. Do you think you could advance the current standings for replay to this:
(https://i.gyazo.com/6e6570451b27690b7f6c013bf5ae5a0d.jpg)
No worries i dont assume that it is for free, pls pm me for more infos.
2. I can't get in touch with Alibaskins, do you know how i can reach him. It's about the Best Laps Service.
Thanks
Good job dude.
good stuff, thanks dude
Im having trouble getting it to work I downloaded it but there isnt any file labeled "plugins" I went into the game and pressed caps lock to try and get the menu to pop up as the pdf said there must be something obvious im missing if anyone can help
Quote from: onthelow on December 15, 2019, 10:01:25 PMIm having trouble getting it to work I downloaded it but there isnt any file labeled "plugins" I went into the game and pressed caps lock to try and get the menu to pop up as the pdf said there must be something obvious im missing if anyone can help
Go to your program files, not your document files.
That being said, I can't get it to give me a .ini file. I have the
Microsoft Visual C++ 2017 Redistributable Package files but its still not working.
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 !
thank you max! happy new year mate
MaX, I'm having trouble with timing in the latest MXB beta..
I'm not sure it's a MaX hud problem but since MXB doesn't give us a way to view real time timing it's the only thing I can see.
When you cross where the centerline is joined it instantly shows you about -60 or more seconds behind your previous lap. It doesn't do this all the time but I get it all the time on Ironman and on a few other tracks too.
Am I the only one?
Same here Fats, get the same problem on JS7 as Ironman, something's changed game side.
I've had it on stock tracks too.. Washington I think from memory but not every lap. Maybe club too..
Either way, I've been over it with PiBoSo and think he said as far as he can see everything game side is OK.
Quote from: 𝖙𝖋𝖈 on January 03, 2020, 11:17:49 PMMaX, I'm having trouble with timing in the latest MXB beta..
I'm not sure it's a MaX hud problem but since MXB doesn't give us a way to view real time timing it's the only thing I can see.
When you cross where the centerline is joined it instantly shows you about -60 or more seconds behind your previous lap. It doesn't do this all the time but I get it all the time on Ironman and on a few other tracks too.
Am I the only one?
Hmm I'll have to look into that.
There was a change in the output plugin structures that I missed (my bad), back on 19th Oct (so I guess it was for beta12).
Questions:
1- It's a regulat track (no straight ryhtm) right ? I didn't do any change for straight rythm so it may screw up badly.
2- It's only the latest version (2.1.7) ? 2.1.6 doesn't have the problem ?
If you can post a link to the track where it shows more often that would also help.
Nice 1 Max, cheers
1/. Yes happens on normal MX tracks. Happens every lap on Ironman, as soon as you've set a lap and about 5-10 secs after crossing the finish line the timer gives you a 50 odd sec lead that gradually counts down until the last sector I think it is, then you get normal timings in the last sector that match lap times as you cross the line. http://forum.mx-bikes.com/index.php?topic=2894.0 << Track link.
2/. I'm not sure exactly what version I had before today, but downloaded the latest as I didn't seem to have 2.1.7 and installed it, no change for me.
OK. Could you post some screenshots showing the issue ? Just to be sure I understand it correctly.
Also, if it happens on a shorter/easier track that would help too :)
I'm not home but thanks Teeds for that! MaX if nobody has I'll get a short video tonight, unless you check the track and experience the same issue with the gap. It happens specifically on Ironman when you cross the point the centerline was joined.
Just been testing and it isn't linked to the sector at all. I went slower than usual and the timer seems to just count down like i'm standing still and bike speed seems to be unrelated. The timer ran out and gave me normal times way sooner than usual as I was going slowly while taking screen shots.
The screenshots in this pdf are in order top down, you can see the gap I get and bear in mind i'm going way slower than the ghost. The time synced up between page 8 and 9. From page 9 it's normal timings, I can gain and loose time again.
https://sealey.iweb-storage.com/s/IjVlMTBjY2U0MWI0Mjg0Yjg4Y2NlMGM5MSI.eO5iqc3K0xueM6BgcDxAerIPBM0 (https://sealey.iweb-storage.com/s/IjVlMTBjY2U0MWI0Mjg0Yjg4Y2NlMGM5MSI.eO5iqc3K0xueM6BgcDxAerIPBM0)
Thanks teeds and tfc, I think I've seen it happen twice on my side: I'll need to take a look (not sure when though).
Long shot: the track's centerline has non-consecutive sections very close to each others (like a long straight then a tight 180deg u-turn and then another long straight parallel and close to the 1st stright): maybe this confuses my code that tries to determine where you are on the centerline (a float between 0.00 and 1.00) from your actual X-Y position. Just specualting, I don't even remember how I wrote this code :P :P :P
Haha well I hope you can fix it I love MaX hud 😁
I tried rebuilding the centerline with no luck btw.
I had a look and, as far as I can see, the problem is not in my code.
I've found some weird data being passed by MXB to the output plugin: in a nutshell, the "position" of the bike along the centerline (what PiBoSo calls fPos in his plugin interface, a float between 0 and 1) has a very weird jump back (something like you're 1515m down the track and then for a few tenths of sec you go back to 196m and after that you're back to 1919m).
This confused my livetiming (well, no wonder :) ).
I've created a bug post for PiBoSo (here (http://forum.mx-bikes.com/index.php?topic=3143.0)), let's wait for some feedback from him.
P.S.
I haven't received a forum notification (e.g. when somebody posts something in this thread) in ages, so I may not be super reactive answering this (guess it's something like gmail blacklisting the forum for whatever reason).
Thanks for looking at this Max, really appreciated.
Over to Pibs now then I guess.
Thanks for this MaX, hopefully a fix is incoming.
I guess you've seen PiBoSo comment in the bug thread so yeah ... let's wait for the fix.
To be honest I could try to put in place a workaround in my code, but it's such an ugly one I'd prefer to wait for the proper fix from PiBoSo.
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).
Thanks Max!
Awesome, cheers Max.
First of all, thanks for the plugin, pretty useful!
I'm not sure if I have the latest version or if the bug got already reported, but live gap bar on testing keeps running when you pause (press escape). Or not exactly running, it freezes as it should and if you resume, the time you had it paused gets added.
Quote from: JNS47 on March 11, 2020, 07:41:50 PMI'm not sure if I have the latest version or if the bug got already reported, but live gap bar on testing keeps running when you pause (press escape). Or not exactly running, it freezes as it should and if you resume, the time you had it paused gets added.
This comes from the fact that MXB internal timing reported to the plugin has a bug(*): it has been reported a long time ago (years) but it is still unfixed. Due to that, in order to have reliable timing info in the plugin (what is used for the livegap stuff), I use Windows precise timer, which of course is unaware of the game being "paused".
Handling the pause state in the plugin would be a bit messy, so I didn't do it: the plugin livegap stuff will be off if you "pause" (as you reported).
All this won't happen if MXB timing was fixed.
(*)
The MXB (and GPB, RS, KRP) timing problem only affects the timing reported to the output plugin (i.e. the lap times MXB reports are correct). What happens is that the timing info in the calls to RunTelemetry tend to drift over time (multiple laps).
If I recall correctly, the problem may come from the way the integration time steps are summed (due to finite precision).
I think I even provided PiBoSo with a link to a more accurate way to do the summation (in case this was the origin of the issue).
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.
Oooh Max, thank you very much!
Can I make a request for the next release? Would it be possible to disable the helmet if in 3rd person? I frequently change from 1st to 3rd and keep having to turn the helmet on and off.
Thanks again!
Quote from: 𝖙𝖋𝖈 on May 06, 2020, 07:17:07 PMOooh Max, thank you very much!
Can I make a request for the next release? Would it be possible to disable the helmet if in 3rd person? I frequently change from 1st to 3rd and keep having to turn the helmet on and off.
Thanks again!
Hi, no I cannot do that: the plugin has no idea if you're 1st or 3rd person.
But that's why I've created the profiles: you can have (for examples) one for 1st person and one for 3rd person.
It's harder to explain than to use :)
Each profile has the on/off status of each widget. Additionally, you can choose for each widget:
- if its position is the same in each profile or not (the "pin" button)
- if each widget parameter is the same in eah profile or not (the "link" button)
Bottom line: you can have 3 different setups of the widgets and switch between the 3 clicking on the "P1" / helmet button.
Thank you for the update Max !
Quote from: HornetMaX on May 06, 2020, 11:08:39 PMQuote from: 𝖙𝖋𝖈 on May 06, 2020, 07:17:07 PMOooh Max, thank you very much!
Can I make a request for the next release? Would it be possible to disable the helmet if in 3rd person? I frequently change from 1st to 3rd and keep having to turn the helmet on and off.
Thanks again!
Hi, no I cannot do that: the plugin has no idea if you're 1st or 3rd person.
But that's why I've created the profiles: you can have (for examples) one for 1st person and one for 3rd person.
It's harder to explain than to use :)
Each profile has the on/off status of each widget. Additionally, you can choose for each widget:
- if its position is the same in each profile or not (the "pin" button)
- if each widget parameter is the same in eah profile or not (the "link" button)
Bottom line: you can have 3 different setups of the widgets and switch between the 3 clicking on the "P1" / helmet button.
Understood, and appreciate it! I'll set them up :)
Would it be possible to have the live timing go further than 9:59.99 for one lap? I'm wanting to use this for Enduro, where the lap time will be over 1hr
hey Max, while we are testing Erzberg which was the reason MXB got support for +50 Checkpoints, the plugin makes the game laggy as hell.
Someone with AMD setup got 15 fps, I had 30-40. Removing MaxHUD resolved the issue, AMD has 80 fps and I with everything maxed out suddenly have 80-100 fps.
Is this anything you can resolve? I think it's due the amount of CPs. Erzberg has around 400ish.
Quote from: iNsane | WW on July 05, 2020, 09:55:22 PMhey Max, while we are testing Erzberg which was the reason MXB got support for +50 Checkpoints, the plugin makes the game laggy as hell.
Someone with AMD setup got 15 fps, I had 30-40. Removing MaxHUD resolved the issue, AMD has 80 fps and I with everything maxed out suddenly have 80-100 fps.
Is this anything you can resolve? I think it's due the amount of CPs. Erzberg has around 400ish.
Hi, sorry for the delay, I was on vacation (and I don't get any forum notification).
Not sure the number ofd CPs is the cause, the plugin doesn't even see them. Is there a place where I can download the track so that I can have a look ?
P.S.
I've PMed you my email, will be faster to communicate this way.
Here's the track link https://mega.nz/file/bI1TTDpL#u6Q7XDGGNAzLXIDJqGpGY0Nc7ZB9NzVRTS7NA8ChXLE
Info http://forum.mx-bikes.com/index.php?topic=3288.0
Hmm it's 40Km long, that's likely the reason. I'll have a look when I have the time.
Thanks Max :)
Quote from: okwes on July 05, 2020, 03:59:06 PMWould it be possible to have the live timing go further than 9:59.99 for one lap? I'm wanting to use this for Enduro, where the lap time will be over 1hr
Yeah that's easy. Won't look very pretty in cases where one lap/split can be below/above 10min as it will show (example) 9:55.123 (below 10min) and 00h10:45 if above but guess that would be ok.
Quote from: iNsane | WW on July 05, 2020, 09:55:22 PMhey Max, while we are testing Erzberg which was the reason MXB got support for +50 Checkpoints, the plugin makes the game laggy as hell.
Someone with AMD setup got 15 fps, I had 30-40. Removing MaxHUD resolved the issue, AMD has 80 fps and I with everything maxed out suddenly have 80-100 fps.
OK, I had a look, here are my findings.
- On my systems (i5-9600K, RTX 2070 super, 3440x1440, all MXB settings maxed out except AA at 8x) my fps at Kreken (start point) drop from ~170 (no plugin) to ~70 with the plugin. Ouch.
- If I compile the plugin without the HUDMap widget, I get ~160fps so the problem, as expected, is in HUDMap due to the very long and twisty track.
The main reason is that HUDMap takes the track centerline (straights + arcs) and approximates it with straights only: in doing this, the number of centerline segments goes up, e.g. for Kraken the centerline has 1493 segments (469 straights and 1024 arcs) but after approximation I have 7041 straight segments.
Now for each segment I draw 4 quads: 1 rectangle for the "main segment" and 1 wider rectangle wider to have the track borders, plus 1 triangle joining two consecutive rectangles in a turn (and another "wider" triangle for the track border). Bottom line, that makes 28K quads and that maybe too much.
One thing you try immediately is edit the MaxHUD.ini file, find the [HUDMap] section in it. It should be as below:
[HUDMap]
_ini_version=2
_enabled={1,1,1}
_pos_x={0.721875,0.721875,0.721875}
_pos_Y={0.123611,0.123611,0.123611}
_pos_linked=1
_optlinked=1023
_color_back=[200,0,0,0]
_color_track=[255,0,0,0]
_color_trackborder=[255,230,230,230]
_color_me=[150,0,0,200]
_color_others=[150,0,128,205]
size={3,3,3}
rotate={0,0,0}
range={1,1,1}
show_racenums={1,1,1}
show_range={1,1,1}
track_width={5,5,5}
trackborder_width={1,1,1}
show_background={1,1,1}In it, you can add these two lines:
_abserr = 0.500
_relerr = 0.002The above values are the default ones. If I change _relerr to 0.020 (instead of 0.002) I get 120fps (instead of 70) for 3183 centerline segments (instead of 7041) and 12788 quads (instead of 28220). Of course in HUDMap, if you zoom a lot, the turns will be less smooth than before.
Explanations of the two parameters: the plugin needs to decide how many straight segments to use to approximate one arc. It picks the numebr of segs so that the error (distance between the "true" centerline arc and the sequence of approximating segments) is below a value. The value is dictated by the two parameters:
- _abserr is absolute error, in meters (default - 0.5m).
- _relerr is relative error: you multiply it by the arc radius and you get an absolute error (default = 0.002 means that for a turn with a radius of 4 meters, the allowed error is 4 * 0.002 = 8mm).
- The min of the two errors is used.
So you can play with the values, that should help a bit.
On my side I can probaly cut the number of drawn quads by a factor 2, drawing a trapezoid instead of a rectangle + a triangle. That's on my todo list :)
Final word, I really think Piboso should have the HUDMap feature in MXB & co: surely he'd do it 10 times better and in a way more efficient manner.
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).
Thanks for the update!
Thanks for adding longer lap time capabilities!
I'm stuck on the install.
QuoteCopy the MaxHUD_data folder and the relevant .dlo file (e.g. MaxHUD_GPB64.dlo for GPB) to
the game's plugins folder, which is (depending on the game):
● C:\Program Files\GP Bikes\gpbikes\plugins
● C:\Program Files\World Racing Series\wrs\plugins
● C:\Program Files\Kart Racing Pro\plugins
● C:\Program Files\MX Bikes\plugins
The plugin creates a MaxHUD.ini file in the data directory corresponding to the game:
● C:\Users\<Your Windows Username>\Documents\PiBoSo\GP Bikes\
● C:\Users\<Your Windows Username>\Documents\PiBoSo\World Racing Series\
● C:\Users\<Your Windows Username>\Documents\PiBoSo\Kart Racing Pro\
● C:\Users\<Your Windows Username>\Documents\PiBoSo\MX Bikes\
or simply in the game directory if you're using "compatibility mode".
I'm not getting that plugin to show up. I see the redistributable package x64 below, but that install doesn't work for me. Says Setup Failed, another version of this product is already installed and it cannot continue to install the file. What do I need to do?
Quote from: BlizzardDUCK on November 08, 2020, 09:20:49 PMI'm not getting that plugin to show up. I see the redistributable package x64 below, but that install doesn't work for me. Says Setup Failed, another version of this product is already installed and it cannot continue to install the file. What do I need to do?
Try this one: https://aka.ms/vs/16/release/vc_redist.x64.exe (https://aka.ms/vs/16/release/vc_redist.x64.exe)
It's the x64 for 2015, 2017 and 2019 from that page: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads (https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads)
If still won't install, uninstall what you have (2015, 2017, 2019) and install the new one.
Quote from: HornetMaX on November 10, 2020, 05:20:58 PMQuote from: BlizzardDUCK on November 08, 2020, 09:20:49 PMI'm not getting that plugin to show up. I see the redistributable package x64 below, but that install doesn't work for me. Says Setup Failed, another version of this product is already installed and it cannot continue to install the file. What do I need to do?
Try this one: https://aka.ms/vs/16/release/vc_redist.x64.exe (https://aka.ms/vs/16/release/vc_redist.x64.exe)
It's the x64 for 2015, 2017 and 2019 from that page: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads (https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads)
If still won't install, uninstall what you have (2015, 2017, 2019) and install the new one.
Thanks so much, that fixed it and I got it working.
I have problems getting the rumble function to work, is there any known issues with it or is it just me?
The inmersion is real, my foots kicking the floor sometimes. ;)
Quote from: Midbeck on November 28, 2020, 11:22:29 PMI have problems getting the rumble function to work, is there any known issues with it or is it just me?
You have to tell the plugin which joypad you want the rumble on. Did you do that ?
Quote from: HornetMaX on December 03, 2020, 02:51:42 PMQuote from: Midbeck on November 28, 2020, 11:22:29 PMI have problems getting the rumble function to work, is there any known issues with it or is it just me?
You have to tell the plugin which joypad you want the rumble on. Did you do that ?
I forgot to update my post here on the forums, my bad on that one. I had x360ce installed and after i removed it, everything worked as it should.
having issues with the hud menu not showing up when hittng caps lock on track all my files are placed in the right spot in plugin folder but idk why its not pulling anything up when on track
Quote from: WestSideWill763 on December 09, 2020, 04:04:37 AMhaving issues with the hud menu not showing up when hittng caps lock on track all my files are placed in the right spot in plugin folder but idk why its not pulling anything up when on track
Check your VC redist.
Quote from: HornetMaX on November 10, 2020, 05:20:58 PMQuote from: BlizzardDUCK on November 08, 2020, 09:20:49 PMI'm not getting that plugin to show up. I see the redistributable package x64 below, but that install doesn't work for me. Says Setup Failed, another version of this product is already installed and it cannot continue to install the file. What do I need to do?
Try this one: https://aka.ms/vs/16/release/vc_redist.x64.exe (https://aka.ms/vs/16/release/vc_redist.x64.exe)
It's the x64 for 2015, 2017 and 2019 from that page: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads (https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads)
If still won't install, uninstall what you have (2015, 2017, 2019) and install the new one.
all i did was re-replace the folders in the plugin folder and everything works dont know what changed but glad its working now love the hud great work max
I need to change the shortcut to open the menu, how can I remove it from CAPS?
Quote from: Beto on December 15, 2020, 01:49:36 PMI need to change the shortcut to open the menu, how can I remove it from CAPS?
You can't. Why do you need to change it ?
I have been strugling for hours to get this mod to work. (aleady succesfully downloaded tracks/bikes/gears before)
I deleted and redownloaded the Visual C++ Redistributable a few times and redownloaded the plugin 2 times but i never could make it to work.
Finally after watching a youtube video from GDUB i discoverd that i also had a mx-bikes "steam map" where i had to put in the plugins instead of the mx-bikes program files map....
And now it finally works :) :)
The Youtube video: https://youtu.be/Uv8VgW7Q6Sg?t=2942
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".
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).
how do you get max hud not to have a grey background, i see some people stream and theirs doesn't have that like mine
Quote from: PanicRevv13 on January 17, 2021, 11:41:39 PMhow do you get max hud not to have a grey background, i see some people stream and theirs doesn't have that like mine
cycle through the "Background" option until you get to "No", you can do this for each thing on your screen (map, leaderboard, speed etc) :)
thank you!
Hey Max, any chance we could get more characters for the standings plugin ?
I mean today it is numbers or name or bith but so you get only 3 or 4 characters of the name. Being able to get 10 or even more would be awesome.
everytime i hit caps to display the hud my game crashes, any tips?
Try deleting the file in \Documents\PiBoSo\MX Bikes\ called maxHUD.ini. When you launch the game again it'll re-create a new one.
I've installed the plugin but can't get the rumble working. Everything works on the HUD, just not the rumble. Is it because I'm on the demo? If not, is there a way enable it that I'm missing? When in-game, I hit caps-lock and it seems to be enabled there. There's a section where I can choose devices and to the right it says "(disconn.)" no matter which device I choose. I'm using a DS4.
MaxHUD rumble only works with XInput connections. DS4 uses DInput natively. To emulate XInput you can use Steam (good) or a 3rd party application such as DS4Windows (not as good). You should buy the game too, really opens up with mods and supports the devs.
I've got two questions. 1.) My lean input isn't showing up in the inputs. All the others work fine. I checked to make sure the lean input is working, and it seems like it does visually. Any idea how to fix this? And 2.) Is there a way to move elements of the HUD around? If so, how do I do that?
Is there anyway to get MaxHud on non steam version of the game?
Quote from: Aido on May 22, 2021, 03:49:35 PMIs there anyway to get MaxHud on non steam version of the game?
It works absolutely the same way.
I know it says only compatible with mxb 15 but has anyone got it to work on mxb 16?
Quote from: Aido on May 22, 2021, 04:35:01 PMI know it says only compatible with mxb 15 but has anyone got it to work on mxb 16?
works just fine
for me its not working, i have the 2.2.3 max hud data and mxb.dlo in there but it doesnt show up
Nevermind thanks for the help 2.2.2 works
Still can't get the lean inputs to show on the HUD. Any help?
EDIT- Never mind, the issue seemed to have resolved itself.
my game crashes when i load to game anyone got a fix for this????
for some reason my Mx Bikes isnt in my steam apps folder can someone help me i cant find anything on youtube or anything
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.
Hey so I have the latest version of mxb and in my programfilesx86/steam/steamapps/common I don't have mxbikes or plugin folder (I do all my mods through documents/piboso/mx bikes I can't find where to put the max hud plug-in if anyone knows where to put it i would be verry great full if they could run me through the precess. I checked YouTube and I found nothing
Quote from: HornetMaX on September 28, 2021, 03:47:33 PMV2.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.
Thanks MaX. Will be interesting, I'll give them a test and come back when I get a chance 👍
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.
Okay, I must be doing something wrong. I followed TKO's video on how to install MaXHUD. The only thing different was that I bought the game directly through the website (not STEAM). I copied the DATA and MXB.dlo files and pasted them in Documents/PoBoSo/MXBikes/Plugins, went in game to "Testing", picked a track, and went "to track", clicked "caps lock", and nothing. Do I need to download an older version of MaXHUD to get it to work? Or is everyone who downloaded MX Bikes through the website screwed?
Quote from: F5_TORNADO on December 09, 2021, 06:08:59 AMOkay, I must be doing something wrong. I followed TKO's video on how to install MaXHUD. The only thing different was that I bought the game directly through the website (not STEAM). I copied the DATA and MXB.dlo files and pasted them in Documents/PoBoSo/MXBikes/Plugins, went in game to "Testing", picked a track, and went "to track", clicked "caps lock", and nothing. Do I need to download an older version of MaXHUD to get it to work? Or is everyone who downloaded MX Bikes through the website screwed?
the files go in the plugins folder that is in your game install directory, not your documents folder. there are some installation instructions in the MaxHUD.pdf
Quote from: fridgedollar on December 09, 2021, 06:39:47 AMthe files go in the plugins folder that is in your game install directory, not your documents folder. there are some installation instructions in the MaxHUD.pdf
Thank you so much. I have been struggling with this for awhile. I was just installing it in the wrong plugins file.
V2.2.5 out (2021/12/19)- Updates for GPB beta20 (only, no changes for MXB, WRS and KRP).
Hey Can you update this to Beta 17
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.
Love you Max! Thanks dude I never realize how much I loved your program until I didn't have it :)
Thx Max! :)
Thank you sir!!
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.
Because i play with keyboard and i use caps lock to ride.How can i change the keybing to another ; For example F5 or anything else.?????
I don't think anybody else in the world does that. I'm afraid for you!
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??
Quote from: Eddi on April 06, 2022, 03:47:31 PMSo 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 ?
MaX.. Do you have any plans to make a VR version? :D
Quote from: 𝖙𝖋𝖈 on April 11, 2022, 10:54:22 PMMaX.. Do you have any plans to make a VR version? :D
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.
Hi max, is there a way to enable all widgets in replay mode? I've been trying to troubleshoot some game bugs and been doing some oem bike testing and it would be super useful to be able to see the suspension, inputs and joypad widgets during replays. Going through the ini file there doesn't seem to be any way to do this myself, but could this feature be added to a future update?
Quote from: HornetMaX on April 12, 2022, 06:58:11 PMQuote from: 𝖙𝖋𝖈 on April 11, 2022, 10:54:22 PMMaX.. Do you have any plans to make a VR version? :D
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.
It works fine for me but resides within the confines of the 2d screen which can be anywhere in the VR view and is quite a small area (for me it's like the area of a 22" monitor at about 1.5ft). But if you position the 2d screen appropriately, it's ok with VR.
hi this is my first time installing maxhud, i installed it correctly and made sure too double check but when im in mxbikes and press caps lock nothing happens. anyone know a fix? thanks
When I installed and entered testing the game was almost unresponsive and could hardly move mouse to access maxhud menu. It was like there was a ton of resources in the background. I have a high end cpu.
Hi, having issues with MAXHUD, game works fine without it. When istalled the game crashes as soon as I load in. PC is not overloaded and is downloaded correctly as ive been through the instructions and youtube videos. If anyone knows how to solve let me know please.
Did you try as described in the included trouble-shooting guide and re-install Visual C++?
update beta 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 8)