WS2812RGB pin out not working

WS2812RGB if the desired number of LEDs is set from the properties it works.
Sometimes you have to adjust the layout by mirroring or rotating the matrix.
But if I connect more leds or more matrices through the input / output pins
only the first led or matrix works.
In reality, however, it is LEDs, strips and matrices are connected via the pins.
Greetings
Giordano

Thanks, I will have a look.

Sometimes you have to adjust the layout by mirroring or rotating the matrix.

I don't understnad this.
Can you explain why you have to do that?

But if I connect more leds or more matrices through the input / output pins
only the first led or matrix works.

Should be solved at:
- 0.4.15 Rev 233.
- Trunk Rev 531.

When testing sketches found online, the author has non-original hardware that behaves unpredictably.
If you use coupled 8x8 matrices just rotate them in the right way and then join them.
With a single 8x32 type matrix you have to modify the sketch while in the simulator you just need to rotate or mirror them.
P.S.
Now it works but it got about 8-10 times slower before my test circuit went 98% now it goes less than 20%.
Greetings
Giordano

When testing sketches found online, the author has non-original hardware that behaves unpredictably.
If you use coupled 8x8 matrices just rotate them in the right way and then join them.
With a single 8x32 type matrix you have to modify the sketch while in the simulator you just need to rotate or mirror them.

ok, now I understand.
Nice to know.

Now it works but it got about 8-10 times slower before my test circuit went 98% now it goes less than 20%.

This component needs to speed up the simulation to match the speed of the MCU.
In case of an AVR/Arduino, this means the simulation needs to run 16x faster, which uses much more cpu.
Also the leds that were not working didn't use cpu, now they use cpu.

The new simulation engine in 0.5.16 is much more optimized  for cases like this.

In Simulide 0.5.16 the same thing happens, only the first matrix works.
Greetings

You are right, I will have a look.

This issue should be solved at Rev 662.