D.R. Greenlaw

Using the latest beta, btw. I'll compare this to an older install I have on another computer.

Thanks...that at least tells me how it should work. I managed to get a new point to insert on one segment of the spline but for some reason, I can't get it to do this on other segments of the spline. At least it's working...sort of. Also I have to hold down Shift and Control--then I will see a green highlight on the spline where it will let me insert a point, but this isn't happening consistently. Very strange because using this key combo apparently isn't how it's supposed to work. Will poke around this some more to see what I'm doing differently to make it work like you described. G.

Hi, I've been working with the Spline tool in the Paint Room today and I want to insert a few points within an existing spline. On-screen help says "Use RMB to resize points, and to insert new points with an interpolated radius," but when I click on a segment of the spline using the RMB, a point is not created there. I also tried different modifer key combos but no luck so far. Thanks in advance for any useful tips. G.

Thanks for working on the Hide/Unhide issues in the UV Room I was running into. I'm downloading the latest build now...will test it tonight. G.

Can't do that but the object is a multilayer .lwo modeled in LightWave, otherwise nothing unusual about it. I'm noticing other weird things when using the HIde command while in the UV room, especially after disabling/enabling layers under Materials--3D Coat seems to get very confused about what's supposed to be hidden and seen. As mentioned previously, this only happens after using Subdivision on import. Straight import with Subdivision set to None appears to work fine. That was on the computer with the GTX 470--will check this on the other computer with the ATI later tonight. I guess it's good that nobody else is seeing this weirdness--maybe I just need to update my graphics drivers. G.

Okay, I figured out the cause, at least in this case. When I import the object and use Set Subdivision, I get the crash in the UV room when using Hide. If I import the object with Subdivision set to None, Hide works fine in the UV Room. I guess this is a bug but at least I can finish working on the UV map now. Will try Hide in the UV room with different geometry later today to see if this crash is repeatable with other 'complex' objects. G.

A little more info: apparently, this only happens here with certain geometry. No crashes when I use Hide for selections on simple meshes in the UV room, but I get repeatable crashes on a more complicated mesh I'm working with today. I'm not yet sure what it is about the mesh that causes the crash. I tried regressing to the stable version of 3DC but same results. Will post again if I figure out why this is happening with this mesh. G.

I installed the latest beta today and I'm finding that when I try to use the Hide tool while in the UV room, 3D Coat will crash. I've been able to repeat this consistently and on two different computers, one with nvidia and the other with an ATI card. Running Windows 7 Pro x64 on both systems. Anybody else? G.

Yes, never mind. Using the Pose tool, I set it to Object mode and it works as expected. I was just using the wrong tool.

Ah, I think I'm supposed to use the Pose tool for this? I can do what I need to with it anyway. G.

BTW, this was on my workstation but I just checked on my laptop and it's doing the same thing there. Wish I had an older version installed on one system so I can compare--might have to do that. G.

Shouldn't be...this is clean install on this computer (my home workstation.) Sorry, I need to check this again, something seems different but it might just be me. Here's the situation: I have a fish with a pectoral fin on either side of the body but the fins are detached from the body (the fins are also in a separate layer.) I thought that if I positioned the transform gizmo over one fin, enabled symmetry, then I could move both fins toward the body. Instead, when I move the gizmo toward the body, the Symmetry Plane moves with the gizmo and both fins move in the same direction, that is, only one fin moves toward the body. Just wondering if this is what I should expect and maybe I'm trying to accomplish this task incorrectly? Thanks for any info. G.

Or is that how it's supposed to work? Sorry...probably not getting enough sleep lately. G.

Is anybody having trouble with Symmetry? I can't seem to lock the plane when working with Voxels. For example, when I use the Transform tool, it moves the Symmetry plane along with the Voxels, causing weird stuff to happen. I checked the Symmetry option and Lock is enabled. If it's working fine for others, would anybody know why it might not be working correctly here? Thanks in advance for any help. I'm using the download from the beginning of this thread, which I'm assuming is the latest build. G.

Thanks! I can use some of the changes in this update right now. G.

Regarding the Cone-Cylinder issue--that must have been a random 'hiccup'. This feature is working correctly today so nevermind. G.

Just got word that this is fixed in the next release.

Andrew, thank you for acting so quickly! Today I think I found another one: in the Voxel room, when I tried to create a Cone Primitive, the tool created a Cylinder instead. I haven't had time to fully investigate this yet but I thought I should mention it. Will check if this error is repeatable tomorrow. (Oh...it's 4 am...I guess I mean later today.) G.

Figured out a temporary solution. See the thead above for info.

Here's a temporary solution for anybody else running into this problem: Open Cylindrical mode and enter a value for Pivot. Switch to Spherical mode--the edited value will appear there. You can now change the value for Spherical and it will persist. It's possible that Spherical may break again during the session but if you do the above, all should be good again. At least for a little while. G.

Confirmed! Spherical mode suddenly stopped accepting offset values for Pivot but when I entered the offsets in Cylindrical mode the settings persisted when I switched back to Spherical mode. Whew! I can actually finish my task now. Hope this gets fixed soon. Today was the first time I used this feature and it was extremely helpful. (When I got it to work I mean.) G.

I think I figured out the 'trigger' for making the feature work correctly. If I first open the Cylindrical mode Settings panel and enter an offset, the value will persist. Then if I switch back to Spherical mode, I can use the value entered from the Cylindrical mode settings or change it, and the new value will persist for Spherical mode after clicking OK. I'm not 100% certain this will work every time but right now I'm afraid to close and restart 3DC until I finish my current task. Will check on the accuracy of the above statement later today. G.

Hi, I'm running into this problem with 16 and 16C: http://3d-coat.com/forum/index.php?showtopic=15859&p=106265 In a nutshell: I can't offset the Pivot position in the Spherical mode panel in the Materials panel. If I enter a value, the preview will update but the values remain at 0,0,0. Changing any other setting or option resets the offset in the Preview. Closing the panel also resets the Preview and the actual Pivot setting will fall back to 0,0,0. Curiously, I got this feature to work briefly earlier today but I'm not sure what I did to trigger the correct operation. After that session, I haven't been able to get it to work correctly again. I'm seeing the same problem on my other computer. I'm running 3DC x64 CUDA.GL on Windows 7. Thanks in advance for any helpful advice. G.

I updated to 16C...problem exists there too. Will post this into to the beta thread. G.

Hi, Are the options in the Spherical Settings panel currently broken? I'm having a problem with changes made to the Pivot offset not sticking--the values keep reverting to 0. Changing any other parameters or options resets the Pivot position to 0 and simply closing the panel resets the position to 0. Here's more information about the problem: http://3d-coat.com/forum/index.php?showtopic=15859&p=106265 I tried this on two different computers and got the same results. I'm thinking of regressing to an earlier version of 3DC but I'm not sure which version to fall back to. I'm currently running with 3DC version 4.0.16, Windows 7. Thanks in advance for any helpful info. G.