Community
Arnold for Maya Forum
Rendering with Arnold in Maya using the MtoA plug-in.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Arnold ver 4.0.73.2020 alterates all camera & lights positions (not happening in ver 3.2.66.2020)

13 REPLIES 13
SOLVED
Reply
Message 1 of 14
pproestos
604 Views, 13 Replies

Arnold ver 4.0.73.2020 alterates all camera & lights positions (not happening in ver 3.2.66.2020)

I have 3ds max 2020.3 and MaxtoA 4.0.0.73


If I open 3ds max and then I click open to load

a max file: as you see in the left of the picture

everything is loading nice with no errors.


When I double click to open the same file,

all directional lights and physical cameras are

mispositioned.


This is not happening with the previous

version 3.2.66.2020


5477-bug2.jpg


Any other can confirm this?


thx.


*I attach the file to test it...


13 REPLIES 13
Message 2 of 14
Stephen.Blair
in reply to: pproestos

That's an osl error. And you don't seem to be rendering, at least not in those screenshots



// Stephen Blair
// Arnold Renderer Support
Message 3 of 14
pproestos
in reply to: pproestos

Thanks Stephen.

I deleted all custom osl I have. Still the same...

Yes in rendering there is no problem, but all lights and cameras

are going crazy.

All this if I open directly a file with double click.

Opening a file inside 3ds max, no problem...

Message 4 of 14
Stephen.Blair
in reply to: pproestos

No problems for me. But then I don't have VRay installed, and that scene is using some VRay stuff.



// Stephen Blair
// Arnold Renderer Support
Message 5 of 14
pproestos
in reply to: Stephen.Blair

Thanks again Stephen. I have vray installed only for converting reasons... Ok tomorrow I will try to remove it and tell you...

Message 6 of 14
pproestos
in reply to: pproestos

Stephen as you see I changed my post...

It's a bug! Can you confirm this please?

Message 7 of 14
Stephen.Blair
in reply to: pproestos

It looks like some display glitch. The actual camera target hasn't moved though. And after I open Render Setup, I see the real line as well.

5469-maxtoa-target.png


Workarounds:

  • Before you open the scene, change the system units to be different than the file units. Then let 3ds Max adopt the file unit settings.
  • Open the scene a second time.


// Stephen Blair
// Arnold Renderer Support
Message 8 of 14
pproestos
in reply to: Stephen.Blair

Stephen Happy New Arnold Year... Yes your workarounds are valid, but none of them needed till now with the previous versions of Arnold... And of course immmagine that I cannot do these tricks especially when I use a batch render script to render multiple max files. They all must have no errors.... And this camera and light position problem affects of course the rendering. Stick with the previous version for the moment...

Message 9 of 14
pproestos
in reply to: Stephen.Blair

Also Stephen, I have another issue I have is that I have messed up

with my profiles here in this forum...

I renamed my Autodesk username from "skifx" to "pproestos" and

here I appear with a new profile.

Is possible to merge all these profiles to one? (pproestos)


https://answers.arnoldrenderer.com/users/7939/pproestos.html

https://answers.arnoldrenderer.com/users/448/skifx.html

https://answers.arnoldrenderer.com/users/7694/cgpetros.html


Or can you forward my msg to somebody else who manage this?

thx...



Message 10 of 14
Stephen.Blair
in reply to: pproestos

Hi

Do you have scene where the renders are different? In my tests, the "bug" scene is the same whether it looks right or not in the viewpoert.



// Stephen Blair
// Arnold Renderer Support
Message 11 of 14
Stephen.Blair
in reply to: pproestos

The problem was reproduced and logged. A fix is in progress.



// Stephen Blair
// Arnold Renderer Support
Message 12 of 14
CarlFrischmuth
in reply to: pproestos

yes i have this bugs in all my scenes as well since upgrading to 4.0.073 in max 2019.3 (when opening previously saved scenes from 3.x.65

I've added my fixes below the issues to help, as it appears some nudging is required to get things back to where they're supposed to be.


the camera targets all get thrown to 0,0,0 when i open a file

if i pan in the active camera view a bit they snap back to where they are supposed to be and i just click undo and carry on


if items have an path animation constraint i find the object is at 0,0,0 on file open

if i go to the % along path parameter and nudge it by a new value it snaps back into place and if i undo its ok from then on until i save and close the file

this may be the same issue as below and hopefully the fix will sort it out.


rigged items (models with vertices --> linked xforms etc also get trashed, if i archive a scene and restore on another machine (used for rendering)

if i re-evaluate the stack by selecting the lowest item and then back to the top the rig rebuilds and is OK again

this seems to be accepted and a fix on the way hopefully soon


Message 13 of 14
Stephen.Blair
in reply to: pproestos

Fixed in MAXtoA 4.0.1.44

https://docs.arnoldrenderer.com/x/bISqBg



// Stephen Blair
// Arnold Renderer Support
Message 14 of 14
Stephen.Blair
in reply to: pproestos

Fixed in MAXtoA 4.0.1.44

https://docs.arnoldrenderer.com/x/bISqBg



// Stephen Blair
// Arnold Renderer Support

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report