On this page you see the project I started working on in late July 2025. After becoming fully immersed in Le Mans Ultimate, I no longer felt motivated to enhance the Simracevault.com website with ACC content.
After several false starts, I finally got myself back to the keyboard and drawing board to resume coding. It was quite challenging, I needed to quickly get up to speed again to implement new data structures and methods for storing and retrieving data from the LMU setups.
The first challenge was the sheer volume of information, and that's where AI came to the rescue using the popular "vibecoding” thought process I was able to rather quickly convert all the data into tables and retrieve them. Also luckily I could re-use parts of the code that is currently on the simracevault.
I also added a "backoffice" where I can add users and perform administrative tasks for future use. In a later iteration, I plan to enable setup creators to upload their setups directly and edit their profiles and social media links. For now, this feature is disabled via a feature toggle in the first releases.
The scaffolding is pretty much done, the addition is up-and-running.
Main task now is adding content and getting consent of the some of the creators. Next up is promotion.
Of course I will check/fix/enhance small things on the site during the next few weeks/months.
Furthermore the site will also contain more content, I manage this via my Notion site that I maintain (which you are now on) this prevents me from changing/adding code so I can just focus on the content. So coding is purely done for the actual setups and pages. all other content like the “hidden” manual and new ABS settings are done via Notion (but integrated in the simracevault)
Another challenge is accommodating "Meta" setups—basic configurations for cars or tracks that perform well overall. These setups differ because their creators don't post specific lap times. For example, we might feature a GT3 McLaren high-downforce setup that works across several tracks. The challenge lies in how to effectively integrate and visualize these types of setups within the system.
Next big (very big) task is the ability to technically read setups from the original files and populate the settings in the database, this would make my life much easier on populating the DB which is now a 100% manual backend task.
Also I’m thinking of adding a compare function for the same car on the same track so you can see what settings differ between the setups.
I already got questions on making the setups available as download, but this is far more complex then some of you may know. The original LMU setup files contains so much data in somewhat cryptic formats and strange conversions factors that is a for now impossible to create them for direct use.
Also I got questions on do you support consoles in the future? To be honest, I have no clue. It all depends on the release schedule and if I will be able to “read” original files and convert them into the format to show them on the web. So yes, it is on the roadmap but have no clue when.
Want to know more? on this page I have created some simple content on each of the pages