If you do decide to submit an official bug report, keep in mind that these forums are not the right place for that.
Thank you for the comment but this ain't my first simulator rodeo.
I started this topic to alert the people trying to use Microchip tools to do real work about a problem that could cost them a few hours before they realize that MPLABX is broken in a new way.
George Pauley does try very hard to help but I suspect he has little sway when it comes to getting the simulator fixed for systemic problems. The Microchip attitude regarding the simulator seems to be one where if issues are ignored for long enough the users will just give up and go away.
This specific issue has been extant in MPLABX for at least releases 5.25, 5.30 and 5.35 and gone undetected by Microchip for that time. What this show me is that if Microchip even does regression tests, what they do is ineffective.
Perhaps it's understandable that "legacy" controllers are not first in line for simulator regression testing but the PIC18F47Q10 was announced around November 2019. The oldest official document I could find that mentioned the PIC18F47Q10 is AN3174 Getting Started with PIC18 Q10
and that was created in August 2018. So not even "new" controllers seem to be tested to actually work with the simulator.
I am sure that Microchip spends a lot to maintain the simulation tool it's just not getting what it's paying for and they are not motivated to fix that.
In all likelihood this not a simulator bug but the MPLABX IDE failing to display the "UART 1 output" message box in the project output pane. Such is Java, a write once and wrong everywhere programming environment.
post edited by dan1138 - 2020/05/26 07:26:19