(Solved) OpenCL - pixels, textured background and crashes

  • 8 Replies
  • 211 Views

0 Members and 1 Guest are viewing this topic.

Offline Micha1982

  • *
  • Fractal Phenom
  • ****
  • Posts: 48
« on: April 09, 2018, 11:25:17 AM »
Hello,
actually I am trying around a bit in functionality and usge of Mandelbulber and "found" some more things:

First thing are textured backgrounds with OpenCL, is it normal that they do not work at the moment? If I activate them nothing happens, when I deactivate OpenCL they work fine.

Next thing are the pixels when I do a hybrid-fractal, fine with CPU, and with GPU they look as in the attached pictures, nothing else changed. Are they normal atm?

Furthermore MB crashes often at my "experiments" and as the second window closes immediately I am not able to exactly tell why...is there any logfile maybe?

One crash I found is reproduceable for me if I open "Hybrid 1.fract" and just change #1 Mandelbox' Iteration just from 2 to 3...when it tries to render the DOF it crashes (but in this case the second window stays open, I attach a picture)

Edit: For my other crashes I look in the mandelbulber_log.txt next time if contains something maybe
« Last Edit: April 16, 2018, 10:14:03 AM by Micha1982 »

Offline buddhi

  • *
  • Fractal Fruit Salad
  • *****
  • Posts: 76
    • Mandelbulber GitHub repository
« Reply #1 on: April 09, 2018, 05:18:00 PM »
First thing are textured backgrounds with OpenCL, is it normal that they do not work at the moment? If I activate them nothing happens, when I deactivate OpenCL they work fine.

Textures are not implemented yet in OpenCL rendering engine. If you open Preferences dialog in the program, then on OpenCL tab, you will se that there is written which functionality is not ready yet.

Next thing are the pixels when I do a hybrid-fractal, fine with CPU, and with GPU they look as in the attached pictures, nothing else changed. Are they normal atm?

It can happen with fractal which use "Delta DE" distance estimation which is not so accurate with single precision calculation used in OpenCL kernels.
To eliminate this side this effect you have to reduce "Maximum view distance" parameter on Rendering engine tab.
I'm going to improve "delta DE" distance to minimize numeric errors.

Furthermore MB crashes often at my "experiments" and as the second window closes immediately I am not able to exactly tell why...is there any logfile maybe?

One crash I found is reproduceable for me if I open "Hybrid 1.fract" and just change #1 Mandelbox' Iteration just from 2 to 3...when it tries to render the DOF it crashes (but in this case the second window stays open, I attach a picture)

Edit: For my other crashes I look in the mandelbulber_log.txt next time if contains something maybe

Look into User Manual (help menu) and read chapter 10.3.1 ("Trouble shooting OpenCL"). There is written how to modify Windows registry entries to avoid this problem caused by nVidia driver. This problem touches all programs which does long calculations using GPU.
Instead of setting registry entries manually you can run script TDR__DISABLE.bat from C:\Program Files\Mandelbulber2 and restart PC

In general read what is written in windows, messages and user manual. There is already a lot of answers.

Offline Micha1982

  • *
  • Fractal Phenom
  • ****
  • Posts: 48
« Reply #2 on: April 10, 2018, 06:39:52 PM »
Thanks, youre right, the batch helped avoid the crash in Hybrid 1 and the pixels in my own Hybrid are going away if I lower the max view distance.

Offline Micha1982

  • *
  • Fractal Phenom
  • ****
  • Posts: 48
« Reply #3 on: April 11, 2018, 08:54:47 AM »
I was too fast, still having many "Runtime Error"-crashes, some are easily to reproduce. It crashes for example after 1 second If I just open "Aexion001.fract"-example and press render...also tried in 1280x720.

It works when I disable "Raytraced reflections and transparency" - and crashes again if I try to render it with "high quality" in DE (cause it is so pixelated if I do not and leave it 0,616595)


Or if I just start the program, select "Abox Mod 12" in objects and just press render....

Or Kaliset 1 with position of fractal x, y ,z = 1...dont know why, maybe I am trying around too much and not doing what I am doing exactly but I attract crashes like a magnet
« Last Edit: April 11, 2018, 09:35:18 AM by Micha1982 »

Offline buddhi

  • *
  • Fractal Fruit Salad
  • *****
  • Posts: 76
    • Mandelbulber GitHub repository
« Reply #4 on: April 11, 2018, 06:46:09 PM »
If you get this OpenCL error, can you copy mandelbulber_log.txt located in C:\users\username and send me?
But before this please set log verbosity level to 2 in Preferences dialog.
This will help me to diagnose the problem.

Offline Micha1982

  • *
  • Fractal Phenom
  • ****
  • Posts: 48
« Reply #5 on: April 12, 2018, 04:05:34 AM »
Sure, here they are

Offline mclarekin

  • *
  • Fractal Fluff
  • *****
  • Posts: 369
« Reply #6 on: April 12, 2018, 03:40:50 PM »
My two cents

Quote
It crashes for example after 1 second If I just open "Aexion001.fract"-example and press render...also tried in 1280x720.

It works when I disable "Raytraced reflections and transparency" - and crashes again if I try to render it with "high quality" in DE (cause it is so pixelated if I do not and leave it 0,616595)


Or if I just start the program, select "Abox Mod 12" in objects and just press render....

Or Kaliset 1 with position of fractal x, y ,z = 1...dont know why

I did a quick test and they all rendered ok for me in Win10 with openCL

I find the program very stable in both Win 10 and Ubuntu. Recently the openCL crashing problems I read about are solved by editing the Win10 time out code in the registry. Other common problems usually occur during installation. However we did just find, and fix with release V2.13.2, an issue with the mouse wheel sometimes causing crashes.

BTW In Ubuntu there are no workable drivers for some older AMD gpus (like mine).

Offline buddhi

  • *
  • Fractal Fruit Salad
  • *****
  • Posts: 76
    • Mandelbulber GitHub repository
« Reply #7 on: April 12, 2018, 08:23:27 PM »
From log files I can see that the script for setting registry keys failed for you (maybe lack of admin rights when was run). Program fails when one continuous calculation is longer than 3 seconds. It triggers gfx driver timeout.
Try to add/modify registry entries manually (using regedit.exe) in a way how it is described in User Manual.

Offline Micha1982

  • *
  • Fractal Phenom
  • ****
  • Posts: 48
« Reply #8 on: April 16, 2018, 10:13:46 AM »
Youre right, it was because I ran the script without admin-rights. Now it really works fine.


xx
"Time Span"

Started by cricke49 on Fractal Image Gallery

0 Replies
103 Views
Last post August 02, 2018, 07:05:21 AM
by cricke49
xx
(Solved) Click image to open link not working

Started by Anon on Testing-Area

9 Replies
622 Views
Last post February 14, 2018, 06:15:02 AM
by Anon
xx
Birdie Style

Started by gannjondal on Fractal Image Gallery

1 Replies
181 Views
Last post May 08, 2018, 02:39:37 PM
by who8mypnuts
xx
Movement of pixels in several keyframes normal?

Started by Micha1982 on Mandelbulber

3 Replies
98 Views
Last post April 04, 2018, 02:06:28 AM
by Micha1982
xx
Buddhabrot-style Burning Ship [65536x24576]

Started by programagor on Fractal Image Gallery

12 Replies
221 Views
Last post October 10, 2018, 02:12:39 AM
by 3DickUlus