Right!?! I am impressed. I have a phone and two computers here and still don’t get it 
3 Likes
From a football game no less!!!
2 Likes
Looks like 3.9.0 is being withdrawn.
I wonder if that means 3.8.4-pre9 will become 3.8.4 or 3.8.5.
3 Likes
I’m really not sure why they don’t either:
- revert just the problem commit that wasn’t tested, and release as it was already tested and give the other developer a chance to look closer at his commit, or
- Make the simple fix suggested last night which at least gets it back in a running state for wider testing to see if there are further problems like Mitch is looking for, and just name it pre10 or whatever…
pre9 seems to be fine, so there’s at least something that works, but I feel like one of the above would help push forward a stable release without the stigma of the “pre” tag
I’m not sure how active this dmyk developer is. I don’t always see him on discord
1 Like
Looks like we are heading into door #1…
3 Likes
Discord says they are pulling 3.9!
((Some unrelated code was added to main after I started to work on the stepping engine stuff that resulted in the prereleases. It made its way into 3.9.0 without any community testing. ))
1 Like
yeah…this
1 Like
And there is the 3.9.1 release with that extra stuff reverted.
4 Likes
so have you tried it? how is it?? 
Not yet. I’ll try it out later tonight.
1 Like
My initial testing of 3.9.1 looks good. I homed each axes a few times, did home all, ran a job from SD which included probing, refreshed Flash file list while running and refreshed whole UI while running. As expected, when $HTTP/BlockDuringMotion is enabled, it loads that basic page, with it disabled, it loads the UI. If you reload the UI during a hold, it shows the basic page. I think Mike was looking to update that for a future release but this is completely fine for now.
3 Likes
Perfect I am actually flashing it right now. Super excited to be back to a stable release.
3 Likes
Only thing I am seeing is the probe panel in the UIv2 is not retracting. I don’t use that panel but I know some do, not sure it that has ever worked really.
Before we get more people testing this thing, I might as well update the configs now.
Any macros or preferences that should be changed? For UIv2?
1 Like
I don’t think that ever has retracted for me lol. But I have been on V3 for a good while now so maybe I just don’t remember V2 lol. The only time I use it is when I am leveling the beam. So not often at all lol.
2 Likes
It has never retracted for me. like JJ said I only use it for beam adjustments…
3 Likes
1 Like
My main gripe with v2 is the macro buttons. Even on your giant screen you can not read them at all. That makes them pretty pointless.
2 Likes
After using it for the first time in a LONG time last night. I am not a fan of the jog buttons. Even zoomed in my fingers don’t like to hit the correct spot every time.
V3 has some connection things I do not like so I will ship with v2 until they get sorted out a bit more. Once you are connected v3 is far superior in my opinion in many ways, but I do not want new users to hit a hurdle trying to connect. (YBR).
I have yet to find a “jog control” interface that NOBODY complains about lol
The V2 jog UI I would hit the wrong button all the time, so I primarily used the Tablet mode there.
The V3 one works better for me.
But I have normal sized fingers 