The issue is that I have created a motion path that allows a circle to smoothly move around the screen in a seemingly random fashion using bezier functions. At present this generates about 2000 pairs of coordinates. My program works perfectly fine locally but of course as soon as I attempt to upload the file to pavlovia, all of the numpy functions break it and the conversion seems too laborious to implement.
So instead, I have written a python script that saves them to csv. I now simply import this file into an array using the above two lines of code but I can’t work out the JS equivalent.
So, as a workaround, I tried to list all the coordinates manually in the begin routine but this throws the path length error even though in that instance I’m not importing the file. When I shorten the array (list) to only two pairs of coordinates it bizarrely works.
My assumption is Pavlovia is baulking at the length (or size) of the file rather than the file path length.
The data when manually coded looks like:
or xList=[0.949560018,0.94552775,0.94149563,0.937463806,0.933432426,0.929401638,0.925371589,0.921342429,0.917314304,0.913287363,0.909261754,0.905237624,0.901215123,0.897194396,0.893175594,0.889158863,0.885144352,0.881132209,0.877122581,0.873115617,0.869111464,0.865110271… up to 2249 instances
But in both cases, when I truncate them to shorter sequences the error goes away.