Messages

[V2.1.8 out (2020/01/23)]

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).

Thank you for the report.

Unfortunately it's not a simple bug, but rather a code design error, that also causes other issues, like the inability to reset the bike under a bridge.
The problem will be fixed as soon as possible.

Thx a lot for the info !

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.

One small request: could you document what exactly is in the argument _pRaceData of TrackCenterline ?

Code Select Expand

__declspec(dllexport) void TrackCenterline(int _iNumSegments,SPluginsTrackSegment_t *_pasSegment,void *_pRaceData)
My understanding is that you have some floats indicating the position along the centerline of the start/finish line, then the split points and the speed trap.

Is it correct to assume (as not documented) that:

• GPB has 1x start line, 3x splits, 1x speed trap
• MXB has 1x start line, 2x splits, 0x speed trap
• WRS has 1x start line, 2x splits, 1x speed trap
• KRP has 1x start line, 2x splits, 1x speed trap

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), 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).

[@PiBoSo:]

@PiBoSo:

In the thread of my MaxHUD plugin there's a report of a strange behavoiur of my LiveTiming (posts from tfc and teeds, from here).

What my LiveTiming does is to save the position (fPos) and time (fTime) in an array all along a lap (your best lap).
On subsequent laps I do the same in a different array and hence I can compute the time gap at the current point on the track, between the ongoing lap and the currently best one.

The RunTelemetry call of the output plugin seems to receive some weird data, here's an example (relevant part only):

Code Select Expand

@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.763742, fT:154767.734375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.763926, fT:154788.375000
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154804.046875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154825.359375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154843.796875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154867.578125
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154887.109375
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154907.015625
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154926.875000
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154945.796875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154965.390625
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.099025, fT:154984.546875
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.765946, fT:155003.312500
@@@LiveGap Telemetry (WIN) step 1: iB:0, iC:1, fP:0.766131, fT:155022.921875

As you can see, fPos is 0.763742 on the 1st call (1st of the ones shown here), then 0.763926 on the 2nd but on the 3rd it goes back to 0.099025 and stays there for a few calls (10 in this case), before resuming with more normal values (0.765946 then 0.766131). This of course screws up my LiviTiming thing (and makes some weird telemetry graphs ).

Notice that the point at which this happens has nothing special (no crashed bike).

According to tfc and teeds, this seems to happen only on some tracks. I can reproduce it systematically on Ironman track: drive first lap out of pits and on the second lap (1st "real" lap) it happens always for me. So my LiveTiming of the 3rd lap is screwed.


P.S.
Another weird thing, likely unrelated.
On Ironman when you go to track from the paddock you don't cross the start/finish line, but the ghost of the 1st lap out of pits is recorded anyway. This is probably unwanted (the 1st lap out of pits is not considered as a valid lap by MXB anyway, in terms of timing).

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     

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

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?

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.

[V2.1.7 out (2020/01/03)]

V2.1.7 out (2020/01/03)

• Changes for KRP beta10 (reference UI is now 16:9).
• GPB only: option in HUDInputs to show either "throttle" or "engine throttle": "throttle" is what comes out of your input device, "engine throttle" is what goes into the engine (i.e. corrected buy the ECU with idle control, traction control, anti wheeling and rev limiter).

Happy New year all !

[v2.2 out:]

v2.2 out:

• Updates for GPB beta16.

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

[V2.1.6 out (2019/09/11)]

V2.1.6 out (2019/09/11)

• Changes for GPB beta16.

[V2.1.5 out (2019/08/18)]

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.

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 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.

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.

Alternative (but annoying) solution: manually editing the MaxHUD.ini file you can see the X and Y position of each widget.

Oh man! Thanks! Where do find this? Is there a readme I didn't read?

I think there's a readme.txt file somewhere in the installtion folder.
The only other shortcuts I recall are Ctrl-F (for an FPS counter), F12 (or F11) for a screenshot and F11 (or F12) for an high-res screenshot.
There may be others (inclufing one to show/hide the dash, probably).