Difference between revisions of "LFS Manual:Proposals"
Line 5: | Line 5: | ||
- [[User:MandulAA|MandulAA]] ([[User talk:MandulAA|talk]]) 18:58, 16 June 2024 (BST) | - [[User:MandulAA|MandulAA]] ([[User talk:MandulAA|talk]]) 18:58, 16 June 2024 (BST) | ||
+ | |||
+ | :For reference, here is a video with a short how-to with a Reverb G2 headset: [https://www.youtube.com/watch?v=L6eCm26O2D8 Live for Speed: How to setup VR and test drive!]. Obviously the article here should cover all 3D modes and be more detailed as you wrote. -- [[User:Flame CZE|Flame CZE]] ([[User talk:Flame CZE|talk]]) 08:22, 17 July 2024 (BST) | ||
== System for retrieving release dates of individual patches / test patches == | == System for retrieving release dates of individual patches / test patches == |
Revision as of 07:23, 17 July 2024
This is a place to discuss proposals and ideas for improving the LFS Manual.
Article / section / guide for 3D and VR modes
Basically, VR and 3D modes are not mentioned on the manual at all (even the Options#View section omits the 2D/3D switch currently). At the very least, some kind of a basic tutorial, describing how to get into the mode and with what kind of device, would be helpful to have at some point.
- MandulAA (talk) 18:58, 16 June 2024 (BST)
- For reference, here is a video with a short how-to with a Reverb G2 headset: Live for Speed: How to setup VR and test drive!. Obviously the article here should cover all 3D modes and be more detailed as you wrote. -- Flame CZE (talk) 08:22, 17 July 2024 (BST)
System for retrieving release dates of individual patches / test patches
In car and track infoboxes, the "Introduced" parameter shows with which version the car or track got introduced in LFS (for example "Introduced: 0.6V"). This could be neatly paired with a date in brackets, so for example the infobox would show "Introduced: 0.6V (Feb 28, 2021)", or with a line break between the version and date, without brackets that way. Could be implemented into Template:LFS version, or an alternative version of this template with dates. Not sure about which way the database of version-date pairs should be stored (hardcoded into the template? or in an universal, separate technical page, which could be used for retrieving dates for any purpose, not just this template?).