Bugzzz

[artman]

The scales of exported .obj are different if I'm using export scene than when I'm using export object in rmb menu.

Export object gives me bigger objects.

Which for example ,gives a much bigger object than the retopologized version exported as raw mesh in retopo menu.

In other words,they don't match.

Can anyone reproduce this?

[Andrew Shpagin]

The scales of exported .obj are different if I'm using export scene than when I'm using export object in rmb menu.

Export object gives me bigger objects.

Which for example ,gives a much bigger object than the retopologized version exported as raw mesh in retopo menu.

In other words,they don't match.

Can anyone reproduce this?

Yes, that is easy to fix.

[3dioot]

Ok, opening problem is fixed. With next update you will be able to open all old problematic files.

Almost all bugs squashed.

@Juan:

I have fixed it. But you can easily avoid it making invisible all voxel layers.

Awesome! Thanks alot.

3dioot

[ggaliens]

New TurnTable render bug ... 720 frames, DirectX Version of 3DCoat, Shiny Skull Shader ...

Every other frame has a different lighting intensity. I suspect an odd-even thing where if I tossed 1/2 the frames ...

I could make a 360 frame video with one brightness level ... and another 360 frame video with a darker level.

Odd Bug.

Anyone seen this ??? Replicated ????

Another turn table bug : Window title has wrong ending frame. I say 720 frames ... it says 1/721

so it is off by 1 where upper limit is concerned. Minor bug.

[akira]

New TurnTable render bug ... 720 frames, DirectX Version of 3DCoat, Shiny Skull Shader ...

Every other frame has a different lighting intensity. I suspect an odd-even thing where if I tossed 1/2 the frames ...

I could make a 360 frame video with one brightness level ... and another 360 frame video with a darker level.

Odd Bug.

Anyone seen this ??? Replicated ????

Well it's not a bug, it's more like a feature request that ask for light direction rotates with camera.

I've made a picture to show this issue.

[ggaliens]

It's a bug ... this is evidenced by the

every other frame behavior.

How could intensity toggling back and forth every other frame

be explained by camera/light coupling or decoupling ???

I doubt it can ... but please give it more consideration if you

really thing what I describe is a feature.

I should have posted a video to show what I mean.

It just seems like there is some kind of roundoff error

that is halving the light intensity every other frame.

I tried to replicate it last night ... with not so much luck.

Next time ... I'll post a video if I find the bug again.

Camera / light coupling and decoupling is a completely different thing ...

unless it was partially implemented and is bug resulting in odd or even frames

having a different intensity.

I like the feature request you mention though.

[philnolan3d]

There seems to b something wrong with the shaders, or maybe just one of them. I loaded my model up and it was entirely transparent, except that you could see it's silhouette in the Symmetry plane. After changing each object to another shader it was fine. 3DC froze up and I had to restart it. This time the whole model was solid black and after moving it around it changed to semi-transparent red, just like the symmetry plane. Here you can see where I changed the body to oren-nayer, but left the others with the semi-transparent red. Unfortunately there's no way to tell which shader I was using, so I can't tell if it was one in particular that's causing this.

Even more weird, in the above example the character's finger nails were on a separate layer that was hidden. if I unhide, then the horns layer becomes solid, but the color changes as I rotate the model around. Here's a video:

http://screencast.com/t/Eci26MVXQE

[akira]

I encountered similar problems as Phil mentioned.

Alpha 60

1. start up 3DC and switch to vox mode.

2. change shaders that have custom variables via tool menu.

3. object become pure black or red.

4. chage shaders via vox tree RMB menu.

5. shader becomes normal

It seems this issue happens to tool menu only.

akira.

[philnolan3d]

Here's another one with Undo. I got this mess when trying to undo Transpose.

[ScoobyDoofus]

I've got a bug where when I launch 3D Coat and hit the voxel mode button it claims my layer is "invisible" and I cannot sculpt on it (or see anything). All voxel models are invisible. Is this a setting or config or driver error? It worked fine on my previous OS XP pro SP3 install, but after upgrading to my new machine, it doesnt work. If I boot into Windows 7 64 bit on the same machine.....it works fine.

[Andrew Shpagin]

There seems to b something wrong with the shaders, or maybe just one of them. I loaded my model up and it was entirely transparent, except that you could see it's silhouette in the Symmetry plane. After changing each object to another shader it was fine. 3DC froze up and I had to restart it. This time the whole model was solid black and after moving it around it changed to semi-transparent red, just like the symmetry plane. Here you can see where I changed the body to oren-nayer, but left the others with the semi-transparent red. Unfortunately there's no way to tell which shader I was using, so I can't tell if it was one in particular that's causing this.

Try to reset shaders for strange objects.

[Andrew Shpagin]

I've got a bug where when I launch 3D Coat and hit the voxel mode button it claims my layer is "invisible" and I cannot sculpt on it (or see anything). All voxel models are invisible. Is this a setting or config or driver error? It worked fine on my previous OS XP pro SP3 install, but after upgrading to my new machine, it doesnt work. If I boot into Windows 7 64 bit on the same machine.....it works fine.

Have you installed latest CUDA drivers and toolkit (2.1 required)?

http://www.nvidia.com/object/cuda_get.html

Are you using 64 or 32 bit Windows?

[philnolan3d]

Try to reset shaders for strange objects.

Not sure what you mean by "reset". Like I said I changed it to another one and it was fine after that.

[akira]

Alpha 61

minor bug:

The alpha image of brush will flip left to right when you press RMB.

[GED]

imported a model through merge tool then right click objects -> add object

object looks fine when positioning it but when I hit enter it turns all messy.

[Andrew Shpagin]

imported a model through merge tool then right click objects -> add object

object looks fine when positioning it but when I hit enter it turns all messy.

This mesh is open, so it produces mess. 3DC tries to close meshes if they are not too big.

[lc8b105]

imported a model through merge tool then right click objects -> add object

object looks fine when positioning it but when I hit enter it turns all messy.

That is probably because the model you imported is not closed.

[GED]

This mesh is open, so it produces mess. 3DC tries to close meshes if they are not too big.

oh ok thanks. it doesnt appear to have closed the mesh properly then. I thought that if I import an open mesh the mesh would get a thickness like cloth has? rather than 3dc trying to close the mesh.

[GED]

got another bug, I was making a model and applying shaders then I hit cast shadows and all the models on all the layers in the voxtree turned transparent and shifted hue as I rotated the model around in the viewport. kinda 80s disco like haha

got the shaders back by manually selecting them all again

but then tried to render and the shaders messed up again

[bigsofty]

The Sphere primitive does not seem to mirror with symmetry 'on'.

[halfknight]

I have got some issues with the surface tools:

1. they are stuttering and a bit unresponsive (triangle count 3200000)

2. If you release the mouse button you have to wait a bit

3. If you don't wait enough you getting artefacts like these (red arrow)

Hopefully you can fix these points because I really like those tools and there are working in some situations better than the voxel tools

Oh, my specs are:

Intel quad Q6600 @2.8

Nvidia 8800 GTS 640MB

4 GB RAM

Win XP with 3GB Switch

[haikalle]

I'm not quite sure is this bug or something else. Maybe I don't just get it how it works but anymway you can try:

1. Sculpt something.

2. Add camera shortcut.

3. Save your sculpt.

4. Load your sculpt

5. Press Render.

And result is that render box dosen't show at all. It will render your sculpt but you don't see it.

[bigsofty]

Well Im a new user and Im afraid Im having quite a few problems...

1) Screen corruption, seems to large sections 'through' the model, i.e. holes.

2) Undo borks, sometimes I hit undo an it does nothing, further attempts to use undo then cuase previous stages to be undone, leaving the original stage untouched.

3) Sometimes all tools have no effect on the model, I have to reload.

[philnolan3d]

Does everyone else have unfinished menu buttons on 32 bit? On 64 bit they are fine, then I installed the 32 bit one on my laptop and I see this. It's the same on both cuda version and the "simple" version.

BTW I mentioned before how I'm having a lot of lagging and general sluggish behavior on my laptop with 61, the "simple" version is also causing that.

Edit: I installed alpha 60, then alpha 59, and have the same lagging. What's more odd though is that I have the same VS tools as the screenshot from 61. Aren't those new tools that weren't in 60 or 59?

Maybe I need to completely uninstall before installing.

Edit 2: Uninstall fixed the lag, still have the weird tool buttons though.

[lc8b105]

Does everyone else have unfinished menu buttons on 32 bit? On 64 bit they are fine, then I installed the 32 bit one on my laptop and I see this. It's the same on both cuda version and the "simple" version.

BTW I mentioned before how I'm having a lot of lagging and general sluggish behavior on my laptop with 61, the "simple" version is also causing that.

Edit: I installed alpha 60, then alpha 59, and have the same lagging. What's more odd though is that I have the same VS tools as the screenshot from 61. Aren't those new tools that weren't in 60 or 59?

Maybe I need to completely uninstall before installing.

Simply click "Language"-"English" one time.

Then the language file should be refreshed. Try it.

[philnolan3d]

Simply click "Language"-"English" one time.

Then the language file should be refreshed. Try it.

Oh great, that was a simple fix. Problem solved, thanks.

[ggaliens]

Was not able to right click on item in VoxTree under OS X.

I'm not a normal OS X user, but I tried like crazy to get

the voxel object right cick menu so I could change the

VOX Object specific shader, or do any other right click operation.

No luck on Mac OS X.

Anyone else have a similar problem. I think it

was version .64 or something new.

[artman]

Hi Andrew,

I'm having problems with sym copy

(on all alphas I think)

sometimes sym copy will only work for one side of the model

regardless of which side was sculpted last.

In this file only left to right copy works,

right to left copy doesn't work.

It is not the first time it happens but usually I have no problems

using sym copy to get either left or right side .

I would like to know if there is something

while I sculpted that I could have done wrong to generate this problem.

(I use "clone space density" and "move to" a lot in my workflow maybe it is related)

Thanx

[Andrew Shpagin]

Hi Andrew,

I'm having problems with sym copy

(on all alphas I think)

sometimes sym copy will only work for one side of the model

regardless of which side was sculpted last.

In this file only left to right copy works,

right to left copy doesn't work.

It is not the first time it happens but usually I have no problems

using sym copy to get either left or right side .

I would like to know if there is something

while I sculpted that I could have done wrong to generate this problem.

(I use "clone space density" and "move to" a lot in my workflow maybe it is related)

Thanx

It will be fixed in next update.

[run]

Hi Andrew,

XP sp2

ALPHA 69 CUDA both DX & GL, haven't had the chance to check this on Simple.

1. Voxel scuplt something

2. In the Vox tree right click and select "Quadrangulate for per pixel painting"

3. When the panel pops up click " Cancel"

4. 3DCoat locks up, (In task manager one core is completely maxed out)

Happens every time.

Also

5. Instead of selecting cancel when the first panel pops up select "OK"

6. When the second panel pops up select "cancel"

7. In a few moments 3DCoat will throw a "Unstable save your work" error and shut down

I sent the auto bug report on this last part

Jeff