Fast VBOs for rendering not supported. Using slower default method.
Error: Line Number is not last Line Number+1, Last Line:2684
Resend:2684
Das anyone know what to do now?
Hi billieboef,
did the display of the “virtual” print area in Repetier Host change when the error occured? Was the filament still visible as usual?
Cheers,
kuraasu
Are you using octoprint? I have that a lot in octoprint (octopi actually).
Some work arounds the combination of which seems to have solved it for me: after each print, reboot the pi (or octoprint). If I dont do this, a second print will fail 90% of the time with that error.
And try another USB cable.
edit: judging by the fast VBO thing, it seems you use repetier. In that case, Id try another USB cable, although I never had it in repetier AFAIK.
I changed the USB cable, no different.
After the stop Windows came with a error in Repetier.
did the display of the “virtual” print area in Repetier Host change when the error occured? Was the filament still visible as usual?
Cheers,
kuraasu
Yes the filament was still visible as usual after the Stop.
Hi billieboef,
which version of Repetier Host are you using? 0.84? 0.90? 0.95?
It seems there are some issues with operating systems using old OpenGL versions. When starting Repetier Host, the first line in the log should report the OpenGL version. What do you get there?
As temporary solution, disabling the “Show Filament” is recommended, since that’s what needs those fast rendering functions.
Cheers,
kuraasu
I am using Repetier-Host V0.84
And which OpenGL version does Repetier report?
I think we may be on the wrong track here. I doubt the VBO message has anything to do with the lines going out of sync. On my venerable laptop with age old integrated graphics, I get the same message about unsupported VBO, and repetier automatically disables the filament view while printing. Its not an issue.
The “Line Number is not last Line Number+1” is something Ive frequently seen on my octoprint server; since its a raspberry without even a GUI running, its not related to the VBO/OpenGL thing. In my case, I believe it was caused either by a bug in octoprint misinterpreting some line Marlin gives when it finished printing, and/or when a timeout occurs. Ever since upgrading octoprint, replacing my USB cable, and increasing the timeout settings in octoprint, Ive not seen it again, so Im not sure where to point the finger exactly. I just have never seen it in Repetier.
edit: on second thought; maybe the old version of repetier does not disable filament view, and this causes the PC to slow down enough to cause a timeout issue, triggering that error. Could be far fetched, but who knows.
Hi P4man,
sorry, but your argument is flawed. Since OctoPrint doesn’t have rendering like Repetier, you can’t deduct anything from the observation that it doesn’t have any rendering related errors. Further, OP seems to have some bug somewhere else, but that again has no relation to Repetier.
One missing line is not a problem, that’s what transmission control through the N commands is there for. The line is resent and it gets logged to inform the user. If it’s ten missed lines, that’s a different story, but so far, there’s only one mentioned here. The more important issue is the print being stopped. The missed line could have been an omen for the error that actually crashed Repetier, or it may also be unrelated.
Not so far fetched imho. But let’s see about the OpenGL.
Cheers,
kuraasu