| |
robo
Registered: Nov 2012
Posts: 9 |
problem with vice 2.4.18
I downloaded the latest vice build from pokefinder (WinVICE-2.4.18-x86-r29549). I want it to always use the "true drive emulation", but it NEVER uses it.
When I try to load something, it works, but without using the true drive emu.
When I try to load sth using the AR6 fastloader, it simply does nothing.
Is there something broken or am I doing sth wrong? |
|
| |
Oswald
Registered: Apr 2002
Posts: 5017 |
turn true drive emu on? you need to be more exact on what settings you have and what happens.
you're doing something wrong, since this works since like ages. |
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
Turn off "handle true drive emulation". Set the autostart method to d64 or inject to ram, not virtual fs. |
| |
Oswald
Registered: Apr 2002
Posts: 5017 |
btw hiding deep the pal filter on/off, doesnt click with me. not good for debugging when you really want to see where some pixels are. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11114 |
TDE is even default for a while now, so to not use it you must explicitly turn it off. *shrug* |
| |
Count Zero
Registered: Jan 2003
Posts: 1821 |
He maybe depacks stuff into his old vice directory. Delete your old configs! |
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
The way VICE handles preferences this will always be a problem. Since every option is saved to the vicerc, regardless of if the user has changed the option or not, means that for a majority of users old stupid defaults (like handle TDE) override new better defaults.
I have like 10 settings I change, yet my vicerc is 406 lines. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11114 |
the way users use it is the problem. start with an actually fresh install instead and the problem goes away. |
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
Don't blame users for bad application design, nothing tells them to delete the config when upgrading. Doing so is completely counterintuitive and also deletes the settings they do want to save. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11114 |
Quote:nothing tells them to delete the config when upgrading
infact, making a mechanism that warns about it is on my todo list :)
however, this is about a snapshot build - and you should never "upgrade" your existing installation with it. this has huge potential for creating all sorts of problems, just dont. |
| |
robo
Registered: Nov 2012
Posts: 9 |
I deleted the vice.ini, setup everything from scratch (to the same settings I use since years) and now it works.
That is strange... I don't know what's different now ;-)
btw: I never overwrite existing vice installations/folders. I still need the old versions to load my old snapshot-files...
A converter tool would be cool... That would also support other tools, like the infiltrator disassembler, which only accepts a small range of snapshot-versions. |
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
Quote: Quote:nothing tells them to delete the config when upgrading
infact, making a mechanism that warns about it is on my todo list :)
however, this is about a snapshot build - and you should never "upgrade" your existing installation with it. this has huge potential for creating all sorts of problems, just dont.
A warning is certainly better than the current situation, but why not fix the actual problem instead? The simplest workaround is probably to only write config values that differ from the default - far from an ideal solution but better than what we have now.
The proper solution would be versioned config files and logic to migrate settings, but that requires more work. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11114 |
thing is, to actually fix the ini problems, tons of stuff must get rewritten. eg a bunch of things rely on the order of how resources are loaded, and will break with such an "incomplete" config file.
that said, my time is limited and i'd rather look at actual emulation problems :) |
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
Well that sucks :/
At some point I guess you just need to kill it with fire and separate the emulation core into libvice, decoupling it from the applications. The source is such a tangled mess that I don't even know where to start - I can't even get it to compile. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11114 |
a while ago i compiled it with a blank configure line on OSX .... perhaps at the moment ffmpeg must be disabled, did not check that yet. (the xcode project does NOT work, i failed at fixing that and i am happy it can atleast be used to edit some dialogs) |
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
Maybe the problem is that I've been following the instructions and using the build scripts... |
| |
Perplex
Registered: Feb 2009
Posts: 254 |
Quoting MagerValpThe proper solution would be versioned config files and logic to migrate settings, but that requires more work.
Including the version string in the name of the config file shouldn't be too much work. Not an ideal solution, but if we're expecting to start from a clean slate anyway this would remove the need for the user to do any manual housekeeping.
A better solution would be a versioned config file with default settings, and a different non-versioned config file containing only local overrides. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11114 |
Quote:Maybe the problem is that I've been following the instructions and using the build scripts...
the real problem is that no bug was reported and complaints posted elsewhere :)
Quote:A better solution would be a versioned config file with default settings
the defaults are built into the app anyway, how would this improve anything? vice.ini ARE the "local overrides". |
| |
Perplex
Registered: Feb 2009
Posts: 254 |
The problem is that vice.ini is not a "local override" at all right now, as it includes *all* settings, even those that have not changed from the default. If vice.ini included only options that were changed by the user, then upgrading the emulator to a new version with new defaults would grant the user the new default values instead of letting her being stuck with defaults from an older version that are now no longer defaults. |
| |
Count Zero
Registered: Jan 2003
Posts: 1821 |
I didnt test this but should/could work:
x64sc -default yoursettings.vrs some.d64
where yoursettings.vrs contains the resources one usually changes. As said: nojoopa (I think) added the possibility for all resources in vrs files a long time ago. Not sure if that is still functional though.
vrs files were meant to be for romset loading but may serve this purpose as well. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11114 |
Quote:The problem is that vice.ini is not a "local override" at all right now, as it includes *all* settings
one doesnt exclude the other. it _IS_ an override. you _CAN_ just put the things you changed into it. (and no, you dont need .vrs for that :=))
i dont see the problem though. you'll have to delete your config every two years when vice is released. big fucking deal =) |
