Rotary encoders do work with LFS, just assign them like any other wheel button: Options -> Controls. Then assign them on the [Wheel Buttons] column in Buttons 1 and Buttons 2.

Which wheel is it you have?

Quote from d_cury :

I do not know how to use the onboard and rear cameras, it appears that I check the file cvw.ini I do not know what to do there

To set these up you need to create the views in LFS without TV Director running, you can save the view manually with:

You can modify the custom view in options > view. It should automatically save once you exit the options menu at which point you can copy it from LFS/data/views.

For TV Director to provide you with the correct onboards you need to create a file for each view per car called:


and

where XXX is the three letter car code of the view you created.

Place those inside the views folder in TV Director before starting it up.

Maybe whoever sold him the wheel threw in their S2 account? The screenshot is of Westhill National.

Quote from MandulAA :

As for streaming, I fully recommend https://simbroadcasts.tv/ !

Thanks Dan.

We'd be happy to help set something up. Either PM me on the forum or drop us a booking request. We may even be able to help with servers too if you need, though you can organise this yourself these days with LFS Hosting.

+1, especially for long races.

Quote from Evolution_R :

On YouTube are plenty of mods that break copyrights and are uploaded years ago and still not deleted.

That is why I mentioned strict moderation. This is the LFS forum, not the world's largest content creation platform.

Is it safe to assume that if a mod were branded as a replica that it would not break copyright, just like if a car manufacturer were to sell a replica car? Selling replicas is legal as far as I'm aware, as long as it's not being branded as original or official.

As long as the thread title has "Unofficial Replica" in it, and the mod is not a straight copy of a model file from another source, wouldn't this be enough? Of course there is a degree of trust that would be placed on the "creator", but as long as the terms and conditions of posting a mod are visible front-and-centre and it's a system comparable to that of YouTube where their terms of upload state you cannot post copyrighted content (along with other strict rules of course), the system could be manageable with moderation.

Quote from Scawen :

I guess we need an example of a MOD that can bypass the OOS check, otherwise I am being asked to solve a problem that I cannot see, understand or reproduce.

Elmo and I spent some time last night testing with a player who had some VOBs to test with us online and as far as we could tell, there were no issues with collisions in this case. The VOBs had been run through a script (which I have been sent) which ensured that the collision box was not modified from stock.

This is not the end of our testing though, we will reach out to other people and see if we can find any examples of VOBs that cause botched collisions because we have certainly had issues since the OOS checker was updated, but have yet to dig up any concrete proof to show here.

Quote from Scawen :

*snip*

Fair enough, but by allowing discussions to take place on the official forum, the use of VOBs online will inevitably increase as more people are exposed to them, whether that was your intention or not, that's the main reason these concerns were brought up here. I had no idea you were not aware that there is an apparent bug in your detection system, but I'm glad it has now been brought to your attention.

EDIT: Bug is unfair, I meant loophole.

Are you considering these concerns before committing to this?

Quote from Degats :

*snip*

Could not have said this better. This announcement is confusing for many reasons, most of all that there are almost certainly ways that people are skirting the OOS detection meaning that VOB checking is still prevalent on [TC] CityDriving by the admin team and we're still having people sending us screenshots of obviously VOB modded cars.

As such, this announcement may lead to problems in races too. I may not speak for everyone but having been aware of the problem that VOB modifications caused for [TC], I was never even tempted to run modified cars in racing for fear that it might cause problems in wheel-to-wheel situations.

Quote from BestRex :

Please don't drop the support of Direct3D 9: there's a lot of people in the world who have old computers, but still want to play some games.

Sorry but this is a ludicrous request in 2020.

Round 1 Livestream Replay:

There's more and more racing happening every week now so it's a good time to upgrade.

Speculation:

It is my understanding that the current spectrum of weather modes will be removed. If static weather is desired for a session you will be able to set the date and time. I assume there will be a number of cloud configurations too in order to replicate clear, partly cloudy, mostly cloudy and overcast weather.

There's now a dedicated discussion channel for this series on the Live for Speed Discord server: #buggyra-zm-gt-cup: https://discord.gg/EZeqASS

Last day to register and set a hotlap for round 1: https://buggyra301.games/

I don't understand this. Your PC specs are more than capable of running LFS in VR flawlessly... It could just be that the Index just asks too much. Have you tried it with other games on your PC? Edit: I noticed you said you tried it with AC and it worked fine in 80Hz mode... Hmm...

@Scawen: Just FYI, with worse specs than Drifteris (GTX 1070, Ryzen 5 1600X), I have used the Valve Index with LFS and it ran just fine with a decent number of cars. That wasn't on the current round of test patches though. Edit again: It might have been on the current round of test patches actually...

Last edited by mbutcher, Mon 6 Apr 2020, 12:06.

Quote from Drifteris :

Using valve index it seems that only 80Hz option is stable and kinda keeps 80fps on LFS. 90Hz seems to drop to 45fps, 120hz to 60fps and 144hz to 72. Not sure why this half the frame things happen.

Also i'm not sure whether i've used 144hz monitor too much and now 80hz VR looks laggy or it's just not optimized as good. I do understand that physics run at 100fps but the game seems smoother on higher frames even if there is some sort of frames ghosting going on or not.

Super Sampling doesn't seem to change much aswell in my case so i just set it to 225%

There are a number of possible reasons that you only get stability at 80Hz. Your super sampling value is too high. Set it to 115% at the very most for best results in LFS. You're right that the LFS physics engine is out of sync with your headset so you will get some noticeable stutter when cornering. The halving of your perceived frame-rate is an effect called asynchronous time-warp (Oculus term), where frames are being interpolated every other frame to try and reduce any effects of cyber sickness.

Drop your super-sampling value and try again.

I'm in love with that.

Rest in Peace MVH!

Last edited by mbutcher, Fri 27 Mar 2020, 15:42.

Maybe don't post that here either...

While your ping is usually high Nova, it's also normally very stable. Problems arise from unstable pings. I've had terrible races with people with relatively low pings because their ping fluctuated a lot.

Sent you a PM.

That. Is. Dope.

I recently upgraded to the GT Omega PRO cockpit. I run a rift but you can probably see why I want to get on the Ultra-wide bandwagon (images attached).

This thread came at a good time. I'm also considering getting a 49" monitor because I would like the option to use a monitor setup from time to time, rather than having to use VR, even for casual racing sessions. I do not get on well with traditional multi-monotor setups, so I'm interested in trying an extra-wide. It's a big expense so I'm interested to get opinions from people who have used them. Rony, nacim, how do you get on with yours?

Last edited by mbutcher, Sun 2 Feb 2020, 17:11.