Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Version 3.6 crashing Not working #630

Open
Groveplace opened this issue Jun 6, 2023 · 33 comments
Open

Version 3.6 crashing Not working #630

Groveplace opened this issue Jun 6, 2023 · 33 comments

Comments

@Groveplace
Copy link

Every issue should include 3 things:

  1. System setup (GPU, CPU, OS version, Blender version)
  2. Most ideally a .blend scene to reproduce this simply. SCREENSHOTS OR RENDERS ARE NOT A SCENE FILE
  3. What the expected behavior or effect is. If possible include the error message.

You can get more information on the error message by opening Window -> Show System Console from blender and copying that text here. On MacOS launch Blender from the Terminal.

Steps to Reproduce

System Setup (Environment)
@Groveplace
Copy link
Author

AMD pro Render crossfire AMD CPU Win 11
Blender 3.5.1 and Alpha 4.0
Crashes on Launch both builds

@Groveplace
Copy link
Author

RPR error in file hybridpro
File "C:\Users\x\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\rprblender\pyrpr.py", line 74, in wrapped
raise CoreError(status, f.name, argv, module_name)
pyrpr.CoreError: RPR call CreateContext(3145985, [1], 1, 3, <cdata 'void *[]' owning 8 bytes>, b'C:\Users\x\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\rprblender\.cache\0x300101_hybridpro', <pyhybridpro.Context object at 0x0000027DFA891CC0>) returned error code <-23> with error message: ''

also the CPU render button is greyed out
not supporting crossfire
Version 3.5 is very stable

@Groveplace
Copy link
Author

AMD pro driver for win 11 Q1.2023

@H3rcu1es
Copy link

AMD pro driver for win 11 Q1.2023

hi , I am having the same issue .what do you mean by AMD pro driver for win 11 Q1.2023? Is this driver working?

@ARozghon
Copy link

Hi, do you have the same issue with the latest weekly build? https://github.com/GPUOpen-LibrariesAndSDKs/RadeonProRenderBlenderAddon/releases/tag/v3.6.2

@H3rcu1es
Copy link

Hi, do you have the same issue with the latest weekly build? https://github.com/GPUOpen-LibrariesAndSDKs/RadeonProRenderBlenderAddon/releases/tag/v3.6.2

In my case , Yes . Same issue .

@bsavery
Copy link
Contributor

bsavery commented Jun 13, 2023

@Groveplace what is your GPU?

@Groveplace
Copy link
Author

Groveplace commented Jun 13, 2023 via email

@Groveplace
Copy link
Author

Groveplace commented Jun 13, 2023 via email

@bsavery
Copy link
Contributor

bsavery commented Jun 13, 2023

What physical GPU hardware, not which driver.

@Groveplace
Copy link
Author

Groveplace commented Jun 13, 2023 via email

@Groveplace
Copy link
Author

Groveplace commented Jun 13, 2023 via email

@bsavery
Copy link
Contributor

bsavery commented Jun 13, 2023

Try enabling the "OpenCL mode" under the debug settings. This older card does not support HIP

@Groveplace
Copy link
Author

Groveplace commented Jun 13, 2023 via email

@bsavery
Copy link
Contributor

bsavery commented Jun 13, 2023

In the render settings for this plugin. At the bottom. Choose the checkbox saying "Use OpenCL".

(As a general statement this isn't the place to go to ask about driver settings, only for support of the plugin for Blender.)

Screenshot 2023-06-13 at 4 43 38 PM

@Groveplace
Copy link
Author

Groveplace commented Jun 13, 2023 via email

@Groveplace
Copy link
Author

Groveplace commented Jun 14, 2023 via email

@Groveplace
Copy link
Author

Groveplace commented Jun 14, 2023 via email

@Groveplace
Copy link
Author

Groveplace commented Jun 14, 2023 via email

@H3rcu1es
Copy link

In the render settings for this plugin. At the bottom. Choose the checkbox saying "Use OpenCL".

Ya now it's working . Works while on Quality > viewport mode > Final . Interactive gives blank viewport . In render Interactive gives error .

@Groveplace
Copy link
Author

Groveplace commented Jun 15, 2023 via email

@H3rcu1es
Copy link

H3rcu1es commented Jun 16, 2023 •
edited
Loading

@bsavery For some reason transparent BG(on Flim option) doesn't working on viewport ,still showing the HDRI. But works on final render .

@bsavery
Copy link
Contributor

bsavery commented Jun 16, 2023

@bsavery For some reason transparent BG(on Flim option) doesn't working on viewport ,still showing the HDRI. But works on final render .

Please make a new issue with that so we can track it.

@JozeKyza
Copy link

JozeKyza commented Jun 28, 2023 •
edited
Loading

Pro Render can't handle sophisticated scenes that cycles can and just crashes ..., the basic cube renders fine... my machine Asus G15 Advantage edition with AMD Ryzen 9 5980HX with Radeon Graphics & RX6800M , version Pro Render 3.6

@Groveplace
Copy link
Author

Groveplace commented Jun 28, 2023 via email

@batero2000
Copy link

Hi, I'm having the same issue here.

Seems like ProRender is glitching with the GPU and interactive mode enabled on Blender 3.6. Hope there is a fix soon.

@bsavery
Copy link
Contributor

bsavery commented Jul 25, 2023

Hi, I'm having the same issue here.

Seems like ProRender is glitching with the GPU and interactive mode enabled on Blender 3.6. Hope there is a fix soon.

What GPU.

@batero2000
Copy link

Hi, I'm having the same issue here.
Seems like ProRender is glitching with the GPU and interactive mode enabled on Blender 3.6. Hope there is a fix soon.

What GPU.

XFX's Radeon RX 6700 XT (12 GB)

@Groveplace
Copy link
Author

Groveplace commented Jul 26, 2023 via email

@bsavery bsavery mentioned this issue Sep 14, 2023
Closed
This was referenced Sep 18, 2023
Closed
Closed
@BrunoDSL
Copy link

I am running into the same issue while trying to render the classroom Blender example render except Blender crashes even if nothing is rendered after a few seconds regardless of the current render settings.

@Groveplace
Copy link
Author

Groveplace commented May 13, 2024 via email

@BrunoDSL
Copy link

That happens even with "OpenCL" selected in debug but it only happens in this particular scene. There's no way to even change the materials to ProRender compatible ones because Blender crashes before you can do that.

@Groveplace
Copy link
Author

Groveplace commented May 14, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@bsavery @BrunoDSL @batero2000 @H3rcu1es @ARozghon @Groveplace @JozeKyza