|
mclarekin
|
 |
« Reply #15 on: October 19, 2013, 10:32:16 PM » |
|
@Mr Lukesleftleg, nothing special maybe, but still very well done. We await in anticipation what ever comes next.  @Mr Quaz0r, thanks for the Win 64 . Minor bug is that on my computer the time elapsed/render time part, the font turns white as the render progresses, making it hard to read. @Mr Buddhi, thanks for the latest version. The new pointer is great for quickly showing the depth in the fractal. |
|
|
|
|
Logged
|
|
|
|
quaz0r
Fractal Molossus
Posts: 652
|
|
« Reply #16 on: October 20, 2013, 01:48:57 AM » |
|
@Mr Quaz0r, thanks for the Win 64 . Minor bug is that on my computer the time elapsed/render time part, the font turns white as the render progresses, making it hard to read. ah sorry i hadnt actually looked at the installer for it, looks like etc/ and lib/ made its way into the win64 installer, which it shouldnt. if you have the win64 version installed to its own directory, just delete etc/ and lib/ as they are not needed and you wont have the font issue any more. etc/ and lib/ contain the theme definition and module for the win32 build so if you have your win64 build sitting in the same install directory as the win32 then you need to install it to its own directory and remove etc/ and lib/ from it. |
|
|
|
|
Logged
|
|
|
|
|
mclarekin
|
|
« Reply #17 on: October 21, 2013, 08:24:59 AM » |
|
Thanks Mr Quaz0r, Sir. That was the easiest "fix" ever!
|
|
|
|
|
Logged
|
|
|
|
meander
Forums Newbie
Posts: 2
|
|
« Reply #18 on: October 21, 2013, 03:08:16 PM » |
|
Thank you Buddhi! It now works on the NVidia card in my Debian Linux machine.
Fast!
One minor issue. I was installing over a previous version, and the render with OpenCL was terribly random...
Removing the /usr/share/mandelbulber directory and reinstalling works perfectly. Perhaps getting rid of the old stuff
should be part of the installation.
FAST!
Thank you so much.
|
|
|
|
|
Logged
|
|
|
|
|
KBeezie
|
|
« Reply #19 on: October 22, 2013, 09:55:49 AM » |
|
Is there by any chance a way to make the app (either official or unofficial 64bit) choose my secondary graphic card for OpenCL (ie: primary is an nvidia card, but secondary is a 1GB ATI card).
When enabling OpenCL it always picks the Nvidia card.
|
|
|
|
|
Logged
|
|
|
|
|
KBeezie
|
|
« Reply #20 on: October 22, 2013, 10:10:41 AM » |
|
PS: Even with the ATI card selected as the default graphics in the bios (PEG2), the application still selects the Nvidia card when initializing OpenCL.
Edit: Would appear that after I installed the Latest Nvidia drivers, the ATI card gets selected in Mandelbulber when initializing OpenCL. (wondering if it'll stay that way).
|
|
|
|
« Last Edit: October 22, 2013, 10:25:55 AM by KBeezie, Reason: clarification »
|
Logged
|
|
|
|
|
KBeezie
|
|
« Reply #21 on: October 22, 2013, 10:55:09 AM » |
|
To update yet again (in case anyone is curious or would actually be weird enough to do the same).
I originally had my Nvidia GTX260 installed, which naturally isn't a good fit for Mandelbulber OpenCL right now. But I did have a spare (newer but 'meh' far as gaming goes) XFX Radeon R6570 (1GB DDR3).
Installed (physically) the R6570, installed latest Catalyst Drivers, rebooted selected PEG2 (ATI card) as default video.
Rebooted back up so both monitors were going.
Then I installed the Nvidia Drivers to the latest, rebooted, selected PEG back again.
Once I did that the AMD/ATI card get selected on OpenCL initialization. Even though I installed Nvidia drivers last, it would appear that OpenCL support was disabled for the Nvidia side, meaning mandelbulber will keep using the ATI card when initializing OpenCL.
This is the case even if I decide to unplug the monitor from the ATI card and only use one monitor.
Attached is a test render (SlowAO, Iteration Fog, Raytrace reflection) from that (which for some reason would normally crash mandelbulber if it selected Nvidia instead to render on).
|
|
|
|
Logged
|
|
|
|
|
Buddhi
|
|
« Reply #22 on: October 22, 2013, 09:56:09 PM » |
|
In next version I will add selection for GPUs. Can you send me (by priv message) output of clinfo command from your computer? Will be helpful for me.
|
|
|
|
|
Logged
|
|
|
|
|
KBeezie
|
|
« Reply #23 on: October 23, 2013, 07:24:51 AM » |
|
In next version I will add selection for GPUs. Can you send me (by priv message) output of clinfo command from your computer? Will be helpful for me.
Thanks I've done this, I noticed CLInfo shows both GPUs, so I guess it'll aid in coming up with a switch (would be interesting if both could be used at the same time, but I kind of doubt that with the different OpenCL implementations). |
|
|
|
|
Logged
|
|
|
|
|
Buddhi
|
|
« Reply #24 on: October 23, 2013, 06:07:38 PM » |
|
Thanks for sending clinfo. You asked about use both GPUs at the same time. Of course it is good idea. But I will don't do this, because I have no possibilities for testing this solution. This will be some open topic for a future. Now will be only switching.
|
|
|
|
|
Logged
|
|
|
|
|
KBeezie
|
|
« Reply #25 on: October 24, 2013, 05:07:43 AM » |
|
Thanks for sending clinfo. You asked about use both GPUs at the same time. Of course it is good idea. But I will don't do this, because I have no possibilities for testing this solution. This will be some open topic for a future. Now will be only switching.
Yea That's quite understandable, you have to be in a similar situation to be able to actively test it, but being able to switch on the fly would be very helpful, and hopefully the clinfo will help in being able to identify the various CL devices (at least the ATI implementation seems more sane especially when it'll also utilize the CPU for OpenCL where as Nvidia will not). |
|
|
|
|
Logged
|
|
|
|
hobold
Fractal Bachius
Posts: 573
|
|
« Reply #26 on: October 24, 2013, 02:00:52 PM » |
|
Thanks for sending clinfo. You asked about use both GPUs at the same time. Of course it is good idea. But I will don't do this, because I have no possibilities for testing this solution. This will be some open topic for a future. Now will be only switching. This is not a request. Not even a suggestion. Just want to mention the possibility of running OpenCL kernels on both GPU and CPU as a way to test setups with more than one compute device simultaneously active. |
|
|
|
|
Logged
|
|
|
|
|
Buddhi
|
|
« Reply #27 on: October 24, 2013, 06:44:57 PM » |
|
This is not a request. Not even a suggestion. Just want to mention the possibility of running OpenCL kernels on both GPU and CPU as a way to test setups with more than one compute device simultaneously active.
Thanks for this good idea. In this way I will be able to test it. Maybe I will try to do this. But now I have other priorities (e.g. possibility to use custom formulas with OpenCL). |
|
|
|
|
Logged
|
|
|
|
|
taurus
|
|
« Reply #28 on: October 27, 2013, 06:34:14 PM » |
|
From the beginning of the opencl development, I dreamt of using opencl versions in my half-automated searches for valuable julia sets. In Linux times, I failed to compile the packadge in a proper way, but now I think the time has come. While I could analyze about 200 parameters per night in cpu rendering mode, I can now make around 2000 parameters in acceptable quality and in full hd. I don't know, whether this will increase quality or number of images, I produce (I doubt that), but I will surely need to find a more effective way to set up my search animations. Else I will run out of tasks soon... Thanks Buddhi for your exceptional work!   |
|
|
|
|
Logged
|
when life offers you a lemon, get yourself some salt and tequila!
|
|
|
nftaylor
Forums Newbie
Posts: 1
|
|
« Reply #29 on: November 05, 2013, 08:50:20 PM » |
|
I downloaded the program dated 2013-10-16 from Sourceforge and installed it. My system is Windows7 Enterprise 64-bit SP1 with 16GB RAM. Running the program gave me an error message on startup, about a missing DLL. I tried re-installing, as advised, and got the same error message. Searching for the same DLL in my existing programs pointed to GIMP 2.8.6 <<C:\Program Files\GIMP 2\bin>>. I copied the file, ran Mandelbulber again, and got another error message, this time for a different DLL. Copy, run again. This was repeated until no error message was generated.
The list of copied DLL's:
libatk-1.0-0.dll
libcairo-2.dll
libffi-6.dll
libfontconfig-1.dll
libfreetype-6.dll
libgcc_s_seh-1.dll
libgdk_pixbuf-2.0-0.dll
libgdk-win32-2.0-0.dll
libgio-2.0-0.dll
libglib-2.0-0.dll
libgmodule-2.0-0.dll
libgobject-2.0-0.dll
libgtk-win32-2.0-0.dll
libharfbuzz-0.dll
libintl-8.dll
libjasper-1.dll
libjpeg-8.dll
liblzma-5.dll
libpango-1.0-0.dll
libpangocairo-1.0-0.dll
libpangoft2-1.0-0.dll
libpangowin32-1.0-0.dll
libpixman-1-0.dll
libpng15-15.dll
libtiff-5.dll
libxml2-2.dll
zlib1.dll
All were copied from the above noted folder, with the exception of <<libatk-1.0-0.dll>>, which was copied from <<C:\Program Files\GIMP 2\32\bin>>.
Now I get to play. Thanks for your work!
|
|
|
|
|
Logged
|
|
|
|
|
November 16, 2011, 11:04:25 AM
Dilber MC Theme by HarzeM