Crystal Focus 4.x and beyond Bug list & Fix

[erv]

I thought it would be a nice way for group bug hunting and fixing to have this stickied. Feel free to add bugs you found. This is NOT a trouble shooting thread for CF. Post here ONLY if you really think you found an bug. Be sure to clearly describe it with accuracy. I'll edit the thread and the bug / fix list.

Erv'

Let's start with a bunch of bugs of the past, that will be fixed on the next batch of CF (aka 4.1)

- Erratic pulse + flicker combo fx values, hard to obtain the expected fx
[fixed] : use of an int instead of a long var in the code leading to int overflow (modulo 3276. [Fixed on 4.1]

- can't access the menu anymore. My last mod in the config.txt file was to set mute parameter to 1.
Last selected bank & configuration file is selected before accessing the menu and... stupidely the mute settings isn't overriden.
You can still "blind select" the next sound font in which mute is disabled, and confirm with the aux button. Or set mute back to 0 in the configuration file.
[Fixed] : mute is disabled during vocal menu access.

- Force Clash doesn't follow the "blaster priority" settings on the configuration file. When set to 1, the blaster parameter asks CF to wait for the end of a blaster / force / force clash sound file before accepting a swing. This is great for playing with a long blaster deflection SF and not getting the long "sound track" cut on the first swing you make. Works for Blaster and Force sound fx, but not force clash, in which an blade impact often makes the hilt "bump back" and trigger a swing. [Fixed] - Added the proper flag in the decision tree.

- clash flash fx not enabled during lockup (at start of the lockup aka initial blade contact) [Fixed] . The aux clash output goes on when lockup starts and lasts the duration configured in the config file (auxflashduration)
Some would like to have the aux flash control output activated during the WHOLE lockup, not during the initial blade clash. Not really a bug, but I could make a variant on this parameter, see discussion page 4. Added parameter xflashl (aux flash during lockup). Set to 1, the aux clash flash output stays on during the whole lockup until the aux button is released. [FIXED]

- New bug : if destination current can't be obtained during blade ignition (low batteries / high Vf luxeon like a lux V) AND quick on is selected AND it's the first startup, the ignition fx engine isn't lauching the hum sound after the poweron sound is played (silly case isn't it ?). [FIXED]

- May '09 : new bug found on the audio engine. Mad Cow actually mentionned this to me a while ago but it does that on long sound ONLY. A long hum sound or a few seconds long blaster blocking sequence tend to pitch down a bit within the last second of the sound. It's due to non constant sample rate in the playback interrupt.
I've reworked the audio engine on another of my boards, Droïd Core, and I will port it to CF asap. to be fixed

- August '09 : clash flash mini bug, stays on if initiated then followed immedialty with a power off. Power on resets the hing. FIXED in 4.3

[erv]

For the MODs, could someone sticky this one, I think it could be useful, thanks.
Erv'

[Novastar]

Thanks Tim! I appreciate it...

Regarding bugs... hey folks, I *JUST* found that one Erv mentioned about the "force2" thing yesterday, so... don't be afraid to mention something that you REALLY have been able to replicate.

Granted... it's going to be all about needles in haystacks now. Not going to be easy to locate bugs on CF v4 anymore.

[erv]

we have the haystack and needles thing in france too, I also like "cutting the rancor hair in 4 (all over the lenght)"
Details & minor bugs fixing but I give some importance to those anyway.
Thanks Tim for making this one as a sticky !

[Novastar]

Anyone?
Anyone?
Bueller? ... ... Bueller?

Not... one... person?
Not... one... finger?
Very well then... I go on.

heheh... seriously, has anyone found any strange "bugs" whilst wiring your new v4.1 CF boards?

[erv]

Silence can be a good news, once for a while

[Revan]

(sigh.) i just hope i can get my hand on one before i ship out for the Navy Seals...

[DarthHideous]

I have 3 sabers waiting on sound. However, I am also waiting on money. I have resorted to temporarily wiring them for illumination until I get the boards. Without sound, a saber is just a flashlight. Am I right? Since I am fairly new here, I first noticed the US boards, however, the more I read/see the more I think the CF is a better board. Especially with the SD chip.

[killphil]

OK, here's the problem. I have a CF 4.0. It's been installed in the same saber for nearly a year now. Only minor things that are easily remedied, but all in all, it's been working great.

Few days ago, I swapped out a couple fonts, double checked all my files and configs, all was alright. I've played around with it for a few more days until the battery indicator started flashing tonight.

I recharged it, and once it was done, I took it and did my usual spiinuing it in the living room, activating the clash by hitting it against the couch and recliner Nothing too hard or oput of the ordinary, and suddenly the board freezes up on me while doing a clash. The blade is still on but no response from the buttons. Then it just reboots itself.

I rebooted the saber again any way and tried it out. Same thing happens. I went thru all the fonts, some have instant on, while others don't. All fonts are doing this to me if a trigger the clash. It usually freezes up after about the 2nd to 4th clash. Not hitting it that hard either, and I know I've hit it harder than that in the past, so what gives?

I just got done reformatting my carrd about 10 times and am about to knit the thing back together again and see if this does the trick.

Anybody know what I'm talking about and what the problem could most likely be? Hope someone can chime in on this. Thanks.

[Obi-Dar Ke-Gnomie]

Mine did the same thing, but it happened when I dropped the saber. (Imagine my horror.) I think the mini-SD card was making poor contact in it's holder.

Make sure the contacts on the card are clean. You may have got oil from your hands on them. Or, the problem may be in the holder. Try inserting and removing the card several times to "freshen up" the contact surfaces. Make sure the kill plug is in when you do this.