I use previous version of 2.0. ordered 2 month before 2.0 release... any chance to have the 2.0 free?? ^^
On this version i have the same result with the app wizard setup. Left red light goes a bit on the top (5 led). Blue line on right goes on bottom (1 led).
My samsung tv near the stand is not straight so the bottom line is a bit longer than the top one. Perhaps its cause of this i have this result but its strange for the other side.
It seems that the strip dont manage each led with different colour but 3 by 3. It adds a difficulties to auto setup if a cutting line isnt exactly on an angle.
They must update firmware and app to setup exactly the length of each edge strip. On both version.
Agree.
And in addition: Alita needs support for 4-side strip.
I got the comparison to the ASUS ROG AURA TERMINAL which got 4-sides connector and it looks so much better!
Oh, and of course a color correction option for both too!
Oh, and a fix for only getting 45 fps instead of 60 with V-Sync on with Alita.
I'm not willing to publish a review before that is done.
@yenca
beginning at 24 fps (frames per second) it's fluid to your eyes.
Many movies in cinema got that.
But on fast cam moves you can still see that it's not perfect.
At least your game should get 30fps (like the old Xbox, but for a fluid experience 60 frames is the goal (that's the refresh rate of most normal TVs and monitors and the newer game consoles.
Pro Gamers are heading for even more with freesync or gsync monitors
V-Sync normally gets you stable 30fps or 60fps (the software sets the FPS to the Monitor Refresh rate.
G-Sync and Freesync gets you variable FPS as the monitors are able to set their refresh rate to the rate of the graphics card.
But it depends also on your hardware and graphics settings of the game, which FPS you get.
In my example: I get 60 FPS when LYTMI software is not running and 45 FPS with Lytmi running.
If I deactivate V-Sync I got over 80 FPS in that game (that's why I get 60 with V-Sync on.
Even with Lytmi software running and V-Sync off I get over 70 FPS which should lead into 60FPS with V-Sync on.
Here's a great example
https://www.youtube.com/watch?v=_SzGQkI-IwM
@Panagiotis Panagiotopoulos@Jack
shouldn't both cuts be with the same length (from a logical point of view)?
Because left + top = right + bottom
If you have cut less off the bottom because of the stand...
the software isn't aware of it and thinks your screen is larger on those 2 sides of the longer strip.
You tried to move the strips a bit?
@ajey when u look at panagiotis shot 1st blue line is shorter than the others. Moving strip will not change something.
I dont think he made a loop at this section which could results like . ^^
It isn't so simple. If you look at horizontal lines at the top everything is ok. But at the bottom isn't
I'm on the same boat, it looks like the box thinks the strip is longer than it really is
As you can see in this picture when setting up the lights with the app, the green part does not start at the corner
I only positioned the strip on top, I don't want to stick anything as long as it doesn't fully work
@Anthony Petiot
I use previous version of 2.0. ordered 2 month before 2.0 release... any chance to have the 2.0 free?? ^^
On this version i have the same result with the app wizard setup. Left red light goes a bit on the top (5 led). Blue line on right goes on bottom (1 led).
My samsung tv near the stand is not straight so the bottom line is a bit longer than the top one. Perhaps its cause of this i have this result but its strange for the other side.
It seems that the strip dont manage each led with different colour but 3 by 3. It adds a difficulties to auto setup if a cutting line isnt exactly on an angle.
They must update firmware and app to setup exactly the length of each edge strip. On both version.
Forgot to mention, I use Neo 2.0
I using neo 2.0 too
Same here! @Jack I think this could be solved with something as simple as being able to define led number per side. Also need in Alita, the PC version
Thanks
Agree. And in addition: Alita needs support for 4-side strip. I got the comparison to the ASUS ROG AURA TERMINAL which got 4-sides connector and it looks so much better! Oh, and of course a color correction option for both too! Oh, and a fix for only getting 45 fps instead of 60 with V-Sync on with Alita. I'm not willing to publish a review before that is done.
@ajey mine shows 22 fps... Im at 165hz monitor with gsync.
Is more fps better?
@yenca beginning at 24 fps (frames per second) it's fluid to your eyes. Many movies in cinema got that. But on fast cam moves you can still see that it's not perfect. At least your game should get 30fps (like the old Xbox, but for a fluid experience 60 frames is the goal (that's the refresh rate of most normal TVs and monitors and the newer game consoles. Pro Gamers are heading for even more with freesync or gsync monitors V-Sync normally gets you stable 30fps or 60fps (the software sets the FPS to the Monitor Refresh rate. G-Sync and Freesync gets you variable FPS as the monitors are able to set their refresh rate to the rate of the graphics card. But it depends also on your hardware and graphics settings of the game, which FPS you get. In my example: I get 60 FPS when LYTMI software is not running and 45 FPS with Lytmi running. If I deactivate V-Sync I got over 80 FPS in that game (that's why I get 60 with V-Sync on. Even with Lytmi software running and V-Sync off I get over 70 FPS which should lead into 60FPS with V-Sync on. Here's a great example https://www.youtube.com/watch?v=_SzGQkI-IwM
@Lytmi care to resolve my problem?
Could you show me how you cut the lights? According to the pictures, it's usually wrong cut
@Jack Sure
@Panagiotis Panagiotopoulos @Jack shouldn't both cuts be with the same length (from a logical point of view)? Because left + top = right + bottom If you have cut less off the bottom because of the stand... the software isn't aware of it and thinks your screen is larger on those 2 sides of the longer strip.
In that case one of the bottom or top LEDs should be ok. In my case both of LEDs stripes are having offset