Jump to content

Complete Guide for Commodore 64 in HyperSpin and HL3 using WinVICE


rfancella

Recommended Posts

Posted
Just in case this matters I am running the newest version of HL at the time of this writing 3.101 (released Dec 29th 2014) Edit - just updated to 3.102b and same problem.

I followed the guide directions, and my configuration seems to match Ron's. Some games launch fine, while others give an error related to having square brackets in the name. Looking at the screen shots in the guide, it appears our roms are named the same, I am using the database from hypersynch so I would assume these were the cannon names for these roms. 7z support is enabled, and roms without the [] in their name work fine. I am going to assume I missed a general HL configuration setting some where, but I havent found anything poking around (thought it might be checkpaths, since that is the last step in the logs before error, byt HL is so insistent about not turning that off that I figured I'd ask here first) In the mean time I am gonna go check the release notes for HL and make sure I didn't miss something there.

As always thanks to Ron for the guide, and everyone for their help, and Happy New Year.

LOL... I mentioned this on the other forum. ;)

In the old HyperLaunch, this was a problem before. But it was only effected if you tried to setup any per-game settings in HLHQ.

Previously, there were no checks on names like this, but with the new HyperLaunch, it checks to make sure there are no brackets in the name.

Thanks,

Ron

Code Monkey and all around Command Line geek!

If you like what someone has said or done for you, be sure and 'Thank' them.  :good:

And if they changed your life, send them a Beer!    :beerglass:

  • Replies 92
  • Created
  • Last Reply
Posted

Well since it sounds like this is an improvement in Hyperlaunch, should we work on implementing proper naming on the files? I can alter the names in the database, as well as rename the files themselves, along with the artwork/videos/etc. I can do that for my own collection easily enough, but it would be nice to share - what is the protocol for that? Just upload the scripts to your ftp directory?

Thanks all,

Xam

Posted
Well since it sounds like this is an improvement in Hyperlaunch, should we work on implementing proper naming on the files? I can alter the names in the database, as well as rename the files themselves, along with the artwork/videos/etc. I can do that for my own collection easily enough, but it would be nice to share - what is the protocol for that? Just upload the scripts to your ftp directory?

Thanks all,

Xam

Just use my unofficial no intro setup makes life easier. All set to go for about 1900+ roms. Rather than renaming your own. You can rename your own if you like. Just want to save you some work.

  • 3 weeks later...
Posted

There's an option for turning on True Drive Emulation via the WinVICE module/ISD in RL. Also, check out my Commodore64.ini in my folder on the FTP, should have most set correctly (I think).

  • 2 weeks later...
Posted

Is it possible to remove the borders or increase the screen size?

Setting VICIIBorderMode=3 removes the borders but some games will start flashing uncontrollably - like they are having a seizure.

Posted

Hi all,

Thanks for the guide? Should this work when running C64 cartridges too? The reason I ask is that I am tryimg to add the Commodore 64 Games System to my setup (cartridges only). I added the system to HypeHQ with correct naming so that it appears in Hyperlaunch Hq with an icon. The system doesn't have any emulators or modules attached to it, so I unchecked the hyperlaunchhq option so I could assign ANY emulator, and added WinVICE v2.4 x64 emulator (using WinVICE module v2.0.5)

I can load catridges fine from the emulator, by attaching the cartridge image, but when trying to launch from hyperlaunch it fails, nothing happens then eventually I get an error saying "There was an error waiting for window "ahk_class VICE""

Do I need to change settings in the emulator or module to get crt files to load? Or have i done something wrong by trying to assign this module and emulator to a different system?

Thanks :)

Posted
Hi all,

Thanks for the guide? Should this work when running C64 cartridges too? The reason I ask is that I am tryimg to add the Commodore 64 Games System to my setup (cartridges only). I added the system to HypeHQ with correct naming so that it appears in Hyperlaunch Hq with an icon. The system doesn't have any emulators or modules attached to it, so I unchecked the hyperlaunchhq option so I could assign ANY emulator, and added WinVICE v2.4 x64 emulator (using WinVICE module v2.0.5)

I can load catridges fine from the emulator, by attaching the cartridge image, but when trying to launch from hyperlaunch it fails, nothing happens then eventually I get an error saying "There was an error waiting for window "ahk_class VICE""

Do I need to change settings in the emulator or module to get crt files to load? Or have i done something wrong by trying to assign this module and emulator to a different system?

Thanks :)

The module should load the crt files just fine. Turn off Fade In and see if WinVICE is erroring out before starting the game.

I just put "Adventure 1 - The Mutant Spiders (USA, Europe).crt" in my setup and it fired right up.

Thanks,

Ron

Code Monkey and all around Command Line geek!

If you like what someone has said or done for you, be sure and 'Thank' them.  :good:

And if they changed your life, send them a Beer!    :beerglass:

Posted

Cheers Ron,

Tested things out, and if I name my system "Commodore 64" it all works sweet :) But, if I name my system "Commodore 64 Games System" I get same error. Everything the same, sam modeules, same emlator, same settings, same rom path. So it must be down to the system name. It's a valid system because I get the icon, and WinVice is a valid emulator for it, because the insides of the Games System are same as Commodore 64 anyway.

What's the protocol for this please? Do I need to request the module and emulator be applied the the "Commodore 64 Games System" somewhere?

I know its just aesthetics, because I could just run it as a Commodore 64, but hey, isn't aesthetics why we all here? ;) Besides, it messes with my plans to build a system with just all consoles included - and the more I play around with this software the more ocd I'm getting over it :)

Thx!

Posted
Cheers Ron,

Tested things out, and if I name my system "Commodore 64" it all works sweet :) But, if I name my system "Commodore 64 Games System" I get same error. Everything the same, sam modeules, same emlator, same settings, same rom path. So it must be down to the system name. It's a valid system because I get the icon, and WinVice is a valid emulator for it, because the insides of the Games System are same as Commodore 64 anyway.

What's the protocol for this please? Do I need to request the module and emulator be applied the the "Commodore 64 Games System" somewhere?

I know its just aesthetics, because I could just run it as a Commodore 64, but hey, isn't aesthetics why we all here? ;) Besides, it messes with my plans to build a system with just all consoles included - and the more I play around with this software the more ocd I'm getting over it :)

Thx!

LOL.. I do understand. There are two ways of attacking this. One would be to do an official request to have it added to the module as an accepted name. That probably will not fly. The other is to edit the module. That is not recommended either, as you future updates will probably overwrite the module changes.

To edit the module there are only two places to change.

1). Change line 9 from:

MSystem = "Commodore 64","Commodore 16 & Plus4","Commodore VIC-20","Commodore 128"

To:

MSystem = "Commodore 64","Commodore 16 & Plus4","Commodore VIC-20","Commodore 128","Commodore 64 Game System"

2). Change line 45 from:

mType := Object("Commodore 64","C64","Commodore 16 & Plus4","PLUS4","Commodore VIC-20","VIC20","Commodore 128", "C128") ;ident should be the section names used in VICE.ini

To:

mType := Object("Commodore 64","C64","Commodore 64 Game System","C64","Commodore 16 & Plus4","PLUS4","Commodore VIC-20","VIC20","Commodore 128", "C128") ;ident should be the section names used in VICE.ini

Thanks,

Ron

Code Monkey and all around Command Line geek!

If you like what someone has said or done for you, be sure and 'Thank' them.  :good:

And if they changed your life, send them a Beer!    :beerglass:

  • 1 month later...
Posted

Hey Ron, thanks for another awesome guide. Just one quick question: I read earlier someone asking about how to get the emu to work w/ an Xbox 360 controller. You had mentioned using xpadder. Could you elaborate what keys you would need to set? I left the option for joystick as Keyset A, and I tried changing Keyset A to the arrow keys for the directions, and space bar for fire; I subsequently set those buttons to my xpadder profile for the 360 controller, but it didn't seem to take any of the button presses.

Posted
Hey Ron, thanks for another awesome guide. Just one quick question: I read earlier someone asking about how to get the emu to work w/ an Xbox 360 controller. You had mentioned using xpadder. Could you elaborate what keys you would need to set? I left the option for joystick as Keyset A, and I tried changing Keyset A to the arrow keys for the directions, and space bar for fire; I subsequently set those buttons to my xpadder profile for the 360 controller, but it didn't seem to take any of the button presses.

Thank you for the kind words.

I don't use XPadder, so I wish I could help. By the sound of it, what you got going on should work.

I would go the other direction. Use the default keys as they are and program XPadder to those keys.

Thanks,

Ron

Code Monkey and all around Command Line geek!

If you like what someone has said or done for you, be sure and 'Thank' them.  :good:

And if they changed your life, send them a Beer!    :beerglass:

Posted
Hey Ron, thanks for another awesome guide. Just one quick question: I read earlier someone asking about how to get the emu to work w/ an Xbox 360 controller. You had mentioned using xpadder. Could you elaborate what keys you would need to set? I left the option for joystick as Keyset A, and I tried changing Keyset A to the arrow keys for the directions, and space bar for fire; I subsequently set those buttons to my xpadder profile for the 360 controller, but it didn't seem to take any of the button presses.

I have to use xpadder for all the special key combos like Swap Joystick ports and Quick snapshots.

N Y & Caps Lock are to get past the trainers. There is probably room for some function keys as well.

Here is my xpadder profile, at least to give you am idea.

;--- Xpadder Profile File ---
DataType=Profile
Version=2014.07.01

[Profile Settings]

[set Settings]

[Assignments]
Set1Button1Slots=Enter
Set1Button2Slots=N
Set1Button3Slots=Space
Set1Button4Slots=Y
Set1Button5Slots=Alt,J
Set1Button6Slots=Alt,W
Set1Button7Slots=Alt,L
Set1Button8Slots=Alt,S
Set1Button10Slots=Caps Lock
Set1DPadUpSlots=Arrow Up
Set1DPadRightSlots=Arrow Right
Set1DPadDownSlots=Arrow Down
Set1DPadLeftSlots=Arrow Left

56uIzxg.png

  • 2 weeks later...
Posted

Ron, do you know of a preferred audio setup in winvice as "daredevil Denis" audio is distorted during the first section and wondered if a tweak would sort it. Can't remember the original being that way....

Posted
Ron, do you know of a preferred audio setup in winvice as "daredevil Denis" audio is distorted during the first section and wondered if a tweak would sort it. Can't remember the original being that way....

Potts,

You might try messing with the SID settings. I don't remember ever playing that game before. If you figure it out, maybe something can be done in the module for it.

Thanks,

Ron

Code Monkey and all around Command Line geek!

If you like what someone has said or done for you, be sure and 'Thank' them.  :good:

And if they changed your life, send them a Beer!    :beerglass:

  • 2 weeks later...
Posted

Fixed this issue by looking at the version of c64 it uses. By choosing a newer version of the c64 and Sid chips made the sound very good and no lag at all.

Posted

Sweet Potts!

Glad it's all sorted now.  What changes did you make?

 

Thanks,

Ron

 

Fixed this issue by looking at the version of c64 it uses. By choosing a newer version of the c64 and Sid chips made the sound very good and no lag at all.

Code Monkey and all around Command Line geek!

If you like what someone has said or done for you, be sure and 'Thank' them.  :good:

And if they changed your life, send them a Beer!    :beerglass:

Posted

I'm not at my PC at the moment but basically I looked on the menu drop downs and found an option for what version loads at startup. I found options for c64c and newer Sid chips. I chose what I presumed were improved/latest iterations and there was a significant improvement. Hope this helps.

  • 4 weeks later...
Posted

Great guide rfrancella. Thanks. Got the emulator up and running with joystick keys mapped.

 

However in WinVice some c64 games require you to press run/stop to start a game. BY default this is set to ESC on a keyboard but this also is the default key to exit the emulator in HS.

 

Is there a setting in WinVICE to change this default key to something ese? Can't find anything in the emu menus.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...