[01:20:44] --- DominusExult is now known as Dominus
[02:13:29] --- DominusExult is now known as Dominus
[03:30:49] <KnightCaptain> Playing around with -p for Portable Mode a bit. ES will blame a missing exultmsg.txt in the data folder, just creating a blank file there fixes it.
[03:31:00] <KnightCaptain> "terminate called after throwing an instance of 'file_open_exception'
[03:31:00] <KnightCaptain> what(): Error opening file Exult_Data\exultmsg.txt"
[05:53:13] <Dominus> KnightCaptain: what I meant was that whenyou ask something here, an answer might come much later and thus read the logs when you asked something and log of
[05:53:54] <KnightCaptain> Oh right. Cheers.
[05:54:08] <Dominus> KnightCaptain: the ES error message was this with the latest snapshot? yesterday, both Exult and Exult Studio received new code, some of it about exultmsg.txt
[05:54:55] <KnightCaptain> Yes. Downloaded and installed to a new folder.
[05:55:10] <Dominus> though I wonder where Studio looks for exultmsg.txt, odd
[05:55:24] <KnightCaptain> In the same Exult\data folder.
[05:55:54] <KnightCaptain> I customized mine so it's Exult_Data but putting a blank file with the exultmsg.txt name there fixed the problem with ES.
[05:56:07] <Dominus> Actually our code changed yesterday and exultmsg should be only in the exult.flx...
[05:56:15] <Dominus> I'll take a look later
[05:56:19] <Dominus> thanks for the report :)
[06:00:35] <KnightCaptain> I can't program but I sure can complain technically.
[06:01:27] <KnightCaptain> I wish I had more understanding of Usecode, but as you've seen on the forum my grasp is like Fitch's in SI.
[06:15:15] <KnightCaptain> Can you email me the details of the changes if they're related to seeing or showing Usecode flags? I'm on the US east coast and really need to enter Gorlab. G'night.
[10:02:11] --- DominusExult is now known as Dominus
[10:07:21] --- DominusExult is now known as Dominus
[14:18:06] <Dominus> KnightCaptain: I have no idea why ES misbehaves with exultmsg.txt and a portable Exult
[14:18:33] <Dominus> BUT Studio is not really meant for portability
[14:20:50] <Dominus> As for that easier viewing of global flags is not in the main code so not in snapshots
[14:21:18] <Dominus> AND it only looks good in theory ;(
[14:21:54] <Dominus> You can't easily see the stdout in Windows command line
[14:22:42] <Dominus> And the in game global flags message is not long enough on the screen. If you are really slow yes, if fast you won't see it
[14:25:25] <Dominus> Wjp: ~2hours until the System Shock kickstarter starts with a demo to play.......
[14:28:18] <SHODAN> hm that sounds interesting..
[14:33:58] <KnightCaptain> Would the <debug> flags in CFG be any use to this flaghunt?
[14:34:52] <Dominus> KnightCaptain: unfortunately no.
[14:35:33] <Dominus> First they don't have an effect in normal builds
[14:36:01] <Dominus> Then they don't affect the display of global flags
[14:36:54] <Dominus> And lastly, again, the Windows build doesn't show stdout in a command prompt but redirects to stdout.txt
[14:37:58] <Dominus> And since I'm not on Windows anymore I can't make you a debug build or experiment with stopping the stdout redirect...
[15:23:41] <Dominus> hmm, I think Exult Studio snapshot needs updating
[15:35:09] <Dominus> KnightCaptain: I've contacted Kirben, so when you see a new Exult Studio (newer than yesterday) it should be fine again without an exultmsg.txt in data
[15:35:44] <Dominus> thanks for pointing that out :)
[18:39:58] <KnightCaptain> Part of the reason I'm using portable mode with ES is to act as a clean mod-dev setup. My main Exult install is "messy" with a lot of my fooling around mixed into SIfixes. This will let me clean up and perhaps submit more things to SIfixes or possibly branch that into something beyond the scope of it.
[18:40:22] <KnightCaptain> From what I can tell there's few limits on what can be done, but the learning curve is steep.