Repository navigation
Same simulator as v1.0.0 — this release adds the macOS build.
Tagged at the same commit (36267c0662). No engine, plugin or configuration changes. If you are already running v1.0.0 on Windows there is nothing here for you.
v1.0.0 was published before the macOS artifact existed, and immutable releases meant it could not be added afterwards — hence a patch release rather than an edit. The Windows zip below is byte-identical to the one on v1.0.0 (sha256 4b0ea48c…, verified before re-publishing).
Downloads
| platform | file | sha256 |
|---|---|---|
| Windows 10/11 x64 | IFSSIM-v1.0.1-Windows-x64.zip |
4b0ea48cfe4f7ecd2b06f921e7a382ecc2295e824f16426aa22b2ea6878e1f31 |
| macOS, Apple Silicon | IFSSIM-v1.0.1-macOS-arm64.zip |
a345ea5ccd90c061a85d0772cf2a29818b3afca9789148911e6426ec4155567d |
macOS
Apple Silicon only. The binary is arm64; there is no Intel or universal build. On an Intel Mac it will not launch.
- Download and unzip. You get
IFSSIM.app— everything is inside the bundle, including the cooked content,settings.jsonand the track CSVs. - First launch needs one extra step. The app is ad-hoc signed, not notarised, so Gatekeeper will refuse a double-click with "IFSSIM.app is damaged" or "cannot be opened". Either right-click the app → Open → Open, or clear the quarantine flag once:
xattr -dr com.apple.quarantine /path/to/IFSSIM.app - Allow the incoming-connection prompt on first run — that is the RPC endpoint on TCP 41451 the ROS 2 bridge connects to.
Changing settings. settings.json ships inside the bundle at IFSSIM.app/Contents/UE/IFSSIM/settings.json. Rather than editing in there, put your overrides at:
~/Library/Application Support/IFSSIM/settings.json
~/Library/Application Support/IFSSIM/tracks/
Both loaders already check that location, and it survives replacing the app.
Verified on an M1 Max: launches headless, RPC server bound on TCP 41451 within 2 s.
Windows
Unchanged from v1.0.0 — see those notes for the full instructions.
Known gaps
- No Intel macOS build. Apple Silicon only.
- Not notarised on either platform, hence the Gatekeeper and SmartScreen prompts.
- The macOS artifact was built by hand.
package-mac.ymlneeds a self-hosted macOS runner with UE5 and there isn't one registered, so the workflow cancels on tag pushes. It also had a bug that would have shipped an app with no cooked content — fixed in #618.