Rayscaper New Releases

pixelcruncher

Are you talking about the black splotches in the area I annotated below? They are not different textures, just artifacts.

Rich already mentioned it, but I think what's happening is that you still have a really noisy render, and then the denoiser will generate these black splotches. You can confirm that by disabling the denoiser and looking at the original image:

Rayscaper is a path tracer and needs to find a path to the light sources. In case it's challenging to find the light source (for example, because they are blocked or can only reach secondary light sources), you would see a lot of noise in the render. As Rich mentioned, Raysaper might be struggling with the glass in the windows and finding it hard to find good light paths to your HDRI image, which is providing the ambient light for your scene.

Check that the windows are made of a glass material that has the transparent option checked. This will ensure that the rays that are looking for lights don't see the glass at all. It's as if you don't have any glass for light rays. Of course, you would still see the reflections in the glass when you look at it directly. It's the best of both worlds, although not physically correct.

You can also increase the number of samples/px, which will increase the render time.

Let me know if this helps. I know it's a bit technical, so I'm happy to clarify.

All the best,
Thomas

pixelcruncher

@Krass

Good to see you are getting great results with Rayscaper!

pixelcruncher

@Krass Fantastic, a good showcase for Rayscaper!

I hope you don't mind, but I shared them on my X account.

X (formerly Twitter) (x.com)

Regards,
Thomas

Krass

With pleasure.
Yes, @Mike-Amos, I also check "transparent shadows" on Pixel cruncher's advice. But I do indeed go up to 35,000 SPP with a 2K resolution. I don't activate denoiser, and if your graphics card is sufficient, it's still fast. Probably 20 or 30 minutes of rendering time.

pixelcruncher

Yes, @Mike-Amos, I also check "transparent shadows" on Pixel cruncher's advice. But I do indeed go up to 35,000 SPP with a 2K resolution. I don't activate denoiser, and if your graphics card is sufficient, it's still fast. Probably 20 or 30 minutes of rendering time.

@Krass - I'm not sure if you've already noticed, but the denoiser is no longer destructive. You can disable/enable it in the viewport without having to restart the render. So you can actually check if the image looks good without having to go all the way to 35,000 samples/px:

pixelcruncher

Hey, Rayscaper users!

A quick hotfix release. More good things are coming later, but this solves some immediate issues that users reported.

Rayscaper 0.9.62 Beta is available in the SketchUcation store. I recommend upgrading to the latest version.

What Changed?

Make sure there's no watermark for licensed users.
Fix the render time counter in the viewport.
Fix a crash happening occasionally when updating geometry.

Help Me Build the Community

If you like Rayscaper, please share your renders (final or work-in-progress, it doesn’t matter)! This is motivating
and helps me showcase its capabilities to new users.

Follow me on X.

Happy Rendering!

nickchun

@pixelcruncher I've just downloaded the latest version but now cannot get any materials to show up at all. Using the colour picker tool doesn't highlight any material in particular. Everything else seems to work, just no textures on renders.. no colour.jpg

block.skp

Krass

I did the same. I am now on 0.9.62 and no problem

pixelcruncher

@nickchun Sorry about that!

Are the materials directly assigned to the faces, or are they assigned to the component/group? If you assign a material to a component/group, then they are not applied to the face. That's a regression reported by @sashapepperspray last week, but I haven't addressed it yet with this release.

Can you confirm that this is the problem, i.e., that the problem is fixed by directly assigning materials to the faces? You can use Fredo's Thrupaint to make it easier: https://sketchucation.com/plugin/2561-thrupaint.

If that doesn't help, there's something seriously botched in this release, and I will investigate further. Anybody else seeing this?

Thanks,
Thomas