You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Engine] gyro engine faults at vision loading stage (windows) #3376
I had some compile issues with this earlier, but mamaged to work around those (issues reported and closed).
Now the build was complete models etc., are downloaded, and optimisation run, the model itself will not start. Same fault every time.
Console log
qwen3.8-flash-next-gyro-gyro-m
qwen3.8-flash-next-iq3_xxs
install another model / change settings
Which one? [1]: 1
[ok] GPU: GPU 0 (NVIDIA GeForce RTX 3060, 12 GB)
Starting qwen3.8-flash-next-gyro-gyro-m: it loads about 92 GB into RAM and locks part of it for the GPU.
While it does, YOUR PC CAN BE SLOW OR STOP RESPONDING FOR 1-3 MINUTES (longer the first time after a
restart). That is normal: please wait and don't close this window - the browser opens when it is ready.
Later, closing this window stops the model.
Settings (strata-gyro-gyro-m.json): --expert-cache auto --prefill auto --spec 4 --max-context 131072
--kv q4_0 --kv-resident 32768 --vision --vram-reserve-mib 400 --pcie-frac 0.75 --spec-min-p 0.70
--adapt-every 1 --adapt-swaps 160 --adapt-decay 0.97; server 127.0.0.1:8080, gpu 0
loading the vision encoder ...
Traceback (most recent call last):
File "H:\Strata\serve\server.py", line 8078, in
sys.exit(main())
~~~~^^
File "H:\Strata\serve\server.py", line 7750, in main
vision = Vision(vcfg, log=open(cfg["log"], "a", encoding="utf-8") if cfg.get("log") else None,
env=vision_env(cfg, env), lazy=lazy)
File "H:\Strata\serve\server.py", line 2521, in init
self._start()
~~~~~~~~~~~^^
File "H:\Strata\serve\server.py", line 2542, in _start
self._start_reader()
~~~~~~~~~~~~~~~~~~^^
File "H:\Strata\serve\server.py", line 2571, in _start_reader
raise RuntimeError(vision_start_error(line, self.spawn[1]))
RuntimeError: the vision encoder did not start:
Press any key to continue . . .
And the window error message
So not a smooth install/setups for me trying to get gyro working on Win 11.
Thanks for the issue. To keep the tracker readable, every item needs an area prefix in the title and the parts of the issue form filled in. This one is missing:
Start the title with its area: [Engine], [GUI], [TUI], [Benchmark], [Docs] or [Other], then a short description. Example: "[Engine] decode stops after 2 minutes".
Edit the issue (title and description) and this note goes away on its own. If it is still missing parts in 5 days it will be closed, which is not a rejection: fix it and comment /reopen.
changed the title [-][engine] gyro engine faults at vision loading stage (windows)[/-][+][Engine] gyro engine faults at vision loading stage (windows)[/+]on Oct 20, 2026
OK, resolved - Problem described and solution here #3359
The above is the same issue I had originally here: #3206 (comment), but my workaround/fix later resulted in my current issue, now resolved. Hopefully these fixes make it into the mainstream. Guessing it only affects Windows builds.
Activity
github-actions commentedon Oct 20, 2026
Thanks for the issue. To keep the tracker readable, every item needs an area prefix in the title and the parts of the issue form filled in. This one is missing:
Edit the issue (title and description) and this note goes away on its own. If it is still missing parts in 5 days it will be closed, which is not a rejection: fix it and comment
/reopen.Details: CONTRIBUTING.md
[-][engine] gyro engine faults at vision loading stage (windows)[/-][+][Engine] gyro engine faults at vision loading stage (windows)[/+]github-actions commentedon Oct 20, 2026
Thanks, this follows the format now.
pjsgsy commentedon Oct 20, 2026
OK, resolved - Problem described and solution here #3359
The above is the same issue I had originally here: #3206 (comment), but my workaround/fix later resulted in my current issue, now resolved. Hopefully these fixes make it into the mainstream. Guessing it only affects Windows builds.