Building Universal Peachy Printer Software

[Anuvin]

How are you running it and on what?????

Intel i5 2500 3.3Ghz
8GB g-skill memory
Radeon 6750 HD

Fresh install of Windows 10 might have made all the difference. Not sure. I wish I was having the same issue so I could try to work on it with you, but everything is running perfectly. Ran the installer and that was it.

[mike_biddell]

Intel i5 2500 3.3Ghz
8GB g-skill memory
Radeon 6750 HD

Fresh install of Windows 10 might have made all the difference. Not sure. I wish I was having the same issue so I could try to work on it with you, but everything is running perfectly. Ran the installer and that was it.

My laptop is a similar spec. Core i5 Dell Inspiron, running windows 10. There is something odd about the openGL check in the Peachy software as it sees my graphic capability as openGL 1.1 when it is actually 3.1 !!!

I'll try installing again.

[mike_biddell]

My laptop is a similar spec. Core i5 Dell Inspiron, running windows 10. There is something odd about the openGL check in the Peachy software as it sees my graphic capability as openGL 1.1 when it is actually 3.1 !!!

I'll try installing again.

Just uninstalled and re-installed ..... no joy

error.jpg

[3dspider]

@mike, this looks like a bug with the kivy framework.
see https://github.com/kivy/kivy/issues/3576

it looks like v1.9.1 introduced this bug, if peachy compiles the windows version with 1.9.0, it should work properly.

[rylangrayston]

@mike, this looks like a bug with the kivy framework.
see https://github.com/kivy/kivy/issues/3576

it looks like v1.9.1 introduced this bug, if peachy compiles the windows version with 1.9.0, it should work properly.

good eye mike_biddle and 3dspider !

in the latest build_linux.sh found here https://github.com/PeachyPrinter/pea...build_linux.sh
on line 80 I see this:
pip install -I -U git+https://github.com/kivy/kivy.git@master

and here: https://github.com/kivy/kivy/releases
you can see that the 1.9.1 relice has been pushed to kivys master branch
so it looks like were are using the latest kivy v1.9.1

you could try changing line 80 to get the 1.9.0 branch instead of the 1.9.1 branch containing the bug :S
of course that could also break other things, so hopfully it wont take long for the good people at kivy to fix this
Better yet someone could help fix the kivy bug.