Print

[Mr. Xirdus]

Wow Xirdus. That actually seems like a very good idea to me!

Don't thank me - it's my job.

[NemesisQc]

I dont know if its been pointed out, but I noticed something on demo 1 patch one: when Rarity says:

Spoiler (click to show/hide)

''I... I cannot explain what I saw any other way than to say that Scootaloo broke the window to my boutique. tore my boutique apart in search for True Blue. and then made off with it.''

The ''it'' is cut short, she only says ''...made off with i-''

[Zeel1]

No, we still don't have a fix for that.  Your best bet is to try out disabling shared contexts and PBuffers.  Also, if there's any log or something (I would think that an error would accompany that, but perhaps not), then email that to Dawn, too.

And how would one do these things...? 

I posted a log in the "Evidence not appearing...?" topic, but I don't think it was of any help, damnmew seemed to expect 'Exception' to pop up, but I didn't see it.

"C:\Program Files\My_Little_Investigations_Demo_1\My_Little_Investigations\data>
java -jar My_Little_Investigations.jar
Mon May 07 13:06:56 CDT 2012 INFO:Slick Build #MLI-001a (based on Slick 2012-03-
05)
Mon May 07 13:06:59 CDT 2012 INFO:LWJGL Version: 2.8.3
Mon May 07 13:06:59 CDT 2012 INFO:OriginalDisplayMode: 1440 x 900 x 32 @60Hz
Mon May 07 13:06:59 CDT 2012 INFO:TargetDisplayMode: 960 x 540 x 0 @0Hz
Mon May 07 13:06:59 CDT 2012 INFO:Starting display 960x540
Mon May 07 13:06:59 CDT 2012 INFO:Use Java PNG Loader = true
Mon May 07 13:06:59 CDT 2012 INFO:Controllers not available
OpenGL shared context support is functional.
Mon May 07 13:07:01 CDT 2012 INFO:Offscreen Buffers FBO=true PBUFFER=true PBUFFE
RRT=true
Mon May 07 13:07:01 CDT 2012 DEBUG:Creating FBO 960x540
Mon May 07 13:07:01 CDT 2012 INFO:Offscreen Buffers FBO=true PBUFFER=true PBUFFE
RRT=true
Mon May 07 13:07:01 CDT 2012 DEBUG:Creating FBO 960x540

C:\Program Files\My_Little_Investigations_Demo_1\My_Little_Investigations\data>"

[GabuEx]

Well, it's just one additional {Pause} at the end of each text...

Yes, but we'd have to go through each line and see exactly how long that pause actually should be.

On another note, that means translators will be forced to make all this syncing crap over again. Can you substitute {Pause} tags with {Duration} tags? This is how I see it working:

Currently, time of speech must be equal to time of text popping out plus time of pause. The {Duration} tag will indicate the time of speech, and the time of pause before the next {Duration} tag will be auto-computated by taking the duration and substracting time of text popping from it.

This is line from current case file:
"{Emotion:Neutral}Well, {Pause:766}I'm afraid there isn't much to tell. {Pause:694}I was sleeping in my bedroom, {Pause:659}{Emotion:Confused}when suddenly I heard a shrill CRASH from downstairs."

This is how it would look like with {Duration} tag:
"{Duration:800}{Emotion:Neutral}Well, {Duration:700}I'm afraid there isn't much to tell. {Duration:690}I was sleeping in my bedroom, {Duration:900}{Emotion:Confused}when suddenly I heard a shrill CRASH from downstairs."
[Values were put only to show the idea and are not accurate.]

This would both ease up syncing process (which eventually can be even automated, if you put each sentence in separate file) and grandly lower the effort needed to make text-only translations. And converting from old to new tag can be done with simple script.

Can you explain more regarding how this would work?  I'm afraid I'm not really following.

And how would one do these things...? 

Through the new launcher menu - there are two checkboxes to do that.

[Mr. Xirdus]

Can you explain more regarding how this would work?  I'm afraid I'm not really following.

Instead of writing how much delay there is between each sentence, you write how long each sentence will last. Internally, you can convert from {Duration} tag into {Pause} tag by moving it immediately before the next {Duration} tag (or the end of text, if it's the last) and decrease the parameter value by number of characters the sentence has multiplied by time needed by single character to pop.

[BronyFurChrist]

Okay, I just tried the demo 1 part 1 on Windows 7 Home Premium 32-bit, and it doesn't get past "Loading sprite sheets..." regardless of if I check the "disable shared contexts" and "disable PBuffers" boxes. If I leave these unchecked and launch the demo normally, it gets to "Loading sprite sheets (67 of 68)" but then stops. Disabling either or both of them gets to just "Loading sprite sheets" without anything in brackets.

I will try the demo again in Ubuntu, but I thought, "hey, while I'm here (in Windows) might as well try it!"

[dawnmew]

Okay, I just tried the demo 1 part 1 on Windows 7 Home Premium 32-bit, and it doesn't get past "Loading sprite sheets..." regardless of if I check the "disable shared contexts" and "disable PBuffers" boxes. If I leave these unchecked and launch the demo normally, it gets to "Loading sprite sheets (67 of 68)" but then stops. Disabling either or both of them gets to just "Loading sprite sheets" without anything in brackets.

I will try the demo again in Ubuntu, but I thought, "hey, while I'm here (in Windows) might as well try it!"

This sounds like a glitch I've seen before. If you listen for several seconds after it stops, can you hear talking? We're still trying to find the cause of this one, on rare occasions the loading screen refuses to get out of the way when the game begins.

[BronyFurChrist]

This sounds like a glitch I've seen before. If you listen for several seconds after it stops, can you hear talking? We're still trying to find the cause of this one, on rare occasions the loading screen refuses to get out of the way when the game begins.

Come to think of it, I'm pretty sure I heard something before I ended the process, though I can't check now because I've already logged back into Ubuntu. 
Let me just copy over the demo from my Windows partition and I'll see if the patch did anything.

Okay, right-clicking and selecting "Open with..." on the .jar file still results in the data folder not being found. Regarding an earlier post about such an issue, please note that this is the .jar file we are (or at least, I am) having that particular issue with, not the .sh. The two are completely different.

Now, regarding the .sh file...

Code: [Select]

alucai@alucai-desktop:~/Downloads/My_Little_Investigations2$ ./launch_linux.shThu May 10 18:23:11 EDT 2012 INFO:Slick Build #MLI-001a (based on Slick 2012-03-05)
Thu May 10 18:23:11 EDT 2012 INFO:LWJGL Version: 2.8.3
Thu May 10 18:23:11 EDT 2012 INFO:OriginalDisplayMode: 1440 x 900 x 24 @60Hz
Thu May 10 18:23:11 EDT 2012 INFO:TargetDisplayMode: 960 x 540 x 0 @0Hz
Thu May 10 18:23:12 EDT 2012 INFO:Starting display 960x540
Thu May 10 18:23:12 EDT 2012 INFO:Use Java PNG Loader = true
Thu May 10 18:23:12 EDT 2012 INFO:Controllers not available
OpenGL shared context support is functional.
Thu May 10 18:23:13 EDT 2012 INFO:Offscreen Buffers FBO=true PBUFFER=true PBUFFERRT=false
Thu May 10 18:23:13 EDT 2012 DEBUG:Creating FBO 960x540

And then the window freezes. 

[GabuEx]

Instead of writing how much delay there is between each sentence, you write how long each sentence will last. Internally, you can convert from {Duration} tag into {Pause} tag by moving it immediately before the next {Duration} tag (or the end of text, if it's the last) and decrease the parameter value by number of characters the sentence has multiplied by time needed by single character to pop.

Oh, hmm, that's actually a pretty interesting idea.  I'll have to think about that.

[dawnmew]

Come to think of it, I'm pretty sure I heard something before I ended the process, though I can't check now because I've already logged back into Ubuntu. 
Let me just copy over the demo from my Windows partition and I'll see if the patch did anything.

Okay, right-clicking and selecting "Open with..." on the .jar file still results in the data folder not being found. Regarding an earlier post about such an issue, please note that this is the .jar file we are (or at least, I am) having an issue with, not the .sh. The two are completely different.

There are a myriad of launcher problems with Linux, so try the .sh file instead, that's what it's here for. Linux is much pickier about launching external processes than Windows and OSX, for some reason.

[BronyFurChrist]

There are a myriad of launcher problems with Linux, so try the .sh file instead, that's what it's here for. Linux is much pickier about launching external processes than Windows and OSX, for some reason.

See my above post that I just edited.

[Mr. Xirdus]

I'll have to think about that.

As in "I'm too tired/drunk/sleepy to think of it now" or "I'm too lazy to make it; maybe in next milestone"?

[dawnmew]

See my above post that I just edited.

The window just... freezes? Huh. Make sure you have the third-party video drivers installed for your video hardware if you don't already, and if that doesn't work and you know what you're doing, try adding the -disablesharedcontext and -disablepbuffer commandline args to the end of the java sh command.

[GabuEx]

As in "I'm too tired/drunk/sleepy to think of it now" or "I'm too lazy to make it; maybe in next milestone"?

As in "I'll test it out and see how well it works, and if it works as well as it seems like it should, then we'll go with it."

[BronyFurChrist]

The window just... freezes? Huh. Make sure you have the third-party video drivers installed for your video hardware if you don't already, and if that doesn't work and you know what you're doing, try adding the -disablesharedcontext and -disablepbuffer commandline args to the end of the java sh command.

Yeah, see, I uninstalled the third party drivers. The ATi ones were just too buggy, and Flash video performance was terrible (tearing, etc.). The open source drivers are a lot better, but I don't see how that would cause this...?

Also, closing the Terminal from which I launched the .sh does not kill the window. Unfortunately, looks like I'll have to restart... until I find some better way of ending it.

Also also, I cannot end java via the System Monitor. Weird.