Author Topic: Trypogen plug-in in VFB bugged  (Read 5821 times)

2018-01-16, 20:18:25
Reply #15

bableveske

  • Active Users
  • **
  • Posts: 10
    • View Profile
Quote
The plugin doesn’t have any render settings and it does the same thing when its by itself with a simple cube for example.

Then what does "Subdivision Renderer" right next to "Subdivision Editor" stand for?

That does the thing. Thanks. All works fine. Sorry for the useless timeconsuming runs guys.

2018-01-16, 20:45:19
Reply #16

bableveske

  • Active Users
  • **
  • Posts: 10
    • View Profile
Quote
The plugin doesn’t have any render settings and it does the same thing when its by itself with a simple cube for example.

Then what does "Subdivision Renderer" right next to "Subdivision Editor" stand for?

That does the thing. Thanks. All works fine. Sorry for the useless timeconsuming runs guys.

Actually that was only one half of the thing...the other half was in Corona Preferences - "Use original Cinema 4D scene" checked in, and now all looks the same.

2018-01-17, 10:41:52
Reply #17

houska

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 1512
  • Cestmir Houska
    • View Profile
So Merk Vilson confirmed our suspition about the editor vs. renderer settings being the problem:
"[...] It is worth mentioning that the most common mistake is when user works only with Subdivision Editor and leaves Subdivision Renderer unchanged. Subdivision in trypogen is split into two parts. If he has subdivision renderer set to 0, it will not give the same results that he can see in the viewport. [...]"

But I am quite surprised that the "Use original Cinema 4D scene" setting makes a difference! It should only concern the material preview! If it does something else, that's a weird bug that you jsut uncovered.