1786 replies to this topic

[BurrMan]

I have had the same problem for a while in the 3.7.x.x series I just put it down to my machine specs,I get about 10 seconds of white screen on startup
and about 6 seconds wait after selecting a voxel primitive,most annoying.

The only other thing would be vid driver update.. A new driver was also recently released for my card, which got changed in this last week also.... I'm on ver. 295.73

FYI

[JimB]

The only other thing would be vid driver update.. A new driver was also recently released for my card, which got changed in this last week also.... I'm on ver. 295.73

FYI

I have been using 295.73 since its release Feb 21st

Btw from the lack of responses it would appear that it does'nt affect Macs.

[LetoAtrell]

I have had the same problem for a while in the 3.7.x.x series I just put it down to my machine specs,I get about 10 seconds of white screen on startup
and about 6 seconds wait after selecting a voxel primitive,most annoying.

Same here on MacOS X 10.7.3

[The Candy-floss Kid]

JimB, on 07 March 2012 - 06:20 AM, said:

I have had the same problem for a while in the 3.7.x.x series I just put it down to my machine specs,I get about 10 seconds of white screen on startup
and about 6 seconds wait after selecting a voxel primitive,most annoying.

I have been using 295.73 since its release Feb 21st

Btw from the lack of responses it would appear that it does'nt affect Macs.

Some start up flickering has always been part of the Mac release but for no more than about one second I am thankful to report.
But tell me because I am unclear? After the 6 seconds lag on pulling out the voxel primitive does all run smoothly henceforth?

For me the glitchy start up elicits concern , sometimes alarm yet thankfully to date, not harm. It is to user expectation the equivalent of the curtain that pulls back jerkily before the movie starts and for conveying certainty it would be cosmetic but nonetheless pleasing to see it improved.

In a similar vein I would prefer to see a progress bar on operations not a spinning beach ball. Beaches for mac users have become places of trauma where spinning beach balls are psychologically associated with peril , doom and disaster. When 3DCoat goes into to operation and the spinning beach ball starts I grip my seat until the lights come back on and it is safe for the angels to leave my side.

[JimB]

As far as I can tell yes.

But tell me because I am unclear? After the 6 seconds lag on pulling out the voxel primitive does all run smoothly henceforth?

[JimB]

I just sent this crash report :-

I started 3.7.06C(CUDA)(DX64)
I then started Windows task manager to check on processor usage,that is when 3.7.06C(CUDA)(DX64) crashed.

Windows also produced this message box

Attached Thumbnails

• 

[JimB]

Make sure you launch it as administrator (compatibility option in properties of the executable) and if that doesn't work I suggest you to reinstall your video drivers (or update them if you're not up to speed).

Thanks BeatKitano,
I dealt with the UAC around ten seconds after installing Windows 7 for the first time it is no longer a problem
Compatibility tried that makes no difference.
I have been running the latest nVidia drivers (295.73) since thier release 21/02/2012

The only thing I can think of is that the delay is caused by a serial number check?

I seem to remember that there was a file we could delete to help solve problems ..trouble is I cant remember
what it was ... anyone remember?

Thanks

[BurrMan]

I just sent this crash report :-

I started 3.7.06C(CUDA)(DX64)
I then started Windows task manager to check on processor usage,that is when 3.7.06C(CUDA)(DX64) crashed.

Windows also produced this message box

Hey Jim,
Running the same driver as you.... Somethimg for me, but has been around for a bit, is if I put the cursor down to the taskbar (I have autohide on my taskbar set on), and then move the cursor from the taskbar to the 3dc area, my 3dc interface does a hop-skip-andajump... I havnt figured out if it's the "popup/rollover" code from 3dc, or some other tie-in... Anyway, maybe you were launchiing your taskmanager with the right clcik on the taskbar??

[moska]

There is no any reason why 3D-Coat should not support Lion :-D Please try this test executable.
http://www.3d-coat.c...D-Coat-10.6.zip
It has been compiled against the latest SDK. But frankly speaking I think that the reason is within another video driver,
which, most probably, was also updated during system update.
Maybe it doesn't support big textures like 8K and above? Have you tried 4K, 2K?
What exactly do you see during import for PPP: crash, flickerings. hang over?

hi Sergy
dont understand this build number,its 10.6(snow)shouldnt be 10.7?whats diferent from last build?
-during PPP import the program stop work ,dont present window for import settings and i quit
ill try this build in lion later
thanks

[Gravin]

In a similar vein I would prefer to see a progress bar on operations not a spinning beach ball. Beaches for mac users have become places of trauma where spinning beach balls are psychologically associated with peril , doom and disaster. When 3DCoat goes into to operation and the spinning beach ball starts I grip my seat until the lights come back on and it is safe for the angels to leave my side.

I have to agree with this, a progress bar would be nice for those operations in 3dcoat that cause the program to become unresponsive until completion. I'm using Windows so there isn't even a spinning beach ball, just a blind wait until the number crunching is done.

[bisenberger]

Thanks BeatKitano,
I dealt with the UAC around ten seconds after installing Windows 7 for the first time it is no longer a problem
Compatibility tried that makes no difference.
I have been running the latest nVidia drivers (295.73) since thier release 21/02/2012

The only thing I can think of is that the delay is caused by a serial number check?

I seem to remember that there was a file we could delete to help solve problems ..trouble is I cant remember
what it was ... anyone remember?

Thanks

Was it "Options.xml" in the "Documents/3D-CoatV3" folder?

[JimB]

Was it "Options.xml" in the "Documents/3D-CoatV3" folder?

I dont know , I deleted it but I did'nt notice any difference.
Thanks

[Andrew Shpagin]

Updated to 3.7.07 (win)

- Voxel LC tools may be duplicated by RMB click. You may customize new tool in own way and share new brush. In so way you may create for example variation of GeneralBrush and store/share it.
- much faster initial loading
- Sketch tool got improvement. Now it is possible to assign images as top and bottom stencils and set tapering angle (positive and negative). Examples - http://bit.ly/xv0491 http://bit.ly/yTHhh9 . It works as advanced loft tool that may join contours of different topology.
- fixed several UI glitches.
- fixed problem http://3d-coat.com/m...hp?id=486#c1396

[JimB]

Ah.. much much faster startup
Thank you

[Andrew Shpagin]

Also removeclay does indeed removeclay:

I also got a crash (but no report form !) after trying to delete a liveclay brush I just duplicated.

I found and fixed crash. But I can't reproduce smoothing problem.
Removelay is still not ready, I forgot to exclude it. It is intended for global removal of details, will work like hypersmoorh to get clean smoothed surface even if there was many details and even holes.

[SERGYI]

whats diferent from last build?
during PPP import the program stop work

The difference is that regular builds are compiled against older SDK 10.5, because there were some requests to include Mac OS X 10.5 Leopard support. When you click File/Import/Model for per pixel painting do you see file selection dialog? Does 3D-Coat stop responding after selecting model file and closing file dialog?

[Zeddicus]

I docked my UV preview window on the left and noticed while clicking on UV islands that my clicks were going through the window and onto the mesh behind it. This results in marking seams you don't want marked, often without realizing it's happened. Doesn't seem to be an issue with Add clusters and Edge loops modes, just Mark seams.

Also is there a way to keep 3D Coat from destroying my smoothing groups? I bought a mesh over in OBJ format so I could do the UV's and discovered after finishing and exporting back to the originating app that my smoothing groups were gone. I asked about this in the new user area but never got an answer. They were time consuming to set up in the first place, and took just as long to redo them. On top of that I may need to send my mesh back to 3D Coat for more UV work. If there is something I'm missing or some trick to it, please let me know.

[moska]

@Sergy
using last build(6b)in lion:it allows to chose mesh in window and then stops (now it flickers)so no new window for import settings.
note:it allows PPP import through the launch window.

your build 10.6 dont work at all in snow or lion
-it shows a crazy frozen window with items from 3dcoat interface and or desktop or whatever.does it work for you?how can it be?
cheers

[BurrMan]

What should happen is that a second list should show next to the first, when the first list reaches the boundary of the Viewport.

Or a means to have a persistent dialogue. Like a modifier key click. With possibly a higher power of management tools and buttons avaiable. Like an "advanced" one.

[Andrew Shpagin]

I docked my UV preview window on the left and noticed while clicking on UV islands that my clicks were going through the window and onto the mesh behind it. This results in marking seams you don't want marked, often without realizing it's happened. Doesn't seem to be an issue with Add clusters and Edge loops modes, just Mark seams.

I agree. Very annoying problem. Same thing happens when you click the Retopo menu...the dropdown list is so long that when you choose an option that is over an object or UV island, it will select through the menu.

Can't reproduce any of that problems even if tried a lot. Maybe short video will help a lot.

Also is there a way to keep 3D Coat from destroying my smoothing groups? I bought a mesh over in OBJ format so I could do the UV's and discovered after finishing and exporting back to the originating app that my smoothing groups were gone. I asked about this in the new user area but never got an answer. They were time consuming to set up in the first place, and took just as long to redo them. On top of that I may need to send my mesh back to 3D Coat for more UV work. If there is something I'm missing or some trick to it, please let me know.

If you exporting from some 3D package you should export OBJ file with normal. 3DC uses normals to detect smoothing groups.