2.09 BETA3+smudge/collapse/expand tool!

[Andrew Shpagin]

I have fixed bugs in 2.09 BETA3 and add new tool - smudge/collapse/expand on paint level. I hope you will find it quickly in interface.

It is still slightly laggy. The link is below:

http://www.3d-coat.com/files/3d-Coat-209B3B-en.exe

[digman]

Andrew, now I get "no" status texture numbers at the bottom of 3D-Coat's interface. I tried several 3DC files and imported Objs with and without uv maps. The same results on models, no status texture numbers. All the other status information is appearing at the bottom.

*Edit: The smudge tool is the sixth icon down on the left side menu.The one with the green horizontal arrows. Andrew, I can barely stay up with you on all the new features you keep adding :lol: . Now do not take that as I'm saying slow down

*Edit: Thank you for drag points working in symmetry mode.

[Andrew Shpagin]

Andrew, now I get "no" status texture numbers at the bottom of 3D-Coat's interface. I tried several 3DC files and imported Objs with and without uv maps. The same results on models, no status texture numbers. All the other status information is appearing at the bottom.

Now that status is not shown because object can contain several textures (uv-sets) . I have decided to remove that value. If you want , I can show size of all textures.

[digman]

I see no need at the bottom but somewhere we could check on the texture size(uv-sets) would be good.That way we would not have to write it in notepad to help us remember.

[wailingmonkey]

wow...quick work, Andrew (as ususal)

perhaps this can be combined (as 4 dropdown options) with the magnify/reduce tool to save

room for further tools?

I can see these tools working on that 'grid' texturing projection functionality you spoke of adding

previously (similar to Photoshop's Liquify filter)...

Nice job once again!

[yukon_28]

Thanks for this cool addition Andrew, i like it! I can think of a few good uses for this new tool.

Now that status is not shown because object can contain several textures (uv-sets) . I have decided to remove that value. If you want , I can show size of all textures.

I also think its ok to remove it, texture sizes can be checked in uv sets manager or "change resolution" dialog.

[digman]

Thanks for this cool addition Andrew, i like it! I can think of a few good uses for this new tool.

I also think its ok to remove it, texture sizes can be checked in uv sets manager or "change resolution" dialog.

Thanks, I missed that one, uv-sets manager, see I can't keep up with the man :lol:

[digman]

Can others please test this problem I'm having to make sure it's not on my end only.

The problem:

When importing obj, the texture size selection appears to be glichy. I would select say 512X512 but after loading the texture size would be different in the change resolution setting dialog box. It would be 1024X1024 etc. The uv-sets manager and somtimes the change texture resolution dialog box would not be updated if I changed the texture resolution. I tested changing a resolution 512X 512 to 1024X1024 but when exporting the texture was still 512x512. I went back and forth importing obj files and exporting textures and it would get glichy as stated above.If I closed the program the first imported obj seem fine but sometimes not with the texture resolution size. Please test this because if It's on my end, I do not want to keep addressing an issue in the forums unnecessary.

*Edit: This is one way I reproduced the error. Load a obj file at 2048x2048 texture resolution with automapping. Then reload same obj without saving at 512X512 using automapping. The uv-sets manager and the change texture resolution dialog box are not updated to the new texture resolution.Your exported texture is not 512x512 but 2048 x2048. picture included.

[ldzywsj]

2) shift - constrains for horisontal/verlical/diaginal movements of the pen. Click on surface and then press SHIFT

I test it ,but it is not working!Am I wrong?

[wailingmonkey]

digman, I can confirm that if I initially set texture res to 512X512 on import, the 'UV-sets manager'

registers them as 2048X2048 when I first check. The 'Change mesh and texture resolution' however,

showed them to be correct at 512X512. I was able to change the 2048 setting in 'UV-sets manager'

to 512 and it stayed that way. I was also able to export out my map at its correct size of 512X512.

(perhaps it's just a 'Uv-sets manager' bug ?)

ldzywsj, the shift-constraining works fine over here (quite nice, in fact, since it works in both 3d and

on the 2d texture in 'view/edit textures' panel). <shrugs>

[digman]

I test it ,but it is not working!Am I wrong?

One thing that was left out of the statement is left click on the surface and keep holding down the left mouse button, then hold down the shift key also. I followed the words of the statement to the letter till I figured it out... sometimes the obivious is as they say in American slang, "if it was a snake it would have bit me"!

[ldzywsj]

ldzywsj, the shift-constraining works fine over here (quite nice, in fact, since it works in both 3d and

on the 2d texture in 'view/edit textures' panel). <shrugs>

Yes,I am wrong,I get it! Thank you wailingmonkey and digman!

[Andrew Shpagin]

Can others please test this problem I'm having to make sure it's not on my end only.

The problem:

When importing obj, the texture size selection appears to be glichy. I would select say 512X512 but after loading the texture size would be different in the change resolution setting dialog box. It would be 1024X1024 etc. The uv-sets manager and somtimes the change texture resolution dialog box would not be updated if I changed the texture resolution. I tested changing a resolution 512X 512 to 1024X1024 but when exporting the texture was still 512x512. I went back and forth importing obj files and exporting textures and it would get glichy as stated above.If I closed the program the first imported obj seem fine but sometimes not with the texture resolution size. Please test this because if It's on my end, I do not want to keep addressing an issue in the forums unnecessary.

*Edit: This is one way I reproduced the error. Load a obj file at 2048x2048 texture resolution with automapping. Then reload same obj without saving at 512X512 using automapping. The uv-sets manager and the change texture resolution dialog box are not updated to the new texture resolution.Your exported texture is not 512x512 but 2048 x2048. picture included.

Export and view resolutions can be different. UV - sets manager manages export resolution, Change mesh and textures resolution - view resolution. In general it is bug that initial settings are different.

[yukon_28]

Export and view resolutions can be different. UV - sets manager manages export resolution, Change mesh and textures resolution - view resolution. In general it is bug that initial settings are different.

Andrew, i think you need to do smal "Statistics" window dialog. Almost any application i know have some kind of statistics, so there no reason the best 3d painter in the universe should not get one

I think it can be new line in "View" menu, called "Show scene statistics", it will open small window dialog with all needed info, such as view and export texture resolution, lowpoly, highpoly and carcass mesh resolution with number of polys, verts and tris, number of maps to export, number of materials and objects etc., any useful info you can think about can be there. I think its should help to user to get all info of this kind in one place, also its should not be very hard to implement for you.

[Rainer]

I can only install 209B1 Beta. Any version after that crashes right after the installation. When I uninstall the version then I can install the older version and register with my serial number and all is good. But none of the newer releases work here. Win XP SP2 and Opteron quad.

Cheers

Rainer

[digman]

I redownloaded the link at the top of the thread. This one crashes on trying to load. Andrew, did you update this version to the lasted version that is on the displacement thread. They both the same in number. 3d-Coat-209B3B-en.exe. That one crashed too. I have a pic of the crash error in the vector displacement thread.

[Andrew Shpagin]

I have fixed the bug, please re-download.

[digman]

When I installed the updated beta. I got this brush error and continue to do so. The program does not crash now. I enlarged the brush so you can see it better. Have not change any hardware settings. I can install an earlier beta and no problems with the brush.

[Andrew Shpagin]

When I installed the updated beta. I got this brush error and continue to do so. The program does not crash now. I enlarged the brush so you can see it better. Have not change any hardware settings. I can install an earlier beta and no problems with the brush.

ops.. I have forgotten to remove local space preview... Will remove it asap

[styx]

where can i turn off the "view of the normal position"? O.o

[rimasson]

Just download the latest beta

[styx]

thx ; )

[Guest Lottmedia]

it may be just me but .9 feels a little more sluggish to me than .7 (last ver I used) anyone else?

Casey

[Guest Lottmedia]

it may be just me but .9 feels a little more sluggish to me than .7 (last ver I used) anyone else?

Casey

beta4 seems to fix it, or else it was somethign else, whatever, it's good now

C-