I have unzipped the latest Windows build .886 and Catapult won't start. It just says Unable to load resources !
.851 was working fine. Not sure if unzipping directly over the previous install made some mess.
@wouter, thx for the tips. So it looks like I can run any Tcl but if I’m connected as a debugger through the socket how can I see the stderr output of such a script? Or the cputrace output?
Is there a way to trigger an just like when a breakpoint is hit.
@S0urceror: Sorry, I overlooked your question.
Short answer: at the moment this is not (yet) possible.
Longer answer: maybe you can use the message command? Full syntax is: message <string> <level>
This will send a log event over the socket connection. More specifically it will send something like: <log level="info">bla</log>
Currently level must be one of info, warning, error or progress. Though this command was originally only intended to show messages to the user, so currently those messages also show up on the openMSX screen. Maybe we could add a new level like debug that (by default) does not show up? (Not a solution, but for now you can experiment with changing the message_callback setting, this callback transforms the log event into an on-screen message box. Execute about message_callback for a bit more information).
@S0urceror: What do you think? Feel free to make other suggestions.
When I record, fast-forward does not work. Is that intentional?
This should be fixed now, can you confirm?
Sorry, I missed your message earlier. I just checked and played around with changing to various speeds before and during recording, and the resulting video seems to be correctly generated while the emulator’s speed changes as expected.
Hello,
I've an issue with openMSX. When i'm playing aleste, the scrolling isn't smooth. I'm under windows X with catapult launcher (all last versions released, tested with SDL and SDLGL-PP Renderer)
If you want any further informations.
Thanks
