1. Home
  2. Categories

Categories

  • 61 Topics
    298 Posts
    R
    I’ve since tried it. It’s fine. I’m sure it’s a very competent piece of software. Despite my initial enthusiasm for it, it now leaves me a bit meh. 360hz seems smoother but I have returned to native 60hz ffb with no ill effects. I didn’t like having too many apps open. I’m looking forward to Sim-plicity getting access to native 360 ffb.

  • 19 Topics
    235 Posts
    S
    I mentioned an update was coming. v26.05.01 is that update, and it's about to go live. Important: use TM_Installer, not in-app update The jump from v25.04.01 to v26.05.01 includes changes to the update system itself. The in-app updater on v25.04.01 can't handle this jump. If you try to update in-app, it will fail and you'll be back where you started. You need TM_Installer for this one. After that, future updates work in-app as normal. Two ways to get there: Run TM_Installer now (recommended) This updates your base installation ahead of the release. When v26.05.01 goes live, you'll get the in-app notification and it will work. Download TM_Installer Or wait and run TM_Installer after v26.05.01 goes live Same result. Just on your timing. What's in v26.05.01 Some of what we have been working on since v25.04.01. The main items visible today: Firmware Loader V3 -- improved firmware installation for all devices External hardware detection -- DIY and Gen 1 OSW controllers identified when connected Profile fixes -- save, rename, delete, create all working as expected Improved sim detection -- faster start-up, more reliable game detection Help section -- built-in guides and troubleshooting Visual refresh -- updated icons, consistent dark theme Changelog There are additional features built-in that will be visible as the back-end infrastructure comes online. I'll update as/when that happens.

  • 19 Topics
    118 Posts
    R
    Hello folks, How goes the work with getting direct 360hz ffb from iRacing? Rowly

  • 2 Topics
    4 Posts
    L
    @loermansa Since there is no activity here and Sim-pli.city sales doesn't reply to emails anymore, I've decided to convert my SW20v3 to an OpenFFBoard build. The plan is to use as much of my current setup as possible such as cables, plugs, power supply, casing and motor. The rest I'll have to source elsewhere based on OpenFFBoard design. I haven't opened my case yet, so I don't know how much I can actually reuse but assuming I can reuse the above items, I've made the following BOM (Bill of Materials) and where to get them: Open FFBoard ~ € 31 Open FFBoard TMC4671 driver kit ~ € 145 OpenFFBoard case ~ € 5 MT6825 based encoder module and magnet ~ € 6 We need a separate encode because the SW20v3 encoder is not supported by OpenFFBoard. The BOM will set you back approx. € 187 so not too bad. I'll need to mount the encoder to the rear of the motor in place of the Tamagawa one and am thinking of somehow reusing the case of the Tamagawa encoder. Either that or I'll have to design and print a bracket. We'll see. OpenFFBoard is not a turn-key solution and will require software configuration but I'll cross that bridge when I get there. The community and the projectlead, Ultrawipf are very active on Discord so there's plenty of help. I'll add to this thread if and when I make progress.

  • 0 Topics
    0 Posts
    No new posts.