Round 4 VOD:

VOD for RTFR Round 4:

Join our team!

We are now accepting applications for English speaking commentators for public and private projects in Live for Speed.

Apply now at: https://simbroadcasts.tv/join

Last edited by mbutcher, Mon 24 Apr 2023, 13:03.

Round 3 VOD:

Quote from Scawen :

I know this doesn't answer everything on the thread.

No, but this is really handy to know and will solve a few of my issues, thanks!

VOD for RTFR Round 3:

Round 3 VOD:

Quote from Gutholz :

Changing brake balance:
Some cars allow to adjust brakebalance/dampers while driving which is very cool.
But it is a bit cumbersome to first open the F11, scroll to correct line with arrow keys, adjust value, close F11 menu.
It would be nice to have some way to just press a button or turn a dial.
(It is somewhat possible via workaround with scripts, like

//move brake balance to front:
/press f11
/press down
/press down
/press left
/press f11

This use-case in particular is why LFS is so great on wheels that have rotary encoders. The DFGT, G29/920 and most TM/Fanatec rims have multi-mode rotary encoders to which you can bind the next/increment/decrement/toggle functions to via LFS scripts. While in truth it is actually easier to bind these in iRacing than in LFS for instance, it's nice that it's still possible, and we're still given full freedom of how we set these up. The way LFS currently works allows you the versatility of being able to assign such encoders to multiple functions, not just one setting (e.g. brake bias). This is akin to iRacing's Blackboxes where a rotary encoder can effectively manipulate every single option with a single wheel control.

In my opinion, a far more useful bind would be one that cycles the F11/F12 menus, again akin to the iRacing blackboxes. In the meantime, that too can be set up with LFS scripts.

Personally, I do not mind the idea of upscaling 1024 skins to 2048, if the price stayed the same.

VOD for RTFRXL Round 1:

VOD for RTFRXL Round 1:

Round 2 VOD:

VOD for round 2:

VOD for RTFR round 2:

Last edited by mbutcher, Wed 27 Jan 2021, 15:37.

Quote from Tazka :

the ability to reconfig the hotkey to some other button on keyboard would be the best solution.

I would be happy with that.

Quote from kagurazakayukari :

*snip*

Cool!

Quote from Scawen :

The problem with the virtual keyboard location is, other dialogs.

I should've realised that's why.

Quote from Scawen :

The only thing that comes to mind is if the vkb could have its top at ordinary dialog height, if there is no other dialog visible. It sounds easy enough though I haven't looked in the code yet. But would that be of any use?

If this is possible, I would be in favour. Could even be given its own layout option: Dialog layout [fixed|centred] (idea attached).

Maybe I should also take this time to remind you of the space click issue I always run into while typing on my actual keyboard in VR while in text-entry mode. While typing with the chat dialog open, sometimes the gaze-cursor can trigger ok/cancel/specials when typing and pressing space, which means I have to make sure the crosshair isn't anywhere near the dialog, which just feels (and looks) ridiculous!

Last edited by mbutcher, Thu 14 Jan 2021, 15:41.

Flame reminded me of a small feature request I made in a VR demo video I made a couple of years ago surrounding the VR keyboard (@2:20). I wonder whether you could move it, or give the option to move it around (maybe directional arrows next to it like the mirror adjustment gimble?)

Just jumping on the tweaks bandwagon here. Cheers.

The contact between Dennis and THREE Brazilian drivers last night in turn 1 was mostly just unlucky. For all three of those guys to be in the same place at that time when the contact was initiated would have set off a chain reaction at any pps most likely. In that situation the drivers really need to be doing everything possible to avoid contact on lap 1, especially in such a multi national race.

Round 1 VOD:

Quote from Scawen :

For minor steering / throttle / brake adjustments it will not go up to the rate set by pps.

That explains what I was seeing on the straights on the test server, the same update frequency I saw before on 4/6pps servers. As the cars turned for a corner, it was noticeably more frequent. I'm sure others will have some feedback and observations, and we plan to test this en masse tomorrow after GT2C on the death rally server, which should give us a good test case for close racing, collisions etc..

Quote from Tazka :

Tell me the server, i'll come by to test it out!

NDR.Death Rally is running U13 DCON. Come test.