[Rochr]

Since NL has stopped responding to error issues regarding the plugins, i though i´ld ask some of you here instead to see if you´ve experienced the same thing, or if it´s just me beeing totally lost.

With the newest Cinemaxwell, the renderer is supposed to render out the active viewport, right?
Well, the problem is that whenever i make a new scene using the 1.1 plugin, it renders out as it should once or twice, then the camera seem to loose focus completely.
At first i though it lost the tags and rendered out a blank sky, but after testing it a number of times, with the same result, everything just seem to get blurred to hell.

This scene here for example. It´s a plane object 5x5 m. The top image is what it looks like in C4D core, the bottom image is the exact same object rendered with Cinemaxwell, using an MXM.
No matter what you do, this is what you get. The same scene rendered in 1.0 (with 1.0 tags and MXM´s) with a camera, work without problems.



I´m also attaching the scene if someone should want to check.
http://www.rochr.com/Cameraerror.c4d

[goncalo]

I don´t have this kind of problems in my files... but i will see your file.
It works perfect with me cinamaxwell.

[beppeg]

If you don't use a target object for controlling the focus, you have to go in the depth tab of the cinema camera and active front and rear for controlling the center focus (maybe only rear ). Remember to set 1 in the unit moltipyer in the first tab of the cinemaxwell

[goncalo]

i totally agree with beppeg

If you don't use a target object for controlling the focus, you have to go in the depth tab of the cinema camera and active front and rear for controlling the center focus (maybe only rear ). Remember to set 1 in the unit moltipyer in the first tab of the cinemaxwell

and one thing more... Can you explain me why you are using f-stop 25 and shutter-speed 1/60 ????? maybe is better to see that to.

http://www.maxwellrender.com/forum/view ... tter+speed

[Rochr]

Thanks for the help guys. Appreciated.

goncalo, the camera was merely a test to see if it would work better. The reason for increasing fstop was because it has helped before to bring focus on objects. The rest is default settings.

I tried beppeg´s suggestion to see if it would work here.
Now i actually do get a clear object. Also tried with a camera target centered in the object but got no object at all.

This seem to do the trick, but by god it´s a completely idiotic, not to mention time wasting way to set up a camera.
The setup in 1.0 with camera targets and allowing multiple cameras was lightyears ahead of what we have now.
If we still need a camera, why take away a feature that actually worked without any problems?

I´ll gladely admit that HD-support and child translation are great improvements and something i need, but this issue forces me to go back to an older version until NL allow the use of camera targets again.
There´s just no way i´ll be able to work with the current camera system.

[dyarza]

Yes, yes, bring the camera selection menu back. It worked great!

D

[lllab]

...no i didnt- it crashed c4d often here.

cheers
stefan

[Rochr]

...no i didnt- it crashed c4d often here.

cheers
stefan

Camera selection worked well for me.
Although Maxwell have a tendency to crash just before/during voxelization when you have a fairly large amount of objects/polygons.
Doesn´t always terminate C4D along with it, but it happens.

[dyarza]

...no i didnt- it crashed c4d often here.

cheers
stefan

I never found the crashes to be related to camera selection when the camera was properly tagged.

[lllab]

well here it did, on all my pcs under 9.6 regulary when switching the camera after the first rendering.

cheers
stefan

p.s. whats wrong with the new system? it renders what you see int the renderviewport. just make sure you dont have another window activated(just like in c4d-AR). it works perfectly and without bugs here.
i just hate the new material workflow.

[Rochr]

p.s. whats wrong with the new system? it renders what you see int the renderviewport. just make sure you dont have another window activated(just like in c4d-AR). it works perfectly and without bugs here.
i just hate the new material workflow.

Well, the difference between AR and Maxwell is that in AR it works with 100 out of 100 renders. Problem is that with Maxwell it works about half of the times, and i use a normal camera with a target applied in the center of the object/structure.

Doesn´t matter if the camera viewport is maximized and active, i still suffer from the problems above. The funny thing is that it can (not always)work a few times while i´m setting up the proper camera view and doing some alterations to models, and then it simply looses focus, completely ignoring the camera target.

Another old annoying "feature" that is really starting to piss me off, is the problem with proper camera view translation to Maxwell, where Maxwell render out more than the camera view that you´ve set up in Cinema. It adds outwards from the borders you´ve set.
I usually spend hours setting up camera views, and if i set up a camera where i have models ending halfway out of the view, that´s how i want it.

NL have had a year to take care of this camera flaw. Think it sais a lot of how much they prioritize the plugin.

[lllab]

Rochr,

this sound like you are having misunderstood some concepts of the maxwell camera,
make sure you alway use the maxwellcamera with the expresse tag (it is in v1.1, ot you can download it here) never change the focal lenght wehn using maxwell. only the film with &height. this is easiest done with the expression.
aslo make sure that the proportion of with&height is the same as the proportion of the renderoutput. (2:1, 5.3, 16:9 etc)

i get 100% camera maching with AR ALL thhe time with this method.
camera matching is very easy so. it works all the time.

also i get no wrong views and errors with the camera system in 1.1. it also works all the time here. are you sure it is maxwells fault in yor system?

cheers
stefan

ps. there are definitly some severe bugs in 1.1 i also see, but to be honest with the camera i am not sure there is a bug, at least for me under about 6 workstations it works.

[dyarza]

p.s. whats wrong with the new system? it renders what you see int the renderviewport. just make sure you dont have another window activated(just like in c4d-AR). it works perfectly and without bugs here.
i just hate the new material workflow.

Not exaclty true. There is a switch under the edit menu of each viewport called "use as render view" C4D or Final Render use that view when you hit render, not just the active viewport. That way you can be making adjustments to your model close up in say a top or side view and if you hit render the top view is not rendered, the camera is.

In my case I use two monitors and have a small perspective viewport with the camera that I want to use and "use as render view" selected. On the main monitor I have four viewports that I use to edit the model or I switch to one large perspactive view to so some tweaks, but it is usually not the camera I intend to render.

With this logic I would be perfectly OK with the way that M~R works now if it would read the "use as render view" and render that specific viewport. I think the list of tagged cameras worked better for me because I use multiple cameras. I have a project now with 11 cameras so far and it made it more convenient. At least for me.

D

[Rochr]

Rochr,

this sound like you are having misunderstood some concepts of the maxwell camera,
make sure you alway use the maxwellcamera with the expresse tag (it is in v1.1, ot you can download it here) never change the focal lenght wehn using maxwell. only the film with &height. this is easiest done with the expression.
aslo make sure that the proportion of with&height is the same as the proportion of the renderoutput. (2:1, 5.3, 16:9 etc)

i get 100% camera maching with AR ALL thhe time with this method.
camera matching is very easy so. it works all the time.

also i get no wrong views and errors with the camera system in 1.1. it also works all the time here. are you sure it is maxwells fault in yor system?

cheers
stefan

ps. there are definitly some severe bugs in 1.1 i also see, but to be honest with the camera i am not sure there is a bug, at least for me under about 6 workstations it works.

Not sure what you mean with "expresse tag" Stefan.
If you´re referring to the maxwell camera tag, i use one in conjunction with the C4D camera, and i rarely touch those setting. The only alteration i do is in the C4D camera tab, changing focal length for a slight "zoom".
I always set proportions(exact pixels) in C4D as well as in Maxwell, so i don´t see why the output should be different.

I know there was a way to bypass this in previous versions, but it´s not really a fix, more a workaround.
Nothing wrong with workarounds, but they shouldn´t be permanent and replacements for flaws in the software.

With AR, i´ve never had these problems, so yeah, they are Maxwell related.

As for the loosing focus-problem, i´ve never experienced it in any previous versions of Maxwell, and i´ve done a few renders with them.

[lllab]

"If you´re referring to the maxwell camera tag, i use one in conjunction with the C4D camera, and i rarely touch those setting. The only alteration i do is in the C4D camera tab, changing focal length for a slight "zoom"

...well,yes this is exactly the mistake i mean.

there is a file with one camera and one target, both have c4d expression tags on it and the camera has a maxwellcameratag on it.
the maxwell camera tag it expanded through the c4d expression.

never ever change any value in the cinema camera, only use the normal camera tag or for your convinience the one decribed above.

then it works easy like a charm! try it....

its not maxwells fault, just adjust your workflow a bit. after a short time you love it.

i use the maxwell camera as objetc in the cinema libary dropdown menue and alos use it when using final render or vray- all views match all the time automaticly, no matter which renderengine i use.

look in your plugin folder there is tha maxwell camera object.

hope it helps,
cheers
stefan