pixelflow particles inconsitency, "brownian" motion
Opened this issue · 0 comments
hi there.
i'm running the flowfieldparticles_opticalflow capture example completely unedited on 2 different computers
both computers are running processing 3.4 64 bit,
glsl version 4.60.0
nvidia driver 397.64
Open pixel flow version 1.3.0 installed from add library menu.
both using same USB webcam
the difference is one is a laptop with 980m and one is a desktop with gtx1080.
the desktop is windows OS build 17134.165
the laptop is windows OS build 17134.165
the laptop runs well, but the when i run it on the dekstop the simulation quickly deteriorates into chaotic "brownian" motion. where as the laptop version settles nicely with no action on the camera, and forms nice waves on action.
now the REAL weird thing is the example used to run well on the desktop, i'm not sure what had changed that would break it, possibly a windows update? my windows version on the desktop with the issue is
"Feature update to Windows 10, version 1803"
but the laptop is W10 version 1803 as well
already reinstalled . processing, opf library, video library, gpu driver.
any suggestions of other things i could check would be very much appreciated.
EDIT: upon further inspection of the motion, the desktop particles are taking velocity from optical flow but not colliding with other particles, this means that each particle keeps its own trajectory without influence from the ones around it.
EDIT2: tried on 3rd PC, desktop ,
identical zotac gtx1080
graphics driver 398.11
fresh install processing 3.4
fresh install of libraries from add library (opf 1.3.0)
glsl 4.60.0
same USB webcam
windows version 1803
Windows OS build 17134.112
3rd PC worked well, properly formed waves. updated desktop with issue to 398.11 to attempt to match that config , still experiencing Brownian motion. is it possible that the difference is windows OS build is causing the issue?
EDIT 3 FIXED:
updated to latest driver 398.82 and it worked.
this to me implies that when windows updated from build .112 to .165 they broke compatibility with nvidia gpu driver 398.11 and earlier.
the reason i didnt try that first was because it was working fine on the other computers with the older gpu driver version numbers so i wanted to try those first for consistency.
i hope this info can be useful to someone,
Thomas, sorry for cross-posting this issue as a comment on your open-processing and vimeo
but i was kind of mind-boggled.
properly formed waves on laptop
info from processing console on desktop