Jump to content
3DCoat Forums

Twitter discussion: What Andrew is currently doing.


Recommended Posts







It guarantees normalmaps compatibility.


0 replies0 retweets1 favorite

 Reply

 Retweet

 Favorite1


More














"Draw on plane" extended on Curves/Text/Snake clay


0 replies1 retweet2 favorites

 Reply

 Retweet1

 Favorite2


More














3D-Coat now may import object space normal maps (with auto conversion to tangent space)


0 replies6 retweets6 favorites

 Reply

 Retweet6

 Favorite6


More







Link to comment
Share on other sites







Hash Animation master <--> 3D-Coat applink beta test - https://www.hash.com/forums/index.php?showtopic=46804 


0 replies2 retweets0 favorites

 Reply

 Retweet2

 Favorite


More














Extra functionnlaity in objectify - removing small flying noise, unifying small pieces, decomposing to child volumes, sorting by size.


0 replies1 retweet0 favorites

 Reply

 Retweet1

 Favorite


More














Seems objectify was super slow. I fixed it in beta6.






Link to comment
Share on other sites

  • Reputable Contributor

Objectify is not a common English word in the context of 3D... Yeah, I went What? too... :blink:

"Separate Pieces" is very easy to understand. 

There is no need for the word  "Disconnected" as pieces in common English usage implies that already...

We would say something like, I can get rid of all those pieces as they are not needed...

Edited by digman
  • Like 1
Link to comment
Share on other sites

  • Advanced Member

Well I agree .Separete Parts is easy to understand... if this tool is about separete parts for a imported object imported with many parts, ( this is the only way I get import objects modeled wit many parts... just with " import to separete instances " activaded in import menu and "imported without voxelization" too.other way I can´t import , always get boolean errors or crash ) the result is a layers with many childrens, and when I click the menu objectify with the mother layer activated , nothing happens...

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...
  • 2 weeks later...
  • Contributor

 

Finished updating render room, now it renders lights derived from panorama correctly.

 

It is already possible to render out lighting almost identical to what is displayed in the viewport. Sort of. Although it requires a little bit of tweaking and it doesn't allow for using additional lights.

The workaround I'm using:

  1. Set primary light intensity to 100.
  2. Set ambient light to 0.
  3. Lightness to 500*.
  4. AO percentage to 25*.
  5. Delete all custom lights.
  6. Black out the remaining light by setting its colour to (0,0,0) and intensity to 0.

* - The relation of AO percentage and lightness seems to be an exponential function. I only looked up some samples that work good.

Few pairs that return almost identical results on the rendered images:

lightness    ao_percentage
  1355            10
   500            25
   262            50
   174            75
   130           100

I mostly use pair 262/50.

The pairs return subtly brighter lighting than the viewport as I like it this way, but you can always darken it to almost perfectly match the viewport by slightly lowering the lightness parameter of each pair.

 

But this all is tedious, so I'm glad it won't be needed any more. :)

Edited by ajz3d
  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...