Messages

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

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

Code Select Expand

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

@PiBoSo: bit off-topic but who knows, maybe related. When I have Visual Studio open to compile my plugin and I run your sims, the game crashes when loading a track.
If I close VS (2015) then the game starts and runs normally.

The weird thing is that the whole thing is not constant: at the moment for example, it happens with MXB but not with GPB. In the past I'm sure I've hat the opposite too (GPB crashing and MXB not).

Weird weird weird ... can you send me the .ini and the .log ?

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.

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.

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.

[@GDUBMX:]

@GDUBMX: any news ? Issue still there ? Can anybody else confirm ?

Width is an angle in fact, half-angle of the tyre profile.

Hmm.......then why do default Rear Tyres have a width (angle) of 75 and front 85??

Seems backwards

If you check the torus radius too you'll probably find the width (in mm) to be bigger at the rear (can't check now, don't have the files at hand).

Width[mm] = TorusRadius[mm] * 2 * sin(Width[angle])

^ That and well.......we need selectable tyres as it is a pain in ass right now having to duplicate things

Isn't that already doable ?
It would be enough to add all Piboso's standard tyres to your tyre set and name them accordingly (like Pib soft, Pib med, ... Geo Soft, Geo med, ...).

So in geo_p_mx.cfg you can probably refrence PiBoSo's tyres and you're done.

Not tried and not ideal, but it should work no?

When I bought the game 2 days ago, I could not go back to MXS anymore.

Just me being honestly curious here: could you explain why ?

And why shouldn't they have the rear tyre? Because of the width? I'm not sure how we can get that in the tyre file.

Tyre width is easy to put in game, you need to play with the parameters Radius, TorusRadius and Width. Width is an angle in fact, half-angle of the tyre profile (assumed circular).



For the rest (tyre properties difference between 250 and 450) you're on your own

P.S.
Not sure, maybe you were all already ware of that I'm being Cpt.Obvious here ... but I'll take the risk

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

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

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 ?

Done. Will be in next release.