Jump to content
3DCoat Forums

erklaerbar

Advanced Member
  • Posts

    304
  • Joined

  • Last visited

Posts posted by erklaerbar

  1. i have that problem, too. it started with v3.5.18 when the mip-mapping thing was introduced. on my side it's not the brush size, but the alpha size. if i use an alpha bigger than 1000x1000 it starts to get really laggy, 5-6 fps. the bigger the alpha, the larger the lag and low fps. it happens on both versions, gl & dx.

    i'm on w7 64bit, i950, gtx 460. the problem is easy to repoduce cause it happens all the time.

    sorry, of course youre right, i meant the alpha size. I mostly use 2048*2048

  2. does anyone else have huge performancfe issues with the recent builds? An empty voxel scene comes at 6 fps when I change camera view or even only slide over the menus with the mouse. The CPU performance goes to over 50 % on a quad core by only navigating an empty scene. Weird thing is that when i select "curves" i can navigate much faster again, as i used to. In fact only a selected "Voxel brush" makes this happen, if i select other tools it works again.

    Is that just my PC?

    EDIT: I found that it happens when i use the combination:

    * large alpha 16 bit on a voxel brush

    * this makes GUI very very slow

  3. sure, its straight forward to reproduce. Pls excuse if it wasnt clear:

    • New Scene
    • make a cube from primitives
    • now switch to merge tool, select a random tool
    • press "on pen"
    • now hoover the mouse over all 3 sides of the cube.
    • voila: it will only work correctly on 2 sides of the cube

    this still is reproducable with 3.5.12 :( Just make sure you have Symmetry = OFF. Could you please have a look? Its quite a showstopper, as i can use voxels only with symeetry turned on.

    PS: But thanks for the update :)

×
×
  • Create New...