On Mon, Nov 30, 2015 at 09:03:37PM +0000, Andrés Muñiz Piniella wrote: > Could it be a graphics card issue? Are the 20% the same brand of > computer? The windows computers I used it with that work are Dell.
There is certainly some bad interaction with the graphics drivers... > We still have computers with low resources so if the preview mode is > deactivated, could it be opt-in rather than opt out? I tried to disable the downsampling on my 4 years old notebook running the default Linux X11 drivers for ‘no bloody idea what graphics card I have’ (until I looked it up). No noticeable difference with ~1000px images. With ~2000px images changing modes/palettes/materials was slow, but scaling, rotation, etc. was still fine. So I really do not think you need some high-end graphics workstation for these things nowadays. From 2004's perspective, everything is a high-end graphics workstation now. But maybe I am utterly mistaken. There is only one way to find out. I changed the downsampling not to actually downsample anything (in r17796). So starting from tomorrow's snapshot the 3D view will be effectively a lot slower than if we killed the downsampling outright because it will be doing everything twice – once for the ‘preview’, which is now of the same size as the final rendering, and once for the final rendering as usual. Please test. Ccing the -devel list to increase the potential number of people who may give useful remarks. Regards, Yeti ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ Gwyddion-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gwyddion-users
