It depends on what coordinate systems(left-hand or right-hand) these apps use internally.Rikk The Gaijin wrote: Ok, but then why does Maya and Marmoset display it correctly?
I use the 349.09 version which seems to be the last one but I had the problem with the 2 or 3 last versions of the drivers.abstrax wrote:Sorry, I've got no idea what the problem is, but it sounds like a driver problem. Which driver do you use and did you try different versions?enricocerica wrote:Hi,
I have two GTX580 in my cubix expansion box, it works fine if I activate only one card but if I activate both of them, it crashes very often with a BSOD. I discovered that if I set the Minimum display samples to at least 2, I have no problem, as soon as I set it back to 1 it crashes again.
Any idea why I got this problem and if there is a way to avoid it as I don't always think to set it to 2.
But the point is that it didn't match any EXIF data, because there is one important component missing: Exposure time. An exposure of 1 doesn't mean 1ms or something. In the past it didn't match anything, now the colour of a texture emitter is reproduced exactly if the exposure is 1 and camera response curves and vignette are disabled. And obviously, this doesn't have anything to do with EXIF data.Phil_RA wrote:Good news all around, except that you should keep Exposure, F/Stop, ISO, as an option. It's useful to match the values from a photo's EXIF data, for example of you want to use the same values as those used to make an HDR image.
A reason why this is really useful is that if you want to be physically correct, you need some sort of reference to match. Currently, people set incorrect light intensities and then just boost the exposure.
If we think like this, we might as well remove the efficiency and power and just have a meaningless "intensity" parameter, but all of this makes it more difficult to be physically correct.
What do you mean by "stopped working immediately"? Usually this should not happen of course, and as far as we have tested it doesn't. -> Could you send us the scene?vitgaus1049 wrote:Hello! After exporting the alembic from 3D MAX I'm trying to render the animated frames in Octane 2.16 Standalone. While scrolling through the animation the standalone stopped working immidiately. Any ideas how to fix? Hopefully this is not a Octane bug.
Sure, here is the abc fileabstrax wrote:What do you mean by "stopped working immediately"? Usually this should not happen of course, and as far as we have tested it doesn't. -> Could you send us the scene?vitgaus1049 wrote:Hello! After exporting the alembic from 3D MAX I'm trying to render the animated frames in Octane 2.16 Standalone. While scrolling through the animation the standalone stopped working immidiately. Any ideas how to fix? Hopefully this is not a Octane bug.
Hi,vitgaus1049 wrote:Sure, here is the abc fileabstrax wrote:What do you mean by "stopped working immediately"? Usually this should not happen of course, and as far as we have tested it doesn't. -> Could you send us the scene?vitgaus1049 wrote:Hello! After exporting the alembic from 3D MAX I'm trying to render the animated frames in Octane 2.16 Standalone. While scrolling through the animation the standalone stopped working immidiately. Any ideas how to fix? Hopefully this is not a Octane bug.
https://www.dropbox.com/s/63kn5il2wcv5w ... d.abc?dl=0
"OctaneRender Standalone has stopped working" that was the massage of my Win 8 immideately after scrolling the animation of the alembic file
