[Yafray GUI] Bagisas v0.1.0

Artwork Works in Progress
1

Heyho!

The new Bagisas version v0.1.0 is online: http://www.fen-net.de/wolfram.kraus/Bagisas.html

New:

  • XML parsing is now faster (switched from DOM to SAX)
  • Doubleclick on shader/ light-branch switches to shader-/ lightpanel (This might be a little confusing under windows)
  • Scene-Directory preference setting (File->Preferences, don’t forget to File->Save Preferences afterwards)

Fixed:

  • UV-mapping don’t get messed up when modifing shaders (and some other things that got messed up due to sorting)
  • AttribGrid doesn’t handle all keys
  • included more self-closing tags in file-output

C&C ?? Problems? Bugs? Improvements?

2

That 's cool !
I’ll try this new bagisas right now.

3

Awesome! I was wondering when you were going to release this, and now you have! Dling now!

dante

4

Finally got to test this - so many new things coming out I’m having trouble keeping up. This release is great works the best on my windows system of all your other ones. One suggestion While I was testing it. I did a render then changed it, then did preview ,works fine. But it saved the preview over my original render. So if I liked the original best I had to re-render. My suggestion is to have some kind of option like a preview save that saves to a preview file and then you can render the last version you like for the final render. Not a problem but an idea.
Paradox

5

Well, if I like a render I just put it somewhere else. I’m going to make different final render versions anywho, so I have to save 'em either way.

6

Hm, it seems to hang everytime I open a 2nd xml. I mean I open one, and if I try to open an another one (or the same again) it hangs. Is it me, or does anyone else have the same problem?

7

Someone else reported this bug, too, so it is not your fault! I will have a closer look at this behaviour!

8

I don’t know if you have figured it out or not, but it seems to me (without looking at the sources, so it’s jut a guess based on it’s behaviour), that when it opens a file it first gets the number of elements it will need to import, than it looks for elements till it reaches that number, and when it does it is done. is that correct?
Now, the bug is because when a file is open, and it tries to open a new one, it reads the number of elements, and instead of storing it as it is, it adds it to the number of elements in the previous file, then it starts reading them from the begining, and when it reaches the end of file, it thinks that there are still elements left to be read (exactly as much as the previous file contained), but can’t find any, so it hangs.
Is this correct? :slight_smile:

9

Yes, that was exactly the error. I fixed it and will upload a bugfixed version on the weekend. (Sorry, I had no time lately, new job, hot weather, new comp,…)

10

First of all, you owe us nothing so no need to apologize. We owe you huge thanks for your work :slight_smile:

And now for something completely different:

I have been working on the bmw for a few hours now and a few things came up, I don’t know if anyone has mentioned it before. It has 1940 elements in the scene and when I do test renders, only the first shows the progressbar and yafray feedback stuff right. The rest stops displaying somewhere and then only shows the #s.
other thingy: it would be nice if
1, the progressbars length would be the same as the 0% 50% 100% titlebars length :slight_smile:
2, it would display what it’s doing continously, right now for me it only shows up for a sec then the progressbar takes over :slight_smile:

Now, these are tiny idi-bidy nothing at all bugsies, don’t pay attention to me, I just tought I would mention them 'cause I’m tired, and I am thankful for the stuff I can work with and so I like to annoy those who make it available :slight_smile: