Eventuell "restore emulator window.... from settings" abgewählt?
(RestoreWindowGeometry=0 in vice.ini)
Du bist in Begriff, Forum64 zu verlassen, um auf die folgende Adresse weitergeleitet zu werden:
Bitte beachte, dass wir für den Inhalt der Zielseite nicht verantwortlich sind und unsere Datenschutzbestimmungen dort keine Anwendung finden.
letzter Beitrag von compyx am
Eventuell "restore emulator window.... from settings" abgewählt?
(RestoreWindowGeometry=0 in vice.ini)
You can indeed save the emulator's window size and position by enabling Preferences -> Settings -> Display -> Host display -> "Restore emulator window(s) position and size from settings" and the saving the settings.
When you restart vice, the window size and position should be restored to when you last saved the settings. This works for me on Debian, Win7 and Win10.
I have a question about the new binary monitor interface.
How can I send control characters via the "keyboard feed" function? I only manage to send standard characters, but no control characters like clear screen, home or cursor keys.
byte 0: Length of text
byte 1+: The text
Special characters such as return are escaped with backslashes.
I'd try "\\x93" for CLRSCR
byte 0: Length of text
byte 1+: The text
Special characters such as return are escaped with backslashes.
I'd try "\\x93" for CLRSCR
Ok that works! Thanks.
The binary monitor interface is great!
Ich nehme an das das Speichern der Größe vom Screen so einfach wird wie beim Vice 3.2
Ich nehme an das das Speichern der Größe vom Screen so einfach wird wie beim Vice 3.2
Ja genau so funktioniert das... Fenster aufziehen, speichern. Mehr nicht.
Falls das nicht geht, liegt es wohl an Posting #82 oder das Speichern klappt generell nicht (fehlende Rechte?)
Wobei das mit dem "Fenster aufziehen" totaler Murks ist. Im Gegensatz zu allen anderen Emulatoren ist es beim Vice ein absoluter Krampf, Scanlines in einem skalierten Fenster ohne wüste Aliasing-Artefakte dargestellt zu bekommen. Da muß man minutenlang pixelgenau rumwerkeln, bevor das Ergebnis OK aussieht Kurioserweise hat sogar die Fensterbreite eine Auswirkung. Und ab und zu ist dann wieder irgendwas verstellt und man kann von vorne anfangen.
VICE 3.5 doesn't work for me at all on my Linux system. My monitor is only capable of running at 30 fps (cheap'n'old 4k). With VICE 3.5 now my emulated PAL C64 runs to 60% speed, as the C64 also runs at 30 ftps instead of 50. Switching back to 3.4 did the trick for me, so I'm stuck to it until I upgrade my display (not gonna happen anytime soon)...
Are you using the Gtk3 UI or the SDL UI? The Gtk3 UI's rendering runs in a different thread and should not impact the CPU speed in any way.
Try running `x64sc -default` to start with default settings, ignoring any vicerc you may have.
-----------------------------------------------------------------------
Wobei das mit dem "Fenster aufziehen" totaler Murks ist.
----------------------------------------------------------------------
Ich spiele ohne Scanline.
Für mich ist wichtig das Technische.
Spiele gerade mit Netzwerk von C64 zu C64.
Welcher C64-Emu kann noch RS232 und Netzwerkübertragung?
Gruss
Looking at those screenshots, it's obvious you're using at most 3.2, not 3.5, so I cannot help you.
VICE 3.5 doesn't work for me at all on my Linux system. My monitor is only capable of running at 30 fps (cheap'n'old 4k). With VICE 3.5 now my emulated PAL C64 runs to 60% speed, as the C64 also runs at 30 ftps instead of 50. Switching back to 3.4 did the trick for me, so I'm stuck to it until I upgrade my display (not gonna happen anytime soon)...
now that's weird. what happens if you use a custom fps as maximum speed?
I forgot to mention that it only happens with the SDL version. GTK has the correct speed, but is at least for me less usable. But, setting the speed to 80% or 120% doesn't make any difference, it always is running at 60%, though the status bar is adjusting slowly to the correct values.
VICE 3.5 doesn't work for me at all on my Linux system. My monitor is only capable of running at 30 fps (cheap'n'old 4k). With VICE 3.5 now my emulated PAL C64 runs to 60% speed, as the C64 also runs at 30 ftps instead of 50. Switching back to 3.4 did the trick for me, so I'm stuck to it until I upgrade my display (not gonna happen anytime soon)...
now that's weird. what happens if you use a custom fps as maximum speed?
I forgot to mention that it only happens with the SDL version. GTK has the correct speed, but is at least for me less usable. But, setting the speed to 80% or 120% doesn't make any difference, it always is running at 60%, though the status bar is adjusting slowly to the correct values.
i did some researching.
even with old SDL versions the speed got synced to the screen (vsync activ) if we set -refresh 1. and it seems 0 was the default.
but with newer versions, -refresh got completely removed.
I forgot to mention that it only happens with the SDL version. GTK has the correct speed, but is at least for me less usable. But, setting the speed to 80% or 120% doesn't make any difference, it always is running at 60%, though the status bar is adjusting slowly to the correct values.
this should be fixed now, i haven't it tested myself though.
I forgot to mention that it only happens with the SDL version. GTK has the correct speed, but is at least for me less usable. But, setting the speed to 80% or 120% doesn't make any difference, it always is running at 60%, though the status bar is adjusting slowly to the correct values.
this should be fixed now, i haven't it tested myself though.
I finally managed to compile a Linux deb package for testing. The result is rather funny: is starts with 50 fps, then drops down to 40% in about 2.5 seconds, then gets back to 50 fps again, dropping to 40 ftps... and so on.
Sorry for the delay...
it used to work (as far as i can tell), but the commit r39874 was reverted here:
A friend of mine just had issues with WinVICE 3.5 and an 8bitdo SN30 pad:
The configuration dialog shows the pad as "Bluetooth XINPUT-kompatibles Eingabegerät", and it's also possible to select this entry from the dropdown box, but the dialog won't keep this setting after closing or switching to a different settings page. My suspicion is that the special character "ä" is the problem (it gets displayed with a <?> placeholder):
This is the VICE version:
You can try some Nightly build.
there have been a lot of changes in the joystick handling.
Thanks for the hint, it works in the newest nightly build!
I've added translating the names to UTF-8 to the joystick combo boxes. Curious to see if it works.
You can download the latest snapshot here: https://github.com/VICE-Team/svn-mirror/releases/tag/r40032