#exult@irc.freenode.net logs for 19 Jul 2013 (GMT)

Archive Today Yesterday Tomorrow
Exult homepage

[02:10:03] <SugarCube> It won't be cool in 13 years, but C still will be.
[03:35:18] <-- ShamblerDK has left IRC (Remote host closed the connection)
[11:57:03] --> TheCycoONE has joined #exult
[12:40:49] <-- SugarCube has left IRC (Ping timeout: 246 seconds)
[12:41:29] --> SugarCube has joined #exult
[12:45:23] <-- Sevalecan has left IRC (Quit: F U)
[12:45:42] --> Sevalecan has joined #exult
[12:59:22] <-- Eviltar has left IRC (Ping timeout: 246 seconds)
[12:59:38] --> Eviltar has joined #exult
[17:54:41] <-- TheCycoONE has left IRC (Read error: Connection reset by peer)
[17:54:56] --> TheCycoONE has joined #exult
[18:58:51] --> ShamblerDK has joined #exult
[19:09:37] <Dominus> hey marzo, got time to do some exulting stuff?
[19:10:07] <Marzo> I fell ill this week; I have just barely begin recovering
[19:11:10] <Marzo> But leave in the logs the things you want me to look at and I will do once I am better
[19:38:16] <Dominus> thanks, Marzo, I'll make a list now
[19:41:13] <Dominus> http://sourceforge.net/p/exult/bugs/1845/ keyring in BGkeyring mod was broken. wjp tracked it down and reverted it in rev 7373 but we were not sure whether that is ok with you
[19:44:20] <Dominus> http://sourceforge.net/p/exult/bugs/1847/ SI stupid ghosts that speak as Chaos Hierophant - I have apossible fix but no idea what that might break (if it breaks anything...)
[19:47:52] <Dominus> https://sourceforge.net/p/exult/bugs/1856/ SI Fixes curing Gwenno is broken. Reverting rev 7367 and putting back "push(ival); // put caller_item back on stack" to "case UC_CALLO:" in usecode/ucinternal.cc:2772 makes it work again but wjp really didn't want to touch that
[19:48:50] <Dominus> these were the important ones
[19:49:51] <Dominus> now there are two interesting ones since it involves unimplemented usecode stuff which I think you might like to take a look at:
[19:51:33] <Dominus> https://sourceforge.net/p/exult/bugs/1848/ not working trap in Abandoned outpost - there are two usecode eggs. one triggers energy fields and the other *should* trigger poison fields and explosion shooters. We only got the energy field coming up
[19:52:18] <Dominus> https://sourceforge.net/p/exult/bugs/1855/ Discipline shrine with varios issues:
[19:54:04] <Dominus> - as the bug above the trap controlling usecode egg doesn't seem to work (placing crystal y-shape should turn off the shooting trap or delete the usecode egg controlling that)
[19:54:58] <Dominus> - stacking order is wrong - the newly placed y-shapes should be above the y-depressions
[19:55:32] <Dominus> - we show the name of the y-depressions (which can be turned off by editing data/si/shape_info.txt in %%section framenames, line 690)
[19:56:20] <Dominus> so, Marzo, five issues that need pondering. most have to do with useocde and our usecode enhancements :)
[19:58:01] <Marzo> The one regarding the y-depressions is one I would really rather not touch; rendering order is extremely finicky
[19:58:23] <Marzo> Back when I was looking into it, I made several tries that fixed some things and broke others
[19:58:48] <wjp> this particular case seems to involve the default fallback when there's no preference for order
[19:59:02] <Marzo> And most of them were very far away from one another, and I quickly reached 30 saves in locations that I had to look to make sure everything was working
[19:59:11] <wjp> U7 draws later placed items on top, while we draw earlier placed items on top
[19:59:20] <wjp> (or vice versa, but I think it was this one)
[19:59:32] <Marzo> The problem then would be to find out which one was placed later
[19:59:38] <Dominus> yes, when I mucked a bit with that code I had a funny world :)
[19:59:56] <wjp> we basically add items on one end of the rendering list
[20:00:12] <wjp> so it's just that
[20:00:33] <wjp> but I agree it's quite sensitive as other places may implicitly be assuming the opposite order
[20:02:39] <wjp> as for the usecode opcode things: I believe there may be some mismatches between what UCC outputs and what Exult expects
[20:02:46] <Dominus> Marzo, when you got time, could you look at the usecode trap part of the y-depressions, anyway? the rendering order is, as you both write, the part we should wait for the planned rendering engine rewrite by Colourless :)
[20:02:56] <wjp> as some of these commits only touched one of the two
[20:03:44] <Marzo> They only touched one of the two because one side (Exult) had a memory leak on the code in question
[20:03:50] <Marzo> (if memory serves)
[20:04:13] <Marzo> So I was modifying UCC to generate output that should work (in theory) and not cause a leak
[20:04:13] <wjp> that can't have been it
[20:04:30] <Marzo> I think the callo was one such case
[20:04:39] <wjp> or maybe it was it, but then the patch didn't do that :-)
[20:04:50] <Marzo> Yeah
[20:05:15] <wjp> (but I didn't understand it fully at the time; let alone now)
[20:06:12] <Marzo> It is because that portion is a maze of interconnected things
[20:12:52] <Dominus> marzo, as a rule of thumb, at the time when I add an entry to a bug report you can expect a lot of questions from me and good analysis from wjp in the logs :)
[21:13:25] <-- TheCycoONE has left IRC (Quit: And then there were n-1)
[22:23:54] <-- Marzo has left IRC (Ping timeout: 246 seconds)
[22:46:23] --> Marzo has joined #exult