What is an engine mod?
OpenTS3 is an independent, community-developed 64-bit engine mod for The Sims 3. It uses the original game content and gameplay code from your own installed copy.
An engine draws the world, loads resources and provides the systems that gameplay code relies on. OpenTS3 is rebuilding that foundation and the connections needed to run the original gameplay on it.
The worlds, objects, animations and original gameplay systems come from The Sims 3. We’re working to preserve their behavior as the engine develops.
For technical readers
The engine uses Vulkan and modern .NET. The launcher and portable engine work also support ongoing Linux and macOS compatibility testing.
The original C# gameplay code is stored in assemblies loaded from your installation. OpenTS3 provides a new engine and compatibility connections for that code. It is not a recreation of every gameplay system in C#.
What will the download include?
OpenTS3 will not run standalone. It needs the original game files from your legally acquired, installed copy of The Sims 3 to work.
The OpenTS3 engine mod and the supporting software we’re allowed to distribute. You’ll point it to your own installed copy of The Sims 3 so it can read the game files already on your computer.
The original worlds, objects, textures, sounds and gameplay code come from your installation. They won’t be bundled with OpenTS3. The same ownership requirement applies to any packs or paid content you use.
Development goals
- Use the memory headroom available to a 64-bit engine.
- Improve loading and responsiveness during normal play.
- Preserve familiar gameplay, worlds and creative tools.
- Support reliable saving, reloading and longer sessions.
These are goals, not current guarantees. Moving to 64-bit does not automatically improve frame rates or prevent crashes. Performance needs to be measured during gameplay.
The core engine and all expansion packs are now integrated. Tea’s major refactor has landed on main, and the team is bug testing the complete game before private alpha playtesting. Windows and native Linux are the main development platforms; macOS testing is experimental, with Apple Silicon the priority.
About JJ
I’m JJ, the project lead and meatbag in the middle.
My background is hobbyist game development in Unity. A lot of half-finished projects, nothing released, and plenty of ideas that got further in my head than they did on screen.
How OpenTS3 started
OpenTS3 started almost as a joke in April 2026. I asked AI how feasible it would be to use AI assistance, start to finish, to get The Sims 3 running on a new 64-bit engine. It basically told me it was impossible. Unfortunately for it, I’m a stubborn bald man. There was a lot of “try it this way” and “keep prodding.”
At first, this was an experiment: I kept hearing AI CEOs call this technology the next big thing, and wanted to see what it could actually do. Could it help build a new engine for a game whose source code we don’t have, using the game files from our own installations? Back in April, I also figured the models would improve as I kept working. From my experience on this project, they have.
The early build in May was laughably rough. I made a YouTube video because I thought it was cool, without expecting my fewer than 100 subscribers to care much. Of course, that was the video that took off. Suddenly this experiment was the thing people knew me for.
People immediately called it AI slop. In fairness, at that point, it was. There was also valuable feedback in the criticism. I listened, human developers joined in to help, and it grew into a community of people who love this game, mod it and still get that very specific 2009 nostalgia from it.
I know people have different views on AI and its impact, and I can’t please everyone. I do want to be clear about the work: this isn’t one prompt producing a finished game. There are human contributors, repeated tests, broken builds and plenty of decisions to make. Seeing what AI can help us do was part of the point from the start; so was finding out where it falls short.
The Sims 3 is a childhood favourite. It was frustrating to still run into its 2009 limitations on a PC in 2026. Getting to work on this has been a childhood dream, even if the route here involved considerably more arguing with a computer than I expected. I love seeing people find new ways to keep older games playable, and I’m happy to be working toward that too.
I’m a normal guy who wants this as much as the other fans following along. There’s a lot left to figure out, and I can’t promise to solve every problem. This is a love letter to The Sims 3. I want to keep playing it, and help other people keep enjoying it too.
Meet the devs
JJ started OpenTS3 and leads it alongside eight other C# developers. Here’s what each of us works on.
JJ
@JJ
Project lead
JJ started OpenTS3 and leads the project. JJ sets priorities, playtests every build, runs the community and drives work on major features.
Win
@Win
Architecture, bugs & retail parity
Win planned an earlier architecture rework and audited the codebase. Win now focuses on finding bugs and checking that OpenTS3 behaves like the original game.
Nicolas
@Nicolas
Launcher, platform ports & debug tools
Nicolas worked on early refactoring that TeaObvious later expanded, ported the launcher to Avalonia, and made the initial macOS and Linux ports. More recently, Nicolas overhauled the debug menu and engine tools.
Amber
@Amber
World compatibility
Amber is one of the original core developers and has supported the project since its early days. Amber now works on getting towns like Moonlight Falls to load reliably, with plans to keep working on worlds and take on foundational expansion work.
Fuyu
@Fuyu
Experimental lighting & audio
Fuyu is testing indirect lighting with a voxel map of the build grid, separate from the work on matching the original lighting. Fuyu is also balancing sound effects and music, developing customizable JSON mixes, and refining channels, buses and submixes.
TeaObvious
@TeaObvious
Engine refactoring, testing & code quality
TeaObvious expanded the engine refactor and works on automated gameplay for debugging, bug fixes and code cleanup. Tea also sets naming and structure rules for AI-assisted changes so files and modules describe what they actually do.
A
@A
Startup, memory & custom worlds
A works on faster startup and lower memory use through parallel and cached loading, preparing the latest save in the background from the main menu, and reducing town-view memory. A also works on Sims3Pack custom worlds, camera presets, code quality, automated checks and diagnostics.
Unreference
@Unreference
Gameplay, runtime & Vulkan
Unreference works on Sim behavior, save persistence and routing, along with Vulkan rendering, shaders, materials and graphics compatibility.
Maddie
@Maddie (minervamagicka)
Original-game parity, modding tools & graphics
Maddie works on matching the original game, modding tools, quality-of-life improvements and graphics. Maddie is also exploring physically based rendering (PBR), multi-world play, in-game physics and Create-a-Sim features inspired by The Sims 4.
Developers make the technical decisions, review changes and test builds. AI tools assist with coding, debugging and review.
The roadmap shows our development progress and the path through QA, private alpha and public release.
What will I need?
You must own a legally acquired, installed PC copy of The Sims 3 and any packs or paid content you use. OpenTS3 will not supply those files or unlock content.
We do not endorse piracy or link to pirated copies of the game.
Don’t own it yet? Buy The Sims 3 from EA ↗. Still worth playing in 2026. Trust me. — JJ
Supported game versions, hardware requirements and pack compatibility will be documented as testing establishes them. Detecting an installed pack does not prove all its features work.
Mods, custom content and saves
Mods and custom content load in current private builds. The launcher accepts drag-and-drop package mods, supported Sims3Pack content, saved Sims and saves. Mods remain off by default until enabled; compatibility depends on the individual mod and build.
OpenTS3 defaults to its own save folder at Documents/OpenTS3/Saves, with separate saved-Sim and Library storage. Original-world loading and save/reload checks have progressed, but broad save compatibility and long sessions still need QA. Keep backups and use a separate test copy of a save you care about.
Current availability
No public download is available, the source repository is private, and there is no announced release date. This website will link to the mod when a public release is ready.
OpenTS3 will always be free. No paywalls, paid builds or paid playtest places. It’s called OpenTS3. Charging you to get in would be a bit awkward.
OpenTS3’s source code will be published alongside the public engine release. The repository remains private during development, and no public release window has been announced. The source release covers our code, not the original game files.
Follow development →