Poor drawing graphics in version 26

[BoNgO]

The display of drawings has become much worse compared to version 25.

Attached are comparative screenshots of versions 25 and 26 in different versions of line widths.

The line thicknesses in version 26 are coarser, blurrier and thicker. In version 25, the graphics are crisper and neater.

[Barry Kelly]

Here is the link to the post with the registry fix.

https://community.graphisoft.com/t5/Document-Visualize-forum/Fonts-displaying-incorrectly-after-movi...

Don't worry about the link tot the Atlassian site as you may not have access to that.

I have copied what it says.

Barry.

[Botonis]

I forgot to paste the link to the relevant post but Barry did it........

[BoNgO]

Working at 100% font scale at 27 in 4k is unrealistic. I attach an example of a screenshot from the screen. The point is that with the same scaling parameters in version 25 all is well, in version 26 immediately caught my eye the difference for the worse (in my opinion). The very idea that you can get used to the deterioration of graphics in the new version compared to the old, at least even sounds strange. I'll wait for the update.

[BoNgO]

The video was recorded with the "check" mode turned on. And these gaps subsequently give incorrect dimensions.

[Barry Kelly]

In the video you seem to be stretching an edge.

The tracker is simply showing you the distance you are moving.

It is rounding to the working units you currently have set.

It will never show you the exact distance.

Do not just watch the tracker to position the edge as that will be inaccurate.

You must type the exact distance that you want to move.

This should be accurate to what ever precision you type.

Barry.

[BoNgO]

The point is that there is a graphically visible and physically possible location of elements outside the measurement area. But at the same time this error multiplied by several such, gives a visible displacement of parallel elements relative to each other and after a series of equal segments at dimensions appears one segment where there is not an integer, but rounded up or down. It is impossible to build everything through numerical input coordinates! This error occurs when using complex profiles of column or beam elements when copying them using mirror placement (even using the "Shift" pressed).

[Barry Kelly]

---

@BoNgO wrote:

It is impossible to build everything through numerical input coordinates!

---

Maybe we are talking about different things?

But NEVER just stretch and click to model an element.

The distance you see in the tracker is not accurate (it is rounded) to the actual distance you are moving the cursor.

You should always type in a distance unless you are snapping to something you know is already place in the correct position or you are going to trim that element at a later time.

Barry.

[Rex Maximilian]

#truth