The old V2 was still using the mshtml and you'll want to consider the IE version you have and also the windows updates.

Moving to V3 will eliminate that.

Hi milkywaif,

> but maybe this was fixed unintentionally with this fix??? -> " Fixed a bug on OSX where window
> resizing behaved strangely on Retina displays."

Nope, couldn't have been that particular change - that one was a change in OSX-only code...

- Michael

Hi Colin,

> I can confirm those same flickering issues & had them for some time.

Did they also go away for you with this latest Nov-19 beta or is it still present?

- Michael

Hi Michael,

The flicker is still there with the latest Nov-19 beta.

Note that the flicker appears only when opening a previously saved model.
It appears to only happen if I've saved & closed the session with a single View on closing, not when "Split".
Just to confirm, if Split is selected prior to closing & saved, reopening the same model will NOT have the flicker.

HTH, Colin

Michael,

I was wrong, this issue is not fixed in nov19 beta at all. Fortunately I've managed to isolate the problem. I can totally confirm something in SidePane.htm is causing the flickering. Couple of days ago I've done some modifications to SidePane.htm and that's why my flickering issue was resolved! New beta was out that time, so I suspected you fixed it. I still can't figure out which particular line causes the flickering though.

Hi milkwaif, possibly something in your edited SidePane.htm causes the width of the side pane to change a little which in turn triggers a resize of the viewport area. That then triggers viewports getting arranged and probably solves the problem.

One question about the flickering - when it does happen if you then switch to split view to get rid of it, does it ever happen again within that same session like if you open the same file up again using File > Open this time instead of double-clicking it in Explorer?

- Michael

> One question about the flickering - when it does happen if you then switch to split view to get rid of it, does it ever happen again within that same session like if you open the same file up again using File > Open this time instead of double-clicking it in Explorer?

It never happens again in same session after you get rid of it by clicking split view.

It only happens when these two conditions are met together;

1) double click open a file "which was saved not in split viewport"
2) MoI window is not maximized.

This is probably why only few people experienced it.

More specifically;

It does not happen if "MoI window is maximized or fullscreen" and "you double click to open the file"
It does not happen if "MoI window is maximized or fullscreen" and "you open the file through file/open"
It does not happen if "MoI window is NOT maximized or fullscreen" and "you open the file through file/open"
It happens if "MoI window is NOT maximized or fullscreen" and "you double click to open the file"

Thanks for the additional info milkywaif! I've finally been able to reproduce the flicker over here and I'll have it fixed for the next v3 beta.

It was tricky to reproduce because under certain timing conditions with UI loading events it would also not happen (even when not maximized or full screen). In order for it to happen a certain piece of the UI layout code had to finish while the main window was still hidden.

It's an easy one line fix, thanks for reporting it.

- Michael

> I've finally been able to reproduce the flicker over here and I'll have it fixed for the next v3 beta.

Good news, thank you :)

Really great beta with a lot of useful stuff... Thanks Michael!

Hi, Michael.

I'm having a problem doing a Circular fillet or any of the G1/2/3 blends on the blue edges in the attached file which I would have thought should be OK because of the circular shape. Constant Distance and chamfer work as expected though.


Really enjoying this beta, thanks.


Martin.

Hi Martin, what radius value are you trying to use for the fillet?

- Michael

I've tried a few values, but I wanted just about the same as the other edges that are already done - I think 0.5mm.

**EDIT** Having reloaded the attached file back in to MoI I'm finding that the small blue edge will now fillet at 0.2mm, but not 0.3mm and the larger blue edge still won't fillet at any circular setting.

Martin.

Yeah, you can do some values but some others don't work well. It seems to be related to the vertical wall attached to the outside of those edges. If you delete those 2 walls and then run a loft/straight/exact on them (no caps) and then join back to a solid, then the fillet will succeed at the values you want.

Hi Martin,

> I've tried a few values, but I wanted 0.2mm, just about the same as the other edges that are already done.

The previous v3 beta seems to have the same problem, so it does not seem to be a regression just from any changes in this most recently released beta.


There may be some kind of accuracy problem with some of the trimming boundaries in there, it may take me a while to be able to investigate it in detail.

In the meantime, in addition to Burr's workaround above, if you scale the object up by 10 times in size it seems that then a fillet of radius 2mm works ok, then scale it back down by 1/10 and you should have a completed 0.2mm fillet on it.

- Michael

Hi Martin, I've tracked down that fillet problem and have it fixed up for the next v3 beta.

It was related to a change back quite a few versions ago in v3 that used a different method to create a closed fillet surface to make them smoother at their closing seam. In this particular case the new fillet surface maker was not refining it until quite enough accuracy that was needed for some of the next fillet operations.

For this particular case right now if you scale it up by 10 times in size you will then be able to get the particular fillets that you need.

- Michael

Hi, Burr and Michael.

Both ways work well and I've got the fillets I wanted, so thanks to you both for your help.

Michael.

I'm pleased you found the problem and managed to fix it.

One further thing I have just noticed though.

If you select the outer boundary curve of the solid shape, the dimension is shown as 221 x 90mm which is correct. If you now extrude that shape down to say -15mm in thickness you should see that the sizes of the solid are now 220.996 x 89.993 x 15. Interestingly, when I check the size of the original solid it comes out at 221 x 89.997 x 15. Is that normal, or could it be causing a problem further down the line?

Thanks for all the help.

Martin.

Hi Martin,

> Interestingly, when I check the size of the original solid it comes out at 221 x 89.997 x 15. Is that
> normal, or could it be causing a problem further down the line?

It's normal - the top level size display is based on the bounding box of the display mesh, because it has to be calculated very quickly since it updates every time you change the selection.

If you click on that line and make the edit dropdown pop out, it will do a more accurate calculation at that time, and also the fields in the drop down show values to a higher number of decimal points than the top level display as well.

- Michael

I also noticed that if you align-horizontal the points of the original profile, the display size changes, then the bounds of the extruded solid read the same as the profile.

It makes me wonder if the profile comes from MoI natively. I also wonder about if the recess on the top of the solid comes from the "inset" command?

Cheers for the comments and explanations chaps.

Burr - the curves were all drawn in MoI and you are correct in thinking that I used the Inset tool for the recess :)


Martin.