settings

[zartan9]

hi, when loading from blocklyvn8bit to test, the c64 runs (on warp) speedily. but if I drag d64 into emulator it shows black and white lines (on warp), how can i set it to test the same way? Im adding delays in the game and on warp it seems its quick no matter what #
i put in? sorry if im not clear, but when I dble click the test c64 batch file, works nice,
but d64 is slow...

[haroldo-ok]

Weird, I think the batch file that calls the emulator is using the default settings, so there should be no difference; gotta take a look at them later.

[haroldo-ok]

Checking the code, it seems it is really using the default settings:

(...)
echo DONE
pause

cd "utils\emulators\WinVICE-2.4"
x64.exe "..\..\..\build\test-c64.d64"

As you can see, x64.exe "..\..\..\build\test-c64.d64" is calling the emulator simply passing the disk as a parameter, dragging and dropping should give the same results in theory.

Some emulator quirk, I guess? Vice's site does not mention anything about that behavior. It's weird.

[zartan9]

i see! if i ever get to makin a game (and try to sell it!) should i distribute the game batch file (with the d64) to make sure their emulators open right?

[haroldo-ok]

If you open the game from the emulator's menu, does it run at normal speed? Does it run at the same speed on other emulators?

[zartan9]

hi i running it from
https://c64online.com/c64-online-emulator/ its slow (says 18 on bottom, the speed?)
and vice same thing. I tried it from the batch and its really quick! if you know another emulator i can try it... thanks

[haroldo-ok]

Weird; I guess the rendering routine is slow, and would probably be slow on real hardware.. but the interesting part is that it is running differently on the emulator's warp mode depending on how it is loaded.

[zartan9]

yes. I wish i could help you speed up your projects (pun intended!) to keep them updated with more and more features (but I dont know code) if you need any graphic stuff or easy to do tasks
Id be happy to help

[haroldo-ok]

Okay, thanks for the report;

Registered an issue to optimize the screen rendering later: #18