jaf

It's the simplest cube one can make. Six sides -- six poly's. Eight edges. I deselect smoothing and chose "6" from the carcas resolution.

Hi Scott. I wondering what you found out that fixed the problem. I can't even get a plain old six sided cube to import correctly from Lightwave (or Silo). I uncheck the smoothing and select 6 from the drop-down resolution list and select auto-map. But I keep getting a weird looking mesh. I can load that cube in Silo, Vue, Terragen2 or UVMapper Pro, but not 3D-Coat (gl or dx). I assume it's something I'm doing wrong.

No problem -- take your time. I can't imagine how busy you must be. I just wasn't sure if my request had gotten to you. It's too bad there's not an automated way of applying for a code via the web site -- maybe some type of secure form.

How do I get a new serial number for the new beta licensing system? I sent an email request a few days ago but haven't received a response.

[edit - 7/17/08]

The model takes a very long time to load in the 2.10 beta's (rescales many times) but when it finally does load, it has what I believe are display artifacts. I don't believe the artifacts are part of the mesh -- I'll need to check that. I loaded the model in UVMapper Pro and I got the message stating that there were UV coordinate problems -- do I want to correct? I selected yes and saved off the model with a new name. The new model then loaded quickly in the 2.10 betas, so I guess that was the problem with the slow loading. However, there were still black lines that weren't (I have to confirm this) part of the mesh. I think the artifacts are a 3DC 2.10 beta problem, though it could also be an ATI driver problem. The mesh looks fine in the 3DC 2.092 release. Oh, and a side note: UVMapper Pro seems to be a good program to re-write OBJ files. I've had a lot of luck fixing OBJ's that have problems loading in other 3D programs. [edit] I forgot an important piece of information: when I imported the model and saw the problems, I had "smoothing" off. If I turn it on, the mesh problems are not obvious in a quick test. Also, they are indeed mesh problems, not 3DC display problems, since the problems stay with the mesh when exported to another rendering application.

No problem Phil. I remember that post now. I downloaded the file you provided and will try it tomorrow when I get back to my workstation. I would be interested to see if I get the same results since we have different brand video cards.

I didn't see a thread that addressed simply Make Human - 3DC -- I assume it's spread throughout the messages here (or I missed it in my search of "Make Human." Anyway, I haven't used Make Human much, but I noticed I could load the basic saved obj mesh directly into 3d-coat 2.092 and then save it as the 3d-coat file (.3b). Then it would load OK into the newest beta (2.10 A2B) both gl and dx. When I tried the Make Human mesh directly to the dx version, it also seemed to work, but the gl version was unrecognizable. I guess what I'm asking is, is there a list or description of problems with MH import to 3DC so I'll know what to look for as I use the software more?

Is was just reading a thread over at the Newtek (Lightwave) forum. There's are some very nice comments concerning 3D-Coat in that thread. Anyone thinking of purchasing 3D-Coat should read those comments. Other packages, like Zbrush, are mentioned. There are some very knowledgeable people making these comments (not me, though I did throw my favorite 3D navigator comment in there.) http://www.newtek.com/forums/showthread.php?t=82236

That's weird. It's what I did to come out of demo mode with the beta. If I remove serial.txt, I get a registration form with a hardware code and a request for a serial number. I assume it's getting my hardware code from the registry or a documents and settings file from when I first purchased 3D-Coat (3D-Brush). [edit] I should add, when you purchased 3D-Brush/Coat, you should have gotten an email with a serial number. This is the number that should be in the serial.txt file. Maybe you made a hardware change that changed the hardware code? Guess Andrew will have to explain what needs to be done.

Just a bit of a warning for ATI user's. I found my problem with the color palette not displaying the colors was the latest ATI driver package 8.6. Backing off to 8.5 fixed the problem. I don't know if this effects 32 bit windows (I'm using x64) too and other ATI graphics card models (I'm using a 1900 XTX).

If you have a registered version (non-beta) look in the 3D-Coat-2 folder (this is where the executable is) and see if there's a serial.txt file. Copy this file to your beta folder (where the beta 2.10 1F executable is). This should take you out of demo mode (demo will come up for a moment or two during loading, but should go away.)

The attached image show the problem I have with the palette in the GL version (1D). The colors a there, because I can click in the palette and I see a color appear in the color box. It works fine in the DX version and the 2.09 release version. [edit - June 28, 2008] OK, I figured this one out. It was my graphics card driver. I was using the latest ATI 8.6 package. By backing off to the 8.5 package, this fixed the problem (my palette colors are visible.)

Yes, that looks like it fixes the display problem. However, I have a new one now and it's very strange, though it's probably something I'm doing wrong. When I start the GL 2.10beta1D version, the Palette does not show any colors. I try to load a palette and it goes through the motions, but still no visible colors -- just a blank area and a little dot at the bottom where I can insert the current color into the menu. I can click in the blank area and a new color will appear down in the Pick Color panel, so the colors are really there -- they just don't display. Now when I try the DX version, the palette colors are visible. Since both the GL and DX versions share the same directory, I can't figure out what's going on. Any suggestions? Oh, and I uninstalled, restarted my computer, and reinstalled, starting with the oldest 2.10 beta and then tried each increment up to the latest, but no change. [edit - June 28, 2008] OK, I figured this one out. It was my graphics card driver. I was using the latest ATI 8.6 package. By backing off to the 8.5 package, this fixed the problem (my palette colors are visible.)

Andrew -- I was looking at the GL version of 2.10 1C and see similar "holes" or artifacts as the DX after drawing a few lines with the pen Again, they don't appear to be part of the mesh -- just displayed. If I do a fill, it looks like they get over-written (disappear.) I find it interesting that if I undo the fill, the original lines are still there but the artifacts do no re-appear until I draw some more.

I appears the "holes" or artifacts are only displayed in 3D-Coat, not exported as part of the model. I just did a quick couple of tests to Lightwave as an .obj and .lwo. Here is a screen capture of the cube (unsmoothed) with a few lines drawn on it and then a couple "undo's". The export of the mesh didn't have the black artifacts.

I see similar problems but have an ATI card with the latest drivers (8.6). I backed off a couple revisions and still saw the same problems.

No crash now with 1C GL. But both show the "holes" or "artifacts" mentioned above. The easiest way to see them (at least on my system) is to start with a default object, set the radius to 50 and use the pen to draw three or four lines. Then do three or four "undo's".

I checked the 2.092 version against the new DX version. The movement sensitivity was set to .62 in 2.092, which I believe was the default. I saw no reason to change it since the speed in all axis seemed fine. In the new DX version, I saw the sensitivity was set to 1.00. The panning and zooming seemed close to the older version, but rotates (spin) and tilts were very slow -- guessing 20% (or 80% slower.) Okay, I just found out I can run both versions at the same time. Setting the Rotation sensitivity, Spin modulator, Tilt modulator, and Roll modulator to 5.00 in the DX version seems to be about the same as the .62 settings in 2.092. Can't check the GL version yet because of the problem I mentioned above -- maybe the latest update will work (it takes me a while to download since I'm on dial-up.) [edit] as I think about it, I may have set the 2.092 sensitivity down a while back from 1.000 to 0.062 -- don't remember. Anyway, with both set to 1.000, the DX version seems about 80% slower in spin and tilt.

The DX version seems to run fine. The only thing I noticed is my 3dconnexion device was real slow doing rotations, but I can take care of that in the device setup. The GL version files with an "unable to compile" message. I'll attach a copy of the log.txt. I saw your message about a new update so I'll download that before more teting. Here's the log.txt: Log.txt

I tried changing the compatibility to win98 and that didn't help. Also, the ATI 8.6 drivers came out yesterday so I tried those and it didn't help either. Simply locks up when loading one of the default objects like "sphere" or any other model. One thing that would help in cases like this is if everyone that has or doesn't have the problem, they provide their basic system specs. The easiest way is to make a signature.

I'm seeing a different problem.... I installed the 2.10 beta1 in a new directory (the installer default). When I started the program, I was in demo mode (expected.) I clicked continue and was still in demo (expected.) I choose "Sphere" and clicked OK. The load process started but when it got to the 92% point, the title bar went blank (normally it would be "sphere - 3D-COAT 2.092" (this is how the previous release worked.) 3D-Coat locks up with the hour glass displayed and the load progress bar at 92%. I watched the 3d-coat process with the task manager and see the memory usage slowly rising -- it's 176,276K and still going. The former release uses 150,752K. I copied my serial.txt file from the previous release to 2.10 beta to see if getting out of demo mode would change anything, but it didn't.

That would be great for dual monitor use. I suspect it would also help increase the render speed of the main window, though that's not a problem now. But as features are added, it may.

an ATI 1900 XTX

The download speed for dialup was 6 to 6.5, which isn't too bad (for dialup).