|
|
Post by spannernick on Jul 3, 2020 17:56:59 GMT
Thanks but I have already updated that code in PCUv1.13.. Ok, then I have a suggestion for a bigger update  . In the attached there's a: - Replacement ' start.sh' (based on PCU v1.12) - New script ' switch-games.sh' - New file bin/evtest binary for reading joystick buttons To use, extract to the root of the PCU USB drive. If you use this then you only have to run the fake upgrade once after switching the Mini/Maxi on, after that you can press the unused 2nd and 4th button (from the 4 buttons row on the joystick) simultaneously and then release them again to switch to the next folder. So you don't need to do a fake upgrade every time to switch folders. This way you also don't need a start.sh and theC64-9_9_94.bin in each games directory. The mounts that are only done once are still in the start.sh, the ones that differ per game directory (game folder, language files, music) are in the switch-games.sh where it waits for the joystick buttons to be pressed. Using the evtest program you can also test at the beginning of start.sh whether e.g. the two fire buttons are pressed and then start X Windows instead of PCU. I have not implemented that though but maybe you can add that to v1.13? Got it now, thanks..  I tried to remove the zip, cause someone might try and add it, next time can you pm me it please, if you post it here for me to download. users might try and download it and add it and mess it up and then complain about it not working, thanks for this your a star.. I have downloaded it now, Thanks again... I had to delete the post to remove the zip file..sorry but a copy of it is here quoted.. oh and btw your a moderator now cause your a member of the new C64 Developer Group... so you can move posts and that if you think there are in the wrong place and delete posts too and that, I trust you.. you should see Actions on the top left now,let me know if you don't see it. |
|
|
|
Post by canicant on Jul 4, 2020 11:23:36 GMT
--NOW SORTED OUT-- Hi, What am i doing wrong? I have downloaded the .img file and copied it to the USB stick and all files are present but when i try to do the update i just get a black screen (nothing happens) i have also tried downloading the PCUv1.12 file and still get the same result, so i'm stumped  Rob. P.S i am using a mini C64 Edit: Managed to figure it out, I had to update the machine firmware before it would work. |
|
|
|
Post by spannernick on Jul 4, 2020 15:49:08 GMT
--NOW SORTED OUT-- Hi, What am i doing wrong? I have downloaded the .img file and copied it to the USB stick and all files are present but when i try to do the update i just get a black screen (nothing happens) i have also tried downloading the PCUv1.12 file and still get the same result, so i'm stumped Rob. P.S i am using a mini C64 Edit: Managed to figure it out, I had to update the machine firmware before it would work. Usually update v1.3.1 and 1.3.2 works fine, something else I forget to add to first post.. |
|
|
|
Post by wini on Jul 4, 2020 16:30:33 GMT
Hi, why is the topic PCU only shown if i am logged in with username and not shown as guest or not logged in?
|
|
|
|
Post by spannernick on Jul 4, 2020 17:29:11 GMT
Guests can't access The CBM Game Zone now, you have to be a member, I did post about it in About the Forum, I am trying to make it worth while been a member of the forum.. |
|
|
|
Post by wini on Jul 4, 2020 17:57:59 GMT
okay, thank You
|
|
|
|
Post by spannernick on Jul 4, 2020 18:39:50 GMT
Had a Idea, when the VIC20 comes out, I be able to add its carousel to PCU so both carousels will be able to be on one device, C64 Maxi or VIC20 so I be able to bring up a gameslist with the Vic20 Carousel so if it has VIC20 Classic mode you be able to use it on a C64 Maxi, unless RGL will stop the VIC20 Carousel running on THEC64 Maxi like you can't Run carousel from the THEC64 Maxi on the Mini.
|
|
|
|
Post by spannernick on Jul 4, 2020 19:01:27 GMT
I actually find "The Maxi Tool" a pain in the arse, I've gone back to doing the old way when we were using the FEL method, for new games at least, once you get a rhythm going it works for me, photoshop,vice and notpad++ open and edit away. Btw span, Nightmare on elm street crashes for me...but it is a 3 disk game...maybe why! Great job with Project Carousel though, re-energized me to fire up the mini again! Is it possible to add more folders? I've reached the limit on most of them already i.e. 0-C, D-K, etc? An explanation on how to do this would be great, given you added the favourites folder so quickly. Glenn FEL method works fine of course though if you haven't tries it yet you might find the X Windows Mod slightly easier to work with? How would I add this to the script, do I add it to switch-games.sh and add it to this part...? I have it in its own script.. |
|
|
|
Post by brook82 on Jul 6, 2020 19:21:52 GMT
How many games does the favourites carousel hold?
|
|
|
|
Post by jj0 on Jul 6, 2020 20:52:16 GMT
FEL method works fine of course though if you haven't tries it yet you might find the X Windows Mod slightly easier to work with? How would I add this to the script, do I add it to switch-games.sh and add it to this part...? I have it in its own script.. It depends a bit on what you want the X Windows mod to be able to do: - If you want to allow it to modify the Mini/Maxi without all the mounts that the PCU does then you have to check for the proper joystick buttons before you do all the PCU stuff in an 'if <joystick buttons pressed> then do X Windows else do PCU stuff' type construction
- If you want to allow it to modify the Mini/Maxi after the PCU mounts have been done then then you do the PCU mounts first and then an 'if <joystick buttons pressed> then do X Windows' and after that (so if no buttons pressed or X Windows exited) do the rest of PCU stuff (starting the switch-games.sh)
Either way I would put the check in start.sh. It is a different check/different purpose than the switch-games.sh, but the code to check for the joystick is of course similar except that it doesn't wait until button(s) are pressed but only checks whether they are pressed:
# Check whether the joystick buttons are pressed
JOY1_BT1=00
JOY1_BT2=00
JOY2_BT1=00
JOY2_BT2=00
/mnt/bin/evtest --query /dev/input/event1 EV_KEY BTN_PINKIE
JOY1_BT1=$?
/mnt/bin/evtest --query /dev/input/event1 EV_KEY BTN_BASE2
JOY1_BT2=$?
/mnt/bin/evtest --query /dev/input/event2 EV_KEY BTN_PINKIE
JOY2_BT1=$?
/mnt/bin/evtest --query /dev/input/event2 EV_KEY BTN_BASE2
JOY2_BT2=$?
# Are they pressed?
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
<do stuff to start X Windows & hold until it exits>
else
<do stuff for PCU>
fi
The code above still checks for the back row buttons but if you run /mnt/bin/evtest from the commandline and press the fire buttons then you can find out what they are named and change the button names above. |
|
|
|
Post by spannernick on Jul 7, 2020 8:30:23 GMT
Do I have to type a command like "/mnt/bin/evtest --query /dev/input/event1" If I type /mnt/bin/evtest its just comes with USAGE: And how to use it...? Oh and if anyone wants to use the Sega Mega Drive Control Pad from The Mega Drive Mini its added to the gamecontrollerdb.txt so it works with PCU.. |
|
|
|
Post by jj0 on Jul 7, 2020 9:00:59 GMT
Do I have to type a command like "/mnt/bin/evtest --query /dev/input/event1" If I type /mnt/bin/evtest its just comes with USAGE: And how to use it...? I do the following on my Mini: # mount /tmp/usbdrive/sda1 /mnt
# /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20-supplyer
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
Or on the Maxi: # /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: RGL Multi Function Power Button
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
And then I select 1 or 2 to select a joystick. I assume you are getting this: # /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
USAGE:
Grab mode:
evtest /dev/input/eventX
Query mode: (check exit code)
evtest --query /dev/input/eventX <type> <value>
<type> is one of: EV_KEY, EV_SW, EV_LED, EV_SND
<value> can either be a numerical value, or the textual name of the
key/switch/LED/sound being queried (e.g. SW_DOCK).
#
This means it doesn't see any devices, your /dev/input doesn't have any eventX devices for the joysticks. So either you have no joysticks attached or something else is wrong. Are you doing this on a Mini, Maxi, DIY Maxi? |
|
|
|
Post by spannernick on Jul 7, 2020 9:05:22 GMT
THEC64 Maxi PI with X-Windows mod so will have use my C64 Mini then, have no access to shell in the C64 Maxi PI. have not changed password yet got to copy it from my mini, need a way of changing the password in X-Windows Mod, maybe a script..?.. maybe this part put in a script or something.. You properly don't need all of it and you would need to get the script to bring up a shell so you can type the new password, linkDam protection... |
|
strud
Creatures
Posts: 18
|
Post by strud on Jul 7, 2020 10:57:50 GMT
Anyone who wants to add support for the Mayflash Arcade Flightstick F300 can add the following code to the appropriate gamecontrollersdb.txt file in PCU: 03000000242f00006800000011010000,Mayflash Arcade Flightstick F300 (DInput),a:b0,lefttrigger:b1,b:b3,dpdown:b4,start:b6,back:b7,righttrigger:b8,dpup:b9,y:b10,start:b11,x:b12,dpup:h0.1,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,platform:Linux, It uses the following button configuration: Unfortunately, you will need to use the original joystick to do the initial launch of PCU as the official firmware does not support this stick at all.
|
|
|
|
Post by spannernick on Jul 7, 2020 11:49:14 GMT
Do I have to type a command like "/mnt/bin/evtest --query /dev/input/event1" If I type /mnt/bin/evtest its just comes with USAGE: And how to use it...? I do the following on my Mini: # mount /tmp/usbdrive/sda1 /mnt
# /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20-supplyer
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
Or on the Maxi: # /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: RGL Multi Function Power Button
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
And then I select 1 or 2 to select a joystick. I assume you are getting this: # /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
USAGE:
Grab mode:
evtest /dev/input/eventX
Query mode: (check exit code)
evtest --query /dev/input/eventX <type> <value>
<type> is one of: EV_KEY, EV_SW, EV_LED, EV_SND
<value> can either be a numerical value, or the textual name of the
key/switch/LED/sound being queried (e.g. SW_DOCK).
#
This means it doesn't see any devices, your /dev/input doesn't have any eventX devices for the joysticks. So either you have no joysticks attached or something else is wrong. Are you doing this on a Mini, Maxi, DIY Maxi? Got it working on THEC64 Mini and X-Windows Mod(XWM takes a while to load up on thec64 Mini, its a lot faster on thec64 Maxi PI), evtest says "fire button 1 is BTN_TRIGGER and fire button 2 is BTN_THUMB" so do I add them to these lines, like this.. |
|
|
|
Post by spannernick on Jul 7, 2020 13:55:18 GMT
This might help someone.. |
|
|
|
Post by jj0 on Jul 7, 2020 14:41:55 GMT
I do the following on my Mini: # mount /tmp/usbdrive/sda1 /mnt
# /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20-supplyer
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
Or on the Maxi: # /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: RGL Multi Function Power Button
/dev/input/event1: THEC64 Joystick THEC64 Joystick
/dev/input/event2: THEC64 Joystick THEC64 Joystick
Select the device event number [0-2]:
And then I select 1 or 2 to select a joystick. I assume you are getting this: # /mnt/bin/evtest
No device specified, trying to scan all of /dev/input/event*
USAGE:
Grab mode:
evtest /dev/input/eventX
Query mode: (check exit code)
evtest --query /dev/input/eventX <type> <value>
<type> is one of: EV_KEY, EV_SW, EV_LED, EV_SND
<value> can either be a numerical value, or the textual name of the
key/switch/LED/sound being queried (e.g. SW_DOCK).
#
This means it doesn't see any devices, your /dev/input doesn't have any eventX devices for the joysticks. So either you have no joysticks attached or something else is wrong. Are you doing this on a Mini, Maxi, DIY Maxi? Got it working on THEC64 Mini and X-Windows Mod(XWM takes a while to load up on thec64 Mini, its a lot faster on thec64 Maxi PI), evtest says "fire button 1 is BTN_TRIGGER and fire button 2 is BTN_THUMB" so do I add them to these lines, like this.. Yes |
|
|
|
Post by spannernick on Jul 7, 2020 21:01:51 GMT
Got it working on THEC64 Mini and X-Windows Mod(XWM takes a while to load up on thec64 Mini, its a lot faster on thec64 Maxi PI), evtest says "fire button 1 is BTN_TRIGGER and fire button 2 is BTN_THUMB" so do I add them to these lines, like this.. Yes I was wondering... What's "/dev/ttyS0" ...? I thought it was the serial..? If I don't ask I don't know.. I trying to understand your code.. I am still learning. The only thing I have coded is in Flash. This is the biggest Projects I have done on Linux or too do with Linux, Well I did make Commodore OS32bit, I learn a lot doing that, I made that in 2012, I was thinking of making X-Windows mod looking like COS32bit.. I am still trying to work out how to add the XWM start code to the switcher code, dose it need its own script or can it be added to the game switcher script, I think it needs it own script... Would this work..? I plain to use the triangle buttons and the 4th Menu button but they act like fire buttons don't they so when you change Carousel Gamelists by pressing TR2+Menu it will try and start a game too, Just realised.. |
|
|
|
Post by jj0 on Jul 8, 2020 8:05:09 GMT
I was wondering... What's "/dev/ttyS0" ...? I thought it was the serial..? If I don't ask I don't know.. I trying to understand your code.. I am still learning. The only thing I have coded is in Flash. This is the biggest Projects I have done on Linux or too do with Linux, Well I did make Commodore OS32bit, I learn a lot doing that, I made that in 2012, I was thinking of making X-Windows mod looking like COS32bit.. /dev/ttyS0 is indeed the serial port / UART. I send the output/messages to it so I can see what's happening when the update is run by the64. I thought about making the X Windows MOd looking lije COS32Bit as well, but never got around asking you about it  That would not work well, as (due to it being an eternal loop because of the ' while true') it would continuously check the joystick buttons and if the right ones are pressed run the X Windows Mod. But if they are not pressed it would not continue to the rest of the PCU script, and also if the X Windows Mod exits the rest of the PCU script (if that's what you want) would also not be executed. It would just go back to waiting for the joystick buttons again. I think the X Windows Mod can be started using it's own script like you've done. But that script should not kill/start the64, that's better done at the beginning of start.sh because you need to do that for PCU as well: # Stop the Carousel
until [ `ps | grep -e the64 | wc -l` -eq 1 ]
do
killall the64
doneAs I mentioned earlier you need to put the 'Does the user want to start the X Windows Mod' at the top of start.sh (as you have done in your example above) but you only need to check once if the right joystick buttons are pressed. If the are then run X Windows Mod, if they are not then run the rest of the PCU. It depends a bit on what you want the X Windows mod to be able to do: - If you want to allow it to modify the Mini/Maxi without all the mounts that the PCU does then you have to check for the proper joystick buttons before you do all the PCU stuff in an 'if <joystick buttons pressed> then do X Windows else do PCU stuff' type construction
- If you want to allow it to modify the Mini/Maxi after the PCU mounts have been done then then you do the PCU mounts first and then an 'if <joystick buttons pressed> then do X Windows' and after that (so if no buttons pressed or X Windows exited) do the rest of PCU stuff (starting the switch-games.sh)
Either way I would put the check in start.sh. It is a different check/different purpose than the switch-games.sh, but the code to check for the joystick is of course similar except that it doesn't wait until button(s) are pressed but only checks whether they are pressed.
So you need something like: ... read joystick button code ...
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
<start X Windows Mod>
# After X Windows Mod exits don't do anything else
else
<do PCU stuff>
fior ... read joystick button code ...
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
<start X Windows Mod>
# After X Windows Mod exits continue with PCU
<do PCU stuff>
fior even <do PCU stuff>
... read joystick button code ...
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
<start X Windows Mod>
fi
<do rest of PCU stuff>
That's why I chose the two unused buttons to swap the games list. But for starting the X Windows mod the two fire buttons are perfect, as the user can then press the left fire button to start the fake upgrade and then press the other fire button as well and keep them pressed until the X Windows Mod has started. |
|
|
|
Post by spannernick on Jul 8, 2020 12:54:11 GMT
I was wondering... What's "/dev/ttyS0" ...? I thought it was the serial..? If I don't ask I don't know.. I trying to understand your code.. I am still learning. The only thing I have coded is in Flash. This is the biggest Projects I have done on Linux or too do with Linux, Well I did make Commodore OS32bit, I learn a lot doing that, I made that in 2012, I was thinking of making X-Windows mod looking like COS32bit.. /dev/ttyS0 is indeed the serial port / UART. I send the output/messages to it so I can see what's happening when the update is run by the64. I thought about making the X Windows MOd looking lije COS32Bit as well, but never got around asking you about it As I mentioned earlier you need to put the 'Does the user want to start the X Windows Mod' at the top of start.sh (as you have done in your example above) but you only need to check once if the right joystick buttons are pressed. If the are then run X Windows Mod, if they are not then run the rest of the PCU. It depends a bit on what you want the X Windows mod to be able to do: - If you want to allow it to modify the Mini/Maxi without all the mounts that the PCU does then you have to check for the proper joystick buttons before you do all the PCU stuff in an 'if <joystick buttons pressed> then do X Windows else do PCU stuff' type construction
- If you want to allow it to modify the Mini/Maxi after the PCU mounts have been done then then you do the PCU mounts first and then an 'if <joystick buttons pressed> then do X Windows' and after that (so if no buttons pressed or X Windows exited) do the rest of PCU stuff (starting the switch-games.sh)
Either way I would put the check in start.sh. It is a different check/different purpose than the switch-games.sh, but the code to check for the joystick is of course similar except that it doesn't wait until button(s) are pressed but only checks whether they are pressed.
So you need something like: ... read joystick button code ...
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
<start X Windows Mod>
# After X Windows Mod exits don't do anything else
else
<do PCU stuff>
fior ... read joystick button code ...
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
<start X Windows Mod>
# After X Windows Mod exits continue with PCU
<do PCU stuff>
fior even <do PCU stuff>
... read joystick button code ...
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
<start X Windows Mod>
fi
<do rest of PCU stuff>
That's why I chose the two unused buttons to swap the games list. But for starting the X Windows mod the two fire buttons are perfect, as the user can then press the left fire button to start the fake upgrade and then press the other fire button as well and keep them pressed until the X Windows Mod has started. The Triangle button 2 and 4th button Menu dose work, it make a sound like its going to start a game but don't and changes to the next gamlist, you have to make sure you press and hold down menu button first then Tringle button 2 and it works every time.. Would this work, where would I put in in the switch-game.sh at the beginning... ? .. I am confused.. oh put it at the top of start.sh..? What I want it to do is load up PCU and if I press and hold down 4th Menu Button and then press Triangle Button 1 it starts X -Windows Mod script and If I press hold Menu buttion down and Triangle Button 2 it changes the Gamelist like it does now.. I finds it hard to understand sometime, I am Dyslexic .. that why I miss words when I am typing I see them in my head that I have typed them but then find there not on the screen. I am Autistic to so it clashes some times... I can be slow sometimes.. , I see the world differently it other people.(and I don't see dead people... ) (In the 80s I went to a special school for kids that could not cope with normal school, I couldn't read or write properly at 16(1987) I can only now cause of Google(spell checker) and the way the internet is... so I am thankful to the internet and how it is now, We had the BBC Model B at school but I use it to just play games on it, I hated Basic could never learn it,(I had a C64 at home so could only use that at half term or summer holidays, I did miss it when I was at school) I hated school, I was bulled most of the time there so when I left at 16, I felt free at last. I was in care from the age of 9 to 18 too so for 9 years. I went back to live with my Mum when I was 18(1989), She was a Alcoholic. That where the name spanner came from cause it sounded like spasss close to spastic or "your a tool, your thick", but now use the name cause I am good a working things out and how things tick, my partner started calling me it, she said its a wicked name, I have been called it for 10 years now, no one calls me Nick no more, not even my son. Now you know why I am called Spannernick.. on the Internet. I use Spannernick or Spanner as a user name. I am Spanner on Lemon 64 and EAB, Properly to much info.. I just wanted you to know why I am the way I am.. ) I am a collector of Retro Computers and Consoles, so some of them I have, have had for over 30 years, I just like them and would never part with them, took a long time to collect them.... Amiga500,600,1200,Amiga CD32, Atari 130XE,800XL,520fm,Atari GS, Mattel Aquarius, C64C(with a 1983 C64 motherboard inside it, 38 years old and still working.. ), VIC20, C16, Acorn Electron, BBC Model B, Sega Dreamcast, Sega Saturn, PlayStation 1,2,3,4, Sega Master System 1 and 2, Sega Mega Drive 2, Sega Mega CD2, Nintendo 64, Super Nintendo, Nintendo DSLXL,3DS,2DS, Xbox Original, Xbox 360... oh and the Minis..THEC64 Mini X2, THEC64 Maxi PI, MD Mini and PS1 Classic.... Think that's all of them.. I love my Amigas and C64, the most.. If you want anything from it I can send it to you but got to be careful of the memory theC64 Mini and maxi have but don't see why not try adding the Cos background(you have to make it smaller in size its like 1900x1050 I think, and change the bar at the bottom to top but it would need the drop down menus too, you can add scripts to the drop down menu to add a script too, well I could in Mint 10, COS32bit is based on, instead of it being on the desktop, like the backup script, COS32 has loads of scripts added to its top bar menu under Commodore OS32bit menu. X windows mod uses Debian, I was organlly going to use that for COS32bit but realise it was Mint 10 they used on the 64bit version so used the 32bit version of Mint 10.. |
|
|
|
Post by spannernick on Jul 8, 2020 17:39:41 GMT
or..
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event1 EV_KEY BTN_TOP
JOY1_BT1=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event1 EV_KEY BTN_BASE2
JOY1_BT2=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event2 EV_KEY BTN_TOP
JOY2_BT1=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event2 EV_KEY BTN_BASE2
JOY2_BT2=$?
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
/mnt/Carousel_Games/Options/X-Windows-Mod/x-win-mod-startup.sh $@
fi
I am not sure how to add the code to start.sh what I have tried so far don't work or stop script working.
|
|
|
|
Post by jj0 on Jul 8, 2020 17:41:57 GMT
or..
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event1 EV_KEY BTN_TOP
JOY1_BT1=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event1 EV_KEY BTN_BASE2
JOY1_BT2=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event2 EV_KEY BTN_TOP
JOY2_BT1=$?
/mnt/Carousel_Games/Games/Z_Other_Scripts/bin/evtest --query /dev/input/event2 EV_KEY BTN_BASE2
JOY2_BT2=$?
if [ "$JOY1_BT1$JOY1_BT2" = "1010" -o "$JOY2_BT1$JOY2_BT2" = "1010" ]
then
/mnt/Carousel_Games/Options/X-Windows-Mod/x-win-mod-startup.sh $@
fiYes, that would work. |
|
|
|
Post by spannernick on Jul 8, 2020 18:55:01 GMT
Yep it did work.. Thanks.. I see now why it has to be the fire buttons cause when you run the update your pressing fire button 1 already so you can quickly press and hold fire button 2 at the same time just after running the update.. to activate X-Windows mod.. its working now.. I have changed the code to it uses the fire buttons now. In the next couple of days PCUv1.13 will be released and will post how to use the buttons to change Carousel Gamelist Screens, its now a lot quicker changing them(thanks to Jerome) so don't need to disable Carousel Gamelist Favourites Screen any more, you can bypass it by holding 2 buttons down now so when LOADING appears on the screen you press and hold down Menu button and then press TR2 then you can now skip that screen, you can even press the buttons in a game and it will change to the next Carousel Gamelist.. its cool, I love it.. |
|
|
|
Post by jj0 on Jul 8, 2020 20:05:26 GMT
Yep it did work.. Thanks.. I see now why it has to be the fire buttons cause when you run the update your pressing fire button 1 already so you can quickly press and hold fire button 2 at the same time just after running the update.. to activate X-Windows mod.. its working now.. I have changed the code to it uses the fire buttons now. In the next couple of days PCUv1.13 will be released and will post how to use the buttons to change Carousel Gamelist Screens, its now a lot quicker changing them(thanks to Jerome) so don't need to disable Carousel Gamelist Favourites Screen any more, you can bypass it by holding 2 buttons down now so when LOADING appears on the screen you press and hold down Menu button and then press TR2 then you can now skip that screen, you can even press the buttons in a game and it will change to the next Carousel Gamelist.. its cool, I love it.. Can't wait for it to be released! 👍 |
|
strud
Creatures
Posts: 18
|
Post by strud on Jul 9, 2020 5:10:20 GMT
Legendary work guys! It's really interesting reading along with you working it out - just like a live changelog.
Excited to test out the next version. Thanks!
|
|
|
|
Post by bamm on Jul 9, 2020 14:06:04 GMT
Great stuff. Looking forward to it.
|
|
|
|
Post by bamm on Jul 9, 2020 14:22:34 GMT
Would it be possible to add the instructions text (what buttons should be pressed) to the loading screen? I know it's simple now but Just thinking a year from now, it would be easily fogotton.
|
|
|
|
Post by spannernick on Jul 9, 2020 17:06:40 GMT
Yes that what I was going to do put in the, HELP FILES and in the Carousel where its says what Carousel Gamelist Screen your on too.. |
|
|
|
Post by spannernick on Jul 10, 2020 20:21:13 GMT
Just an aside thought: how about tweaking the64 source to add more smarts to it. Perhaps it could be possible to embed a few things in there. E.g. I'm seeing presently that you've got a bash script that decides which sid chip to use, or whether to use jiffy dos or not. I was wondering, whether if instead some smarts could be added to thec64emu when it starts: 1. It knows the name/path of the vsf file that was passed into it. 2. From that path, it could infer the path of the associated .tsg file 3. It could then parse the .tsg file, look for new fields you're supporting (let's say for sid chip choice, jiffydos choice, etc) and apply those settings to the emulator. That way, you could configure such things per game? Sorry just seen your post, the64 is the Carousel but we only have the source for the Mini's Carousel and not sure if anything in it can be added or changed and I don't know what's in that, never looked at it really, this was the easier way I could do it, maybe jj0 could answer this question better than me, he knows more than me.. I do think the way RGL has done the games files and folders are wrong and could be organized better, the way they are at the moment its a pain to split the games up cause there not in there own game folder, I mean each game should be in its own folder and named the title of the game so you have all covers and screenshots png's, the games tsg and vsf.gz file all in one folder. |
|
|
|
Post by spannernick on Jul 10, 2020 21:35:26 GMT
I was thinking of using Carousel USB Folder Chooser to choose a folder by pressing both buttons down then Carousel USB Folder Chooser comes up then you use the joystick to pick one, what you think..? I have posted on that thread so hope FaberfoX replies to it soon, Good Idea, would make it easier to pick a folder... Do not worry, I will not be putting it in PCU v1.13, properly in PCU v1.14, if everything goes the way it should.. so will not put back the release. Just realised the name of PCU is very close to Carousel USB Folder Chooser, I might of had it in the back of my mind at the time of renaming the project.. |
|
.
I tried to remove the zip, cause someone might try and add it, next time can you pm me it please, if you post it here for me to download. users might try and download it and add it and mess it up and then complain about it not working, thanks for this your a star.. 
