Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Krzysztof Marczak
@buddhi1980
thanks for info. I will check it and correct readme files.
Krzysztof Marczak
@buddhi1980
I have just switched to Qt 5.9.1. Everything works properly.
Krzysztof Marczak
@buddhi1980
With Qt 5.9.1 my gamepad works! So I will be able to improve and finish development of gamepad control.
Krzysztof Marczak
@buddhi1980
There is one problem with Qt 5.9.1. qDebug() doesn't output anything. This needs investigation.
Krzysztof Marczak
@buddhi1980
I have solved problem qith missing qDebug() output. I was system configuration problem. It returned working when I deleted /etc/xdg/QtProject/qtlogging.ini
Sebastian Jennen
@zebastian
Thats good news. The debug channel is probably deactivated by default, since it is only to meant to be used by developers, i guess.
Krzysztof Marczak
@buddhi1980
Probably you are right. qWarning() and qCritical() worked properly.
Sebastian Jennen
@zebastian
hmm, what about qInfo()?
Krzysztof Marczak
@buddhi1980
We need to change all temporary qDebug() outputs to WriteLog()
I haven't tested qInfo
Sebastian Jennen
@zebastian
The problem about qInfo was that in old versions of qt it did not work properly
At least that is what i remember
Anyway it would be rasonable to have one "consistent" logging mechanism, best to use our own WriteLog
BTW: What are the next steps you want to do in the project?
Krzysztof Marczak
@buddhi1980
I think it's good time to start cleaning up the code. DOF effects are almost done.
We need to add more error checking to the code to make all more robust
Sebastian Jennen
@zebastian
Yes, i also encountered some crashes and shutdowns, mostly some race conditions about new opencl code.
I will try to find a way to reproduce and investigate with debugger whats wrong.
Krzysztof Marczak
@buddhi1980
One actual issue is to use GPU for rendering DOF and SAAO using GPU. On most of GFX cards it's only possible to allocate 512MB per memory block. When image resolution is high (like 6400x4800) rendering of DOF fails.
Sebastian Jennen
@zebastian
I also could reproduce the problem with julia vector copy: buddhi1980/mandelbulber2#352 but i could not identify the error
Krzysztof Marczak
@buddhi1980
I'm going to predict memory usage and switch to CPU rendering when would be not possible with GPU
Sebastian Jennen
@zebastian
how much of a pixel range do you need to calculate these effects? maybe its possible to make these effects tile based to save memory. That would maybe only require little overhead of copying overlapping areas
Krzysztof Marczak
@buddhi1980
i will look at issue #352. It's also reproducible for me
these effects have to have access to full image, so it's not possible to divide image
Sebastian Jennen
@zebastian
#352 is probably a use after free, maybe the parameter stuff interferes with the preview below the julia parameters...
Krzysztof Marczak
@buddhi1980
So as you see now we should focus on debugging and cleaning up. Actual state of development is enough for new release. Most of effects and fractal calculations already works. More will came in v.2.13
Preparation for release will take probably more than month, because there was a lot of major changes. We need to check all old functions (like calculation of fractal formulas, which are now 4D), bring back compatibility with older versions, and make application more stable.
Sebastian Jennen
@zebastian
we will also need to test that queue / cli / netrender is working as expected with and without opencl (at least not crash, when opencl in not yet supported).
I will also add stuff to the test.cpp so we can check this more frequently, though this will need a lot of manual testing
Sebastian Jennen
@zebastian
There are two points which are a little controversial:
  • installation maybe do with make install (needs to be added to pro file)
  • recombine mandelbulber.pro and mandelbulber-opencl.pro
    see also here: buddhi1980/mandelbulber2#345
qmake and cmake take also instructions for installation, which could enable putting the shared data to the target location. but this will confuse existing package managing.
Also IMHO we can remove mandelbulber-opencl.pro again, and make the opencl inclusion based on a check, like the other optional packages. In the end its still not harmful for someone who buillds mandelbulber with opencl support and with no proper opencl setup, as long he does not enable the opencl in his settings.
Krzysztof Marczak
@buddhi1980
I want to have install option for make. If we need to do any chages in directory structure, we have to do them.
Sebastian Jennen
@zebastian
enabling make install with qmake should not be to hard and should work with existing structure, see here for more info: http://doc.qt.io/qt-5/qmake-advanced-usage.html
for cmake it should be possible as well: https://stackoverflow.com/a/11097012
Martin
@acidhunter

after some time of absence (new job, new home etc) i t team up with lachs0r to optimize the build process

the first step was to build the linux binaries with gitlab-ci

the whole mandelbulber team is invited to use this gitlab instance!
my personal goal (just for fun) is to provide builds, packages and a signed repository for linux/bsd/win(32/64)

after my success providing automated mandelbulber2-headless images there is time to improve the build time of the docker images

is there some interest to join this thing?

today i did a first build (ubuntu:trusty target) on gitlab-ci

i have to provide a deb repo in my job in near future

mandelbulber with its (2, 3 or 4? seperated buildbots) is the thing i need to "master"

Martin
@acidhunter
image.png
how could the osx build pass when there is no config to build them?

the magic the mandelbulber team did tu get up this great tool is awesome!!
i love this project but my coding skills cannot help here

i want support this project!
because i cant code the only way is to take the build and testing

Martin
@acidhunter

the project is mirrored to my gitlab in an automated way

creating the CI workflows, build packages and host them is the only way for me to give something back to the community!

Martin
@acidhunter
if u agree i could invite u to my git lab (got the public leaked email addys from .travis.yml)
Sebastian Jennen
@zebastian
Hi Martin,
Setting up a gitlab for custom CI is a great idea,
i am glad you are into packaging / building / testing, this is a skill we are currently low on.
I also have some basic experience with gitlab, so i would appreciate, if you can give me access to it.
My mail is: sebastian.jennen@gmx.de
BTW: MacOS Build is also tested in .travis.yml, its the else condition to if [ "${TRAVIS_OS_NAME}" = "linux" ]
Martin
@acidhunter
oh, i was a bit late yesterday
was better to go sleeping
account is created
Sebastian Jennen
@zebastian
@acidhunter do you got a dedicated runner?
Martin
@acidhunter
The runner for mandelbulber is dedicated.
Hexacore i7 with ssd storage
Bandwith is a bit limited (100/44mbit)