New test release, please test

oort · 10-07-2016, 10:46 PM

povmaniac,
Just trying to avoid confusion for users who are not aware of the difference between how we see things on the computer vs the way things are in a camera. I have used cameras and computers for years but never knew that 35mm was the height of the film... Smile

Never needed to know that to take pictures... Smile

oort

nemyax · 10-12-2016, 12:05 PM

(10-07-2016, 12:12 PM)dgud Wrote: Ok you should be getting a 'Move win X:Y' line for every pixel you change when moving the window,
(so it seems like something is different on your computer),
that is the event wings are using to display the dock information and to dock the window.

I have no ideas what might be wrong or how to fix that sorry.

I tried the build from the original post on a different computer with 64-bit Windows 10 and nVidia graphics. Docking and screen updates worked fine there.

(10-07-2016, 12:12 PM)dgud Wrote: Does things things work after you have moved a window?
If you use the camera in geom window, like rotating camera does the geom window update/work as it should?

The geom window works fine. The artifacts from moved windows disappear after the viewport gets the focus.

micheus · 10-12-2016, 01:49 PM

[b]nemyax[b], is there any chance Windows had updated your graphic drivers?
I already experienced a graphic card issue (fliker) once with an automatic update.
If so, I recommend you to look at http://support.amd.com/.
I'm also running this version in a PC with Win7 and Intel graphics without any problem.

nemyax · 10-12-2016, 02:53 PM

micheus
I updated the driver and tried again, but nothing changed.

dgud · 10-12-2016, 07:57 PM

Micheus I don't think it have anything to do with gfx-drivers, it's looks like a windows bug? or another tool that steals the events. Also I tried on my sons Win-10 with AMD and it works fine.

Nemyax have you tried when temporary stopping Virtua-Win.

Also sometimes docking don't work on the Mac either for me and a reboot helps there,
which is kind or ironic :-)

micheus · 10-12-2016, 09:36 PM

(10-12-2016, 07:57 PM)dgud Wrote: Micheus I don't think it have anything to do with gfx-drivers, it's looks like a windows bug? or another tool that steals the events.

Maybe start Windows in safe mode when it loads the minimum necessary to run...(?)

OXO · 10-19-2016, 08:35 AM

When will there be a new version to try?

dgud · 10-19-2016, 09:55 AM

(10-19-2016, 08:35 AM)OXO Wrote: When will there be a new version to try?

When it's done :-)

But it will probably not take half a year again.

OXO · 10-21-2016, 07:44 AM

Is this the correct place for a little feature request?

The material properties dialog, it shows the numeric values for the Shininess and opacity.

Could you add numeric values for the diffuse, ambient, specular and emission?

micheus · 10-21-2016, 10:19 AM

OXO, you can use "Design and Development" session for that.

Fonte, thanks for test and report your findings - we appreciate. Smile

This thread was intended to be used for the test release before 2.1 be available. So, to keep things organized and do not lose the track about the bugs found, please - all users - do the reports in the 2.1 bug's export (in a separated thread always the subject changes): http://www.wings3d.com/forum/forumdisplay.php?fid=18

Thanks.