Color display progress

[Vic_n78]

@profezzorn

Does it help to compile with optimization on?

If you mean to optimize for fastest code, I just did it and it does seem to be more fluid, it still slows down a tiny bit but not as noticeable, and it also seems faster when the saber is not ignited.

And lockups look very cool!

Here’s a link to a video:

Proffieboard Color Display Test

[profezzorn]

@Vic_n78

• The screen does not always boot up. Some times I need to turn on and off the saber several times for the screen to work.
• With the neopixel accents (38 total) fps looks smooth, but when I ignite it and it the proffieboard has to drive the extra 144 neopixels, it slows down noticeably, the crystal on the screen seems to get brighter but can’t really see clashes as they happen, I’m not sure if it’s because of the decrease in frame rate.

I was not really able to reproduce the boot up problem. However, I have tweaked the command delays a bit, so maybe it works better now?
I also recommend trying the v4.1 arduino-proffieboard plugin from the beta stream, as that seems to fix some problems for me.

I also put the display on the HF (high frequency) loop which should make it run smoothly even with lots of neopixels. (Of course, that could mean that the neopixels gets slower, we’ll see…)

[Vic_n78]

@profezzorn

I was not really able to reproduce the boot up problem. However, I have tweaked the command delays a bit, so maybe it works better now?
I also recommend trying the v4.1 arduino-proffieboard plugin from the beta stream, as that seems to fix some problems for me.

I also put the display on the HF (high frequency) loop which should make it run smoothly even with lots of neopixels. (Of course, that could mean that the neopixels gets slower, we’ll see…)

The boot up issue got resolved when I turned optimizations on.

I’ll try v4.1 when I get a chance.