LFS can be quite overwhelming with all its options, so if you have any questions about it, feel free to ask here on the forums, or on the LFS Community Discord server: https://discord.gg/wZrUTJN. You usually can get near-instant replies there, as there are more than 1,4k members on the server now
What do you define as a "good cruise server"? I'm more of a racer type, probably did under 10 kms on cruise servers overall throughout the years, so not an expert in the field, but the TC CityDriving servers are really popular, as I always see them on the top of the servers list. Do you count them as not-good-enough cruise servers?
Hi. If not you, someone else surely used your account to unlock LFS. Those unlocks don't just evaporate. More info about unlocks and when you'll get your next one: https://www.lfs.net/faq/33
Having a brief look, I think you should be able to play LFS in VR. Purely from performance point of view, the weaker link is definitely your CPU (passmark avg score: 4641), but your GPU (passmark: 8008) seems fine.
For reference, I was able to run LFS with Oculus Rift CV1 perfectly, using an i7-6700k (passmark: 8970) and an EVGA GTX 1060 3GB (passmark: 9659).
Welcome!
For skinning, one shouldn't miss using CMX Viewer, which is a standalone app for loading skins on the car models. Download here, on the right panel: https://www.lfs.net/downloads
Your #55 entry is okay, if you add the chosen car later.
For the #55 car you just registered, you have the 3 spots filled up and can't add more (rule: you can only have a maximum of 3 drivers per car/entry). Any additional drivers will have to be registered in another entry, like you said, a FordRallyeSportTeam 2 for example. That will be a separate car with those drivers you add there. So yes, it is possible to register a second team.
Unfortunately, it's what LFS recognizes as a pitstop, that is time from the stop and until the first movement, and that's right. It's what gets stored in the .mpr and that's what Rony runs the analyzer on. I messed up my pits too, at 8 seconds work finished and I instantly moved a little. There wasn't even an Airio confirmation of my pitstop time (Airio bug, I guess), but I knew it would be useless that I stay there any longer, as the pitstop was completed already. I just did another pitstop to account for that messed-up pitstop of mine, so that my overall recognized pitstop time is 10s+.
It's just how it works, and I think it's the right way, no need to argue about that
I somehow don't feel I'd be part of any of the groups of people you mentioned, yet still here I am, racing every day online in events that have full, packed grids every week (40+ players trying to qualify for a a race, weekly). Sometimes I also join the public pick-up style multiclass server, and have fun with quite a few people. For me, I'd rather not do the maths, but was worth every penny I spent on LFS, especially when spread over 10+ years, and I'm still looking forward enjoy it whenever my time allows in the future. Sorry, but you won't be able to convince me about what you just said
Hi! I have this with an Oculus Rift CV1 as well. Here is my way of reproducing it:
- set LFS to 3D mode, that automatically launches Oculus software in the background. Works fine, can drive fine with the headset
- exit LFS
- disconnect Rift (I unplugged both headset and sensor USB cables, left HDMI in)
- open LFS, red "Could not initialise Oculus Rift headset" message, but seemingly it defaults to 2D mode (confirmed that in Options)
- exit the still running Oculus software, confirming closing a "running VR app"
- LFS crashes after ~15-20 seconds, regardless of being on-track or staying still in menu
Additional note, when running LFS again after the crash, it still tries to enable 3D mode, and if Rift is still disconnected, the red "Could not initialise Oculus Rift headset" error appears. It still automatically launches the Oculus software, and when I close that, the crash happens again after some seconds. I can loop this many times.
The only way to stop LFS crashing, is to Close LFS the way it's supposed to be closed (by clicking Exit in-game) while it's in 2D mode. Based on this, the constant crashing might be related to settings not being saved (since it crashes and misses the usual exit of LFS, when settings are saved, I guess), that way LFS always tries to start in 3D mode, and launches Oculus sw as well.
(attached deb.log in .txt format, but I found nothing there, only traces of the startup)
(if you need any more help debugging, I have the CV1 here and can try out things)
Update 0.8.2
This small patch contains fixes and user experience improvements, also a crash fix.
New version can be downloaded in the attachments of original post.
Please try it out, and as always, if there are any crashes, please post feedback here. I hope you enjoy the update and the app overall.
Changes:
0.8.2 | 31/03/2021 - FIX: Content of different pages now persist upon switching between them - FIX: Hotlap Upload Log: landscape notice no longer visible once in landscape - FIX: All input text fields are now single-line - FIX: Username input fields on "Online Racer Stats" and "Hotlaps by Racer" pages can now be submitted using the "Action" button on keyboard - FIX: Fixed a crash caused by an empty friends list (upon opening "Online Racer Stats" and "Hotlaps by Racer" pages)
Not that we couldn't help you here on the forums, but if you have more questions about how to start and would like to have answers faster, I recommend joining the LFS Community Discord Server Most of the time you can get near-instant replies for your questions there. You can join the Discord server by clicking this invite link: https://discord.com/invite/wZrUTJN
I tried it myself on your server:
- when closing the base, empty !times panel, it went away fine (in 0,5s I guess)
- when I had times on screen (I opened times of Stage 1), it took like 2 seconds for all elements to gradually disappear