continuously changing output to the screen. It has everything to do with a blinking cursor, i.e. The issue has nothing to do with whether or not there's a disk image involved. That version does not blink the cursor and the end result is the same problem. Try it with Model 1 emulation and TRSDOS version 2.3. The original TRS-80 did not have input or display delays like this, so the emulator shouldn't The input works 'fine' if the cursor is blinking (see below). The Raspberry Pi 4 has so much more power than the TRS-80 that it can easily emulate it in full with an enormous amount of room to spare, enough that it is supposed to be able to easily get cycle-exact emulation. That alone is a bug, and I fully expect it's being caused by the same thing. Note, finally, that there should be no noticeable delay between when you type a key in sdltrs and when the character appears on the screen. This makes me think we're up against a fundamental bug in SDL2 on this platform (or, at least, the version that sdltrs requires). There, clicking on a button that is supposed to bring up a second dialog will often result in the second dialog not showing up unless you press a direction key or something that would cause the display to change.īoth are linked against SDL2. Just a line or two will do, generally.Īlso note that I've seen a similar phenomenon with hatari (not lr-hatari), with respect to its configuration GUI (which you get into via F11). You can reproduce it by typing relatively quickly. Note that I don't see the problem immediately.

I'll happily supply logs and configurations if asked, but this should be trivially I have that set to the default of 4000, but I've played with it and it makes no difference whatsoever what value I set it to. This suggests that the display refresh in the emulator is dependent upon something being drawn to the display, as if there's a drawing queue that isn't being flushed or something. I've noticed, too, that when typing in the Model 3 and 4/4P emulators, the character I type can be delayed for a small period of time until the cursor blinks, at which point it'll appear. There is one thing that is notable about the Model 3 and 4/4P emulators: the cursor they display blinks, while the Model 1 cursor does not. This issue does not happen with the Model 3 or Model 4/4P emulators. Once this happens, it stays behind no matter how long one waits.

If one uses the TRS-80 Model 1 emulator (with either level1.rom, which has MD5 checksum of 1136f64e2c249848f956343862742e1e, or level2.rom, which has MD5 checksum of ca74822ebc2803c6635a55116ecd9539), when one is typing, it won't be long before the emulator 'falls behind' what one is typing by one character, such that the emulator doesn't display the character one typed until one types another character. USB Devices connected: Keyboard, mouse, Atari joystick via Monster Joystick adapter (shows up as 'Van Ooijen Technische Informatica Joystick' in 'lsusb' output)Ĭontroller used: Atari 800 joystick (keyboard for Emulationstation navigation)Įmulator: sdltrs (executable file name is sdl2trs) Power Supply used: CanaKIt USB-C 3.5 ampsīuilt From: Pre-made SD card image from RetroPie web site Pi Model or other hardware: Raspberry Pi 4, 2GB model

Retropie sdltrs