|
|
| Line 1: |
Line 1: |
| ==No Longer Needed== | | ==No Longer Needed== |
| The bug has been fixed and a new update is available! Just go grab the latest! | | The bug has been fixed and a new update is available! Just go grab the latest! |
| ==I need your help fixing kJams!==
| |
| Can you help me?
| |
|
| |
|
| If you have '''Windows 10''' and are willing to do some testing, '''PLEASE help me''', as kJams is currently '''STUCK''' and can't move forward.
| | ==Old Info== |
| | | [[Debug/Old click here]] for the old info |
| ==Install Procedure== | |
| # [[History/x.1beta|go to this page]] and under the section '''x.1b17''', click the link that corresponds to your edition. eg: if you have "kJams 2", then click "2 Win"
| |
| # install that version. if you're installing under Windows for the first time, beware [[Defender|the Windows Defender problem]], and you'll need DotNET 3.5 , see [[Paddle|section 5.2 for video tutorial]].
| |
| # run kJams. Ensure it says b17 when it is starting
| |
| | |
| ==Testing Procedure==
| |
| # play songs. the crash happens at the start of a song, or right at the transition between songs
| |
| # you may need to play 30 DIFFERENT songs to get into the state where it crashes
| |
| # If you CAN get it to crash, send the crash report
| |
| # see if you can make it crash in that place '''consistently''', ie: play more songs and try to crash several times right at the start of songs.
| |
| # If you can get kJams to crash '''consistently''', only then please '''contact me''' via text:<br>'''(206) 419-2049''' <-- text, iMessages, whatsApp<br>'''kjamskaraoke''' <-- skype chat
| |
| # Then i will give you a version you can test to see if the problem is fixed.
| |
| | |
| When you're done, you can uninstall kJams (in "Add or Remove Programs"), then re-install the release version from [https://karaoke.kjams.com/product_downloads/ the downloads page].
| |
| | |
| ==Why the fuss?==
| |
| Last october, november, and december, i made a series of updates to kJams that caused problems for some windows users.
| |
| | |
| Always in the past, I've been able to identify and fix these types of problems, making a new release.
| |
| | |
| This time was different: i was unable to reproduce the problem locally, so i could not fix it.
| |
| | |
| So i simply reverted to the release i made BEFORE the problem started, which was b12. If you stay up to date, you've been on b12 since then, or told to downgrade if you sent me a crash report from a version greater than b12.
| |
| | |
| I've heard anecdotal evidence that b13 is stable, so today i set that as the current release.
| |
No Longer Needed
The bug has been fixed and a new update is available! Just go grab the latest!
Old Info
Debug/Old click here for the old info