Already fixed... that and pile of others in 0.8.0
Already fixed... that and pile of others in 0.8.0
because him as a dev earned that trust and respect.It's interesting in that regard, some devs face huge amounts of toxicity in here regarding that issue, so much so that i can understand them leaving this site completely. Yet some threads like yours and few others stay quite civil. Can't exactly say what causes it, but i'm thankful for those civil threads. I rather like having and watcing good discussions, even if i were to disagree with something. It's environment that encourages constructive criticism rather than just outright negativity.
ToaM is the first work of Talothral I found. I was so impressed I've been playing some of the devs older releases. He writes a great story. Definitely one of the best.because him as a dev earned that trust and respect.
and that says alot. He is one of the few good ones in my eyes.
All his games to me been great.
and it also helps the dev got completed games under his belt, and stayed true to what he likes,
and gained a pretty loyal following from those.
I get excited for every new game of his, because I know it's right on track with all of my taste.
Whoa there! That's more like... 0.9.0 material!
I think when it comes to ren'py it is called a "feature" not a bug... >.>Talothral I think I've encountered a bug caused by the mix of opacity and multi speaker systems as you have implemented. The second speakers background overlaps the first speaker. This seems to be caused by having the background in the window declaration it renders the style disabling of the second speakers background ineffective. By which I mean if you remove the background used to add opacity namely lines 149,151,157 and 159 of screens.rpy it will work as expected. One possible work around is by assigning multispeaker windows I managed to get something similar to what would normally be produced by replacing your muliple2 stuff (lines 2160 to end of screens.rpy) with:
I really have no idea what I'm doing. The numbers are all trial and error by someone that doesn't know renpy trying to make something look like the original settings. There is almost certainly a better way to do it hopefully seeing this doesn't end up confusing the issue.You don't have permission to view the spoiler content. Log in or register now.
You don't have permission to view the spoiler content. Log in or register now.
I imagine its the issue you face with all middleware/game engines etc the easier they are the more you end up fighting with the defaults to do things that are not already there. Its all those situations where the engines devs go "Your trying to do what? why?".I think when it comes to ren'py it is called a "feature" not a bug... >.>
I'll look into it more deeply once I get a chance. While it can be annoying it isn't exactly game breaking. And I think I missed it completly because I use completly transparent textbox. Although solution probably will be just "resizing" the png that is used to darken the area where ever it is set.
My opacity slider is at 0 always so the issue wouldn't be visible, simply because ren'py stacks the textbox.png. Hypothetically speaking the "background Null()" should have removed it, but we are talking about ren'py... Anyway...You don't have permission to view the spoiler content. Log in or register now.
beer or stronger?Needs more tweaks but way too sober for that.
Usually stronger, whiskey or rum depending on the mood. Which is about once a year.beer or stronger?
Glad its sorted and the reason the null doesn't work is that the backgrounds are part of the function and not contained in a style which would allow it to be overridden as the multispeaker system is implemented at the style level. As styles are compiled at initialization any changes to opacity would require styles be rebuilt or renpy restarted which is why the backgrounds are added where they are. As I understand it.Needs more tweaks but way too sober for that.
I get a fatal error with the full PC gofile link.And it is time once more for the public release. As usual if you want additional links wait until the OP is updated or grab them from discord or the blog.
Tribulations of Mage 0.8.0
PC:You must be registered to see the links
PC Compressed:You must be registered to see the links
MAC:You must be registered to see the links
MAC Compressed:You must be registered to see the links
Update only:You must be registered to see the links
Compressed Update only:You must be registered to see the links
Android:You must be registered to see the links
Changelog:
You don't have permission to view the spoiler content. Log in or register now.
Interesting. What browser? The link failed with Firefox, worked on Chrome on another computer.I get a fatal error with the full PC gofile link.
View attachment 3408172
I tried Chrome, Midori and Edge.Interesting. What browser? The link failed with Firefox, worked on Chrome on another computer.
Interesting, the link works for me on the tablet but not on my phone. Although the error is different and looks like the GoFile's account system is getting hammered. All the links works on tablet, and fail on the phone. Same with Chrome vs Firefox.I tried Chrome, Midori and Edge.