Messages

4306

News / Re: Corona Renderer 1.7 for 3ds Max (Hotfix 3) released!

« on: 2018-03-21, 16:33:03 »

In our tests with a simple scene, with one cam with Vertical Shift only and one with Horiz and Vertical Shift (neither with Tilt) saved from 1.7.2 and opened in 1.7.3, the Legacy checkbox appeared as expected, and the FOV looked the same.

To look into it we'd need your 1.7.2 scene to see why it is different from what we are testing here, sorry we don't have anything else at the moment, but everything is working normally in our tests.

4307

News / Re: Corona Renderer 1.7 for 3ds Max (Hotfix 3) released!

« on: 2018-03-21, 16:22:55 »

Hi Alex, still investigating, sorry - we'll see what we can come up with. Two thoughts, can you send a simplified version of the scene for testing just in case we can't duplicate?

Another idea as a temporary workaround, depending on how much you like MaxScript, the useLegacyTiltShift parameter should still be accessible via maxscript to force the Legacy mode on. Of course this is just if you have one scene affected, no good if this is affected lots of scenes as you can't keep doing maxscript changes - but just in case it helps.

We'll let you know as soon as we have anything on this end, apologies for the inconvenience.

4308

[C4D] General Discussion / Re: Team Render very slow?

« on: 2018-03-21, 14:59:37 »

You can remove that effect simply by making the packet size large enough to send the whole image at once, I would think (it did in my tests) - but as noted, this could lead to network congestion if you are sending very large packets very frequently from lots of machines.

There isn't anything to "fix" here though as nothing is broken :) The data has to be sent across in chunks of some size... I guess the only way to change it would be to make the packets a whole number of the data size required for the entire image at once, but that would be a feature request rather than a fix. It certainly has no impact on the final image or result or rendering speed.

4309

News / Re: Corona Renderer 1.7 for 3ds Max (Hotfix 3) released!

« on: 2018-03-21, 14:05:49 »

Here's where it should appear - this should be only for cameras where Tilt & Shift was actually used (if it wasn't, then no Legacy checkbox will show up; and same for any new cameras created in 1.7.3 and later, the checkbox won't show up). Was it Auto or Manual Tilt & Shift that was used in your 1.7.2 scene?

4310

[C4D] General Discussion / Re: Team Render very slow?

« on: 2018-03-21, 12:53:33 »

I should add, larger packet sizes may cause more network congestion (as far as I know), especially depending on how often they are sent.

4311

[C4D] General Discussion / Re: Team Render very slow?

« on: 2018-03-21, 12:49:19 »

It isn't rendering in scanline :) What you are seeing is the effect of the limit of the data packet, which limits how much data the node sends back at once. This means the image builds in blocks, as it receives packets of that size, though on the node regular progressive rendering is going on as normal. Corona simply can't do scanline rendering at all under any conditions :) As a note, once rendering is complete, all the data packets from the nodes will be sent over, so you still get all the results of the (progressive) rendering from all the machines, just received in batches based on the packet size.

You can adjust the size of the chunks in the Render Setup dialog, Corona, Team Render settings by changing it to Manual and entering a size for the maximum packet to be sent at once (see screengrab) - larger values will send larger packets, meaning the image will build up in larger chunks. Again though, it has no effect on how things are being rendered on the workstation or node, and only affects how that data is transferred between the two.

The other parameter in there changes how often data should be collected from the TR nodes (longer will mean a longer waits for results from the nodes to come in, but they will have had more passes done since they'd have run for more time).

4312

[Max] I need help! / Re: I need some help on this 360 with Gear VR and vrto.me

« on: 2018-03-21, 12:32:23 »

Ah so that was to change into "Cardboard" mode by disabling the Oculus / GearVR system by the look of what it says there. Does make it easier to type in the weblink, as you can do that in the phone's keyboard before inserting it into the GearVR - using the Oculus browser you have to type in VR, not a problem if you have someone to read the URL to you, but fiddly when it's just you and you have to keep taking the GearVR off to read the next few characters to type in :) However, you only have to do it once, if that's the only thing that will be running on the device!

4313

[Max] Daily Builds / Re: Daily builds version 2

« on: 2018-03-21, 12:24:48 »

If you want to actually change it to a Corona Material (a "destructive" change to the scene), then that would be where the existing Converter script comes in, as that is what it does.

4314

[Max] General Discussion / Re: Corona Interactive, possible to use Distributed Rendering?

« on: 2018-03-21, 12:17:22 »

Not possible at this time, since DR involves sending the scene to all nodes, which takes time and so would make IR not Interactive any more.

4315

Learner’s Corner / About Learner's Corner

« on: 2018-03-20, 15:54:11 »

If you are taking your first steps with Corona Renderer, or even with 3D in general, and you'd like some encouragement, feedback, and constructive criticism on your finished works, then this is the place for you.

We look forward to seeing your art!

4316

[Max] I need help! / Re: I need some help on this 360 with Gear VR and vrto.me

« on: 2018-03-20, 15:02:38 »

(tested on an S7, and original GearVR headset, but I doubt either should make a difference... may depend on what browser / viewing app they are using, is my main thought here)

4317

[Max] I need help! / Re: I need some help on this 360 with Gear VR and vrto.me

« on: 2018-03-20, 14:58:44 »

It seemed ok to me - depends how they are viewing it, maybe? I went into the Oculus system, ran the Oculus browser, entered the URL (sooo tedious lol), then used the "Cardboard" icon on the web page to turn it into a full view, and I didn't see any issues with it.

4318

[Max] I need help! / Re: Render take huge time !!

« on: 2018-03-20, 13:15:20 »

Sounds very much like memory, especially when changing resolution changes the render speed from what would be expected.

This article covers most of the causes / solutions, e.g. LightSelect render elements each need more memory, so higher resolutions with lots of those can require a lot of memory (reducing the LightSelect layers, or even backing LightMix to scene and removing the layers, can help). https://coronarenderer.freshdesk.com/support/solutions/articles/12000023310-i-am-getting-a-sudden-rise-in-ram-usage-

4319

[C4D] General Discussion / Re: Vray to Corona Converter for C4D

« on: 2018-03-20, 13:12:02 »

A converter is on the roadmap for Beta 2 (V-Ray will be the priority for that) - https://trello.com/c/nvWgzgZy/33-scene-converter

4320

[Max] General Discussion / Know Your Devs - Ondra Karlik

« on: 2018-03-19, 16:03:40 »

With Corona, you don't just get the software, you also get the team behind it. Using the software will teach you about that, but how do you get to know about the team?

That thought gave us a new idea, "Know Your Devs". Here's how it works:

- Ask your questions in this forum thread
- We'll leave this thread open for 5 days, to give you time to ask your questions, then we'll lock it
- The developer will take a look through and answer the interesting questions, which we'll publish in the Corona Blog (probably a week or two after closing the thread)
- If it's successful, we'll repeat it for another developer!

So, what about that "interesting questions" part? Here are some guidelines:

- Please post only personal questions or questions about inner workings of the team. You can already ask technical questions in other parts of this forum, and this is about getting to know the developers as people.
- Keep your question relevant to the particular developer.
- Only ask, don't answer - even if you think you know the answer!
- It will be up to the developer to choose which they answer and which they don't.

With all that out of the way, please welcome our first developer to the Q&A hotseat.... Ondra Karlik!