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

Pages: [1] 2 3 ... 53
1
Support / Re: Cant Have Gloves and protection at the same time
« on: October 15, 2018, 11:03:58 AM »

Are you using the default neck brace / protection?
Is the name of the custom gloves very long?

2
General Discussion / Re: MX Bikes beta10 WIP
« on: October 05, 2018, 10:15:15 PM »

More like second half of the month, unfortunately  :-[
A lot of changes are in progress.

3
Support / Re: Online access
« on: October 02, 2018, 08:51:43 PM »

When did you send the emails?
What is the problem?

4
Documentation / Windows desktop scaling
« on: September 23, 2018, 03:22:04 PM »

If the Windows scaling is set to a value over 100% then MX Bikes will start at a lower resolution to compensate for the automatic scaling.

To solve the issue and use the full resolution: right-click on the MX Bikes icon -> Properties -> Compatibility -> Disable display scaling on high DPI settings

5
General Discussion / Re: Steam version
« on: September 20, 2018, 02:08:50 PM »
- possibility to paint bike, helmet, kit, boots and gloves  coming with steam version ?Or before?

Do you mean an editor integrated in MX Bikes?  ???

6
Documentation / Re: VR Support
« on: September 15, 2018, 09:37:37 PM »

First post updated with info about the Oculus pixel density.

7
Plugins / Re: Output Plugins
« on: September 09, 2018, 03:02:13 PM »

Example source code updated to add more structure members descriptions.

8
Plugins / Re: Output Plugins
« on: September 08, 2018, 09:31:13 AM »
Another quirk I just noticed: in MXB m_iSessionNumLaps in SPluginsRaceSession_t dopesn't seem to be set, it's always zero.
Seems to work fine in GPB however.

Thank you for the report.
The fix will be integrated in the next update.

9
General Discussion / Re: MX Bikes beta9
« on: September 05, 2018, 08:54:27 PM »
The netcode is a lot smoother, but it seems like everyone is further behind than they actually are. As you can see in Gdub's video, which you can find below, it looks like I ran him over from behind, while on my screen I 200% passed him on the braking bumps right before the corner. I've had a lot of these funky things happen to me since Beta 9. Always getting the holeshot myself, but when watching someone's video, they get the hole shot. And no, that is definitely not a FOV problem.

These issues are due to the netcode changes that favour smoothness over accuracy.

10
Physics / Re: Alta conversion
« on: September 05, 2018, 07:17:24 PM »
Figured it out, engine inertia. 0.001 feels like a proper value.

The bike is direct drive, so the engine inertia is added to the rear wheel.
Problem is, it also affects the gyroscopic forces, while it shouldn't.

Lowering the engine inertia is a workaround, but 0.001 is not a proper value.

11
Plugins / Re: Output Plugins
« on: September 05, 2018, 08:04:36 AM »

Thank you for the report.

12
Physics / Re: Alta conversion
« on: September 04, 2018, 08:48:25 PM »
Code: [Select]
batterypack
{
Capacity = 5.8
}
Is this a random number or what we should use for a standard Alta?

According to the official Alta data, the real bike uses a 5.8 kWh pack.

13
Physics / Alta conversion
« on: September 04, 2018, 08:35:12 PM »
Steps to convert the Alta to make use of Beta9 electric engine support.

1) open the file MX2OEM_2018_Alta_Redshift_MXR.cfg

2. go to the "engine" section.
2a. add
Code: [Select]
electric = 1This tells the physics that there is no fuel tank, no idle and no engine stall.
2b. the "stall" section is still used to make sure that engine braking goes down to zero at zero rpm.  Example:
Code: [Select]
stall
{
RPM = 500
torque = 0.1
}
2c. "IdleThrottle", "IdleRPM", "FuelRatio", "shiftRPM" can be removed.
2d. the "Clutch" section must be removed to tell the physics that the engine is direct drive.
2e. the real engine primary ratio, "Ratio0", is actually 19, 67  :P

3. remove the "fueltank" section, and replace it with:
Code: [Select]
batterypack
{
Capacity = 5.8
}

4. remove the "gearbox", "autoclutch" and "shifthelp" sections.

5. go to the "driveline" section.
5a. delete "SecondAxisInertia".

6. "data" in "tyres" is not used anymore.

7. save and close the file.

8. open the file sfx.cfg

9. the "starter" and "gearbox" sections can be removed.

10. save and close the file.

11. all done, but you can also delete the files "engine.wav", "p_mx.cfg", "p_mx_f_midsoft.tyre" and "p_mx_r_midsoft.tyre", because they are unused.

14
General Discussion / Re: Steam version
« on: August 31, 2018, 01:55:10 PM »
Admittedly, I haven't tried that recently: does the server still reply "Missing bike" or "Bike mismatch" without telling you which holy-fuc#!n-bloody bike is missing / mismatching ?

Yes  :-[
Isn't that the perfect situation for a hotfix-style patch ? As in "Release9b, just download the updated exe"

Patches are meant for code-only quick bug fixes, not improvements that need time and testing.

More connection information will be packed with other features and fixes in Beta10.

15
General Discussion / Re: Steam version
« on: August 31, 2018, 11:14:35 AM »
Admittedly, I haven't tried that recently: does the server still reply "Missing bike" or "Bike mismatch" without telling you which holy-fuc#!n-bloody bike is missing / mismatching ?

Yes  :-[

Pages: [1] 2 3 ... 53