Messages

1651

[Max] I need help! / Re: Daily builds

« on: 2015-02-20, 21:04:31 »

So is this in a daily build? Do you have a CameraMod applied to your camera? This will lock the VFB controls, also, if you enable color mapping in the CameraMod, you won't be able to control it from the VFB anymore.

1652

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-19, 10:04:23 »

Please, can the db changelog get an update to reflect the changes in db from 2015-02-18?

1653

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-18, 16:07:46 »

Hi everyone!
I don't know is this bug or not, but for me scenes that was made in corona build from 29 january 2015 don't want to load in corona starting from february builds. 3dsmax crashes.
I was working on build from 29 jan and decided to install latest build and all this happens for me, so right now i'am back to 29 jan build.
Is this happens only for me? Any ideas why is this happens?)

I am working now on a very heavy scene and it's not very good if this scene will corrupt and wil not load on the next 3dsmax start)

I have been working and saving files with most of the builds from January and didn't have this issue... the most obvious thing would be to try to merge the old scene content into a clean one, did you try that?

1654

[Max] Resolved Feature Requests / Re: Bump intensity (the new rescaling from [0-1] to [0-100]

« on: 2015-02-18, 15:54:40 »

One can always increase bump intensity in texmap's output rollout if needed.

Sure, though I am always trying to avoid this because you easily overlook something that needs 3 click to be visible and the numbers multiply which makes it less intuitive. Also, it's a potential error source if you have to share your files with others.
Imo, the best is one value in one place.

1655

[Max] Resolved Feature Requests / Re: Bump intensity (the new rescaling from [0-1] to [0-100]

« on: 2015-02-18, 12:50:20 »

For me anything beyond 1 is too strong anyways so having it in a 0-100 range would be easier to type (and see) than 0.009 for example. The question is if you could go beyond 100, which is probably needed in some cases. If not, keeping it in 0-1 range makes sense indeed.

1656

[Max] Resolved Bugs / Re: CoronaMultiMap : IR and production different color (instance)

« on: 2015-02-16, 17:20:42 »

FWIW, I had a different random pattern in yesterday's build (15-Feb-2015) than in one from last week, so the random change doesn't seem to be fixed entirely.

1657

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-16, 12:35:37 »

Aargh, I've written an lengthy report and then our internet crashed.

So, the latest build is somewhat instable for me (max 2014, db 2015-02-15).

Issue 1
After rendering a couple of images, I am getting random scene prep hangs:
- on 'Parsing scene', max seems to iterate through an UVW modifier (modifier stack displays an UVW modifier that's instanced across 250 objects, UI flashes)
- CPU usage at one core, max' memory grows by 4 kb in 2 secons, max doesn't response and has to be closed forcibly

Issue 2
CoronaMultiMap renders a different random pattern than in earlier builds. Not sure if it differs from max session to max session or whatever else is causing it. I'd love to see it locked AND to have a random seed spinner like requested here: https://forum.corona-renderer.com/index.php/topic,7026.0.html. The current behavior makes it almost unusable in production unfortunately, it needs to produce stable and controllable results. It is super useful, it's just missing the last step.

Other than that, great improvements and fixes in the last days! IR is faster - great! - UI is still flashing on scene parsing however, but general changes don't seems to cause UI flashes anymore.

1658

[Max] Resolved Feature Requests / Re: CoronaMultiMap seed spinner

« on: 2015-02-16, 12:30:09 »

Oh yes, please add a seed spinner!

1659

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-13, 11:31:54 »

Old file opened in new builds: framebuffer gamma sets always 2.2.
but if you change framebuffer gamma in my script and save max file, then framebuffer gamma will be your value until you don't change it.

Thanks a lot, exactly the info I needed.

1660

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-12, 15:29:23 »

Some feedback on IR in db from 11-Feb-2015:

- generally slower than it used to be some weeks ago (didn't test IR so much lately so not sure when it became slower)
- parameter changes (environment U offset for example) result in UI flashing and current UI element losing focus (cursor not in U offset field anymore, for example)

Generally, we absolutely NEED an indication when IR launches and does its scene prep, it needs to print 'IR working...' somewhere so the user knows that max isn't about to freeze.
Also, we need an IR launch button. I know the stance is not to have too many buttons but the dropdown IR launch is neither intuitive, nor do I get any feedback if it's been pressed or not (besides that there's no indication on the main Render button for a dropdown option). Please rethink this.

1661

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-11, 20:25:32 »

Thanks, handy little script. How do I just get to know Corona's current gamma setting? Is it always 2,2 in newer builds even if I load a scene where an earlier Corona build was set to 1,8?

1662

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-11, 19:14:29 »

What's the mxs command to print and set Corona's current gamma value?

I have a scene I've set up with gamma of 1,8 and some maps loading gamma override suggest 1,8. I am not sure if Corona loads the scene with 1,8 or 2,2 and would like to check but it's not exposed in the newer builds anymore.

1663

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-11, 13:47:23 »

Yes that. It crashes on loading the Corona plugins, so I thought they could become somehow corrupted but purely replacing them didn't help. It's reported only as unhandled exception...so not very helpful to diagnose.

Dumb question, but are you sure you replaced the old ones with the correct max version?
The newest build works here, too, max 2014.

1664

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-08, 20:16:46 »

What's odd is that while some say IR works just fine others find it extremely unstable. Having an identical set of scenes to test against the daily builds would hopefully reveal bugs that are related to system specs.

What may be helpful is a focused bug hunting initiative like for example 2 or 3 scenes that are posted here for every db tester to test with DR and IR. This way we could catch some of the more esoteric bugs related to system specs as these have proved to be produce the random buggy behavior especially with IR, I guess that applies to DR as well. I'd contribute a scene for this, if some of us do we may achieve more in one week than with the random general use that most of us do.

1665

[Max] Daily Builds / Re: Daily builds

« on: 2015-02-04, 11:01:56 »

http://en.wikipedia.org/wiki/Color_temperature

so why white balance (K) in VFB and color mapping are invert ?

Because it's applied as white balance correction.