Articulations don't always take [SOLVEDish]

Having a problem with articulations.
Happens with Opus, and Halion Iconica
ie. I put in a Sustain, yet it will play a stacatto.
The main thing I notice is that when I open the instrument, I can see the keyswitch depressed on the virtual keyboard for an articulation I did not enter.
When I play the part through, I can see the keyswitch for Sustain depressed momentarily and then back to another key that is not entered.
Looking on the list editor, the erroneous “text” for unwanted articulation is not there.
Frustrating as heck.
Using a Panarama P6.

there must be a keyswitch problem
Are you sure you have configured the joints correctly?
because it has already happened to me to make a mistake, for example
between a C-1 and a C1

FWIW, direction articulations are the only ones that are reliable for me across all libraries. Some libraries don’t react properly to attribute.

Perhaps, but I don’t see it. The “import key switch” functions has so far worked well with Opus-Cubase.
In this case, the keyswitches are all up in the 5th and 6th octave of the keyboard.
Yes, I have also had issues where the EastWest instruments had a playable range that overlaps the keyswitch range, causing some issues.

I’ll keep troubleshooting.

Yes true. I’ve given up on attributes as they’re unusable… I’m always late.
I already expressed this type of behavior a long time ago, but nothing has changed…
In any case the forum is full of these complaints about Expression Maps.

What issues are you having with attributes? they are rock solid for me, but i remember i had to keep pre-roll engaged during playback and recording otherwise it might not trigger the first note articulation correctly.

Something in the project is changing the articulation Mid-part. I can see it happen at the same spot, but no corresponding control-msg in the MIDI list editor.
I’ve had the problem occasionally for quite a while, but now it seems worse.
I mostly work from the same custom template, and I think something is off with the expression maps.
I’m going to remake my template from scratch and see how that goes.

SOLUTION: Created a new project from scratch. Copy and pasted parts from project into the new template. So far, no problems.
I believe (cant prove) that the problem was a wonky Expression Map imbedded in my template.