Recently updated to 1.5.5 and when trying to surface a board alteration of dimensions refused to change after multiple attempts. Appeared to import dimensions from previous version but could never have the changes accepted. Back to 1.5.4 and all worked fine.
@mwbeard1957 FWIW, Mitch, I just tried it and it worked fine. You may want to try to uninstall and re-install 1.5.5.
Third time installation with same result, really strange!
One version Auto-Zero wont work, another Visualizer didnāt work, 1.5.4 all seemed to work and then something new in 1.5.5. Love the software all the same, another challenge to vanquish I guess.
@mwbeard1957 Could you send a screenshot of your surfacing settings so I can try to troubleshoot this problem?
Iāve tried multiple times on a Dell G7 Laptop with latest Nvidia drivers with no success. Will try on an AMD based machine later and test the outcome. Had an instance in the past where a video driver rollback was required to correct a bug.
Settings were
X 16 Y7. Wouldnāt accept and change in size
0.04 - 0.08
.75 Bit
.33% Stepover
16000 rpm
Will let you know how it comes out.
Thanks for your assistance.
100ipm
Actually, an update on this, I can confirm this is a bug with surfacing on 1.5.5. It looks like thereās an issue with the latest input box values not being used when generating the surfacing g-code.
Itās in our backlog now and will be addressed in the next patch release.
@walid_kayhan I was able to change the values. Are you saying that the gcode would not have reflected the values that I put in, Walid? I didnāt go so are as to look at the gcode or run it. The OP seems to be saying that he could not even change the values - a different issue.
Yes, exactly, the input box values are changeable, itās just not reflected on the g-code output (it is referencing the old values for some reason).
I believe heās talking about the output not being correct, but maybe youāre right; he might be talking about not being able to update the input values at all. @mwbeard1957 Could you clarify this for us?
1 Like
Correct, values were edited but resulting gcode was not updated to new parameters. Iāll just wait for the official release and try again, sure it will be corrected by then,
Thanks for all your support in this matter!
1 Like
No worries, and thanks for the clarification. Iāll post here once we have the next release patching this bug 
Thank you sir!
Love everything you guys produce, truly top notch!!
1 Like
@mwbeard1957 @walid_kayhan I changed the values and reported on being able to do that. I didnāt think to look at the generated gcode.
I apologize for doing nothing but adding the any confusion.
I bet this kills my chances at that testing job. 
Not my decision but Iād say based on the large volumes of help and guidance Iāve seen from you in the past you should by a no brainer in that department.
1 Like
FWIW, I just went to surface a new spoil board and set the depth per pass and total to .2mm (my sub base is really flat). the Gcode that was generated was 1mm dpp and 2 total. The last settings I used. This is my first time surfacing on 1.5.5. I use the surfacing tool a lot and this is going to be a problem. After a couple of tries getting out of the surfacing tool and back in then changing the values again I can get it to stick at 0.2 but canāt switch it back to 1mm to fix where I stopped the job when I realized what was happening. Iām going be a little tin foil hatty here but the use of AI for code writing does not negate the necessity of regression testing. Iāve noticed a lot of other established software/web sites that are getting put into production with silly bugs and broken features that have existed for a long time. Guess Iām manually modifying the surfacing gcode now. Looks like the issue was closed on the github about 5 minutes ago. Weāll see on the next release.
@Kerryh2012 Tks for that. I donāt use it so I was only trying to help the OP with his issue - which I got completely wrong as it turns out.
Iām sure that Sienci will get it fixed in the next gSender release.
1 Like
Not to be cynical but it sure seems like there are some gaps in testing before release. I get itās not the SCM/Testing environment Iām used to from my last Dev ops job but breaking pre=existing features looks bad.
New version of gSender, 1.5.6, has fixed this surfacing input bug:
Thank you sir, I appreciate the heads up!