[BUG]SUN PRO V2.1.6 Meters display

[F6Bernie]

Hi Kosta, as I've said previously, there was a big display issue when I tried to install various meters (container).
This afternoon I've installed Thetis (just to take a look) and I've installed one of the faulty meters which was OK.
But, when I started again Artemis, the meter was OK (without doing anything peculiar).

During the first install of Thetis in my computer, I noticed (when I ran this program for the first time) that the process said he was intalling "OE3IDE various skins" and I'm not sure Artemis did the same when I ran it the first time...

Just for your information ;) This issue seems fixed to me.

Best 73' Bernie

[kk68]

Hi Bernie, root cause found and fixed in v2.1.7:

📦 https://github.com/kk68/ArtemisSDR/releases/tag/v2.1.7

MeterManager.cs had a leftover hardcoded %APPDATA%\OpenHPSDR\ path for skin + meter asset lookup — a holdover from upstream Thetis that never got renamed when Artemis split off. Every other path bootstrap in the app correctly uses %APPDATA%\ArtemisSDR\ (DBMan, Skin, MemoryList, etc.), but MeterManager was missed. So the bundled OE3IDE-TheBlue meter assets were extracting to the right place but the renderer was hunting in a non-existent OpenHPSDR folder. Your "first install broken, second-launch-after-Thetis worked" pattern matched exactly: Thetis's MeterSkinInstaller populates %APPDATA%\OpenHPSDR\, which then accidentally satisfied Artemis's wrong lookup path.

Fresh Artemis installs after v2.1.7 should get a working cross-meter (and all the other elaborate meter types) straight from the bundled OE3IDE-TheBlue assets — no Thetis side-trip required. For existing users with Thetis history on the same machine (you), a legacy fallback in v2.1.7 keeps the OpenHPSDR meter folder as a secondary lookup path, so nothing regresses during the transition.

Thanks for the careful report — the "Thetis fixed it" observation was the smoking gun that pointed straight at the path mismatch.

Heads up: I'm less involved with Artemis day-to-day right now while work commitments take priority, so follow-up turnaround on remaining items may be slower than the recent cycle. I'll still see and respond to reports here, just not at the same pace.

73, Kosta