v1.5.2

Less time spent placing floating frames

Frames the interface positions to sit clear of the ones already on screen went through a search that rebuilt its working queue from scratch on every placement, and grew that queue through the process heap several times along the way. In a crowded outdoor scene that was a measurable slice of the interface's frame cost. The queue is now reused between placements and the reallocation is gone, with the search itself unchanged.

Repeat lookups in the game's data archives are remembered

The client asks the archive layer for the same files over and over, and wow_turbo keeps a memo so the second ask does not walk the archives again. Until now only the misses were remembered: every successful lookup went the long way round, through the stock hash probe under two locks. Successful lookups are now remembered too, recorded in whatever form the caller asked for, so the ordinary file-open path is served from the memo. Mounting or unmounting an archive discards the memo, so a newly mounted patch is picked up.

Diagnostics

With RUST_LOG=wow::events=debug the per-minute summary gains a line for the floating placement search: how many placements ran, and how much work each one did.

Compatibility

Drop-in replacement for 1.5.1. No gameplay, interface or configuration change.