|
|
Post by spannernick on Mar 25, 2020 19:59:53 GMT
Its True Drive Emulation its not enabled, you need Accurate Disk enabled (_AD) for it to load a .g64 image. its disabled by default.
|
|
|
|
Post by bamm on Mar 25, 2020 21:51:08 GMT
So as you indicated, TAP files don't load with Jiffy so I disabled and now DK Jr loads.
I have just noticed that R-Type hangs just after starting it from the Carousel and selecting 1 Player. It does this with or without Jiffy enabled.
|
|
|
|
Post by bamm on Mar 25, 2020 22:05:40 GMT
So as you indicated, TAP files don't load with Jiffy so I disabled and now DK Jr loads. I have just noticed that R-Type hangs just after starting it from the Carousel and selecting 1 Player. It does this with or without Jiffy enabled. Ok, that's strange. R-type needs you to press fire to start the game, that bit isn't strange but i tried pressing fire and it just hangs at the Ready screen within the game. I was using my Innex controller. When I started the game with the original Maxi controller and pressed fire the game started .
Some sort of incompatibility problem with this game and the Innex?
|
|
|
|
Post by spannernick on Mar 25, 2020 22:50:59 GMT
New update, fixed some of the games now and added some more..  (Friday The 13th,Arcade Hall of Fame and more) v1.06 uploaded now, all games should work now. |
|
|
|
Post by Disc Master I on Mar 26, 2020 0:42:19 GMT
Its True Drive Emulation its not enabled, you need Accurate Disk enabled (_AD) for it to load a .g64 image. its disabled by default. ***UPDATE*** I saw you just uploaded a newer version. I'm going to download it and try it out to see if the below issue is resolved. I'll update this with my testing result.Test results for 1.06 is the same issue as reported below. I can't load any d64 or g64 images from the classic mode with JiffyDOS. I can try diabling JD and then I'll see what happens. I'll report back. OK... So I disabled JiffyDOS and the d64 files load fine. Activate the JiffyDOS lines within the .sh file and the below issues still occur. Span, I'm trying d64 files as well and I don't think True Drive emulation is the issue (I do understand about g64 images and the need for true drive emulation). Even with the d64 files when I try to load a game, after hitting RETURN I get the following LOAD"*",8,1 SEARCHING FOR * and it just hangs there. I haven't made any changes to the content of your USB Carousel package, haven't edited the .sh file at all, etc. It just seems that trying to launch any d64 (and g64) seems to lock up the computer. Just to be specific, I'm not trying to launch anything through the carousel menu, but from the classic mode with the JIFFYDOS V6.01 (C) 1989 CMD basic desktop window. I didn't have this issue with the earlier releases of your USB Carousel packages. Can you confirm that you can load up your USB carousel package, go to classic mode, mount a disk and then load the disk witht he typical LOAD"*",8,1 command and have your maxi not lock up, but actually load the file? Everything I tried so far has the system lock up after using the LOAD command and pressing RETURN. John. |
|
|
|
Post by kugelblitz on Mar 26, 2020 10:25:07 GMT
@spannernick a) For people saying that Jiffydos does not work - is the mounting of 1541 ROMs tested and correct for the Mini? b) I see that your script mounts the MAXI carousel, THEN checks whether this is a MINI and then mounts the MINI carousel. I think you should rework that with an if then else clause - mounting TWICE might eat some more memory on the Mini and it can not spare any.
|
|
|
|
Post by spannernick on Mar 26, 2020 14:52:31 GMT
JiffyDos for some reason is having a problem now with its kernal, I disabled the drives and its still freezing so its the kernal ROM .bin file thats doing it, I even tried a different kernal, the JiffyDos SX64.bin file and its still doing it, will have look into it more, been working on it all morning, it doing my head in..  why is it doing it, will have to disable JiffyDos for now cause its broken and not working no more, I did try and disabled everything I could in the start.sh to see if it was a addon I added and its not so its not down to memory(I have 1 GB on Mine), its like its not mounting the kernal properly or something. |
|
|
|
Post by spannernick on Mar 26, 2020 17:11:34 GMT
Ok.... Good NEWS Update! I got it fixed. Now TheC64 actually loads a bit faster than the Ultimate64 Elite. LOL I added the following lines to the start.sh file. mount --bind /mnt/C64vic20kernalroms/JiffyDOS_1541-II.bin /usr/lib/vice/DRIVES/d1541II mount --bind /mnt/C64vic20kernalroms/JiffyDOS_1541-II.bin /usr/lib/vice/DRIVES/dos1541 NOTE: I had to add the JiffyDOS_1541-II.bin file to my "C64vic20kernalroms" folder on my USB stick.The reason for d1541II is because I read somewhere that the version of Vice within TheC64 uses the 1541-II drive and not the original 1541. I originally tried with just the following line, but it did not help. mount --bind /mnt/C64vic20kernalroms/JiffyDOS_1541-II.bin /usr/lib/vice/DRIVES/dos1541 That typically works in Vice on the PC, so I tried adding the line... mount --bind /mnt/C64vic20kernalroms/JiffyDOS_1541-II.bin /usr/lib/vice/DRIVES/d1541II After another firmware update, I got into classic mode, mounted disk 1 of ACS and then pressed the @ command to get the drive info. The response was... 73, JIFFYDOS 5.0 1541,00,00 I then proceeded to perform the speed test vs. the Ultimate64 Elite. This time TheC64 actually was a few seconds faster than the already fast loading Ultimate64 Elite! Well, I'm off to go play some games, with much QUICKER load times! Thanks again Span for putting this package together for us. I don't understand why this now don't work,I have even removed everything and just had JiffyDos mount commands in the start.sh and still freezing. I even checked to see if the files were corrupt and copied over them with new copies of the files and its still doing it. Tried putting the C64vic20kernalroms folder back in the root of USB stick and still the same. I have tried every thing I can think of, Just no luck getting JiffyDos v6 to work now,anyone have any ideas..? |
|
|
|
Post by spannernick on Mar 26, 2020 17:45:59 GMT
***GOODS NEWS*** It was not working at all until I turned off THEC64 and left it for 30 Minutes while I when to the shop and then tried again when got back and it worked fine.. I got it working but... You NEED _AD added to the name of the .d64 file(Buck Rodgers_AD.d64)or a easier way would be to make a cjm file and name it the same as the disk and put accurate disk in it,then you just copy the cjm file and rename it for the next disk you want to run with Jiffydos, it don't work without True Drive Emulation(it emulates the drive roms and the way it loads),it does it on Vice 2.4 on the PC too cause its looking for JiffyDos disk ROM(thats a .bin file) in the 1541 Disk Drive. In one of the posts on Lemon64 it does say you need TDE enabled in Vice for JiffyDos to work and it does make sense. If its off then its in SD2IEC mode and that don't use a Disk Drive ROM, it works like a 1581 disk drive then. A lot of disks need the ROM to work, like .g64 files(they have the extra sectors where the copyright code is) cause they are full copies of the games disks. In a real 1541 Disk Drive TDE is enabled automatically cause it has ROMs inside it(it even has the CPU 6502 from the C64 in it, its like it has a C64 computer in the 1541 disk drive) so don't understand why its off in the emulator when it should be on really, TDE is off by default in Vice in Mini/Maxi. I do have a 1541C Disk Drive(I had to buy a new head for it,well it not new but works and reads and write fine),its the same colour as my C64C.. This will show you how to setup JiffyDos in Vice and you need True Drive Emulation(AD, accurate disk) enabled to use JiffyDos... www.c64-wiki.de/wiki/VICE/JiffyDOS , If its off then JiffyDos can't find the 1541 JiffyDos disk ROM and freeze Vice on Mini/Maxi.  Updated it and changed the name of the folder that the jiffydos roms were in to JiffyDos_v6_roms.. You can download it now. |
|
|
|
Post by spannernick on Mar 27, 2020 22:09:33 GMT
I can't get THEC64(Commodore Key) key to work in the TSG file,Even setting it with TheC64 Maxi Game Tool, its called "CM" in the Joystick settings, I am trying to get the left fire button to be THEC64 key so when you press it it, it that key. the game that uses that key (Left flipper)is the 3D Pinball game,Pinball Power by Mastertronic, it included with the Carousel Games from USB.
If someone can test it for me to see if the left fire button makes the left flipper works in the game cause it don't work here..?
|
|
|
|
Post by bamm on Mar 27, 2020 23:56:01 GMT
I can't get THEC64(Commodore Key) key to work in the TSG file,Even setting it with TheC64 Maxi Game Tool, its called "CM" in the Joystick settings, I am trying to get the left fire button to be THEC64 key so when you press it it, it that key. the game that uses that key (Left flipper)is the 3D Pinball game,Pinball Power by Mastertronic, it included with the Carousel Games from USB. If someone can test it for me to see if the left fire button makes the left flipper works in the game cause it don't work here..? Just tried the latest update on my Maxi and the left fire button does not operate the left flipper in 3D Pinball from the carousel. |
|
|
|
Post by spannernick on Mar 28, 2020 12:29:27 GMT
Thanks so it not just me then, I noticed THEC64 key does not work of the Virtual keyboard on THEC64 Maxi too.It works on THEC64 Mini ok. Well thats the main thing, I did added the keys to THEC64 Joystick so you could play the game on THEC64 Mini.. |
|
|
|
Post by spannernick on Mar 28, 2020 15:39:50 GMT
Retro Games Ltd know about this now and should be fixed in the next update.. but cause of Covid 19, don't know when that will be. |
|
|
|
Post by bamm on Mar 28, 2020 19:23:24 GMT
Retro Games Ltd know about this now and should be fixed in the next update.. Wow, I'm surprised it went this long without anyone noticing. |
|
|
|
Post by spannernick on Mar 29, 2020 14:17:03 GMT
Well thats the only game I know that uses THEC64 Key..(Commodore Key) and the other problem is if you use keys then if you try and press both fire buttons together, you can't you can only use one button at a time so only fire 1 or fire 2 but not together.. weird |
|
|
|
Post by spannernick on Mar 30, 2020 14:46:42 GMT
Will be adding to the start.sh the gamecontollerdb.txt so you can add a controller that don't work with TheC64 Mini/Maxi, make it easier to get too.
|
|
|
|
Post by alterego on Mar 31, 2020 6:34:30 GMT
Will be adding to the start.sh the gamecontollerdb.txt so you can add a controller that don't work with TheC64 Mini/Maxi, make it easier to get too. Great news spannernick, thanks for your effort! One question: how i can find the correct string for my custom controllers to add into gamecontrollerdb.txt? Thanks in advance!  |
|
|
|
Post by spannernick on Mar 31, 2020 12:46:11 GMT
This will help.. www.generalarcade.com/gamepadtool/ (You might be able to run it on THEC64 X-Windows Mod, it has a Linux version or the Windows version with Wine)  I update it today with the gamecontrollerdb.txt, it will be the one for TheC64 maxi, but will include the one from TheC64 Mini too,just need to get it from mine so might not be not inclued for the mini we will see.. |
|
|
|
Post by spannernick on Mar 31, 2020 16:42:39 GMT
Added the option for the Game Controller Database txt file now and uploaded. sorted it so it has TheC64 Mini and Maxi versions of it now. They are in the folder "Carousel_Games\addons\controllers". under folders "thec64mini" and "thec64maxi", if you need to add a Game Controller.. |
|
|
|
Post by alterego on Mar 31, 2020 20:40:33 GMT
Added the option for the Game Controller Database txt file now and uploaded. sorted it so it has TheC64 Mini and Maxi versions of it now. They are in the folder "Carousel_Games\addons\controllers". under folders "thec64mini" and "thec64maxi", if you need to add a Game Controller.. Really thanks for this update and info above |
|
|
|
Post by spannernick on Mar 31, 2020 22:44:11 GMT
Just added 3 The Sales Curve games, Silkworm,St Dragon and SWIV.
|
|
|
|
Post by lantzelot on Apr 1, 2020 8:23:07 GMT
Hi Span, thanks for the USB hack, it work really great with the carousel games. But I have some problems when adding new controllers. I tested to use the gamepad tool to add two controllers, but I can't get them to work. I also have a Speedlink Competition Pro and modified the button mappings based on some info I found here : thec64community.online/thread/100/usb-gamepad-ninento-snes-controllerBut that does not work either, the same mappings are still used after upgrading the firmware. To me it seems like the gamecontrollerdb.txt file is not picked up. But perhaps I'm doing something wrong, I'm not that familiar with the controller mappings and how that works. I use the C64 Maxi. I did the following changes to the gamecontrollerdb.txt for the maxi: I added: 030000005e0400008e02000000007801,XInput Controller,a:b0,b:b1,back:b6,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b10,leftshoulder:b4,leftstick:b8,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b9,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,platform:Linux,
030000001008000001e5000000000000,NEXT SNES Controller,a:b2,b:b1,back:b8,dpdown:+a1,dpleft:-a0,dpright:+a0,dpup:-a1,leftshoulder:b4,rightshoulder:b6,start:b9,x:b3,y:b0,platform:Linux,and modified the Speedlink mapping: 030000000b0400003365000000010000,Speed-Link Competition Pro,x:b0,y:b1,back:b2,start:b3,b:b4,a:b5,lefttrigger:b6,righttrigger:b7,leftx:a0,lefty:a1,platform:Linux,Any ideas what's happening here? |
|
|
|
Post by spannernick on Apr 1, 2020 15:23:16 GMT
Hi Span, thanks for the USB hack, it work really great with the carousel games. But I have some problems when adding new controllers. I tested to use the gamepad tool to add two controllers, but I can't get them to work. I also have a Speedlink Competition Pro and modified the button mappings based on some info I found here : thec64community.online/thread/100/usb-gamepad-ninento-snes-controllerBut that does not work either, the same mappings are still used after upgrading the firmware. To me it seems like the gamecontrollerdb.txt file is not picked up. But perhaps I'm doing something wrong, I'm not that familiar with the controller mappings and how that works. I use the C64 Maxi. I did the following changes to the gamecontrollerdb.txt for the maxi: I added: 030000005e0400008e02000000007801,XInput Controller,a:b0,b:b1,back:b6,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b10,leftshoulder:b4,leftstick:b8,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b9,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,platform:Linux,
030000001008000001e5000000000000,NEXT SNES Controller,a:b2,b:b1,back:b8,dpdown:+a1,dpleft:-a0,dpright:+a0,dpup:-a1,leftshoulder:b4,rightshoulder:b6,start:b9,x:b3,y:b0,platform:Linux,and modified the Speedlink mapping: 030000000b0400003365000000010000,Speed-Link Competition Pro,x:b0,y:b1,back:b2,start:b3,b:b4,a:b5,lefttrigger:b6,righttrigger:b7,leftx:a0,lefty:a1,platform:Linux,Any ideas what's happening here? I don't know, Maybe THEC64 Maxi reads the gamecontrollerdb.txt file before its over-mounted... anyone know ..? I was thinking is there some code that I could try to get the C64 Mini/Maxi to read thegamecontrollerdb.txt again when the Carousel reloads..? |
|
|
|
Post by kugelblitz on Apr 1, 2020 16:09:18 GMT
The gamecontrollerdb might get searched every time a controller is plugged in. So you might want to plug the controller out and back in again, that might help.
|
|
|
|
Post by spannernick on Apr 1, 2020 16:12:30 GMT
|
|
|
|
Post by lantzelot on Apr 1, 2020 19:01:57 GMT
The gamecontrollerdb might get searched every time a controller is plugged in. So you might want to plug the controller out and back in again, that might help. I thought so too, but that does not help. Anyone else that have tried this and got it to work? |
|
|
|
Post by spannernick on Apr 2, 2020 13:40:49 GMT
It looks to me like it reads the file before it executes the64 file, if so then mounting it here will not make any difference.(I will keep the code cause you never know maybe one day get it to work, just need THEC64(SDL) to read the gamecontrollerdb.txt again but I don't know the code to get it to do it, can't find anything on the net. The only other way of editing it is using TheC64-X-Windows v2 Mod and in its firmware under "/usr/share/the64/ui/data/gamecontrollerdb.txt". Make sure to make a backup of the gamecontrollerdb.txt file first before editing it. |
|
|
|
Post by jj0 on Apr 2, 2020 20:12:31 GMT
It looks to me like it reads the file before it executes the64 file, if so then mounting it here will not make any difference.(I will keep the code cause you never know maybe one day get it to work, just need THEC64(SDL) to read the gamecontrollerdb.txt again but I don't know the code to get it to do it, can't find anything on the net. The only other way of editing it is using TheC64-X-Windows v2 Mod and in its firmware under "/usr/share/the64/ui/data/gamecontrollerdb.txt". Make sure to make a backup of the gamecontrollerdb.txt file first before editing it. You can kill 'the64' at the beginning of start.sh and then run it again at the end. |
|
|
|
Post by spannernick on Apr 3, 2020 13:02:07 GMT
It looks to me like it reads the file before it executes the64 file, if so then mounting it here will not make any difference.(I will keep the code cause you never know maybe one day get it to work, just need THEC64(SDL) to read the gamecontrollerdb.txt again but I don't know the code to get it to do it, can't find anything on the net. The only other way of editing it is using TheC64-X-Windows v2 Mod and in its firmware under "/usr/share/the64/ui/data/gamecontrollerdb.txt". Make sure to make a backup of the gamecontrollerdb.txt file first before editing it. You can kill 'the64' at the beginning of start.sh and then run it again at the end. I am doing that, I klll the64 file at the beginning and start it at the end of start.sh file, but he say its still not reading his controller(its not working),so I am guessing that Linux on THEC64 is reading the gamecontrollerdb.txt as THEC64 is booting,I don't know,do you know a way to get Linux or sdl to read that file again,with some code or something, Jeroen..? I can't see what it doing cause I can't log on to it via UART. |
|
|
|
Post by jj0 on Apr 3, 2020 17:47:09 GMT
You can kill 'the64' at the beginning of start.sh and then run it again at the end. I am doing that, I klll the64 file at the beginning and start it at the end of start.sh file, but he say its still not reading his controller(its not working),so I am guessing that Linux on THEC64 is reading the gamecontrollerdb.txt as THEC64 is booting,I don't know,do you know a way to get Linux or sdl to read that file again,with some code or something, Jeroen..? I can't see what it doing cause I can't log on to it via UART. It must be something else, the file is read by 'the64'. |
|
(Friday The 13th,Arcade Hall of Fame and more) v1.06 uploaded now, all games should work now.
Feb 5, 2024 14:16:57 GMT