| |
blacky
Registered: Sep 2007
Posts: 41 |
VICE 3.0 has been released
VICE 3.0 has been released.
VICE is a program that runs on a Unix, DOS, Win32, OS/2, BeOS, Amiga
or Mac OS X machine and executes programs intended for the old 8-bit
computers. The current version emulates the C64, the C64DTV, the C128,
the VIC20, practically all PET models, the PLUS4 and the
CBM-II (aka C610/C510). An extra emulator is provided for C64 expanded
with the CMD SuperCPU.
VICE is *free* software released under the GNU General Public License,
and as such it comes with full source code.
The most important changes from the last version can be found at the end
of this posting.
For more information and download instructions check out the VICE home
page at:
http://vice-emu.sourceforge.net/
This release marks the start of a new release schedule. We will be
releasing a new source version every 3 months. The binaries that will
be built for a new version will depend on the downloads of the
previous version and available maintainer for the port. This means that
ports without maintainers and/or not enough downloads will no longer be
made. This means that this might be the last release for mac os x and
windows, since we do not have any official maintainers (or people
helping out) for those ports.
=======================================================================
Note that some of the binaries are not available yet, we are still
working on them, they will be added to the download page(s) as soon as
they become available.
=======================================================================
The VICE team.
----------------------------------------------------------------------
* Upgrading
===========
If you run into trouble please try removing any VICE configuration files
left from previous installs.
(vice.ini / .vicerc / vice2.cfg / vice-sdl.ini depending on platform)
* Changes in VICE 3.0
======================
** General
----------
- New SDL based Android port.
- New Windows RT port.
- New Sortix port.
- New SDL2 support.
- New SCPU64 emulator (xscpu64).
- New KoalaPad emulation.
- New high pass filter emulation for DAC based devices (SFX sound sampler,
DigiMAX cartridge, DigiMAX shortbus device, userport DAC,
userport DigiMAX device, DigiBlaster SIDcart add-on).
- New sampler sound input support, used by sfx sound sampler, digiblaster
and userport/joyport sampler devices.
- New tapeport system supporting the following devices: datasette, tapelog,
cp-clockf83, tape-sense dongle, (not yet working) dtl basic dongle.
- New Inkwell Systems lightpen emulation.
- New scroll wheel support for the Micromys mouse emulation.
- New "printer/plotter" Commodore 1520 emulation.
- New 1540 drive emulation.
- New native (koala/doodle) screenshot support.
- new godot screenshot support.
- New keyrah keymaps.
- Extended the 'RS232 net' support to all platforms that support networking.
- RTC offset and RAM contents can now be saved.
- Documentation in PDF and TXT format.
** C64(SC)/C128 changes
-----------------------
- New IDE64 v4.2 emulation.
- New IDE64 USB server emulation.
- New IDE64 DigiMAX short bus device emulation.
- New IDE64 ETFE short bus device emulation.
- New RGCD cartridge emulation.
- New Final Cartridge III+ emulation.
- New rrnet mk3 cartridge emulation.
- New easy calc result cartridge emulation.
- New GMod2 cartridge emulation.
- New MMC64, MMCReplay, RetroReplay and IDE64 clockport emulation.
- New RRNET clockport device emulation.
- New MP3@64 clockport device emulation.
- New joyport system which currently supports attaching the following
devices to the native ports: joystick, paddles, 1351 mouse, neos mouse,
amiga mouse, atari cx22 mouse, atari-st mouse, smartmouse, micromys
mouse, koalapad, generic lightpens, datel light pen, magnum light phaser,
stack light rifle, inkwell light pen, 2bit sampler, 4bit sampler, bbrtc,
paperclip64 dongle, coplin keypad, cardco cardkey 1 keypad, atari cx85
keypad, rushware keypad, atari cx21 keypad. And the following devices to
the various userport joystick adapters: joystick, neos mouse, amiga mouse,
atari cx22 mouse, atari-st mouse, 2bit sampler, 4bit sampler, bbrtc,
paperclip64 dongle, coplin keypad, rushware keypad.
- New Userport system which currently supports attaching the following
devices: rtc58321a, ds1307 rtc, dac, digimax, 4bit mono sampler, 8bit
stereo sampler, cga joystick adapter, pet joystick adapter, hummer
joystick adapter, oem joystick adapter, hit joystick adapter, kingsoft
joystick adapter, starbyte joystick adapter.
** C128 changes
---------------
- New Swiss ROM support.
** C64(SC) changes
------------------
- New Sony CXA2025AS NTSC palette.
- New CP/M (Z80) cartridge emulation.
** C64SC changes
----------------
- New VICII VSP-bug emulation.
** C64DTV changes
-----------------
- New joyport system which currently supports attaching the following
devices to the native ports: joystick, 2bit sampler, 4bit sampler,
bbrtc, paperclip64 dongle, coplin keypad, rushware keypad. And the
following devices to the hummer userport joystick adapter: joystick,
2bit sampler, 4bit sampler, bbrtc, paperclip64 dongle, coplin keypad,
rushware keypad.
- New Userport system which currently supports attaching the following
devices: hummer joystick adapter.
** VIC20 changes
----------------
- New UltiMem cartridge emulation.
- New I/O-2 RAM cartridge emulation.
- New I/O-3 RAM cartridge emulation.
- New BehrBonz cartridge emulation.
- New mike's VFLI modification emulation.
- New joyport system which currently supports attaching the following
devices to the native port: joystick, paddles, 1351 mouse, neos mouse,
amiga mouse, atari cx22 mouse, atari-st mouse, smartmouse, micromys
mouse, koalapad, generic lightpens, datel light pen, magnum light phaser,
stack light rifle, inkwell light pen, 2bit sampler, 4bit sampler, bbrtc,
paperclip64 dongle, coplin keypad, cardco cardkey 1 keypad, atari cx85
keypad, rushware keypad, atari cx21 keypad. And the following devices to
the various userport joystick adapters: joystick, neos mouse, amiga mouse,
atari cx22 mouse, atari-st mouse, 2bit sampler, 4bit sampler, bbrtc,
paperclip64 dongle, coplin keypad, rushware keypad.
- New Userport system which currently supports attaching the following
devices: rtc58321a, ds1307 rtc, dac, cga joystick adapter, pet
joystick adapter, hummer joystick adapter, oem joystick adapter.
** PLUS4 changes
----------------
- New userport emulation.
- New joyport system which currently supports attaching the following
devices to the native port: joystick, neos mouse, amiga mouse, atari cx22
mouse, atari-st mouse, 2bit sampler, 4bit sampler, bbrtc, paperclip64
dongle, coplin keypad, rushware keypad. The following devices to the
various userport joystick adapters: joystick, neos mouse, amiga mouse,
atari cx22 mouse, atari-st mouse, 2bit sampler, 4bit sampler, bbrtc,
paperclip64 dongle, coplin keypad, rushware keypad. And the following
devices to the sidcart joystick port: joystick, paddles, 1351 mouse,
neos mouse, amiga mouse, atari cx22 mouse, atari-st mouse, smartmouse,
micromys mouse, koalapad, 2bit sampler, 4bit sampler, bbrtc, paperclip64
dongle, coplin keypad, cardco cardkey 1 keypad, atari cx85 keypad,
rushware keypad, atari cx21 keypad.
- New Userport system which currently supports attaching the following
devices: dac, pet joystick adapter, hummer joystick adapter, oem
joystick adapter.
** PET changes
--------------
- New PET HRE (High Res Emulator) board emulation.
- New 2-chip colour board emulation.
- New joyport system which currently supports attaching the following
devices to the various userport joystick adapters: joystick, neos
mouse, amiga mouse, atari cx22 mouse, atari-st mouse, 2bit sampler,
4bit sampler, bbrtc, paperclip64 dongle, coplin keypad, rushware
keypad.
- New Userport system which currently supports attaching the following
devices: rtc58321a, ds1307 rtc, dac, cga joystick adapter, pet
joystick adapter, hummer joystick adapter, oem joystick adapter.
** CBM6x0/7x0 changes
---------------------
- New joyport system which currently supports attaching the following
devices to the various userport joystick adapters: joystick, neos
mouse, amiga mouse, atari cx22 mouse, atari-st mouse, 2bit sampler,
4bit sampler, bbrtc, paperclip64 dongle, coplin keypad, rushware
keypad.
- New Userport system which currently supports attaching the following
devices: rtc58321a, ds1307 rtc, dac, digimax, 4bit mono sampler, 8bit
stereo sampler, cga joystick adapter, pet joystick adapter, hummer
joystick adapter, oem joystick adapter.
** CBM5x0 changes
-----------------
- New joyport system which currently supports attaching the following
devices to the native port: joystick, paddles, 1351 mouse, neos mouse,
amiga mouse, atari cx22 mouse, atari-st mouse, smartmouse, micromys
mouse, koalapad, 2bit sampler, 4bit sampler, bbrtc, paperclip64 dongle,
coplin keypad, cardco cardkey 1 keypad, atari cx85 keypad, rushware
keypad, atari cx21 keypad.
** PETCAT changes
-----------------
- New Kipper Basic support.
- New Basic on Bails support.
- New The Tool 64 support.
- New Eve Basic support.
** VSID changes
---------------
- New RSID BASIC tunes support.
- New Compute Gazette SIDplayer files (mus/str) support.
- New psid v4 3sid support.
** Unix changes
---------------
- New multi-threaded GUI display.
- New joystick status items in the GTK GUI.
- New hardware SID I/O access system which allows PCI CW3,
ISA/PCI HardSID, ParSID and SSI2001 to work with and
without device drivers.
** MS-Windows changes
---------------------
- Documentation in CHM and HLP format.
- New hardware SID I/O access system which allows PCI CW3,
ISA/PCI HardSID, ParSID and SSI2001 to work with and
without device drivers.
** AmigaOS changes
------------------
- New hardware SID I/O access system which allows
clockport/Zorro/PCI CW3, ISA/PCI HardSID and SSI2001 to
work with and without device drivers.
- Documentation in AmigaGuide format.
** BeOS/Haiku changes
---------------------
- GUI fixes and improvements.
- New support for Haiku native x86_gcc2, x86, and x86_64 binaries.
- New "bsp" sound driver inspired by SDL (and used by default on Haiku,)
which should produce sound on all systems where SDL programs can.
This has been tested on Haiku R1 Alpha3 where the old "beos" driver
produces only crashes.
- New hardware SID I/O access system which allows PCI CW3,
ISA/PCI HardSID, ParSID and SSI2001 to work with and
without device drivers.
- Due to the addition of the hardware SID I/O access system, binaries built
for BeOS no longer run under Haiku. Please use Haiku native binaries.
** DOS changes
--------------
- New hardware SID I/O access system which allows PCI CW3,
ISA/PCI HardSID, ParSID and SSI2001 to work with and
without device drivers.
** OS/2 changes
---------------
- Documentation in INF format.
Enjoy!
Signed, Marco van den Heuvel. |
|
| |
TheRyk
Registered: Mar 2009
Posts: 2076 |
Thanks a lot for that! Good news, with regard to future, especially for Linux Users! |
| |
Mr.Ammo
Account closed
Registered: Oct 2002
Posts: 228 |
You might want to remove the mac version of 3.0 and put 2.4 back on the website until 3.0 actually works. It crashes immediately after launch on my mac, complaining about:
Dyld Error Message:
Library not loaded: /usr/local/opt/portaudio/lib/libportaudio.2.dylib
Referenced from: /Applications/Vice3/x64.app/Contents/MacOS/x64
Reason: image not found
So, there's no need to excite mac users with a new build just yet ;-) |
| |
Jammer
Registered: Nov 2002
Posts: 1289 |
Now that's a news! \o/
I spotted no new crt emulation yet :( (however, saturation parameter has surely been corrected) :( VSP bug works flawless - Monumentum crashes as planned :D |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
er perhaps just delete the osx port and be done with it.... |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quoting Mr AmmoYou might want to remove the mac version of 3.0 and put 2.4 back on the website until 3.0 actually works. It crashes immediately after launch on my mac, complaining about:
Dyld Error Message:
Library not loaded: /usr/local/opt/portaudio/lib/libportaudio.2.dylib
Referenced from: /Applications/Vice3/x64.app/Contents/MacOS/x64
Reason: image not found
So, there's no need to excite mac users with a new build just yet ;-)
Which bin did you download? |
| |
Mr.Ammo
Account closed
Registered: Oct 2002
Posts: 228 |
Quoting Compyx
Which bin did you download?
The only one available through the vice-emu website?
http://vice-emu.sourceforge.net/macosx.html There's a download link to a disk image with binaries for all vice emulators. |
| |
Jammer
Registered: Nov 2002
Posts: 1289 |
Ok, emulation of VSP bug seems a bit unforgiving - Lunatico will crash using any available VSP channel :( |
| |
Mr.Ammo
Account closed
Registered: Oct 2002
Posts: 228 |
Quoting Groepazer perhaps just delete the osx port and be done with it....
Yeah, that's probably the best solution ;-) |
| |
blacky
Registered: Sep 2007
Posts: 41 |
Quote: Quoting Compyx
Which bin did you download?
The only one available through the vice-emu website?
http://vice-emu.sourceforge.net/macosx.html There's a download link to a disk image with binaries for all vice emulators.
The page has been updated with new bins (as supplied by IanC). |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
Jammer: the "channels" thing is not accurately emulated right now |
| |
Mr.Ammo
Account closed
Registered: Oct 2002
Posts: 228 |
Quoting blackyThe page has been updated with new bins (as supplied by IanC).
The link says: "The "/releases/binaries/m..4-10.8-clang-3.0.dmg" file could not be found or is not available. Please select another file."
The webpage should probably link to this file: vice-macosx-cocoa-x86_64-10.12-3.0.dmg in lieu of the old one (vice-macosx-cocoa-i386+x86_64-10.8-clang-3.0.dmg)
Thanx! |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Did you refresh the page? I can't reproduce this. |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
OS X version seems to work out of the box here, but x64 crashes when I go into SID settings. |
| |
riq
Registered: Feb 2015
Posts: 10 |
Quote: You might want to remove the mac version of 3.0 and put 2.4 back on the website until 3.0 actually works. It crashes immediately after launch on my mac, complaining about:
Dyld Error Message:
Library not loaded: /usr/local/opt/portaudio/lib/libportaudio.2.dylib
Referenced from: /Applications/Vice3/x64.app/Contents/MacOS/x64
Reason: image not found
So, there's no need to excite mac users with a new build just yet ;-)
yes, I guess I built that first binary. I requires portaudio
$ brew install libportaudio
should do the trick. |
| |
Jammer
Registered: Nov 2002
Posts: 1289 |
I have complaint that sid/vic noise is a bit of overdone or emulating very low quality output ;) It doesn't sound exactly like this:
https://www.youtube.com/watch?v=7lY5-wg_LHE
Any plans to make it tweakable? High pitched tone matches the origano on the other hand ;) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
no, nothing planned like that. it varies a lot between individual setups anyway. feel free to provide a patch :) |
| |
Jammer
Registered: Nov 2002
Posts: 1289 |
If it requires only some config tweaking, I might surely give it a try :) So far it sounds a bit like very sensitive gate-off. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
its just some random noise plus line frequency AM modulated by average brightness. not exactly what really happens - but simulating the bus noise for example would eat a LOT of CPU for very little gain :) |
| |
Frantic
Registered: Mar 2003
Posts: 1627 |
I must be blind or something? I go to:
http://vice-emu.sourceforge.net/index.html#download
...and click on the link in "Binary for Mac OS X systems: Please visit the Mac OS X download page.", ending up at:
http://vice-emu.sourceforge.net/macosx.html
...but no matter how hard I look at that page I do not see the 3.0 version, though other people in this thread mention a mac version? Where is that one hidden? |
| |
Fred
Registered: Feb 2003
Posts: 284 |
The link is correct. Just clear your cache from your browser and you will see the new page. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Yes, you seem to be blind. Use your browser's Find function to search for "3.0.dmg", there's a binary using Cocoa and a binary using SDL. |
| |
MagerValp
Registered: Dec 2001
Posts: 1056 |
No (new :) issues with the mac port here, 3.0 running fine on mine. Thanks to whoever stepped up and compiled a release.
PS: vice-macosx-cocoa-x86_64-10.12-3.0.dmg link is visible on http://vice-emu.sourceforge.net/macosx.html for me at least. |
| |
Frantic
Registered: Mar 2003
Posts: 1627 |
I can confirm that it was a cache issue. Sorry to cause fuzz about nothing! I thought I had cleared it, but I must have fucked up somehow. Now I can see it just fine!
To bad (for me) that binary was only for the very latest version of macOS! :) Thanks anyway to the person who complied this for us mac users. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Hmmm, mouse emulation seems to be completely broken now. OK back to 2.2 again, at least for pixelling. :)
EDIT: on Win7, that is. |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
I tried geos 1.2 and works for me, Control port setting, port #1 set to mouse 1351
Also tried Operation wolf USA/Nostalgia, mouse 1351 in port 2. works nicely.
What specifically doesn't work for you? |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Well, the only effect of Alt-Q seems to be the Windows cursor disappearing, but the cursor in AmicaPaint wouldn't move at all. No matter, I can keep 2.2 for that purpose; still have to figure out how to make the new VICE the default program to start .d64, .prg and so on - if anyone has a hint, I'd appreciate of course. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I have used an Amica Paint 1.8 version patched for the Amiga Mouse without problems in VICE trunk, a few months ago.
Of course I can't find the disk now. It was a disk which allowed one to select between joystick and mouse. Don't remember who cracked/patched it, but it wasn't a recent release.
I'll try to locate it. But I've never had any problems grabbing the mouse in VICE. |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
Quote: Well, the only effect of Alt-Q seems to be the Windows cursor disappearing, but the cursor in AmicaPaint wouldn't move at all. No matter, I can keep 2.2 for that purpose; still have to figure out how to make the new VICE the default program to start .d64, .prg and so on - if anyone has a hint, I'd appreciate of course.
I told in my reply what to do, in settings/Control port settings you have to set which port is joystick, mouse or anything else.
To make Vice default for those extension is like any other program under windows, right click on file, "open with", select x64.exe or x64sc if you prefer it, and set it as default for this extension. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Ah sorry, "control port settings" it was indeed. Will have to play around more, to figure out things; so far it seems to overtax my system, with framerates between 10 - 40 fps only.
Re: default setting, that doesn't seem to work - if I choose x64 from the file browser, it simply brings me back to the previous menu, and the VICE icon is not there to choose. I had that problem before, if I only could remember how I solved it... |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quoting bugjamAh sorry, "control port settings" it was indeed. Will have to play around more, to figure out things; so far it seems to overtax my system, with framerates between 10 - 40 fps only.
The control port settings shouldn't cause any FPS drops, what are you running VICE on, a 486?
Quote:
Re: default setting, that doesn't seem to work - if I choose x64 from the file browser, it simply brings me back to the previous menu, and the VICE icon is not there to choose. I had that problem before, if I only could remember how I solved it...
Where did you install the latest VICE? Usually OS's have an option to select an 'atlernative' program to asscociate with *.d64 etc, maybe use that? As in "C:\Documents and a ridiculous long path\x64sc.exe" |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Its a dual core i3 at 2.53 GHz.
The slowdown did not refer directly to the controlport settings, just to VICE in general - but it appears to be an OS or h/w problem for sure. Old VICEs occassionally dropped massively in their performance as well, albeit not so fast at 3.0, it seems.
I have VICE on my D drive, but I tried copying it to other locations on C as well, including to Program files - to no avail. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quoting bugjamIts a dual core i3 at 2.53 GHz.
The slowdown did not refer directly to the controlport settings, just to VICE in general - but it appears to be an OS or h/w problem for sure. Old VICEs occassionally dropped massively in their performance as well, albeit not so fast at 3.0, it seems.
Perhaps, I usually run VICE on a dual core E6750 @ 2.66MHz, and even x64sc with memmap and debugging it runs at full frame rate with ReSID at its most accurate settings and CRT emulation enabled. Basically the same performance in Haiku or FreeBSD VMs running on an i-3 laptop.
Quote:
I have VICE on my D drive, but I tried copying it to other locations on C as well, including to Program files - to no avail.
Don't move VICE to anything you don't have write access to. This is a know Windows bug. All ports use $HOME to store their settings and such, except the Windows port. Which our (missing) Windows maintainer should fix. |
| |
Steppe
Registered: Jan 2002
Posts: 1510 |
I'm missing the resid-fp settings. Are they incorporated into the regular resid now? If so, is there a way to pick my preferred blend of 6581 somewhere? |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
There is no more resid-fp in vice since 2.4.5, circa 3 years ago. Now there are 3 settings in the sid settings/resid tab that can be altered, but don't ask me what they are for =)
from http://vice-emu.pokefinder.org/index.php/Developer_log_old
Quote:
r27549
Resid-FP has been removed.
To compensate for the missing SID-Type selection, GUI items (slider) should be added for the following Resources: SidResidPassband (0..90), SidResidGain (90..100), SidResidFilterBias (-5000...5000)
|
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
@Compyx: I was really hopeful when I found that there was indeed no write permission for /users in the VICE folder - unfortunately the change did not have the desired effect. I'll reboot and see if that helps maybe. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I just installed the latest nightly build inside a Win7 64-bit VM and I can't get the mouse emulation to work in Amica paint 1.4 (Amiga mouse hack by Faces) either.
When switching to 1351 the cursor jumps all over the screen, so VICE is reading the control port input.
On Linux AP 1.4 doesn't accept input from the Amiga mouse either, but switching to 1351 makes the cursor move, but clicking doesn't work. Weird. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
The mouse emulation does work for me now - as it is intended, switching off the Win mouse pointer. But that is in AP 1.8 with 1351 emulation. Maybe the problem is with the Amiga mouse emulation?
With the file attribution, rebooting didn't help unfortunately - I am sure it is some small thing, but I can't seem to figure it out. :-/ |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quoting bugjamThe mouse emulation does work for me now - as it is intended, switching off the Win mouse pointer. But that is in AP 1.8 with 1351 emulation. Maybe the problem is with the Amiga mouse emulation?
I'll have to look into that. I had no problems with AP 1.8 with 1351 support.
Quote:
With the file attribution, rebooting didn't help unfortunately - I am sure it is some small thing, but I can't seem to figure it out. :-/
I installed a Win7 VM today and managed to get *.d64 associated with x64.exe. I had right-click a d64, click a 'Change' button and select the x64.exe binary.
I did however create a first user named 'vice', which appears to have Admin-like privileges. The VICE nightly I unpacked into $HOME/Desktop and I also stored the test images into my $HOME/Desktop.
Maybe this will help: https://answers.microsoft.com/en-us/windows/forum/windows_7-fil..
Althought VICE doesn't use an installer and thus no registry entries are created. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Great, thanks a lot - in fact I did find what I needed in that M$ forum. Of course it was not the answer given by the M$ guy. :-) I had to go through Regedit to change the path of the exe.
Now I have to find out how to tell it what to do if I double-click a .prg - as of now, it just brings up the C64 start screen.
On top of that, I sometimes get an "Extra arguments on command-line..." error... |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
OK, doubleclicking a d64 does not work either, so regedit did not really help, at least not as I was meant to. Do I maybe have to change the argument in the registry as well? |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
If you're using Winvice 3.0 instead of 3.0a there is a problem with quoted filenames passed on commandline (which is by default done by windows when you associate an extension), try downloading 3.0a and replace it, and retry.
https://sourceforge.net/p/vice-emu/bugs/840/ |
| |
Pantaloon
Registered: Aug 2003
Posts: 124 |
really buggy release :(
worst bug i've found so far is drag'n drop that doesn't work and my settings keep getting resetted. |
| |
blacky
Registered: Sep 2007
Posts: 41 |
Quoting Pantaloonreally buggy release :(
worst bug i've found so far is drag'n drop that doesn't work and my settings keep getting resetted.
Which port, what os is it running on, did you use an old config file or started fresh and saved the config file ?? |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
Quote: really buggy release :(
worst bug i've found so far is drag'n drop that doesn't work and my settings keep getting resetted.
Same problem as my reported bug and bugjam's, get WinVICE 3.0a to fix it.
For the settings, check if you have write permissions in your VICE directory (C:\program files\ perhaps?), or disable UAC (I did on 1st day of win7 installation) |
| |
Pantaloon
Registered: Aug 2003
Posts: 124 |
Tested with Windows 10 + UAC (on) but starting Vice with Admin rights. Drag'n drop fails, i did check with my own compiled version and it seems it gets garbage when resolving the drag'n drop data. I'll get back with some more data on this soon. |
| |
Pantaloon
Registered: Aug 2003
Posts: 124 |
Same drag'n drop error with 3.a.
The drag'n drop action is issued with a PostMessage WM_DROPFILES to the vice window. The same thing works fine with 2.4 |
| |
blacky
Registered: Sep 2007
Posts: 41 |
Quoting PantaloonSame drag'n drop error with 3.a.
The drag'n drop action is issued with a PostMessage WM_DROPFILES to the vice window. The same thing works fine with 2.4
Please report this as a bug on the vice bug tracker, so it can be investigated. |
| |
Steppe
Registered: Jan 2002
Posts: 1510 |
The demo Fantasmolytic shows a weird horizontal stripe in one screen in x64 3.0. Which isn't there in x64 2.4 and also not in x64sc 3.0.
https://www.dropbox.com/s/6zytz87d8m290uy/fantasmolytic_Vice3.p.. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
OK, how exactly should the registry entry look like?
"D:\Commodore\C64-Related\WinVICE-3.0a-x86\x64sc.exe"
and then what?
Regarding the frame rate, this seems to be a problem with my computer (whatever it might be); sc is therefore unusable, but x64 works more or less ok. |
| |
jailbird
Registered: Dec 2001
Posts: 1576 |
Vice was always lagging on my machines (even on those where Photoshop was going extra smooth while editing 5000x5000px+ .PSDs with dozens of layers), but I've learned from someone here that I have to set a realtime priority to x64.exe's process in Task Manager (Task Manager > Details > right click on x64.exe > Priority) and then it will be fine. And indeed it is.
The only thing I find a bit annoying is that I have to do this every time I start Vice since I haven't realized yet how to start a process with realtime priority by default. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
@Jailbird: great hint, I'm gonna try that out! Yes, having that setting on by default would be handy - what on Earth could have a higher priority than the C64 emulator?! :-) |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
Quote: OK, how exactly should the registry entry look like?
"D:\Commodore\C64-Related\WinVICE-3.0a-x86\x64sc.exe"
and then what?
Regarding the frame rate, this seems to be a problem with my computer (whatever it might be); sc is therefore unusable, but x64 works more or less ok.
you have to add "%1" after the exe, but that should have been already there. In my case it's
"C:\C64\vice\x64.exe" "%1"
these are my exported regkeys, you can copy them in a txt file, edit the path of the exe (remember \\ instead of \ and \" instead of single quotes) name it d64.reg and double click on it
REGEDIT4
[HKEY_CLASSES_ROOT\.D64]
@="D64_auto_file"
[HKEY_CLASSES_ROOT\D64_auto_file]
@=""
[HKEY_CLASSES_ROOT\D64_auto_file\shell]
[HKEY_CLASSES_ROOT\D64_auto_file\shell\open]
[HKEY_CLASSES_ROOT\D64_auto_file\shell\open\command]
@="\"C:\\C64\\vice\\x64.exe\" \"%1\""
|
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
Quote: Vice was always lagging on my machines (even on those where Photoshop was going extra smooth while editing 5000x5000px+ .PSDs with dozens of layers), but I've learned from someone here that I have to set a realtime priority to x64.exe's process in Task Manager (Task Manager > Details > right click on x64.exe > Priority) and then it will be fine. And indeed it is.
The only thing I find a bit annoying is that I have to do this every time I start Vice since I haven't realized yet how to start a process with realtime priority by default.
make a batch with
start /abovenormal x64sc.exe %1 %2 %3 %4 %5
if not enough replace abovenormal with high or realtime |
| |
jailbird
Registered: Dec 2001
Posts: 1576 |
Quote: make a batch with
start /abovenormal x64sc.exe %1 %2 %3 %4 %5
if not enough replace abovenormal with high or realtime
Cool, this works!! Thanks! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
realtime is not a good idea most of the time - since the sound driver runs at realtime priority, one might block each other, causing the machine to lock up. |
| |
jailbird
Registered: Dec 2001
Posts: 1576 |
Quote: realtime is not a good idea most of the time - since the sound driver runs at realtime priority, one might block each other, causing the machine to lock up.
Personally, haven't experienced any problems yet, but right, an above normal priority seems to do the job as well. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
its one of those things that work "most of the time" :) however if it does not, it will cause a hard lock-up, requiring a reset.... which sucks =P |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Excuse my n00b question, but is the batch file executed automatically, whenever x64sc is launched? (I placed it in the WinVICE folder).
And thanks for the hint with "%1" - it was there before, but I ha edited it out because it did not work. Now things are finally working again! |
| |
jailbird
Registered: Dec 2001
Posts: 1576 |
Quote: Excuse my n00b question, but is the batch file executed automatically, whenever x64sc is launched? (I placed it in the WinVICE folder).
And thanks for the hint with "%1" - it was there before, but I ha edited it out because it did not work. Now things are finally working again!
You have to execute the batch file, not x64sc.exe |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
But normally I open VICE through a attributed file type. How to make it run the batch file? If I edit the registry to start the batch file instead of VICE directly, it tries to start x64sc from the folder where the disk image is located, and not from the original VICE location. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
i am amazed how easy this windows stuff is these days :o) |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
@gpz: :-D
Never mind my last question, I just copied the whole path of VICE into the registry. However, my frame rate is still shit, even with HIGH priority - gonna try realtime now, to see if that helps at least.
EDIT: nope, still doesn't help - using x64 now instead, that seems to work fine. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Hmmm, parsing from inside a zip file doesn't work? x64 starts, but just with the basic screen, d64 is not attached, and nothing is loaded. From Explorer it works fine now (launching the batch file). |
| |
Fred
Registered: Feb 2003
Posts: 284 |
@bugjam, this has nothing to do with Vice. It's your zip utility that deletes the file after your command to open the file is ended. Especially when you use "start x64" then it runs the executable in a different process while the other process that your zip utility has started to open the file ends and then your zip utility thinks the file can be removed. To avoid this problem, don't use "start" or make sure your zip utility doesn't remove extracted files after opening a file. |
| |
Count Zero
Registered: Jan 2003
Posts: 1825 |
Quick note for people who had troubles with the nightlies since the 3.0 tagging: the build script wasn't quite fit for the 3 :)
Fixed now and all the previous 3.0 builds were deleted. Wondering though that nobody reported even on the borked folder structure :( |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
@Fred: I have to use start /high, otherwise my frame rate is very low (see above). How do I prevent 7zip from deleting the file (from Temp, I assume) after running it? Or do I have to use Filzip instead? |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
maybe that is a dumb question - but WTF does 7zip have to do with all this? |
| |
Fred
Registered: Feb 2003
Posts: 284 |
@bugjam: using the /wait parameter of "start" so that it will not automatically terminate, would be a solution. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Bugjam, what exactly are you trying to achieve?
Running VICE from some zipped dir? Won't work. Running a d64 from inside a zip will work (VICE uses whatever is available to extract the first file in the zip and puts that into a temp dir), but any other files in that zip won't be accessible.
So if you want to use multiple d64's from a zip, just unzip the bloody thing and use that. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
I want to run programs from inside a zip. Often I just want to check stuff briefly, so unzipping would be a bit inconvenient. As described above, I have to take the detour over a batch file to give VICE high process priority, otherwise I'll end up at 10 fps. However, the location in the .zip does not seem to get parsed to VICE (unlike from a normal folder).
@Fred: currently my batch file looks like this:
start /high D:\Commodore\C64-Related\WinVICE-3.0a-x86\x64.exe %1 %2 %3 %4 %5
Where would I have to add the /wait exactly there?
Maybe it is easier to revert to 2.4 or even earlier, after all... My machine apparently just can't handle it. |
| |
Fred
Registered: Feb 2003
Posts: 284 |
@bugjam: start /high /wait "D:\Commodore\C64-Related\WinVICE-3.0a-x86\x64.exe" "%1" "%2" "%3" "%4" "%5"
Also mind the quotes that I added to avoid opening C64 files with a space in the filename. |
| |
Scan
Registered: Dec 2015
Posts: 110 |
People with slower PC's might want to change the ReSID settings from "resampling" to "fast", at the sacrifice some sound quality. On my PC this changes warp speed from 300% to about 700% with x64sc.
 |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I think the nightlies are also built with --enable-memmap, which also slows stuff down significantly. Maybe we should change that, only usefull for serious debugging.
Turning of CRT emulation will also speed up things a lot.
But any decent PC from the last 5-10 years should be able to run x64sc without problems. That said, Windows probably adds a lot of overhead with its useless processes. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
@Fred: this batch just sets off a neverending, unstoppable cascade of opening command line windows.
@Compyx: I know - I am suspecting something is seriously borked with my hw and/or OS. |
| |
Luca
Registered: Apr 2002
Posts: 178 |
I'm still waiting for the juicy AnVICE-(all)-3.0.apk build nobody has done yet... |
| |
gorans
Registered: Aug 2008
Posts: 14 |
Hi,
I compiled 3.0 on OS X 10.11.
Problems:
- VIC II settings window is empty
- when started on second monitor (Desktop on Display 2), Vice dissapears when switched to full screen
- if second display is connected via HDMI and set to PAL 50HZ, framerate is unstable and varies from 80% to 100%
- control window is always in front of all other windows even when Vice is in background
... |
| |
blacky
Registered: Sep 2007
Posts: 41 |
Quoting goransHi,
I compiled 3.0 on OS X 10.11.
Problems:
- VIC II settings window is empty
- when started on second monitor (Desktop on Display 2), Vice dissapears when switched to full screen
- if second display is connected via HDMI and set to PAL 50HZ, framerate is unstable and varies from 80% to 100%
- control window is always in front of all other windows even when Vice is in background
...
We have no osx maintainer, so none of these issues are going to get fixed, feel free to submit patches though if you can fix those issues. |
| |
Skate
Registered: Jul 2003
Posts: 491 |
I just noticed TAP images doesn't load with Vice 3.0 (on Windows). Virtual device traps option is enabled.
I tried it with the tap image that hedning has shared below.
http://csdb.dk/forums/?roomid=7&topicid=122228#122239
Older Vice versions load it correctly. Vice 3.0 doesn't start loading and keeps waiting at "Press play on tape" message. |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
tap loading works of for me, try deleting/renaming your vice.ini |
| |
Skate
Registered: Jul 2003
Posts: 491 |
@iAN CooG: You're right, some option seems to cause that. TAP loading works with default settings but doesn't work with my current vice config. I'm kinda busy now, i'll figure out which option causes it later. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
my bet is on device traps, as usual :) |
| |
Skate
Registered: Jul 2003
Posts: 491 |
@Groepaz: I've tried both device traps on and off. Unfortunately, i (accidently) deleted my old config file and now i can't reproduce the same bug. I'll open a ticket if i can reproduce it and it really is a bug. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Maybe support for t64 should be removed, that'll remove the confusion when it comes to t64 vs tap. |
| |
Sith
Account closed
Registered: Jul 2013
Posts: 17 |
Did winvice 3.0 break "I love the cube 100%" by Samar? I tried to fiddle with all kinds of settings but disk side 2 just won't load... |
| |
Rastah Bar
Registered: Oct 2012
Posts: 336 |
When I run my sierpinsky intro (sieRpiński fRActal) on x64sc of Vice 3.0 only a few dots appear:
http://imgur.com/a/PV8Nf
I tried a few VICE builds including the latest. On x64 it runs fine. It also runs as it is supposed to be on x64sc of Vice 2.4 (and on Hox, micro64 and ccs64).
Is there something wrong with the emulation of SID random number generation in x64sc of Vice 3.0?
Or should I change some emulator settings? |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
works just fine for me in VICE (recent trunk). SID is exactly the same in x64 and x64sc too.... so if there is a difference, it cant be that :)
that said, when you find bugs, report them on the bug tracker. please. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Sorry, gotta revive this thread once more due to my awkward batch file solution to set the priority. I have changed to VICE 3.1, adapted the batch file accordingly, and it works fine; only now, when starting a .t64 (though the batch file), it tells me "press play on tape". Didn't have that behaviour with 3.0... Other file types (.d64, prg etc) work fine. What did I do wrong again? |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
perhaps tell what exactly you are doing? =) |
| |
Skate
Registered: Jul 2003
Posts: 491 |
@bugjam: i had the same problem with v3.0. vice default config works fine. try deleting/replacing the original vice.ini file. see the dialog starting from message #79. i still don't know the actual cause of it. if you find out which setting causes it, please share. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Hm, there doesn't seem to be a VICE.ini file in the folder to start with?!
@gpz: described a couple of posts above - I am linking C64 file types with a batch file instead of directly with x.64.exe to give VICE a higher process priority before starting it:
mkdir "D:\Commodore\temp\"
copy %1 "D:\Commodore\temp\"
D:
cd "D:\Commodore\C64-Related\WinVICE-3.1-x86\"
start /abovenormal x64.exe "D:\Commodore\temp\%~nx1"
Worked flawless with 3.0, doesn't work on 3.1 for .t64, works fine for .d64 and .prg. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
first try without that batchfile, please. somehow it doesnt make sense that this matters :) (also use x64sc *sigh*) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quoting bugjamHm, there doesn't seem to be a VICE.ini file in the folder to start with?!
If I'm not mistaken its in the directory "%APPDATA%/vice".
But like groepaz said, try without batch file and with clean config first: `x64sc.exe -default foo.t64`. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
OK, it DOES work when I replace .x64 by .x64sc in the batch file - so .x64 is broken apparently in that aspect. However, when using x64sc, I am back to 10 fps and 70% speed, despite "above average" process priority... |
| |
Dano
Registered: Jul 2004
Posts: 226 |
@bugjam: on my tests regarding speed i found that x64sc needs more than the standard 1,9ghz of my ultrabook to run at 50fps constantly. disabling output filter like CRT improves performance. as for x64 in the current state the main problem is, that somehow it does not support filters properly anymore, so you can't rely on soundplayback in x64 from vice3.0 on. |
| |
bugjam
Registered: Apr 2003
Posts: 2492 |
Disbaling CRT does not change much here with regards to speed... |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
Quote:as for x64 in the current state the main problem is, that somehow it does not support filters properly anymore, so you can't rely on soundplayback in x64 from vice3.0 on.
thats just wrong. there is exactly zero difference between x64 and x64sc regarding sound (and even less regarding SID).
however, yes, x64 is borken. yes. |
| |
Oswald
Registered: Apr 2002
Posts: 5021 |
btw where to ask for features ? tried to play turrican and it was annoying not to have autofire, why cant one assign a key to autofire ? :( |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
on the tracker at sourceforge, of course :) |
| |
Dano
Registered: Jul 2004
Posts: 226 |
Quoting GroepazQuote:as for x64 in the current state the main problem is, that somehow it does not support filters properly anymore, so you can't rely on soundplayback in x64 from vice3.0 on.
thats just wrong. there is exactly zero difference between x64 and x64sc regarding sound (and even less regarding SID).
however, yes, x64 is borken. yes.
Well then try playing Toggle's "Defier of Deadlines" on x64 and please tell that i doesn't sound totally broken there. On x64sc it plays correctly though. Took me some time on Revision to figure out it's not me falsely replaying it, but vice not playing the tune correctly. |
| |
spider-j
Registered: Oct 2004
Posts: 446 |
As I stopped using x64 a long time ago I can't tell anything about SID in that version.
But I just wanted to drop a *huge* "Thank You!" to whoever fixed the ringmod / sync on 8580 x64sc reSID. I tend to use those more and more and real machine tweaking was really a pain in the bum for me for quite a while.
I must admit I didn't update since end of 2015, so it could be that it was already fixed for some time, but anyhow: thank you! Making 8580 music on emulator has become more and more equal to real machine since replacing that old reSID-fp stuff. And even if many probably don't notice the development since then (or got so used to the *wrong* sounds, that they "believe" it's getting worse) *I* do appreciate this very much.
Great job! :-)
Btw.: Also perfomance seems to be a lot better on my *Arsch*-Linux machine with VICE 3.x ... Thx! |
| |
soci
Registered: Sep 2003
Posts: 474 |
Quoting danoWell then try playing Toggle's "Defier of Deadlines" on x64 and please tell that i doesn't sound totally broken there. On x64sc it plays correctly though. Took me some time on Revision to figure out it's not me falsely replaying it, but vice not playing the tune correctly.
Tried it and there are big differences between recordings even if played on the same version of VICE multiple times, so it's difficult to tell. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
besides that there is absolutely no need to "test" anything in that regard - the code is the same afterall. the only differences you can possibly hear can only be related to CIA or VIC differences - which even more tells you: use x64sc =) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
Quote:But I just wanted to drop a *huge* "Thank You!" to whoever fixed the ringmod / sync on 8580 x64sc reSID.
send your flowers to leandro nini - he did all the recent SID related patches. (he also maintains residFP these days and is making sure both residFP and regular resid are accurate, btw) |
| |
soci
Registered: Sep 2003
Posts: 474 |
Quoting Groepazbesides that there is absolutely no need to "test" anything in that regard - the code is the same afterall. the only differences you can possibly hear can only be related to CIA or VIC differences - which even more tells you: use x64sc =)
I've tested it anyway on r33304 just in case. Surprisingly the result is the same after switching off the random start-up delay, independent if it's x64/x64sc.
If it sounded consistently crap it's likely due to configuration differences between the two emulators and not the emulators themselves. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
did someone check what it does on the real thing then? :) from past experience i'd say.... chances are that VICE is actually quite right =) |
| |
Toggle
Registered: Jul 2003
Posts: 32 |
Hey guys! :-) I always compose on a real machine (new SID) and it definitely sounds normal there, at least as normal as I intended. Since I'm a lazy updater I also never encountered any emulation issues with Vice 2.4. When Dano played the tune at Revision (Vice 3.x) I was totally surprised and had no idea what was going on - that was way too avantgarde for my taste ;-)
PS - This is pretty much what it SHOULD sound like:
https://www.youtube.com/watch?v=3g021vKSebA |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
so, here is an mp3, one side is the audio from that video, the other side is recorded from current VICE (trunk) with default settings.
so, who can tell what is what? =) i cant, i must be deaf or sth =)
edit: the tracks are not perfectly aligned, so there is a little bit of delay/echo/whatever. i'm lazy :) |
| |
soci
Registered: Sep 2003
Posts: 474 |
The left one sounds more like VICE. |
| |
Jammer
Registered: Nov 2002
Posts: 1289 |
Groepaz, try #6 and #9 from my 'Caren' soundtrack or anything with deep filters ;) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
somehow every time i try "it sounds totally broken!!!!!ELEVEN" things here, it always sounds completely sane. *shrug* (yes there is this this "farting filters" bug - but that does not apply in this case) |
| |
Toggle
Registered: Jul 2003
Posts: 32 |
Quote: somehow every time i try "it sounds totally broken!!!!!ELEVEN" things here, it always sounds completely sane. *shrug* (yes there is this this "farting filters" bug - but that does not apply in this case)
In your MP3 everything sounds fine to me, but that's all very far from Dano's "remix". I have no clue what caused the problem there. |
| |
Dano
Registered: Jul 2004
Posts: 226 |
Tested it on my work laptop with latest vice from pokefinder.org
The current default settings are ok on both x64 and x64sc.
What killed the song on my ultrabook was my "FastSID" setting i had there. Me was forced to use FastSID all the time as my Ultrabook could not run ReSID due to faulty Intel Win10 drivers.
When switching x64 to FastSID "Defier" is totally broken, not just sounding less good. Switching to ReSID restores normal sound.
Not sure what Toggle uses there what breaks Vice. Honestly i never had such issues playing any tunes the months and weeks before.. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
Quote:When switching x64 to FastSID "Defier" is totally broken
doh - of course ;_; |
| |
iAN CooG
Registered: May 2002
Posts: 3136 |
no shit, really =) |
| |
Slajerek
Registered: May 2015
Posts: 62 |
Oh, how I love such bug reports :)
I remember trying to track error in my calculations for more than hour just to realise they were for PAL and I accidentally switched to NTSC...
That's a feature not a bug :-) |
| |
Skate
Registered: Jul 2003
Posts: 491 |
Quote: I just noticed TAP images doesn't load with Vice 3.0 (on Windows). Virtual device traps option is enabled.
I tried it with the tap image that hedning has shared below.
http://csdb.dk/forums/?roomid=7&topicid=122228#122239
Older Vice versions load it correctly. Vice 3.0 doesn't start loading and keeps waiting at "Press play on tape" message.
I've reported this problem before and found not an ideal solution like deleting vice.ini file. Today it happened to me again. I found the problem.
Datasette=0
This line causes the problem. I don't know which config adds this line. Removing that line solves the stuck at "press play on tape" issue but i don't know how it is being added to the ini file. I know i didn't add it manually, some settings from GUI must be adding it. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
If you disable the c2n and then safe the settings, it will be saved to the config. (please dont use 3.0) |
| |
Skate
Registered: Jul 2003
Posts: 491 |
Quote: If you disable the c2n and then safe the settings, it will be saved to the config. (please dont use 3.0)
I knew "don't use v3.0" would come after that message and normally i don't. But i have multiple PCs, laptops, macs etc. Some of them have older versions. I already tried it with the latest Vice version. It auto enables tape if you attach a tape image. But many people still use older version (some of them for performance reasons). I wanted to share the solution.
Also, i believe it's caused by attaching some cartridges, REU etc. Because i don't think any of us would go to the Settings > Cartridge/IO Settings > Tape Port Devices > Enable Datasette Device and uncheck it. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
Quote:But many people still use older version (some of them for performance reasons)
Which is just nonsense, because the performance differences are close to zero with the same settings. Just dont.
Quote:Also, i believe it's caused by attaching some cartridges, REU etc. Because i don't think any of us would go to the Settings > Cartridge/IO Settings > Tape Port Devices > Enable Datasette Device and uncheck it.
The only things that would touch this setting are tapeport devices - so eg attaching a tapecart and then saving settings could do this. |
| |
TheRyk
Registered: Mar 2009
Posts: 2076 |
yeah if you want Warp 3,000% on a machine that's got problems with VICE 3.x at 100% (no warp), then the .x doesn't make much of a difference and you should rather go for 2.4 or older x64.exe (without .SE) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
I dont get this fetish about warpspeed myself, are you in a real hurry when watching demos? :) |
| |
Endurion
Registered: Mar 2007
Posts: 72 |
Warp speed is really really useful when developing and fast forwarding to the relevant part. Don't underestimate features you maybe don't use yourself :) |
| |
Krill
Registered: Apr 2002
Posts: 2850 |
Maybe VICE should (optionally) disable things like SID and maybe true-drive emulation entirely during warp.
Might sound a bit bumpy afterwards or maybe make the loader fail, but could speed up debugging turn-around times here and there. :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
Partselectors do all the magic for me, no need to fast forward a lot :) (and i cant imagine how its useful in a game to be honest, are you playing at 10000% then?) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
We actually even thought about limiting the warp speed to sth like 10x - because its *too fast* to be useful on anything half modern already. |
| |
Endurion
Registered: Mar 2007
Posts: 72 |
Please don't! Or make it configurable.
Sometimes parts build upon themselves, so shortcutting isn't good.
In Forum64 someone is currently comparing emulators, and methods to speed them up/conserve battery. Quite an interesting read; stop updating drive code if it isn't in use etc. |
| |
Burglar
Registered: Dec 2004
Posts: 1031 |
Quoting GroepazWe actually even thought about limiting the warp speed to sth like 10x - because its *too fast* to be useful on anything half modern already. please don't! |
| |
Oswald
Registered: Apr 2002
Posts: 5021 |
can be optional. max warp speed. |
| |
TheRyk
Registered: Mar 2009
Posts: 2076 |
@groepaz: there even ARE games that are (at least in parts) so hell slow that it's preferrable to use emulator and warp to playing on real hw :D
But yeah mostly it's very good to test out work in progress - not for stability of course (that wouldn't make sense with an obsolete version) but for general performance. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
Quote:In Forum64 someone is currently comparing emulators, and methods to speed them up/conserve battery. Quite an interesting read;
Actually that thread should be linked in wikipedia under "apples and oranges" :=P
Quote:
stop updating drive code if it isn't in use etc./quote]
VICE can *already* do this. It's no more the default because it introduced weird subtle problems.
However, warpmode does - and will - not sacrifice accurracy for speed. So removing frame-lock: yes, anything else: no. |
| |
Krill
Registered: Apr 2002
Posts: 2850 |
Quoting GroepazHowever, warpmode does - and will - not sacrifice accurracy for speed. So removing frame-lock: yes, anything else: no. If not done already, bypassing the entire SID emulation audio output stage including filters and oversampling and whatnot during warp should be a-okay, no? :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11123 |
yes and no - the digital part must still be emulated, and resid doesnt allow to just skip the filter+output stage i think. (feel free to provide a patch =D) |
