Issues using CS4.5 new unstable parameters and FOC settings (neopixel)

[Shadeslinger]

I'm trying to use the unstable neopixel feature in a VV Acolyte with poor results. I read the blog on the VV site and changed the fcolor profile to an orange and left the main color red in the config. When I use that font though, what I get is an interesting "candy cane" saber of red with white flashes. I haven't found a CS4.5 manual and I'm new to both neopixel and colormixing. Is there something in the override file thats causing problems? Here's what's in the banks config:

drive=1023,0,0
fdrive=1023,550,0
focmix=111
tridenton=0
tridentoff=0
tridentm=000
tridentfx=0
tridentflk=0
tridentquick=0
shmrd=210
shmrp=6
shmrr=13
shmr%=0,50
focd=150
focp=10
focr=10
foc%=0,80
qon=300
qoff=0
flks=12
flkd=22
pulsed=0
pulsel=0
fade=0
shft=3
lsfadeon=0
lsfadeoff=0
lightstick=0
omnisabers=0
unstable=1
hcool=183
lcool=58
sparkf=143
sparkd=19
drift=0
mapb=13
mapc=63

Any help would be appreciated. It's been a while since I've been on this site and a lot has changed and advanced lol
 

[Shadeslinger]

Ok, so I screwed around with the color profile in the override and got it to work

I guess my next question is, as far as neopixel is concerned is there any point to have the drive and fdrive colors set if the overide will, well, override it anyway?

Also, if I want a red with orange FOC and a red with white FOC I have to have 2 seperate color profiles set up for that right?

Does that also mean that every time I take the battery out and reinsert every font bank will start on the first color profile (color0)?

[erv]

glad you got it to work !
legit question : I tend to leave the drive and fdrive just as a safe principle to have it defined to something, like if you decide to suddenly discard all the profiles, it still goes to something valid.

last used color profile is stored for each font. Once you have selected a profile while blade is on (or via RICE), use act. switch to have blade retraction, that will automatically save the profile as last used.
I haven't implemented start color yet on the CS, but that's an override setting on CF (just as an example) which allows to force the saber to always start with a specific profile when you cycle power (kill key or wake up from deep sleep)

[Shadeslinger]

Ahha! That makes sense now. Thank you for the response erv :)

[Darth Brooks]

Good info, thanks guys... I've got a neo with CS4.5 in the works coming down the road here.