Itoo Software Forum

Author Topic: Explicit Normals  (Read 1380 times)

Shawn Olson

  • Jr. Member
  • **
  • Posts: 86
  • Wall Worm
    • Wall Worm
Explicit Normals
« on: October 25, 2018, 08:27:17 PM »
I would be awesome if FP could retain the explicit normals of the source geometry. Please consider adding support for this.

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 3261
    • iToo
Re: Explicit Normals
« Reply #1 on: October 26, 2018, 01:32:44 PM »
When using Forest Tools to create instances from scattered objects- explicit normals are retained.
Hope this is suitable workaround for You.
Rokas
iToo Software

Shawn Olson

  • Jr. Member
  • **
  • Posts: 86
  • Wall Worm
    • Wall Worm
Re: Explicit Normals
« Reply #2 on: October 27, 2018, 04:29:34 PM »
Rokas,

Yeah, I know about this workaround. But it's really not a good solution. It breaks the parametric workflow flow of using Forest as well as introduces performance issues if there are thousands and thousands of nodes. I would love to see Forest simply be able to retain the explicit normal of the incoming meshes. My coworkers and I use Forest for game environments and this is a challenge for us when scattering foliage that has specific normal needs for good lighting when sent to the game engine.

MattYoungWI

  • Newbie
  • *
  • Posts: 1
Re: Explicit Normals
« Reply #3 on: October 27, 2018, 10:56:17 PM »
+1. This would help out a lot!

ben_img

  • Newbie
  • *
  • Posts: 21
Re: Explicit Normals
« Reply #4 on: January 11, 2019, 02:23:01 PM »
+1. Useful thing indeed!

ben_img

  • Newbie
  • *
  • Posts: 21
Re: Explicit Normals
« Reply #5 on: January 29, 2020, 05:00:35 PM »
One year later, is there any news on this retaining normal option ?

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3720
    • iToo Software
Re: Explicit Normals
« Reply #6 on: January 29, 2020, 06:02:16 PM »
No, i'm sorry. We have been very busy lately with other issues (specially RailClone).

I will raise the priority in our wishlist, so it can be implemented as soon as possible.
Just to confirm: do you use V-Ray, isn't ?

« Last Edit: January 29, 2020, 06:04:48 PM by iToo »
Carlos Quintero
iToo Software

Shawn Olson

  • Jr. Member
  • **
  • Posts: 86
  • Wall Worm
    • Wall Worm
Re: Explicit Normals
« Reply #7 on: January 31, 2020, 01:53:14 PM »
For my purposes, it should not be renderer dependent because I'm sending the mesh data into a game engine.

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3720
    • iToo Software
Re: Explicit Normals
« Reply #8 on: January 31, 2020, 02:03:42 PM »
For my purposes, it should not be renderer dependent because I'm sending the mesh data into a game engine.

Then, are you exporting the full mesh of the Forest objects (as displayed in the viewport) to the game engine ?
It's important for us to understand your workflow, because depending of the process (viewport, render, etc.), the geometry is handled in different ways.

Thanks,
Carlos Quintero
iToo Software

Shawn Olson

  • Jr. Member
  • **
  • Posts: 86
  • Wall Worm
    • Wall Worm
Re: Explicit Normals
« Reply #9 on: January 31, 2020, 02:11:44 PM »
We have two cases where we are sending Forest data to the game engine:

1) Just transform and object ids... in this case, the explicit normals are not needed because the data for each prop is simply used to place the assets at export time.

2) Clustering: in this case, we are converting sections of forest objects into static meshes--and in this process the explicit normals are needed. This is the case where the current limitations becomes a bottleneck especially if iteration is needed.

ben_img

  • Newbie
  • *
  • Posts: 21
Re: Explicit Normals
« Reply #10 on: September 20, 2020, 04:30:49 PM »
Just wanted to keep this alive.
As the explicit normals would save up a lot of time for game engines indeed...

At the moment i have to use a script to put all the normals up on each forestpro object before exporting, it's quite time consuming!

Cheers

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3720
    • iToo Software
Re: Explicit Normals
« Reply #11 on: September 22, 2020, 10:12:11 AM »
I tried to implement this for FP7, but it was more problematic than expected.

3DS Max uses explicit normals only for viewport models, and requires a specific mesh class to store them. Unfortunately Forest 7 uses a different class to store the geometry, so we should rewrite several parts of the core to support it.
It's doable, and the issue continues in our to-do list. But it requires a lot of code rewrite and testing (to be sure we don't break anything in the process). I hope it can be done for next versions.

Carlos Quintero
iToo Software

ben_img

  • Newbie
  • *
  • Posts: 21
Re: Explicit Normals
« Reply #12 on: March 15, 2021, 01:51:12 PM »
Hi, it's me again :D

Just back checking about that explicit normals.
Sorry to be a pain.
I've just checked so many alternatives these last months and there are none...

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3720
    • iToo Software
Re: Explicit Normals
« Reply #13 on: March 15, 2021, 01:58:54 PM »
No changes on this yet, i'm sorry.
Carlos Quintero
iToo Software