Author Topic: Daily builds version 2  (Read 130422 times)

2018-06-05, 23:11:59
Reply #615

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8779
  • Let's move this topic, shall we?
    • View Profile
    • My Models
Is it possible to make that create Corona cam from view button in Corona toolbar, would select the camera after its creation? I find that 95% of the time, i need to select freshly created camera, to tweak its settings.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2018-06-06, 09:47:57
Reply #616

Frood

  • Active Users
  • **
  • Posts: 1903
    • View Profile
    • Rakete GmbH
select the camera after its creation?

Agree. Our internal CreateCoronaCam button does this.

Plus: If in perspective view and some camera selected it will not create a new one but change the selected one to match the viewport (with warning + warning if camera is locked).

Would be a nice addition (I could ask a moderator to move this to feature requests ;)


Good Luck

Never underestimate the power of a well placed level one spell.

2018-06-06, 09:54:23
Reply #617

Ryuu

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 654
  • Michal
    • View Profile
Is it possible to make that create Corona cam from view button in Corona toolbar, would select the camera after its creation? I find that 95% of the time, i need to select freshly created camera, to tweak its settings.

This is super simple, so we're already working on it.

Plus: If in perspective view and some camera selected it will not create a new one but change the selected one to match the viewport (with warning + warning if camera is locked).

This is a bit more complex with a chance to break something. So please somebody make this into a separate feature request so that we won't forget about it once we start working on v3 :)

2018-06-06, 10:38:57
Reply #618

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8779
  • Let's move this topic, shall we?
    • View Profile
    • My Models
I could ask a moderator to move this to feature requests ;)
I think it would be easier for you to create new feature request, than for me to figure out how to elegantly cut this conversation in to separate meaningful message ;]
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2018-06-06, 11:07:17
Reply #619

Frood

  • Active Users
  • **
  • Posts: 1903
    • View Profile
    • Rakete GmbH
Hehe, just joking Romullus - don't neglect your lawn by working too hard for the forum ;]

I will not request this directly, I just described how our button works to add some ideas. Not sure if this kind of (multi-) functionality fits into Corona philosophy anyway, but it turned out to be quite useful.


Good Luck


Never underestimate the power of a well placed level one spell.

2018-06-06, 14:10:06
Reply #620

peblguzzi1966

  • Users
  • *
  • Posts: 1
    • View Profile
My system is 2x intel xeon cpu e5-2660 v3, 32gb ram .. 3ds max 2018..It seems that this version is a bit slower in rendering than the old one. But maybe that's just because it's not completely finished yet.
The scene that I have attached is about 2 minutes slower with version 2 than version 1.7.4.
36 minutes with version 2 and 34 minutes with version 1.7.4

2018-06-07, 07:51:41
Reply #621

Zray

  • Active Users
  • **
  • Posts: 43
    • View Profile
    • 3darcspace studio
In my opinion, I like the exclude nodes of material override in 1.7 version. Now I have to click one more time to use it.

2018-06-08, 15:19:10
Reply #622

kalininpark

  • Users
  • *
  • Posts: 4
    • View Profile
Is it normal for volumegrid? One object covers another. Max 16 RC1

2018-06-08, 16:07:31
Reply #623

Ryuu

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 654
  • Michal
    • View Profile
Is it normal for volumegrid? One object covers another. Max 16 RC1

Please send the scene for investigation.

2018-06-08, 16:35:47
Reply #624

kalininpark

  • Users
  • *
  • Posts: 4
    • View Profile
uploaded file 1528468376_volumegrid-test.rar
here a some other wired things, something wrong with bounding box
also somehow i was unable to post it on mantis today

2018-06-08, 16:53:36
Reply #625

sevecek

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 197
    • View Profile
Hi,

unfortunately it is a known bug that will not be fixed in v2, as it requires heavy rewrites in Corona core.
To avoid problems, please make sure the Volume grids are not intersecting each other and always place the camera outside the medium.

2018-06-08, 17:06:45
Reply #626

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8779
  • Let's move this topic, shall we?
    • View Profile
    • My Models
I noticed strange behaviour of noise level reporting in VFB. I set noise level to 7,0 as stopping conditions. Usually it takes 10 passes to reach this level, but for some renders it takes a bit longer and after 10 passes noise level shows 7,2 or so. If i notice that and stop render manually, then VFB shows very small noise level, like 1,5 or so, but if i let it render to 15 passes then after that, noise is shown at about 5%. Not that it bother me much, but i thought i let you know.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2018-06-08, 23:22:03
Reply #627

Njen

  • Active Users
  • **
  • Posts: 557
    • View Profile
    • Cyan Eyed
Yes! I can finally read information in the information in the pixel probe for the first time!
Thanks Ondra.

2018-06-10, 10:23:56
Reply #628

andreholzmeister

  • Active Users
  • **
  • Posts: 19
    • View Profile
Trying to animate the Corona Camera target distance by the value slider and keep getting crashes after frame 3... 

2018-06-10, 13:27:25
Reply #629

sevecek

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 197
    • View Profile
Trying to animate the Corona Camera target distance by the value slider and keep getting crashes after frame 3...

Reproduced, it should be fixed in the next RC. Thank you!