• Welcome to MX Bikes Official Forum. Please login or sign up.
 
September 22, 2020, 03:46:42 AM

News:

MX Bikes beta14e available! :)


Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - HornetMaX

76
Quote from: Asdrael on April 01, 2017, 03:21:10 PM
Quote from: HornetMaX on April 01, 2017, 03:13:42 PMWow, I just noticed something *very* weird: I have Avast free as antivirus

TLDR of HornetMax post for the lazy ;)

(Avast, Norton etc are memory hogs, shit ton of false positives and false negatives, especially with programs writing in files outside of their own folder). I know it's not fashionable but Windows Defender (yes it's free) and a bit of common sense trumps any 3rd party antivirus those days for home use, in particular the free alternatives.
I had avast for the past 3 or more years, no big issue. Had plenty of others before, no big issue either (until the day I get annoyed by offers to upgrade to pro or similar spam).
Not many false positives, not much resource usage either.

win Defender ? No thx, I'll skip on that one :)  It's ok-ish as it's free, but there are others free that do a better job.

Quote from: TFC on April 01, 2017, 04:23:51 PM
Strange, I use Avast and MaXhud and don't have any problems.. Maybe there is more to it..?
Pay attention if there's any Avast update (the program, not the virus db). I didn't have any issue before that (past 3 years or more) ...

For me it was absolutely clear the problem was coming from Avast. After that, it could be limited to my situation (Win7 x64, specific avast settings etc etc).
77
Wow, I just noticed something *very* weird: I have Avast free as antivirus and it updated 1-2 days ago.
Since I noticed weird things: my plugin was very slow each time I was interacting with it (show/hide widgets, move stuff around, etc), like a 1 sec freeze of everything in MXB (except sound).

I spent 2 hours trying to find a bug in my code, no joy. Then noticed other weird stuff: all Piboso's sims were way slower to load and to go to track.
But if I removed my plugin, they were as fast as they have usually been. So 3 more hours of bug hunting, no joy.

Then I noticed that Visual Studio was slightly slower in compiling my code, something like 10% slower.

So I started thinking Avast was playing games and I switched it off, but no joy. So 2 more hours of bug hunting, still for zero results.

Only after intense headbanging I noticed the problem in my plugin seemed to arise when it writes its status to the .ini file (i.e. startup and any time you change something).
From there I was pretty sure it was Avast's fault, but hey, I switched it off and that didn't make any difference ...

So I tried the silly approach: remove Avast. Problem gone  :o  >:(  :o  >:(  :o  >:(

I don't know if the latest Avast updates screwed anything of if they just rest some options I had previously tuned. At any rate, that's a bug no-no in my book, so Avast gone.

Just in case you have the same issue.
78
Bug Reports / Re: beta6 bug list
April 01, 2017, 03:02:12 PM
Quote from: Bj Slice on April 01, 2017, 03:47:16 AM
in real life, in mid air, you can't lean forward without pulling the handlebars back. If you are on the ground or shall we say stand still, then you can lean forward or back without pulling or pushing the fron end. This is not a bug. This not a mistake either. This just how it would have to.
+1 for the above.

Quote from: Bj Slice on April 01, 2017, 03:47:16 AM
The rear brake tap however could use a little bit more effect when looping out and of course the auto clutch is horible. When you use your rear brake, whether mid air or on the ground, automatic the clutch is held until you hit the throttle again coz your bike will continue to run freewheel. Looping out could be compensated by tapping the rear brake (of course everyone knows) but the bike always goes clutch-engage and lose engine braking.
Just use manual clutch no ?

Quote from: Bj Slice on April 01, 2017, 08:41:55 AM
What went wrong? Was my landing so bad?

check this video out. thanks!

https://www.youtube.com/watch?v=QVzRBjinZzE&feature=youtu.be
Landing hard on the rear, suspension bottoming out, force impulse being transmitted to the rider, rider legs/arm springs not soaking it up enough ==> rider "core" sees an instant g force above its max threshold and separates from the bike. That what I'd put my money on, if really obliged to :)


79
Quote from: Asdrael on April 01, 2017, 12:18:30 AM
Massive load times here. We need a "lower the size of bikes and skins" campaign.
Can't agree more. Just downloaded SM pack: 1 bike = 180-240MB + 105-188MB for the tyres. And that's ZIPPED (.pkz) ...  :o
80
Quote from: Asdrael on March 31, 2017, 03:34:07 PM
As far as I understand Direct Steer, high values mean your stick is actually your handlebar turning force, low value your bike leaning force (roughly don't burn me), which is a result of the handlebars turning.
As far as I've understood (from GPB) Direct Lean 100% means your stick is the target lean angle. With Direct Lean 0% (long time ago, Direct Lean was only On/Off, no intermediate value) there's some sort of "magic" filtering applied to your stick position  so that the control becomes less sensitive (Piboso himself used to say that Direct Lean ON/100% is supposed to be used with high precision devices like joysticks or better, not really joypads).

From what I see, it seems to me that starting with bike vertical and wanting to lean fully left, Direct Lean 0 or 100 behaves in a similar manner. The big difference seems to be when you want to pick your bike up (e.g. go from leaning left to vertical, or clearly from leaning left to leaning right): with Direct Lean 0%, if you just put your stick in the middle, the bike will react slowly, it will come back vertical veeeeery slowly. So slowly than in fact you're obliged to "overshoot", i.e. you will push your stick not to center but to the right, to make the bike pick up faster. Once the bike is vertical, you will move your stick to the middle. With Direct lean 100%, you don't need that. On the contrary, as the stick output is the target lean, you have to move it more carefully.

Short version: with Direct Lean 0% you can bash your stick left/right like a madman (actually, you almost must). With Direct Lean 100% you have to gently move the stick as if conducting brain surgery on a beloved one.

After years of debates in GPB (mind, MXB is pretty different) my conclusion is that one is not better than the other, in GPB you can be fast with any of the two. But it takes time to get accustomed to one coming from the other, so that's why people using it at 100% say 0% is shit (and vice versa, of course).

Personally, I tend to use very high values of direct lean in both GPB and MXB (by high I mean 100% :) ).

P.S.
I have a joypad ans I've put some "stick extensions" on it (something like this: https://www.kontrolfreek.com/thumbsticks/fps-freek-classic.html). I think they make you more precise.
81
General Discussion / Re: Newbie MX Bikes Demo player
March 31, 2017, 05:49:05 PM
Quote from: Sandbiter on March 31, 2017, 05:47:26 PM
Quote from: HornetMaX on March 30, 2017, 03:36:35 PM
Quote from: Sandbiter on March 28, 2017, 04:10:04 PM
Geo! Buy me WRS please ;)
There's also MXGP 3  ;D
WRS had more potential, at least if the netcode is good. If the netcode is good I'll buy it myself and host championships. Until then, Geo can buy it for me.
I was being ironic/sarcastic ...
82
Plugins / Re: MaxHUD plugin
March 30, 2017, 03:42:39 PM
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 :)
83
General Discussion / Re: bravo
March 30, 2017, 03:41:17 PM
Oxford comma ... mark +1 in the colum of things I've learnt today :) Have to admit the pros have a point:

QuoteAmong those interviewed were his two ex-wives, Kris Kristofferson and Robert Duvall.
VS
QuoteAmong those interviewed were his two ex-wives, Kris Kristofferson, and Robert Duvall.

Funny :)
84
General Discussion / Re: Newbie MX Bikes Demo player
March 30, 2017, 03:36:35 PM
Quote from: Sandbiter on March 28, 2017, 04:10:04 PM
Geo! Buy me WRS please ;)
There's also MXGP 3  ;D
85
Plugins / Re: MaxHUD plugin
March 29, 2017, 02:56:11 PM
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 :)
86
Plugins / Re: MaxHUD plugin
March 29, 2017, 01:58:02 PM
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.
87
Bug Reports / Re: 450 gameplay glitch
March 29, 2017, 09:12:27 AM
@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).
88
Plugins / Re: MaxHUD plugin
March 28, 2017, 11:51:08 PM
Weird weird weird ... can you send me the .ini and the .log ?
89
Plugins / Re: MaxHUD plugin
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.
90
Plugins / Re: MaxHUD plugin
March 28, 2017, 05:05:06 PM
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.