Announcement

Collapse
No announcement yet.

mismatched cameras after switching to scanline

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • mismatched cameras after switching to scanline

    Hi all, thought you might wanna hear about this , not sure of anyone has come accross it before.
    I am working with a colleague accross the other side of the states on the same project and we all of a sudden noticed that there was a mismatch between cameras even though we had ensured we always sent each other any camera changes. It turns out that if for any reason you switch from Vray to Scanline the cameras will be different and switching back to Vray doesnt fix it. From then on all cameras will be slight;y different unless you start with a blank Max and imprt all to it and then the cameras are back in place again. A damn nuisance that cost my buddy and I a days work and because he had already rendered a bunch and it was his sytem that had the scanline issue, I had to jump to scanline and back to get my cameras to match his. Just an FYI folks
    Yes, but is it Art ???

  • #2
    well...never tried it with scanline, but as far as I know it works. It seems that you have some kind of aspect mismatch more then camera mismatch. Ie. when you had your scene in vray you had a sertain pixel aspect put in, it could have changed when you switched to scanline.
    Dmitry Vinnik
    Silhouette Images Inc.
    ShowReel:
    https://www.youtube.com/watch?v=qxSJlvSwAhA
    https://www.linkedin.com/in/dmitry-v...-identity-name

    Comment


    • #3
      Yeah, I don't think the problem is the switching. I mix renderers all the time and have not had any issues.
      Eric Boer
      Dev

      Comment


      • #4
        well, its now gotten even worse,, I have version 1.48.03 supplied by Vray some time ago to fix a distributed bucket rendering snag in 1.47 I got when I bought Vray . My colleague has still 1.47 and we have an enormous problem which may cost us a huge amount of money. If my colleagues sends me a complete file all set up in vray along with the vrmap for irradiance GI and I render it on 1.48.03 its different slightly the angle just doesnt match. Now, if I send the file back to him saved from my system it renders correctly again on his 1.47. If I have a mismatch due to versions Its gonna cost me a fortune, we already missed the first deadline which was/is tomorrow Anyone with any clues as to what the hell is going on I would owe you forever
        Yes, but is it Art ???

        Comment


        • #5
          You should try to use the same versions of V-Ray. It would be best if you both use the 1.47 version; as noted, 1.48 is an intermediate internal build.

          Best regards,
          Vlado
          I only act like I know everything, Rogers.

          Comment


          • #6
            yes Ok Vlado but how do I manage to go back to 1.47 ?
            Yes, but is it Art ???

            Comment


            • #7
              The easiest way would be to go to the support page, download and run the installation; the .max files between the two versions should be compatible.

              Best regards,
              Vlado
              I only act like I know everything, Rogers.

              Comment


              • #8
                Ok well I did that , I had the original 1.47.03 but now I am in even deeper do doo's . My colleague and I split up the job into terrain etc and structures, I am a terrain and ground work specialist and he is a buildings specialist. The snag now, is that in order for us to both have the same camera angles I switched back to 1.47.03 and that worked but, now, I get unhandled exceptions almost everytime I try to render anything. We are now in very very big trouble having missed our deadline. Could you not furnish my colleague and I with perhaps version 1.49 since I hear from some of your testers that this version is way more stable and memory friendly. We are in big trouble here totally as a result of Vray. Please help
                Yes, but is it Art ???

                Comment

                Working...
                X