PiBoSo Official Forum
21
Suggestions and wishlist / Whitelist - force livery and a...
Last post by Ricoway46 - February 03, 2024, 10:44:22 AM- Possibility to force the livery via the whitelist
- Ability to specify the BOP, then add/remove kilos and add/remove horsepower
Thank you
22
General Discussion / Re: Daily development reprise
Last post by PiBoSo - January 31, 2024, 11:52:33 PM* GPB / WRS / KRP / MXB: added muffling to distant sounds
* Tools: fixed the LODs of heightmaps when using the top-down view in Track Editor and Map Viewer
* Tools: more fixing of the Track Editor centerline close feature
* Tools: fixed the LODs of heightmaps when using the top-down view in Track Editor and Map Viewer
* Tools: more fixing of the Track Editor centerline close feature
23
Virtual Reality / Re: Where to configure VR trac...
Last post by infected247 - January 31, 2024, 11:46:33 PMcheers mate, looks like I missed this one
24
Virtual Reality / Re: Where to configure VR trac...
Last post by Chris_Beeves - January 29, 2024, 08:52:10 PMIt's in the profile.ini
under the "input" section, add:
a value greater than 0 increases the gain. 1 doubles the gain
under the "input" section, add:
Code Select
rider_tracking_fbgain = 0
rider_tracking_lrgain = 0
a value greater than 0 increases the gain. 1 doubles the gain
25
Virtual Reality / Re: Where to configure VR trac...
Last post by infected247 - January 28, 2024, 06:49:51 PM^
26
Support / Re: SimTools Motion Plugin for...
Last post by Chris_Beeves - January 25, 2024, 09:28:39 PMIt's a little different from v2 but it's really nice having everything in one place.
Let us know how it works out!
Let us know how it works out!
27
Support / Re: SimTools Motion Plugin for...
Last post by Prototype - January 25, 2024, 02:08:09 PMThank you! 
Ill upgrade to V3 and then try it out .. appreciate the response ...
Ill upgrade to V3 and then try it out .. appreciate the response ...28
General Discussion / Re: Daily development reprise
Last post by PiBoSo - January 19, 2024, 11:57:08 PM29
Javiliyors' Mods / Re: SBK22 v1.1
Last post by javiliyors - January 14, 2024, 10:35:47 PM01/14/2024
Update v1.1
Added Extra Bike:
BMW M1000RR 2024
Tuned suspensions.
Tuned geom.
Tuned tyres.
Tuned virtual rider.
Added 250rpm to Kawasaki.
Reduced 250rpm to Ducati.
Changed the image of the garage for the tire information.
Added aero physics.
Tuned ECU.
Update v1.1
Added Extra Bike:
BMW M1000RR 2024
Tuned suspensions.
Tuned geom.
Tuned tyres.
Tuned virtual rider.
Added 250rpm to Kawasaki.
Reduced 250rpm to Ducati.
Changed the image of the garage for the tire information.
Added aero physics.
Tuned ECU.
30
Support / Tripple monitor support - Prob...
Last post by nor_bak - January 11, 2024, 10:39:42 PMI have it working but:
-I still don't know how gp-bikes names or selects or whatever the monitors.
-For third person playing isn't the best but also not the worst. I can't see the whole bike. GPBikes could have a FOV setting specific for this camera.
Correction: It has a distance setting but it does not have enough range.
-No real support for different monitor sizes. Height and Width settings for non main monitor work funny. Side monitors size and bezel correction calculation missleading.
For first person playing is fine, everything is much bigger.
Vertical fov can get quite small, and under braking with head movement horizon goes away.
My setup is:
Position: Left - Center - Right
Windows ID: 3 - 1(main) - 2
24" 1920x1080 - 29" 2560*1080 - 24" 1920x1080
core.ini
[display]
monitor=1
setup=monitors.cfg
1 for main one. Here I can also put 0. 0 seems to mean default monitor or main.
monitors.cfg
primary
{
screen_distance = 500
screen_width = 675
screen_height = 283
width = 688
height = 313
}
global
{
angle_x = 60
angle_y = 0
}
monitor0
{
display = 1
res_x = 1920
res_y = 1080
multisample = 4
bpp = 32
width = 666
height = 298
pos_x = -1
pos_y = 0
shift_x = 0
shift_y = 0
shift_z = 0
angle_x = 0
angle_y = 0
}
monitor1
{
display = 2
res_x = 1920
res_y = 1080
multisample = 4
bpp = 32
width = 666
height = 298
pos_x = 1
pos_y = 0
shift_x = 0
shift_y = 0
shift_z = 0
angle_x = 0
angle_y = 0
}
Monitor naming or addressing or whatever - UFO
monitor0 - display=1 - pos_x=-1 - left
monitor1 - display=2 - pos_x= 1 - Right
I have no idea why monitor0 has to be display 1 and left, and monitor1 display 2 and right.
Monitor angle - OK
If they are aligned they are at 0 degrees. 500mm distance and 60 degrees give me 180 degrees FOV.
Monitor sizes - Buggy / Basic
Gpbikes works as if all monitors were of the same total size(width*height) and probably aspect ratio but lets you define sides screen size (height and width settings) and a custom resolution.
This means:
-bezels are calculated for main monitor (29" 21:9 2560x1080) with given parameters.
screen_width = 675
screen_height = 283
width = 688
height = 313
Calculated horizontal bezel each side is = 6.5mm
My side monitors are 24" 16:9 1920x1080, and their measures are:
screen_width = 528
screen_height = 298
width = 550
height = 327
Calculated horizontal bezel each side is = 11mm
But in order to have the right bezel compensation my settings must be:
width = 688mm - 2*11mm = 666mm
height = 298mm looks fine, its smaller than main height = 313.
Image on side monitors will be stretched but is not too important.
At least transition between perspectives is between monitors. ACC, RF2, RR work even worst triple support and have them in center monitor.
Best support goes to AMS2 (direct multimonitor support without obscure config files or nvidia surround/AMD eyefinity) followed by AC with CM.
-I still don't know how gp-bikes names or selects or whatever the monitors.
-For third person playing isn't the best but also not the worst. I can't see the whole bike. GPBikes could have a FOV setting specific for this camera.
Correction: It has a distance setting but it does not have enough range.
-No real support for different monitor sizes. Height and Width settings for non main monitor work funny. Side monitors size and bezel correction calculation missleading.
For first person playing is fine, everything is much bigger.
Vertical fov can get quite small, and under braking with head movement horizon goes away.
My setup is:
Position: Left - Center - Right
Windows ID: 3 - 1(main) - 2
24" 1920x1080 - 29" 2560*1080 - 24" 1920x1080
core.ini
[display]
monitor=1
setup=monitors.cfg
1 for main one. Here I can also put 0. 0 seems to mean default monitor or main.
monitors.cfg
primary
{
screen_distance = 500
screen_width = 675
screen_height = 283
width = 688
height = 313
}
global
{
angle_x = 60
angle_y = 0
}
monitor0
{
display = 1
res_x = 1920
res_y = 1080
multisample = 4
bpp = 32
width = 666
height = 298
pos_x = -1
pos_y = 0
shift_x = 0
shift_y = 0
shift_z = 0
angle_x = 0
angle_y = 0
}
monitor1
{
display = 2
res_x = 1920
res_y = 1080
multisample = 4
bpp = 32
width = 666
height = 298
pos_x = 1
pos_y = 0
shift_x = 0
shift_y = 0
shift_z = 0
angle_x = 0
angle_y = 0
}
Monitor naming or addressing or whatever - UFO
monitor0 - display=1 - pos_x=-1 - left
monitor1 - display=2 - pos_x= 1 - Right
I have no idea why monitor0 has to be display 1 and left, and monitor1 display 2 and right.
Monitor angle - OK
If they are aligned they are at 0 degrees. 500mm distance and 60 degrees give me 180 degrees FOV.
Monitor sizes - Buggy / Basic
Gpbikes works as if all monitors were of the same total size(width*height) and probably aspect ratio but lets you define sides screen size (height and width settings) and a custom resolution.
This means:
-bezels are calculated for main monitor (29" 21:9 2560x1080) with given parameters.
screen_width = 675
screen_height = 283
width = 688
height = 313
Calculated horizontal bezel each side is = 6.5mm
My side monitors are 24" 16:9 1920x1080, and their measures are:
screen_width = 528
screen_height = 298
width = 550
height = 327
Calculated horizontal bezel each side is = 11mm
But in order to have the right bezel compensation my settings must be:
width = 688mm - 2*11mm = 666mm
height = 298mm looks fine, its smaller than main height = 313.
Image on side monitors will be stretched but is not too important.
At least transition between perspectives is between monitors. ACC, RF2, RR work even worst triple support and have them in center monitor.
Best support goes to AMS2 (direct multimonitor support without obscure config files or nvidia surround/AMD eyefinity) followed by AC with CM.